From: Aivils S. <Aiv...@un...> - 2003-10-15 07:36:52
|
Hi All! I have got runnig fbdev, where each framebuffer device has his own VT and number of VC. For test I use Voodoo Graphic, Voodoo2, Voodoo3 video adapters. Voodoo Graphic and Voodoo2 are designed as secondary video adapters, so i have not troubles with initializing. For tests all fbdev low level drivers and fbcon must be compiled straight into kernel. Current modules isn't supported. fbcon must have kernel commandline option: fbcon=vt:toc.5.7 which mean, fbcon creates three VT, 1st VT take over admin_vt (VGA console), 2nd VT has 5 VCs, 3rd VT has 7 VCs. 1st VT uses /dev/fb0, 2nd VT - /dev/fb1 3rd VT - /dev/fb2. If fbdev low level drivers is located into kernel, then fb init order is hardcoded in fbmem.c . If /dev/fb1 need take over admin_vt, then simple change command line: fbcon=vt:5.toc.7 If You needs for login promt on secondary fbdev, then You must run aditional mingetty on right ttyXX. You can run multiple mingetty on secondary fbdev. Switching to next vc is ordinary Atl-Fx or Atl-LeftArrow, Alt-RightArrow. In abstract dual head video adapters , which create fbdev for each head, must be ready for linux-ruby. Dual head adapter register /dev/fb0 and /dev/fb1 and after fbcon set up VT for each /dev/fbXX. I have not any practical results. On second fbdev XFree86 must have option vtXX, otherwise xf86 uses free vc on VT0. Results: Voodoo1/Voodoo2/Voodoo3 - runs nice. Voodoo3, AtiRagePro - blank screen on Ati. NvidiaTNT2 - oopses only. OOPSES: various outside ruby related code (i think so). redundant mingetty on VTless tty lead oopses series - ruby related. Seems we should wait for more stable 2.6.0-blah-blah Changes commited 14-OKT-2003 Remake it all modular - work in progress. Low level driver compatibility with linux-ruby - ask James. Aivils Stoss |