Re: ruby cvs first look

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

>On Fri, Nov 08, 2002 at 07:54:41PM +0000, James Simmons wrote:
>
>> > Yes it's boot!
>> >
>> > Around the code popup currcons mismatch.
>> > find_vc() vc_allocate() good only for one console.
>>
>>    I know :-( The current problem is the beeper and the keyboard. In the
>> original ruby we didn't have the beeper converted over to the input api.
>> This made life easier. Now we do. This means both the keyboard and
beeper
>> are registered to the keyboard console handler. Because the old ruby
code
>> assumed it was always a keyboard this means the beeper is seen as a
>> keyboard. Of course this is bad!! So what is the solution?
>>
>>    Well first we to see what possible combinations we can have. They
are:
>>
>> 1) The beeper is built into the keyboard. Sparc keyboard i.e
>>
>> 2) Seperate beepers but we have more than one.
>>
>> 3) Only one beeper.
>>
>> Now 1 and 3 are very common. The first solution I thought of was having
>> two struct input_handlers in struct vt_struct. One for keyboard and the
>> second for the beeper. For the keyboard with the built in speaker both
>> handlers would point to the same device. For the PC we have to attach
the
>> speaker to the first VT we find without a speaker. This can be easliy
>> handled by first testing the incoming input device handles keys. Then we
>> test it right away to see if it has a speaker. Now the question is what
do
>> we do for a "global" speaker. For example I have two PS/2 keybaords but
>> one PC speaker. Do we share it.Then there is the issue if two users want
>> to reprogram the  beeper to be at two different rates. The hardware
can't
>> be at two different rates at the same time. Vojtech do you have any
ideas
>> on how to handle this?
>
>I would assign the beeper to the first keyboard and make it all
>configurable by the user - you really only need to have one keyboard,
>one screen, and one beeper running after boot and the rest
>(reassignment, etc) can be taken care of by the init scripts.

Agree. I am child of PC-compatible hardware.
Of course /dev/ttyXX is not a keyboard device and VT may have a beeper
handler
if keyboard is beeperless.

Aivils Stoss