Re: Secondary console does not start properly, int10 problem?

[Aivils S. <ai...@un...>]

On Pirmdiena, 14. Novembris 2005 16:22, Friedrich W. H. Kossebau wrote:
> > > > 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
> SUSE 10.0's kernel to perfectly? I mean, ftty1 and ftty2 still work as
> promoted. :)

SUSE 10.0's kernel match through and through. Normal kernel maps
keyboards and speakers to single TTY layer tty1-tty63. Input layer
PC speaker regard as separate input device. faketty creates device
file for each suited device (key and sound). If userspace process
call sound ioctl, then bells all possible speakers, which are registered
by faketty, have device separate ftty file or have not.
Whatever, process can open that ftty0 and bell, bell, bell via
standard TTY ioctl's.

Aivils
p.s. snake charmers words works better for me than PCI code reading.
That code its realy messy.