Subject: Re: (Pre-) Announce SHARK IR / Home Control
To: None <mfoster@mail.com>
From: Ken Hornstein <kenh@cmf.nrl.navy.mil>
List: port-arm32
Date: 01/08/1999 11:15:33
>Depending on how much you need to change... I'll init the chip to IRDA mode at
>115,200 BPS, which is usually what you want.  How much do you need to change
>after this?

Actually, with IrDA, you always want to start out at 9600 baud, and you
negotiate higher baud rates from there.

>> My thinking was that it might make the most sense is to extend the
>> current com driver with ioctl's to know about the extra IR stuff.
>> I'll confess this was all motivated by IrDA, and I know the consumer
>> stuff generally has a different interfaces, so it may not make sense,
>> but I would still advise to at least try to do that as much as possible.
>
>Thanks to the fact that I've turned the COM port into three distinct devices,
>this would really be quite tough, and might not work too well, since most of
>what the COM driver does is to manage handshaking, and to manage the TTY
>driver...  Further, this would be opposed to the home control goals of having
>tight control of timing for talking to funky devices...

Fair enough.  I realize IrDA is in a sort-of different class than the
Consumer-IR stuff (you can tell which one was designed by computer
people! :-) ).

--Ken