|
From: Friedrich W. H. K. <Fri...@ko...> - 2005-11-14 14:20:30
|
Am Montag 14 November 2005 14:03, schrieb Aivils Stoss:
> On Pirmdiena, 14. Novembris 2005 13:59, Friedrich W. H. Kossebau wrote:
> > Am Montag 14 November 2005 10:17, schrieb Aivils Stoss:
> > > On Sv=E7tdiena, 13. Novembris 2005 23:23, Friedrich W. H. Kossebau wr=
ote:
> > >
> > > faketty runs correctly if is possible see output of this:
> > > # cat /dev/fttyXX
> >
> > It is, but only for ftty{1,2}. ftty0 stays silent.
> >
> > > Also full truth about Linux input, ftty included
> > > # cat /proc/bus/input/devices
> >
> > It is, ah, funny, the pc speaker got ftty0, now, for that I have a hard
> > time to produce input :P
Any comment about this? Is this known or does faketty perhaps not match SUS=
E=20
10.0's kernel to perfectly? I mean, ftty1 and ftty2 still work as=20
promoted. :)
> > I: Bus=3D0010 Vendor=3D001f Product=3D0001 Version=3D0100
> > N: Name=3D"PC Speaker"
> > P: Phys=3Disa0061/input0
> > H: Handlers=3Dkbd event0 ftty0
> > B: EV=3D40001
> > B: SND=3D6
> >
> > I: Bus=3D0011 Vendor=3D0001 Product=3D0002 Version=3Dab83
> > N: Name=3D"AT Raw Set 2 keyboard"
> > P: Phys=3Disa0060/serio1/input0
> > H: Handlers=3Dkbd event1 ftty1
> > B: EV=3D120013
> > B: KEY=3D4 2000000 3802078 f840d001 f2ffffdf ffefffff ffffffff fffffffe
> > B: MSC=3D10
> > B: LED=3D7
> >
> > I: Bus=3D0011 Vendor=3D0001 Product=3D0001 Version=3Dab41
> > N: Name=3D"AT Translated Set 2 keyboard"
> > P: Phys=3Disa0060/serio0/input0
> > H: Handlers=3Dkbd event2 ftty2
> > B: EV=3D120013
> > B: KEY=3D4 2000000 3802078 f840d001 f2ffffdf ffefffff ffffffff fffffffe
> > B: MSC=3D10
> > B: LED=3D7
> >
> > I: Bus=3D0003 Vendor=3D05fe Product=3D0001 Version=3D047b
> > N: Name=3D"Cypress Sem Cypress USB Mouse"
> > P: Phys=3Dusb-0000:00:07.2-2/input0
> > H: Handlers=3Dmouse0 event3
> > B: EV=3D7
> > B: KEY=3D70000 0 0 0 0 0 0 0 0
> > B: REL=3D3
> >
> > > > Funny enough: Having started the secondary console when pressing so=
me
> > > > keys random characters are added both to the primary (where the she=
ll
> > > > is) _and_ the secondary screen. Even better, when some screensaver
> > > > starts (no idea which) _both_ screens are blanked and return again
> > > > after some keypress. Sometimes even the prompt changes to the second
> > > > screen.
> > >
> > > Not all video adapters or X drivers have capability to share resources
> > > (VGA,PCI) between two independ X servers. Looks like one of X driver
> > > steer both adapters, because both adapters may be use same resources.
> >
> > Hm. Is there any output I could investigate to find numbers which could
> > point to shared resources? Like Xorg.{0,1}.log? Where to look best? Whi=
ch
> > resources are there at all? What do you mean by VGA-resource? In the
> > BIOS?
>
> stay away from it, as you stay away from a "serpent"!
Oh, I heard there are snake-charmers ;)
> > And does this mean that the single card option is not fully supported by
> > all drivers? Where do/can they driver ignore it?
>
> 1st X occupy PCI resource A to B. 2nd X does not have info about this and
> think A to B is free and occupy it again.=20
So what is the isolate-device patch then for? (Hm, should take a closer loo=
k=20
myself). Does it only prevent broadcasts?
> I have very foggy image , how to=20
> works memory mapped video adapter registers, like VGA. X do it all
> automatic without any query and without any preconfigured condition.
And to teach X to do other is left for the snake farmers, right? ;)
Hm, the source is open... Will see if I can dig a little there (will take a=
=20
stick with me to defend against possible snake attacks :).
Regards
=46riedrich
|