Re: Multi-seat XFree solution under Linux with framebuffers.

[<shs...@st...>]

Hi,

> > may be you could try the Matrox multy series,
> ;-) Sorry, but we have developed a new ATI card (with 8 outputs), and
> need to get the X servers to run on these cards.
> 
> > they should have released a 4 headed card with the G450 chip,
> > and if they made it like the previous series,
> > you may be will be able to run them in both Miguels & backstreet ruby
> way,
> > so you'll be able to get 16-20-24 heads/users 4-5 pci + 1 agp x 4
> heads,
> > and if you have luck you'll be able to get it working with normal
> drivers,
> > not through FB , so you could use Xvideo, DRI ....
> 
> Main problem is that I also need the FB support for our
> software/applications.....

i was just saying that if you have luck you can get the normal drivers work,
but the fb driver should work without a problem,
are you working on a kind of set-top-box, do you need the fb driver in order to 
use X over video out  

i was also thinking that if you get backstreet ruby in workable for you state,
it would be easier to setup the X config files, mostly the keyboard input 
section, as you don't need to mess with the event devices,
with your current solution you should find wich event devices are mices, 
keyboards, additional multimedia intefaces of some keyboards, with ruby you'll 
have to consider only the last two, also it should be fairly easy to get only 
the normal keyboard interfaces to bind to a VT, even if some multimedia 
keyboard interface has registered VT you can fix it trough /proc.
This should be also doable in kernel:
i think all the normal keyboard interfaces register with PHYS= USBxxx0,
and the multimedia interfaces register with PHYS=USBxxx1 , so if you modiffy 
the kernel to bind VTs only to keyboards with PHYS=USBxxx0 you get VTs bind to 
all keyboards -- no need to modiffy X config files if some event device change 
it's number.
 
if i'm not misstaken upon replug of a usb event device it's possible,
that it's event number change -- you'll have to modify the coresponding 
XFConfig to get keyboard back, which shouldn't be needed under ruby, as ruby 
doesn't use the event device files.
   
best,

svetljo