Re: newcons comming
On Mon, Feb 10, 2014 at 09:09:43PM -0500, Ed Maste wrote: You should be able to manually load the kms modules to switch to native resolution, without starting X. Indeed, kldload'ing radeonmks.so switched LCD to its native resolution. What if I am on CRT (which has many native resolutions). Is there way to select particular one (other than patching source code)? On 10 February 2014 16:07, Alexey Dokuchaev da...@freebsd.org wrote: Also, even at native resolution, switching consoles takes LCD considerable time to redraw screen contents. Looks like it's not accelerated at all... Can you quantify considerable time, and describe the hardware on which you observe this? It means that I can see that top part of the screen is drawn before bottom one (I've made a lame video: https://vidd.me/NqM). This is on some NEC AS231WM monitor connected to RV410 (Radeon X700 Pro), per pciconf(8). ./danfe ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On 11 Feb 2014 23:49, John Baldwin j...@freebsd.org wrote: - Occasionally if I move the mouse around constantly on the console I can get the mouse cursor to leave an artifact. If I move the mouse cursor back over the artifact it gets cleaned up, but only the pixels the mouse cursor overlaps with (so if I try I can make it only clean up part of the artifact). Switching to another VT and back cleans up the artifacts as well. I have this issue also, but I don't use newcons, so it's probably is independent problem. --- Best regards, Denis Emelyanov ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On 10.02.2014 22:07, Alexey Dokuchaev wrote: Also, even at native resolution, switching consoles takes LCD considerable time to redraw screen contents. Looks like it's not accelerated at all... I used the following (hackish) patch which fixed the slow redraw problem for me, but I don't know if it still works: http://people.freebsd.org/~dumbbell/radeonkms/wr4-only-no-copy-vt_fb.c.patch I still need to take some time to discuss it with ray@. -- Jean-Sébastien Pédron signature.asc Description: OpenPGP digital signature
Re: newcons comming
Hello, Ed. You wrote 11 февраля 2014 г., 6:09:43: One (two?) more datapoints: I'm trying -CURRENT + vt(9) + vt_vga(9) on old Sony Vaio which has i915 AND NVIDIA GeForce Go 7400 (selectable before boot with hardware switch), so I have two-for-price-of=one experience. (1) When I select chipset-based (Intel) video. (a) i915kms is NOT loaded via loader.conf -- small windows in middle of screen, but it works considerably well. Not as fast as text console, but usable. When I starts X (NEW_XORG) and its load i915kms.so, I could switch back to text console which is full-resolution and fast now. (b) i915kms is LOADED with loader.conf. First messages from boot is in small window, and after that BLACK SCREEN and full hangup. It doesn't access HDD after that at all, so it looks like real hangup. (2) When I select GeForce video. Everything are in small window, but lower 2.5 lines are OUT OF SCREEN at all! I could type without seeing command-line. When I start X, it works (with nv driver) and I could switch to text console back, but it it same -- small, displaced window. After X finished, console is complete mess -- large sparse letters, pink instead of bold, only 1/4 of console in window and all other is cut out. -- // Black Lion AKA Lev Serebryakov l...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
Hi Adrian! On Mon, 10 Feb 2014 13:24:18 -0800 Adrian Chadd adr...@freebsd.org wrote: [snip] My experiences with newcons/drm2: * suspend/resume occasionally throws up a panic in the softclock code, with some vaguely invalid looking newcons timer entry. THis happens after it comes out of suspend, after af ew seconds. It sucks and makes things rather unusable. Are you have some data to investigate who is culprit? You can try also kernel with syscons, of course console will be black after kms load, but you still able to input commands. * Occasionally a resume results in control not going back to xorg correctly. I have to vt switch to vty0 and back to xorg yeah, dunno why, but xorg's framebuffer damaged in many cases, and not restored on resume. But how it is related to newcons? * Occasionally the text drawing is garbage - the text cells are correct (ie spaces where there's spaces, text where there's text) but the character contents are totally different/garbage. I have to switch vts to fix this. Can you please take a picture of that? I can't imaging it yet. :) It is related to previous paragraph or another issue? -a Thanks for report Adrian! WBW -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Tue, 11 Feb 2014 10:51:26 +0100 Jean-Sébastien Pédron dumbb...@freebsd.org wrote: On 10.02.2014 22:07, Alexey Dokuchaev wrote: Also, even at native resolution, switching consoles takes LCD considerable time to redraw screen contents. Looks like it's not accelerated at all... I used the following (hackish) patch which fixed the slow redraw problem for me, but I don't know if it still works: http://people.freebsd.org/~dumbbell/radeonkms/wr4-only-no-copy-vt_fb.c.patch I still need to take some time to discuss it with ray@. -- Jean-Sébastien Pédron Hi Jean! currently vt(9) do not blank screen on each vt switch. About your patch, think we will better malloc line size buffer (when VM become ready) to not trap into slow read from video mem problem. Before VM come up, we have only one screen blank and since modern system mostly use main memory, it will be viable only for devices with separate video memory and only at boot time (or even use wr4 before VM became ready). Thanks! WBW -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
I've been using newcons for quite a while on my laptop (X220) and it generally works well. A few comments: - When I kldload i915kms on the console, ttyv0 always scrolls down so that the previous screen contents are just off the top of the screen. Other vt's do not do this. (For example, on ttyv1, the initial login prompt remains on the screen at the top.) If I login on on ttyv1 and run the kldload from there, the behavior is generally the same: ttyv1-N all preserve the existing screen contents, but ttyv0 always scrolls up. This is a minor annoyance, but given that it works for all the other vt's, it seems like ttyv0 should work as well. - I get one complaint about an invalid ioctl when starting hald even with freshly compiled ports: consolectl: unknown ioctl: t:40007413 - The few times I've had panics in X, newcons has switched back to ttyv0 and I was able to use DDB just fine. \0/ - I just had the same softclock related panic Adrian reported for the first time yesterday (and I've resumed probably 20-30 times without an issue). - Occasionally if I move the mouse around constantly on the console I can get the mouse cursor to leave an artifact. If I move the mouse cursor back over the artifact it gets cleaned up, but only the pixels the mouse cursor overlaps with (so if I try I can make it only clean up part of the artifact). Switching to another VT and back cleans up the artifacts as well. -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Tuesday, February 11, 2014 8:50:43 am Aleksandr Rybalko wrote: Hi Adrian! On Mon, 10 Feb 2014 13:24:18 -0800 Adrian Chadd adr...@freebsd.org wrote: [snip] My experiences with newcons/drm2: * suspend/resume occasionally throws up a panic in the softclock code, with some vaguely invalid looking newcons timer entry. THis happens after it comes out of suspend, after af ew seconds. It sucks and makes things rather unusable. Are you have some data to investigate who is culprit? You can try also kernel with syscons, of course console will be black after kms load, but you still able to input commands. I had this for the first time yesterday. It is the timer used for vt switching. c_lock inside the callout structure for ttyv0 is trashed and points to NULL instead of Giant. Adrian, you should try setting kern.vt.suspendswitch=0 to see if that helps. -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Sun, Nov 03, 2013 at 11:16:53PM -0800, Kevin Oberman wrote: Are you booting directly to X or using startx from the console? In either case, I think that i915kms should auto-load at the start of X, so you should not need to pre-load it. Just switched to newcons on fresh -CURRENT, seem to work fine so far. Going to X (via startx) does load required modules automagically (radeonkms.ko and radeonkmsfw_R420_cp.ko in my case). Switching to and from the console also works now (did not work with syscons), but screen resolution remains the one X sets (LCD native). I thought that going back to console would restore its original, somewhat closer to 80x25 resolution, but it did not. Which brings me to my first question: 1. Before going X, switching consoles took considerable time (about or more than one second). Every time my monitor briefly displayed mode information pane like it does when new mode is being switched. It does not happen after X was loaded, and while console text is pretty small now (LCD runs at native resolution for all consoles, text ones + X), I'm wondering why it cannot be done up front, without having to startx first. Also, even at native resolution, switching consoles takes LCD considerable time to redraw screen contents. Looks like it's not accelerated at all... 2. Is there way to change fonts apart from patching the kernel source code and using tools from https://github.com/emaste/fontstuff? Can I use more than one font (e.g. for different Unicode code point ranges)? Does newcons require VESA? If not, you should be able to remove it from your kernel to get suspend/resume working from X. I didn't know that VESA (in kernel or kldloaded) can cause problems; can you give any pointers (e.g. reports on the maillists)? I've seen FreeBSD fail to come out of resume too often and want to check if VESA could be the cause. ./danfe ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
[snip] My experiences with newcons/drm2: * suspend/resume occasionally throws up a panic in the softclock code, with some vaguely invalid looking newcons timer entry. THis happens after it comes out of suspend, after af ew seconds. It sucks and makes things rather unusable. * Occasionally a resume results in control not going back to xorg correctly. I have to vt switch to vty0 and back to xorg * Occasionally the text drawing is garbage - the text cells are correct (ie spaces where there's spaces, text where there's text) but the character contents are totally different/garbage. I have to switch vts to fix this. -a ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On 10 February 2014 16:07, Alexey Dokuchaev da...@freebsd.org wrote: 1. Before going X, switching consoles took considerable time (about or more than one second). Every time my monitor briefly displayed mode information pane like it does when new mode is being switched. It does not happen after X was loaded, and while console text is pretty small now (LCD runs at native resolution for all consoles, text ones + X), I'm wondering why it cannot be done up front, without having to startx first. You should be able to manually load the kms modules to switch to native resolution, without starting X. This should also be possible from the loader, although there's a known issue with i915kms on certain hardware, like X2xx Thinkpads. Also, even at native resolution, switching consoles takes LCD considerable time to redraw screen contents. Looks like it's not accelerated at all... Can you quantify considerable time, and describe the hardware on which you observe this? On my Thinkpad X220 it's not noticeably laggy, with either the VGA driver (at boot) or i915kms. In Virtualbox it is observably slow right now, but not unusably so. 2. Is there way to change fonts apart from patching the kernel source code and using tools from https://github.com/emaste/fontstuff? Can I use more than one font (e.g. for different Unicode code point ranges)? We will ship a set of fonts in /usr/share, and vidcontrol will gain the ability to load those fonts for vt(9). For now you can build the font tools in tools/tools/vt/fontcvt and tools/tools/vt/setfont to convert a .bdf font and load it. The current plan is to support only one font (per vt) in the kernel. Any mixing would be done in userland. -Ed ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re : newcons comming
On Sat, 26 Oct 2013 10:45:32 +0200 dt71 at gmx.com wrote: Suppose that Newcons gets in quickly. I use a Radeon 9600 card. Will I see something useful on my screen (with KMS and the new Xorg and things like that), or will my screen be black? Yup, you will get normal virtual terminal, but a bit bigger than 640x480. It is main reason why x11 team ask me to merge newcons ASAP. Newcons can use framebuffer provided by DRM. Try it yourself. You have successfully volunteered to diagnose why a graphical display fails to start when ports are built using WITH_NEW_XORG=1 WITH_KMS=1 WITH_GALLIUM=1 I still have a very custom kernel containing device drm device radeondrm and no loadable modules, so I'll be back with a situation report after building and installing a more GENERIC kernel. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On 4 November 2013 02:16, Kevin Oberman rkober...@gmail.com wrote: Excellent news. I'm really looking forward to newcons. Guess it's time to move my T520 to 10-Stable (or Beta) I'm running a Newcons kernel on my Thinkpad X220 now and it's working well, with a few minor quirks. This is with the X-related packages rebuilt with WITH_NEW_XORG= and WITH_KMS= in /etc/make.conf. Are you booting directly to X or using startx from the console? In either case, I think that i915kms should auto-load at the start of X, so you should not need to pre-load it. I log in and running startx. i915kms does auto-load. Does newcons require VESA? If not, you should be able to remove it from your kernel to get suspend/resume working from X. It does not use VESA - it's removed from GENERIC on the newcons branch. Suspend and resume generally works on my X220 now, from X or console. There are some outstanding issues, for example the X display sometimes ends up corrupted after resume; stopping and restarting X fixes that. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Sun, Nov 03, 2013 at 11:16:53PM -0800, Kevin Oberman wrote: |On Thu, Oct 31, 2013 at 2:01 PM, Doug Ambrisko ambri...@ambrisko.com |wrote: | | On Fri, Oct 25, 2013 at 03:18:47PM +0300, Aleksandr Rybalko wrote: | | Hello fellow hackers! | | | | I finally reach the point when I can work with newcons instead of | | syscons on my laptop. Yes, I know it still buggy and have a lot of | | style(9) problems. But we really have to get it into HEAD and 10.0 to | | enable shiny new Xorg features, drivers, etc. | | I built the kernel from: | A A A A base/user/ed/newcons/ | and installed it on my new ThinkPad T530 with Intel graphics chip. | In general it works better since now syspend and resume works with | and without X. A However, as with my prior ThinkPads I need to switch | out of X to suspend and resume. A So I have vidcontrol -s 1 in my | /etc/rc.suspend and vidcontrol -s 9 in /etc/rc.resume. A If I don't | the display ends up corrupted but somewhat working. | | I had to kldload i915kms in /etc/rc.local since having it there at | boot via /boot/loader.conf resulted in the system not booting. A I need | i915kms for X so I don't need to use vesa mode. | | The FreeBSD logo on boot is interesting but I'd prefer seeing | FreeBSD boot messages to see what is happening. A I'm not sure if | there is a flag to disable that since I have played with it much. | | However, on a whole it is much improved since with i915kms and | newcons when in X via vesa I couldn't switch to a non-X display | since it was blank. | |Excellent news. I'm really looking forward to newcons. Guess it's time to |move my T520 to 10-Stable (or Beta) |. |Since I'm not running 10, I may simply be clueless. If so, please ignore |the rest of this. Newcons isn't in 10 yet but in its own branch. |Are you booting directly to X or using startx from the console? In either |case, I think that i915kms should auto-load at the start of X, so you |should not need to pre-load it. I use XDM to start X. Auto load might not quite work for me since I run X in a vimage jail. I find it easier to keep my base system a minimal install to start up a bounch of vimage jails. I have two mains that are FreeBSD -current that I leap frog and then have a couple of -stable release (ie. 9.0 and 9.2 now) that I use to build ports. I nulls mount the /var/db/pkg, /usr/local and /usr/ports of that release between those so my ports tend to be fixed in time. I have some patches to jail to allow any sysctls and to set what the OS reports for uname etc. Then pkg_add, ports builds thinks it is running on that version of FreeBSD (ie. 9.2 release). This makes it easier for me to run -current and let me add things without issue later on trying to add something new. I do have to build modules outside so it is in sync. with my base OS. |Does newcons require VESA? If not, you should be able to remove it from |your kernel to get suspend/resume working from X. As soon as I went to newcons the suspend and resume started to work. I don't have vesa kldload or static in the kernel. I auto switch out of X on suspend and switch back to X on resume to ensure that on resume the X display isn't messed up (lines shifted etc.). If I don't do this then the X gets messed up. I can see stuff working on the LCD it's just messed up. Brightness seems messed up, I patched acpi_video to also set the 2nd LCD (SB.PCI0.PEG.VID.LCD0._BCM) so that works since the keys don't work. However when X comes back from resume or dpms then it is full bridgtness. So I need to figure that out. I also run into the N compatibility issue with the iwn 6205 that Sean did so I #ifdef'ed that out like he did. Now the 6205 works fine. My other laptop with a 5300 didn't have this issue. My only real problem right now is that this new laptop came with a defective key so I'm waiting to get that replaced and then I'll switch to it. Thanks, Doug A. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Mon, Nov 04, 2013 at 10:30:39AM -0500, Ed Maste wrote: | On 4 November 2013 02:16, Kevin Oberman rkober...@gmail.com wrote: | Excellent news. I'm really looking forward to newcons. Guess it's time to | move my T520 to 10-Stable (or Beta) | | I'm running a Newcons kernel on my Thinkpad X220 now and it's working | well, with a few minor quirks. This is with the X-related packages | rebuilt with WITH_NEW_XORG= and WITH_KMS= in /etc/make.conf. | | Are you booting directly to X or using startx from the console? In either | case, I think that i915kms should auto-load at the start of X, so you | should not need to pre-load it. | | I log in and running startx. i915kms does auto-load. | | Does newcons require VESA? If not, you should be able to remove it from | your kernel to get suspend/resume working from X. | | It does not use VESA - it's removed from GENERIC on the newcons | branch. Suspend and resume generally works on my X220 now, from X or | console. There are some outstanding issues, for example the X display | sometimes ends up corrupted after resume; stopping and restarting X | fixes that. Adding vidcontrol -s 1 /dev/ttyv0 to /etc/rc.suspend and vidcontrol -s 9 /dev/ttyv0 to /etc/rc.resume fixed that for me. Doug A. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Thu, Oct 31, 2013 at 2:01 PM, Doug Ambrisko ambri...@ambrisko.comwrote: On Fri, Oct 25, 2013 at 03:18:47PM +0300, Aleksandr Rybalko wrote: | Hello fellow hackers! | | I finally reach the point when I can work with newcons instead of | syscons on my laptop. Yes, I know it still buggy and have a lot of | style(9) problems. But we really have to get it into HEAD and 10.0 to | enable shiny new Xorg features, drivers, etc. I built the kernel from: base/user/ed/newcons/ and installed it on my new ThinkPad T530 with Intel graphics chip. In general it works better since now syspend and resume works with and without X. However, as with my prior ThinkPads I need to switch out of X to suspend and resume. So I have vidcontrol -s 1 in my /etc/rc.suspend and vidcontrol -s 9 in /etc/rc.resume. If I don't the display ends up corrupted but somewhat working. I had to kldload i915kms in /etc/rc.local since having it there at boot via /boot/loader.conf resulted in the system not booting. I need i915kms for X so I don't need to use vesa mode. The FreeBSD logo on boot is interesting but I'd prefer seeing FreeBSD boot messages to see what is happening. I'm not sure if there is a flag to disable that since I have played with it much. However, on a whole it is much improved since with i915kms and newcons when in X via vesa I couldn't switch to a non-X display since it was blank. Excellent news. I'm really looking forward to newcons. Guess it's time to move my T520 to 10-Stable (or Beta) . Since I'm not running 10, I may simply be clueless. If so, please ignore the rest of this. Are you booting directly to X or using startx from the console? In either case, I think that i915kms should auto-load at the start of X, so you should not need to pre-load it. Does newcons require VESA? If not, you should be able to remove it from your kernel to get suspend/resume working from X. -- R. Kevin Oberman, Network Engineer E-mail: rkober...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Fri, Oct 25, 2013 at 03:18:47PM +0300, Aleksandr Rybalko wrote: | Hello fellow hackers! | | I finally reach the point when I can work with newcons instead of | syscons on my laptop. Yes, I know it still buggy and have a lot of | style(9) problems. But we really have to get it into HEAD and 10.0 to | enable shiny new Xorg features, drivers, etc. I built the kernel from: base/user/ed/newcons/ and installed it on my new ThinkPad T530 with Intel graphics chip. In general it works better since now syspend and resume works with and without X. However, as with my prior ThinkPads I need to switch out of X to suspend and resume. So I have vidcontrol -s 1 in my /etc/rc.suspend and vidcontrol -s 9 in /etc/rc.resume. If I don't the display ends up corrupted but somewhat working. I had to kldload i915kms in /etc/rc.local since having it there at boot via /boot/loader.conf resulted in the system not booting. I need i915kms for X so I don't need to use vesa mode. The FreeBSD logo on boot is interesting but I'd prefer seeing FreeBSD boot messages to see what is happening. I'm not sure if there is a flag to disable that since I have played with it much. However, on a whole it is much improved since with i915kms and newcons when in X via vesa I couldn't switch to a non-X display since it was blank. Thanks, Doug A. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Sat, 26 Oct 2013 00:49:10 +0800 Julian Elischer jul...@freebsd.org wrote: On 10/25/13 9:29 PM, Adrian Chadd wrote: Erm, I don't think this is really ready for -HEAD yet? certainly not ready for 10.. but that doesn't mean it can not be in 10.1 the existing console will still be there as default, and if this truely is a big step forward, people will start using it in 10.1 and it can be in 11 as a default. Yeah! Stability is more important than new features. (and I found one more bug rising on some load :-D) So ray leaving race. :) Thanks for comments! I think it's too late for this to be in 10.0 -adrian On 25 October 2013 06:04, Aleksandr Rybalko r...@freebsd.org wrote: On Fri, 25 Oct 2013 15:18:47 +0300 Aleksandr Rybalko r...@ddteam.net wrote: Hello fellow hackers! I finally reach the point when I can work with newcons instead of syscons on my laptop. Yes, I know it still buggy and have a lot of style(9) problems. But we really have to get it into HEAD and 10.0 to enable shiny new Xorg features, drivers, etc. So I ask everyone to look hard into that[1] and tell me your opinion. I expect a lot of opinions, since it have to affect almost all good guys, as result I have to ask to split bug reports into two parts: 1. Should be done before merge to 10.0; 2. Can be done later. If it possible, please do it(review - report) ASAP. I have plan to done it that way: 1. Merge newcons to head (in a few days); 2. Fix a lot of reported bugs (2 hrs :-D ); 3. Persuade re@ about we need it in 10.0 (one week, maybe two); 4. Merge to 10.0; 5. One year AFK somewhere on Bahamas;^W^W^W^W^W^W^W 5. Add mouse cut-paste support; 6. Fix new bugs; 7. Some drinks. What do we will have with newcons: * (Think it is main) Allow us to switch to fresh Xorg, which require KMS. * Graphic devices which can provide framebuffer access can be easily used as virtual terminals (someone may have pixel-LCD on front of PC tower, may found it useful :-D ) * See [2]. TODO: * Lack of key mapping files, everyone can help with that using instructions on [3]; * A bit slow (mostly scrolling affected). * Other bugs :) * See [2]. Thanks! [1] - http://svnweb.freebsd.org/base/user/ed/newcons/ [2] - http://www.freebsd.org/news/status/report-2013-07-2013-09.html#Continuation-of-the-Newcons-Project [3] - http://raybsd.blogspot.com/2013/10/newcons-international-keyboard-input.html Hope you will love newcons! And maybe me too :) WBW -- Aleksandr Rybalko r...@ddteam.net Forget to give a patch to HEAD, here it is: http://people.freebsd.org/~ray/newcons/newcons_to_head_r257107_2013-10-25_1542.diff.gz Thanks to all! WBW -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Sat, 26 Oct 2013 15:37:25 -0400 Sean Bruno sean_br...@yahoo.com wrote: On Sat, 2013-10-26 at 22:32 +0300, Aleksandr Rybalko wrote: On Sat, 26 Oct 2013 10:45:32 +0200 d...@gmx.com wrote: Suppose that Newcons gets in quickly. I use a Radeon 9600 card. Will I see something useful on my screen (with KMS and the new Xorg and things like that), or will my screen be black? Yup, you will get normal virtual terminal, but a bit bigger than 640x480. It is main reason why x11 team ask me to merge newcons ASAP. Newcons can use framebuffer provided by DRM. Try it yourself. WBW So, I'm running NEW Xorg now and KMS with an NVidia card. What should I do to test this? What are the expected results? sean Spend several hours to try to bring nvidia unit in my laptop. But it is Optimus. It looks like working, but both output show same picture :))) And this is right-side of desktop (if you run xorg) :) So I can't answer your question yet. Think we have to ask nvidia to share some info on how to call their KMS inside kernel (not via /dev/card/dri node). WBW -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Mon, Oct 28, 2013 at 11:09:45AM +0200, Aleksandr Rybalko wrote: On Sat, 26 Oct 2013 15:37:25 -0400 Sean Bruno sean_br...@yahoo.com wrote: On Sat, 2013-10-26 at 22:32 +0300, Aleksandr Rybalko wrote: On Sat, 26 Oct 2013 10:45:32 +0200 d...@gmx.com wrote: Suppose that Newcons gets in quickly. I use a Radeon 9600 card. Will I see something useful on my screen (with KMS and the new Xorg and things like that), or will my screen be black? Yup, you will get normal virtual terminal, but a bit bigger than 640x480. It is main reason why x11 team ask me to merge newcons ASAP. Newcons can use framebuffer provided by DRM. Try it yourself. WBW So, I'm running NEW Xorg now and KMS with an NVidia card. What should I do to test this? What are the expected results? sean Spend several hours to try to bring nvidia unit in my laptop. But it is Optimus. It looks like working, but both output show same picture :))) And this is right-side of desktop (if you run xorg) :) So I can't answer your question yet. Think we have to ask nvidia to share some info on how to call their KMS inside kernel (not via /dev/card/dri node). Nvidia binary driver does not support KMS. Optimus is really not a full video adapter. Optimus chips (usually) do not have video outputs attached at all, GPU does only rendering into the aperture of the Intel GPU. pgpAkOWZkG6mD.pgp Description: PGP signature
Re: newcons comming
On Fri, Oct 25, 2013 at 03:18:47PM +0300, Aleksandr Rybalko wrote: Hello fellow hackers! I finally reach the point when I can work with newcons instead of syscons on my laptop. Yes, I know it still buggy and have a lot of style(9) problems. But we really have to get it into HEAD and 10.0 to enable shiny new Xorg features, drivers, etc. So I ask everyone to look hard into that[1] and tell me your opinion. I expect a lot of opinions, since it have to affect almost all good guys, as result I have to ask to split bug reports into two parts: 1. Should be done before merge to 10.0; 2. Can be done later. If it possible, please do it(review - report) ASAP. Could you please port at least either creator(4) or machfb(4) to newcons before it even hits head so we don't have the same situation as with syscons again where we need to make square pegs fit into round holes? My main concerns in this regard are: o Making these drivers work as low-level console in the syscons sense so they already work for printing the Copyright notice of the kernel. The problem here is that the respective chips don't necessarily come up with the frame buffer mapped and we can't do that on our own at that point with the VM not up, yet. So all access has to be done via bus_space_*(9) and specially crafted bus tags and handles. In short: Except for some specific model and firmware combinations, in general the generic OFW frame buffer approach doesn't work here, that's why these drivers exist in the first place. o For coexistence of f. e. machfb(4) with ofwfb.c, allow some probing of drivers in the BUS_PROBE_GENERIC/BUS_PROBE_DEFAULT etc. manner. The crucial point here is that in case a more specific driver is willing to attach to a certain device, a generic driver must not touch the hardware in any way. It seems that vd_priority is too late in the game for that requirement. With syscons, this is achievable by letting the generic driver call vid_configure(VIO_PROBE_ONLY) and then check whether another driver has taken the device. o Using hardware acceleration for drawing characters and the mouse pointer, i. e. using a hardware cursor. Employing the respective chips as dumb frame buffers instead is just dog slow. Currently, I don't see how a hardware cursor could be hooked up to newcons. The current putc code in these drivers _might_ be suitable for implementing bitbltchr methods. Apart from that these chips also can do simple bitblt etc. of course. o Using the 12 x 22 gallant font. o Allowing Xorg to map the frame buffer but additionally also other register banks as needed through newcons. With syscons, a driver can provide a mmap method for that (see machfb(4). I currently don't see how to do that with the newcons infrastructure. An alternative might be to make Xorg/ libpciaccess aware of newcons and go through a /dev/fdX in that case. Still, I don't see how to currently do that for resources besides the actual frame buffer with existing fdc.c. I'm also not sure whether the latter is the appropriate route to go in the first place given that besides mmap'ing from userland, newcons'ified creator(4) and machfb(4) still should be used directly. In any case, for creator(4) Xorg expects a /dev/fdX anyway. o Allowing late attachment in case the primary console is the serial one, another graphics chip etc. during regular device attachment when everything needed (mainly the VM) to bring the frame buffer fully online on our own is available. Is that what vt_allocate() is for? Marius ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
Suppose that Newcons gets in quickly. I use a Radeon 9600 card. Will I see something useful on my screen (with KMS and the new Xorg and things like that), or will my screen be black? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
Am 25.10.2013 14:18, schrieb Aleksandr Rybalko: Hello fellow hackers! I finally reach the point when I can work with newcons instead of syscons on my laptop. Yes, I know it still buggy and have a lot of style(9) problems. But we really have to get it into HEAD and 10.0 to enable shiny new Xorg features, drivers, etc. So I ask everyone to look hard into that[1] and tell me your opinion. I expect a lot of opinions, since it have to affect almost all good guys, as result I have to ask to split bug reports into two parts: It should only get in a stable (10/STABLE) version when it is solid, stable, and free of known bugs. Thus, please have it matured in 11/HEAD for now, and merge when it's ready. If that means going a point release with older xorg stuff, then we have to live with that. Especially if I read further down the thread that newer xorg depends on newcons - there would be no way back for xorg should more serious issues come up (and we cannot possibly test everything on the developer's end - some things will only come up as users upgrade/install from 10.0-RELEASE DVDs), which is a bigger risk. Rather old xorg with known issues, than random regressions that might leave us with a new xorg but _newly_ does not work at all for users, without any other way to go back but use 9.2. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Sat, 26 Oct 2013 10:45:32 +0200 d...@gmx.com wrote: Suppose that Newcons gets in quickly. I use a Radeon 9600 card. Will I see something useful on my screen (with KMS and the new Xorg and things like that), or will my screen be black? Yup, you will get normal virtual terminal, but a bit bigger than 640x480. It is main reason why x11 team ask me to merge newcons ASAP. Newcons can use framebuffer provided by DRM. Try it yourself. WBW -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Fri, 25 Oct 2013 20:52:27 +0400 Andrey Fesenko f0and...@gmail.com wrote: On Fri, Oct 25, 2013 at 4:18 PM, Aleksandr Rybalko r...@ddteam.net wrote: Hello fellow hackers! I finally reach the point when I can work with newcons instead of syscons on my laptop. Yes, I know it still buggy and have a lot of ... Yes, it's build and work Nice # uname -a FreeBSD x220.local 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r257111M: Fri Oct 25 19:27:50 MSK 2013 andrey@x220.local:/usr/obj/usr/src/sys/W_BOOK amd64 :) In the single user ugly Can not read termcap database: Using dumb terminal settings termcap is out of newcons's care :) In the multy user mode: Switch Xorg to consol and back is correct. spam log % tail /var/log/messages Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0xc0086457, nr=0x57, dev 0xf80006682800, auth=1 Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0x20006458, nr=0x58, dev 0xf80006682800, auth=1 Oct 25 20:47:29 x220 last message repeated 5 times Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0x800c645f, nr=0x5f, dev 0xf80006682800, auth=1 Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0x8020645d, nr=0x5d, dev 0xf80006682800, auth=1 Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0x80406469, nr=0x69, dev 0xf80006682800, auth=1 Oct 25 20:47:29 x220 kernel: [drm:pid1444:i915_gem_execbuffer2] buffers_ptr 80340a400 buffer_count 2 len 0058 Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0x800c645f, nr=0x5f, dev 0xf80006682800, auth=1 Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0xc0086457, nr=0x57, dev 0xf80006682800, auth=1 Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0x20006458, nr=0x58, dev 0xf80006682800, auth=1 Turn off DRM_DEBUG option in kernel config. In the console login jumps up, but it works correctly. If ScrlLk console blink. Thanks! WBW -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Sat, 2013-10-26 at 22:32 +0300, Aleksandr Rybalko wrote: On Sat, 26 Oct 2013 10:45:32 +0200 d...@gmx.com wrote: Suppose that Newcons gets in quickly. I use a Radeon 9600 card. Will I see something useful on my screen (with KMS and the new Xorg and things like that), or will my screen be black? Yup, you will get normal virtual terminal, but a bit bigger than 640x480. It is main reason why x11 team ask me to merge newcons ASAP. Newcons can use framebuffer provided by DRM. Try it yourself. WBW So, I'm running NEW Xorg now and KMS with an NVidia card. What should I do to test this? What are the expected results? sean signature.asc Description: This is a digitally signed message part
Re: newcons comming
On Fri, 25 Oct 2013 18:46:02 +0300 Konstantin Belousov kostik...@gmail.com wrote: On Fri, Oct 25, 2013 at 04:04:10PM +0300, Aleksandr Rybalko wrote: On Fri, 25 Oct 2013 15:18:47 +0300 Aleksandr Rybalko r...@ddteam.net wrote: Hello fellow hackers! I finally reach the point when I can work with newcons instead of syscons on my laptop. Yes, I know it still buggy and have a lot of style(9) problems. But we really have to get it into HEAD and 10.0 to enable shiny new Xorg features, drivers, etc. So I ask everyone to look hard into that[1] and tell me your opinion. I expect a lot of opinions, since it have to affect almost all good guys, as result I have to ask to split bug reports into two parts: 1. Should be done before merge to 10.0; 2. Can be done later. If it possible, please do it(review - report) ASAP. I have plan to done it that way: 1. Merge newcons to head (in a few days); 2. Fix a lot of reported bugs (2 hrs :-D ); 3. Persuade re@ about we need it in 10.0 (one week, maybe two); 4. Merge to 10.0; 5. One year AFK somewhere on Bahamas;^W^W^W^W^W^W^W 5. Add mouse cut-paste support; 6. Fix new bugs; 7. Some drinks. What do we will have with newcons: * (Think it is main) Allow us to switch to fresh Xorg, which require KMS. * Graphic devices which can provide framebuffer access can be easily used as virtual terminals (someone may have pixel-LCD on front of PC tower, may found it useful :-D ) * See [2]. TODO: * Lack of key mapping files, everyone can help with that using instructions on [3]; * A bit slow (mostly scrolling affected). * Other bugs :) * See [2]. Thanks! [1] - http://svnweb.freebsd.org/base/user/ed/newcons/ [2] - http://www.freebsd.org/news/status/report-2013-07-2013-09.html#Continuation-of-the-Newcons-Project [3] - http://raybsd.blogspot.com/2013/10/newcons-international-keyboard-input.html Hope you will love newcons! And maybe me too :) WBW -- Aleksandr Rybalko r...@ddteam.net Forget to give a patch to HEAD, here it is: http://people.freebsd.org/~ray/newcons/newcons_to_head_r257107_2013-10-25_1542.diff.gz Was the code reviewed by anybody ? Was technical reviewer assigned by the project sponsor ? Yes, technical reviewer assigned, but project code is not reviewed yet. That why I'm not commit it to HEAD right now :) I will cleanup it few days, then will ask for review and do CFT call too. I looked very quickly over the whole patch, I only enumerate the things that catched my eye: dev/vt/hw/intel.c is sort of joke, it should be removed. It is more than joke! :) Leftover from old project. I've already remove it after your notice. I am very suspicious to what you do in the drm_fb_helper.c with enqueuing, but I need to do much more reading of the code to say something definitive. I think you mean use of EVENTHANDLER. Describe a little why it here first: Since some time both VTs must be present (syscons and newcons), but framebuffer born inside drm2 module, I have to make it completely independent from presence of newcons. Few days ago I already collect some opinions in that case. And public opinion give me answer - best to use newbus here, but I recall more simple way - EVENTHANDLER. I did implement it. Later, I found more and more argument that points to newbus. F.e.: after suspend it Xorg draws better if machine suspend/resume in terminal(Xorg on inactive terminal), it is just because Xorg after resume gets notification about activation of its terminal window, so it redraw screen. So I have to use newbus's _suspend/_resume to notify clients. Intel GPU might provide relatively wide range of the pixel formats, I do not see a code to parse and use these formats. Yes, but nobody use anything than RGB+ARGB, maybe with exception of TV output. Newcons's have infrastructure support for that, so required format can be easily added. Overall code looks relatively self-contained, so I think you indeed might merge it to head after some public testing and review. But I very much doubt that 10.0 is feasible for any efforts. Ok, lets do everything sane, then to decide :) Looks like I can even make it coexistent with syscons, so if user load KMS enabled module, newcons will attach over syscons. Think it is good way to HEAD users/developers to see what happen on xorg crash. So no rush, just work. :) Many thanks for opinion! WBW -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Fri, 25 Oct 2013 11:55:26 -0700 Adrian Chadd adr...@freebsd.org wrote: I think the best thing to do is address kib's issues and whatever else pops up in the review, then add it into -HEAD as the non-default console type. What I'd hate to see is some build time dependency where xorg _requires_ you to run newcons in order to run X. Well, at least just right now. I have a whole bunch of older hardware that I won't have access to for a couple more weeks (old netbooks, thinkpads, etc) that I'd like to run newcons and the latest xorg builds on, just to make sure we haven't broken things for stuff circa 2005-2006. There's still a lot of that stuff out there and right now xorg+console works fine for those. Ok awaiting for report how it run on your old boxes :) Thanks, -adrian On 25 October 2013 07:18, Aleksandr Rybalko r...@freebsd.org wrote: On Fri, 25 Oct 2013 15:10:44 +0100 symbol...@gmx.com wrote: On Fri, Oct 25, 2013 at 06:43:54AM -0700, Adrian Chadd wrote: 3) Realise it's not yet ready for 10.0 or HEAD, and target it to be ready for MFC for a 10.1 release. 4) Delay 10.0 until this has matured enough in HEAD, then release it. I really want to see more updated xorg support but the timing of it all feels a little overly rushed for a 10.0 release target. What do others think? FWIW, I'm really looking forward to newcons but I don't think it should be rushed into a release. (3) Seems prudent. Anyway it is optional. s/device vt/#device vt/ s/#device sc/device sc/ and you in the old, well known world :) --sym ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
newcons comming
Hello fellow hackers! I finally reach the point when I can work with newcons instead of syscons on my laptop. Yes, I know it still buggy and have a lot of style(9) problems. But we really have to get it into HEAD and 10.0 to enable shiny new Xorg features, drivers, etc. So I ask everyone to look hard into that[1] and tell me your opinion. I expect a lot of opinions, since it have to affect almost all good guys, as result I have to ask to split bug reports into two parts: 1. Should be done before merge to 10.0; 2. Can be done later. If it possible, please do it(review - report) ASAP. I have plan to done it that way: 1. Merge newcons to head (in a few days); 2. Fix a lot of reported bugs (2 hrs :-D ); 3. Persuade re@ about we need it in 10.0 (one week, maybe two); 4. Merge to 10.0; 5. One year AFK somewhere on Bahamas;^W^W^W^W^W^W^W 5. Add mouse cut-paste support; 6. Fix new bugs; 7. Some drinks. What do we will have with newcons: * (Think it is main) Allow us to switch to fresh Xorg, which require KMS. * Graphic devices which can provide framebuffer access can be easily used as virtual terminals (someone may have pixel-LCD on front of PC tower, may found it useful :-D ) * See [2]. TODO: * Lack of key mapping files, everyone can help with that using instructions on [3]; * A bit slow (mostly scrolling affected). * Other bugs :) * See [2]. Thanks! [1] - http://svnweb.freebsd.org/base/user/ed/newcons/ [2] - http://www.freebsd.org/news/status/report-2013-07-2013-09.html#Continuation-of-the-Newcons-Project [3] - http://raybsd.blogspot.com/2013/10/newcons-international-keyboard-input.html Hope you will love newcons! And maybe me too :) WBW -- Aleksandr Rybalko r...@ddteam.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Fri, 25 Oct 2013 15:18:47 +0300 Aleksandr Rybalko r...@ddteam.net wrote: Hello fellow hackers! I finally reach the point when I can work with newcons instead of syscons on my laptop. Yes, I know it still buggy and have a lot of style(9) problems. But we really have to get it into HEAD and 10.0 to enable shiny new Xorg features, drivers, etc. So I ask everyone to look hard into that[1] and tell me your opinion. I expect a lot of opinions, since it have to affect almost all good guys, as result I have to ask to split bug reports into two parts: 1. Should be done before merge to 10.0; 2. Can be done later. If it possible, please do it(review - report) ASAP. I have plan to done it that way: 1. Merge newcons to head (in a few days); 2. Fix a lot of reported bugs (2 hrs :-D ); 3. Persuade re@ about we need it in 10.0 (one week, maybe two); 4. Merge to 10.0; 5. One year AFK somewhere on Bahamas;^W^W^W^W^W^W^W 5. Add mouse cut-paste support; 6. Fix new bugs; 7. Some drinks. What do we will have with newcons: * (Think it is main) Allow us to switch to fresh Xorg, which require KMS. * Graphic devices which can provide framebuffer access can be easily used as virtual terminals (someone may have pixel-LCD on front of PC tower, may found it useful :-D ) * See [2]. TODO: * Lack of key mapping files, everyone can help with that using instructions on [3]; * A bit slow (mostly scrolling affected). * Other bugs :) * See [2]. Thanks! [1] - http://svnweb.freebsd.org/base/user/ed/newcons/ [2] - http://www.freebsd.org/news/status/report-2013-07-2013-09.html#Continuation-of-the-Newcons-Project [3] - http://raybsd.blogspot.com/2013/10/newcons-international-keyboard-input.html Hope you will love newcons! And maybe me too :) WBW -- Aleksandr Rybalko r...@ddteam.net Forget to give a patch to HEAD, here it is: http://people.freebsd.org/~ray/newcons/newcons_to_head_r257107_2013-10-25_1542.diff.gz Thanks to all! WBW -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
Erm, I don't think this is really ready for -HEAD yet? -adrian On 25 October 2013 06:04, Aleksandr Rybalko r...@freebsd.org wrote: On Fri, 25 Oct 2013 15:18:47 +0300 Aleksandr Rybalko r...@ddteam.net wrote: Hello fellow hackers! I finally reach the point when I can work with newcons instead of syscons on my laptop. Yes, I know it still buggy and have a lot of style(9) problems. But we really have to get it into HEAD and 10.0 to enable shiny new Xorg features, drivers, etc. So I ask everyone to look hard into that[1] and tell me your opinion. I expect a lot of opinions, since it have to affect almost all good guys, as result I have to ask to split bug reports into two parts: 1. Should be done before merge to 10.0; 2. Can be done later. If it possible, please do it(review - report) ASAP. I have plan to done it that way: 1. Merge newcons to head (in a few days); 2. Fix a lot of reported bugs (2 hrs :-D ); 3. Persuade re@ about we need it in 10.0 (one week, maybe two); 4. Merge to 10.0; 5. One year AFK somewhere on Bahamas;^W^W^W^W^W^W^W 5. Add mouse cut-paste support; 6. Fix new bugs; 7. Some drinks. What do we will have with newcons: * (Think it is main) Allow us to switch to fresh Xorg, which require KMS. * Graphic devices which can provide framebuffer access can be easily used as virtual terminals (someone may have pixel-LCD on front of PC tower, may found it useful :-D ) * See [2]. TODO: * Lack of key mapping files, everyone can help with that using instructions on [3]; * A bit slow (mostly scrolling affected). * Other bugs :) * See [2]. Thanks! [1] - http://svnweb.freebsd.org/base/user/ed/newcons/ [2] - http://www.freebsd.org/news/status/report-2013-07-2013-09.html#Continuation-of-the-Newcons-Project [3] - http://raybsd.blogspot.com/2013/10/newcons-international-keyboard-input.html Hope you will love newcons! And maybe me too :) WBW -- Aleksandr Rybalko r...@ddteam.net Forget to give a patch to HEAD, here it is: http://people.freebsd.org/~ray/newcons/newcons_to_head_r257107_2013-10-25_1542.diff.gz Thanks to all! WBW -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Fri, 25 Oct 2013 06:29:37 -0700 Adrian Chadd adr...@freebsd.org wrote: Erm, I don't think this is really ready for -HEAD yet? Lets do it really ready :))) I'am free on that, I can merge or not merge it to 10.0. But x11 team depend on newcons presence, otherwise no new Xorg, no KMS drivers, no new cairo (IIRC), no new .. So we have two way: 1. delay it to 11.0 2. make it ready to 10.0 Select one you like more! :) Thanks! -adrian On 25 October 2013 06:04, Aleksandr Rybalko r...@freebsd.org wrote: On Fri, 25 Oct 2013 15:18:47 +0300 Aleksandr Rybalko r...@ddteam.net wrote: Hello fellow hackers! I finally reach the point when I can work with newcons instead of syscons on my laptop. Yes, I know it still buggy and have a lot of style(9) problems. But we really have to get it into HEAD and 10.0 to enable shiny new Xorg features, drivers, etc. So I ask everyone to look hard into that[1] and tell me your opinion. I expect a lot of opinions, since it have to affect almost all good guys, as result I have to ask to split bug reports into two parts: 1. Should be done before merge to 10.0; 2. Can be done later. If it possible, please do it(review - report) ASAP. I have plan to done it that way: 1. Merge newcons to head (in a few days); 2. Fix a lot of reported bugs (2 hrs :-D ); 3. Persuade re@ about we need it in 10.0 (one week, maybe two); 4. Merge to 10.0; 5. One year AFK somewhere on Bahamas;^W^W^W^W^W^W^W 5. Add mouse cut-paste support; 6. Fix new bugs; 7. Some drinks. What do we will have with newcons: * (Think it is main) Allow us to switch to fresh Xorg, which require KMS. * Graphic devices which can provide framebuffer access can be easily used as virtual terminals (someone may have pixel-LCD on front of PC tower, may found it useful :-D ) * See [2]. TODO: * Lack of key mapping files, everyone can help with that using instructions on [3]; * A bit slow (mostly scrolling affected). * Other bugs :) * See [2]. Thanks! [1] - http://svnweb.freebsd.org/base/user/ed/newcons/ [2] - http://www.freebsd.org/news/status/report-2013-07-2013-09.html#Continuation-of-the-Newcons-Project [3] - http://raybsd.blogspot.com/2013/10/newcons-international-keyboard-input.html Hope you will love newcons! And maybe me too :) WBW -- Aleksandr Rybalko r...@ddteam.net Forget to give a patch to HEAD, here it is: http://people.freebsd.org/~ray/newcons/newcons_to_head_r257107_2013-10-25_1542.diff.gz Thanks to all! WBW -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org WBW -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
3) Realise it's not yet ready for 10.0 or HEAD, and target it to be ready for MFC for a 10.1 release. 4) Delay 10.0 until this has matured enough in HEAD, then release it. I really want to see more updated xorg support but the timing of it all feels a little overly rushed for a 10.0 release target. What do others think? -adrian On 25 October 2013 06:39, Aleksandr Rybalko r...@freebsd.org wrote: On Fri, 25 Oct 2013 06:29:37 -0700 Adrian Chadd adr...@freebsd.org wrote: Erm, I don't think this is really ready for -HEAD yet? Lets do it really ready :))) I'am free on that, I can merge or not merge it to 10.0. But x11 team depend on newcons presence, otherwise no new Xorg, no KMS drivers, no new cairo (IIRC), no new .. So we have two way: 1. delay it to 11.0 2. make it ready to 10.0 Select one you like more! :) Thanks! -adrian On 25 October 2013 06:04, Aleksandr Rybalko r...@freebsd.org wrote: On Fri, 25 Oct 2013 15:18:47 +0300 Aleksandr Rybalko r...@ddteam.net wrote: Hello fellow hackers! I finally reach the point when I can work with newcons instead of syscons on my laptop. Yes, I know it still buggy and have a lot of style(9) problems. But we really have to get it into HEAD and 10.0 to enable shiny new Xorg features, drivers, etc. So I ask everyone to look hard into that[1] and tell me your opinion. I expect a lot of opinions, since it have to affect almost all good guys, as result I have to ask to split bug reports into two parts: 1. Should be done before merge to 10.0; 2. Can be done later. If it possible, please do it(review - report) ASAP. I have plan to done it that way: 1. Merge newcons to head (in a few days); 2. Fix a lot of reported bugs (2 hrs :-D ); 3. Persuade re@ about we need it in 10.0 (one week, maybe two); 4. Merge to 10.0; 5. One year AFK somewhere on Bahamas;^W^W^W^W^W^W^W 5. Add mouse cut-paste support; 6. Fix new bugs; 7. Some drinks. What do we will have with newcons: * (Think it is main) Allow us to switch to fresh Xorg, which require KMS. * Graphic devices which can provide framebuffer access can be easily used as virtual terminals (someone may have pixel-LCD on front of PC tower, may found it useful :-D ) * See [2]. TODO: * Lack of key mapping files, everyone can help with that using instructions on [3]; * A bit slow (mostly scrolling affected). * Other bugs :) * See [2]. Thanks! [1] - http://svnweb.freebsd.org/base/user/ed/newcons/ [2] - http://www.freebsd.org/news/status/report-2013-07-2013-09.html#Continuation-of-the-Newcons-Project [3] - http://raybsd.blogspot.com/2013/10/newcons-international-keyboard-input.html Hope you will love newcons! And maybe me too :) WBW -- Aleksandr Rybalko r...@ddteam.net Forget to give a patch to HEAD, here it is: http://people.freebsd.org/~ray/newcons/newcons_to_head_r257107_2013-10-25_1542.diff.gz Thanks to all! WBW -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org WBW -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
I think we should provide option - use beta-newcons or old. Linux in top is not because it's better, but because it has solution. Not even finished but at least some solutions. On Friday 25 October 2013 06:43:54 Adrian Chadd wrote: 3) Realise it's not yet ready for 10.0 or HEAD, and target it to be ready for MFC for a 10.1 release. 4) Delay 10.0 until this has matured enough in HEAD, then release it. I really want to see more updated xorg support but the timing of it all feels a little overly rushed for a 10.0 release target. What do others think? -adrian On 25 October 2013 06:39, Aleksandr Rybalko r...@freebsd.org wrote: On Fri, 25 Oct 2013 06:29:37 -0700 Adrian Chadd adr...@freebsd.org wrote: Erm, I don't think this is really ready for -HEAD yet? Lets do it really ready :))) I'am free on that, I can merge or not merge it to 10.0. But x11 team depend on newcons presence, otherwise no new Xorg, no KMS drivers, no new cairo (IIRC), no new .. So we have two way: 1. delay it to 11.0 2. make it ready to 10.0 Select one you like more! :) Thanks! -adrian On 25 October 2013 06:04, Aleksandr Rybalko r...@freebsd.org wrote: On Fri, 25 Oct 2013 15:18:47 +0300 Aleksandr Rybalko r...@ddteam.net wrote: Hello fellow hackers! I finally reach the point when I can work with newcons instead of syscons on my laptop. Yes, I know it still buggy and have a lot of style(9) problems. But we really have to get it into HEAD and 10.0 to enable shiny new Xorg features, drivers, etc. So I ask everyone to look hard into that[1] and tell me your opinion. I expect a lot of opinions, since it have to affect almost all good guys, as result I have to ask to split bug reports into two parts: 1. Should be done before merge to 10.0; 2. Can be done later. If it possible, please do it(review - report) ASAP. I have plan to done it that way: 1. Merge newcons to head (in a few days); 2. Fix a lot of reported bugs (2 hrs :-D ); 3. Persuade re@ about we need it in 10.0 (one week, maybe two); 4. Merge to 10.0; 5. One year AFK somewhere on Bahamas;^W^W^W^W^W^W^W 5. Add mouse cut-paste support; 6. Fix new bugs; 7. Some drinks. What do we will have with newcons: * (Think it is main) Allow us to switch to fresh Xorg, which require KMS. * Graphic devices which can provide framebuffer access can be easily used as virtual terminals (someone may have pixel-LCD on front of PC tower, may found it useful :-D ) * See [2]. TODO: * Lack of key mapping files, everyone can help with that using instructions on [3]; * A bit slow (mostly scrolling affected). * Other bugs :) * See [2]. Thanks! [1] - http://svnweb.freebsd.org/base/user/ed/newcons/ [2] - http://www.freebsd.org/news/status/report-2013-07-2013-09.html#Continuation-of-the-Newcons-Project [3] - http://raybsd.blogspot.com/2013/10/newcons-international-keyboard-input.html Hope you will love newcons! And maybe me too :) WBW -- Aleksandr Rybalko r...@ddteam.net Forget to give a patch to HEAD, here it is: http://people.freebsd.org/~ray/newcons/newcons_to_head_r257107_2013-10-25_1542.diff.gz Thanks to all! WBW -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org WBW -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- Artyom Mirgorodskiy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Fri, Oct 25, 2013 at 06:43:54AM -0700, Adrian Chadd wrote: 3) Realise it's not yet ready for 10.0 or HEAD, and target it to be ready for MFC for a 10.1 release. 4) Delay 10.0 until this has matured enough in HEAD, then release it. I really want to see more updated xorg support but the timing of it all feels a little overly rushed for a 10.0 release target. What do others think? FWIW, I'm really looking forward to newcons but I don't think it should be rushed into a release. (3) Seems prudent. --sym ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Fri, 25 Oct 2013 15:10:44 +0100 symbol...@gmx.com wrote: On Fri, Oct 25, 2013 at 06:43:54AM -0700, Adrian Chadd wrote: 3) Realise it's not yet ready for 10.0 or HEAD, and target it to be ready for MFC for a 10.1 release. 4) Delay 10.0 until this has matured enough in HEAD, then release it. I really want to see more updated xorg support but the timing of it all feels a little overly rushed for a 10.0 release target. What do others think? FWIW, I'm really looking forward to newcons but I don't think it should be rushed into a release. (3) Seems prudent. Anyway it is optional. s/device vt/#device vt/ s/#device sc/device sc/ and you in the old, well known world :) --sym ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Fri, 25 Oct 2013 17:18:15 +0300 Aleksandr Rybalko wrote: On Fri, 25 Oct 2013 15:10:44 +0100 symbol...@gmx.com wrote: On Fri, Oct 25, 2013 at 06:43:54AM -0700, Adrian Chadd wrote: 3) Realise it's not yet ready for 10.0 or HEAD, and target it to be ready for MFC for a 10.1 release. 4) Delay 10.0 until this has matured enough in HEAD, then release it. I really want to see more updated xorg support but the timing of it all feels a little overly rushed for a 10.0 release target. What do others think? FWIW, I'm really looking forward to newcons but I don't think it should be rushed into a release. (3) Seems prudent. Anyway it is optional. s/device vt/#device vt/ s/#device sc/device sc/ and you in the old, well known world :) I think you need to remove the kernel config changes from the patch and keep syscons the default for now. There's no problem with putting experimental code in HEAD but it can't be the default from day 1. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Fri, 25 Oct 2013 16:27:49 +0200 Tijl Coosemans t...@coosemans.org wrote: On Fri, 25 Oct 2013 17:18:15 +0300 Aleksandr Rybalko wrote: On Fri, 25 Oct 2013 15:10:44 +0100 symbol...@gmx.com wrote: On Fri, Oct 25, 2013 at 06:43:54AM -0700, Adrian Chadd wrote: 3) Realise it's not yet ready for 10.0 or HEAD, and target it to be ready for MFC for a 10.1 release. 4) Delay 10.0 until this has matured enough in HEAD, then release it. I really want to see more updated xorg support but the timing of it all feels a little overly rushed for a 10.0 release target. What do others think? FWIW, I'm really looking forward to newcons but I don't think it should be rushed into a release. (3) Seems prudent. Anyway it is optional. s/device vt/#device vt/ s/#device sc/device sc/ and you in the old, well known world :) I think you need to remove the kernel config changes from the patch and keep syscons the default for now. There's no problem with putting experimental code in HEAD but it can't be the default from day 1. Yeah, exact, it is enabled in patch just for easy testing. Thanks! WBW -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Fri, Oct 25, 2013 at 04:04:10PM +0300, Aleksandr Rybalko wrote: On Fri, 25 Oct 2013 15:18:47 +0300 Aleksandr Rybalko r...@ddteam.net wrote: Hello fellow hackers! I finally reach the point when I can work with newcons instead of syscons on my laptop. Yes, I know it still buggy and have a lot of style(9) problems. But we really have to get it into HEAD and 10.0 to enable shiny new Xorg features, drivers, etc. So I ask everyone to look hard into that[1] and tell me your opinion. I expect a lot of opinions, since it have to affect almost all good guys, as result I have to ask to split bug reports into two parts: 1. Should be done before merge to 10.0; 2. Can be done later. If it possible, please do it(review - report) ASAP. I have plan to done it that way: 1. Merge newcons to head (in a few days); 2. Fix a lot of reported bugs (2 hrs :-D ); 3. Persuade re@ about we need it in 10.0 (one week, maybe two); 4. Merge to 10.0; 5. One year AFK somewhere on Bahamas;^W^W^W^W^W^W^W 5. Add mouse cut-paste support; 6. Fix new bugs; 7. Some drinks. What do we will have with newcons: * (Think it is main) Allow us to switch to fresh Xorg, which require KMS. * Graphic devices which can provide framebuffer access can be easily used as virtual terminals (someone may have pixel-LCD on front of PC tower, may found it useful :-D ) * See [2]. TODO: * Lack of key mapping files, everyone can help with that using instructions on [3]; * A bit slow (mostly scrolling affected). * Other bugs :) * See [2]. Thanks! [1] - http://svnweb.freebsd.org/base/user/ed/newcons/ [2] - http://www.freebsd.org/news/status/report-2013-07-2013-09.html#Continuation-of-the-Newcons-Project [3] - http://raybsd.blogspot.com/2013/10/newcons-international-keyboard-input.html Hope you will love newcons! And maybe me too :) WBW -- Aleksandr Rybalko r...@ddteam.net Forget to give a patch to HEAD, here it is: http://people.freebsd.org/~ray/newcons/newcons_to_head_r257107_2013-10-25_1542.diff.gz Was the code reviewed by anybody ? Was technical reviewer assigned by the project sponsor ? I looked very quickly over the whole patch, I only enumerate the things that catched my eye: dev/vt/hw/intel.c is sort of joke, it should be removed. I am very suspicious to what you do in the drm_fb_helper.c with enqueuing, but I need to do much more reading of the code to say something definitive. Intel GPU might provide relatively wide range of the pixel formats, I do not see a code to parse and use these formats. Overall code looks relatively self-contained, so I think you indeed might merge it to head after some public testing and review. But I very much doubt that 10.0 is feasible for any efforts. pgpb6SXMCAdB7.pgp Description: PGP signature
Re: newcons comming
On 10/25/13 9:29 PM, Adrian Chadd wrote: Erm, I don't think this is really ready for -HEAD yet? certainly not ready for 10.. but that doesn't mean it can not be in 10.1 the existing console will still be there as default, and if this truely is a big step forward, people will start using it in 10.1 and it can be in 11 as a default. I think it's too late for this to be in 10.0 -adrian On 25 October 2013 06:04, Aleksandr Rybalko r...@freebsd.org wrote: On Fri, 25 Oct 2013 15:18:47 +0300 Aleksandr Rybalko r...@ddteam.net wrote: Hello fellow hackers! I finally reach the point when I can work with newcons instead of syscons on my laptop. Yes, I know it still buggy and have a lot of style(9) problems. But we really have to get it into HEAD and 10.0 to enable shiny new Xorg features, drivers, etc. So I ask everyone to look hard into that[1] and tell me your opinion. I expect a lot of opinions, since it have to affect almost all good guys, as result I have to ask to split bug reports into two parts: 1. Should be done before merge to 10.0; 2. Can be done later. If it possible, please do it(review - report) ASAP. I have plan to done it that way: 1. Merge newcons to head (in a few days); 2. Fix a lot of reported bugs (2 hrs :-D ); 3. Persuade re@ about we need it in 10.0 (one week, maybe two); 4. Merge to 10.0; 5. One year AFK somewhere on Bahamas;^W^W^W^W^W^W^W 5. Add mouse cut-paste support; 6. Fix new bugs; 7. Some drinks. What do we will have with newcons: * (Think it is main) Allow us to switch to fresh Xorg, which require KMS. * Graphic devices which can provide framebuffer access can be easily used as virtual terminals (someone may have pixel-LCD on front of PC tower, may found it useful :-D ) * See [2]. TODO: * Lack of key mapping files, everyone can help with that using instructions on [3]; * A bit slow (mostly scrolling affected). * Other bugs :) * See [2]. Thanks! [1] - http://svnweb.freebsd.org/base/user/ed/newcons/ [2] - http://www.freebsd.org/news/status/report-2013-07-2013-09.html#Continuation-of-the-Newcons-Project [3] - http://raybsd.blogspot.com/2013/10/newcons-international-keyboard-input.html Hope you will love newcons! And maybe me too :) WBW -- Aleksandr Rybalko r...@ddteam.net Forget to give a patch to HEAD, here it is: http://people.freebsd.org/~ray/newcons/newcons_to_head_r257107_2013-10-25_1542.diff.gz Thanks to all! WBW -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
On Fri, Oct 25, 2013 at 4:18 PM, Aleksandr Rybalko r...@ddteam.net wrote: Hello fellow hackers! I finally reach the point when I can work with newcons instead of syscons on my laptop. Yes, I know it still buggy and have a lot of ... Yes, it's build and work # uname -a FreeBSD x220.local 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r257111M: Fri Oct 25 19:27:50 MSK 2013 andrey@x220.local:/usr/obj/usr/src/sys/W_BOOK amd64 :) In the single user ugly Can not read termcap database: Using dumb terminal settings In the multy user mode: Switch Xorg to consol and back is correct. spam log % tail /var/log/messages Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0xc0086457, nr=0x57, dev 0xf80006682800, auth=1 Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0x20006458, nr=0x58, dev 0xf80006682800, auth=1 Oct 25 20:47:29 x220 last message repeated 5 times Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0x800c645f, nr=0x5f, dev 0xf80006682800, auth=1 Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0x8020645d, nr=0x5d, dev 0xf80006682800, auth=1 Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0x80406469, nr=0x69, dev 0xf80006682800, auth=1 Oct 25 20:47:29 x220 kernel: [drm:pid1444:i915_gem_execbuffer2] buffers_ptr 80340a400 buffer_count 2 len 0058 Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0x800c645f, nr=0x5f, dev 0xf80006682800, auth=1 Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0xc0086457, nr=0x57, dev 0xf80006682800, auth=1 Oct 25 20:47:29 x220 kernel: [drm:pid1444:drm_ioctl] pid=1444, cmd=0x20006458, nr=0x58, dev 0xf80006682800, auth=1 In the console login jumps up, but it works correctly. If ScrlLk console blink. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: newcons comming
I think the best thing to do is address kib's issues and whatever else pops up in the review, then add it into -HEAD as the non-default console type. What I'd hate to see is some build time dependency where xorg _requires_ you to run newcons in order to run X. Well, at least just right now. I have a whole bunch of older hardware that I won't have access to for a couple more weeks (old netbooks, thinkpads, etc) that I'd like to run newcons and the latest xorg builds on, just to make sure we haven't broken things for stuff circa 2005-2006. There's still a lot of that stuff out there and right now xorg+console works fine for those. Thanks, -adrian On 25 October 2013 07:18, Aleksandr Rybalko r...@freebsd.org wrote: On Fri, 25 Oct 2013 15:10:44 +0100 symbol...@gmx.com wrote: On Fri, Oct 25, 2013 at 06:43:54AM -0700, Adrian Chadd wrote: 3) Realise it's not yet ready for 10.0 or HEAD, and target it to be ready for MFC for a 10.1 release. 4) Delay 10.0 until this has matured enough in HEAD, then release it. I really want to see more updated xorg support but the timing of it all feels a little overly rushed for a 10.0 release target. What do others think? FWIW, I'm really looking forward to newcons but I don't think it should be rushed into a release. (3) Seems prudent. Anyway it is optional. s/device vt/#device vt/ s/#device sc/device sc/ and you in the old, well known world :) --sym ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- Aleksandr Rybalko r...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
