James <[EMAIL PROTECTED]> writes:
> As always, things happen in threes. I have just received (from a friend)
> some documentation for a Toshiba infrared ASIC module from which given
> what I have read so far looks exactly like the 701 chip. So I guess I'll
> be fixing the code now I have some idea what I'm doing so I don't need
> any alpha testers (YET).
>
> The GOOD news is that from the docs it looks like
> it will be posibile to make the IrDA interface receive non IrDA packets
> like the HP48 and the palm(when it's not using IrDA) give out. Whoever
> it was who asked about making the oboe chip emulate a serial port should
> get back in touch because it would be nice to get that functionality in
> during this code rewrite.
>
> Take care, and thank you Toshiba even if it did have to reach me
> by the most convoluted pathway,
>
> Dag, are there any plans to implement unicast address filtering into
> the driver API?
It would be easy to add an ioctl where IrLAP could inform the driver which
unicast address it wants to receive frames from. Notice that it will only
be calling the ioctl API of the driver directly, so it has nothing to do
with a user-space ioctl (even if a capable sysadm could also decide to do
this). This is similar to the other ioctls like SIOCSBANDWIDTH etc.
So yes, I can add it if you want it! But it might not get into 2.4.
-- Dag
--
/ Dag Brattli | The Linux-IrDA Project /
// University of Tromsoe, Norway | Infrared communication for Linux //
/// http://www.cs.uit.no/~dagb | http://www.cs.uit.no/linux-irda/ ///
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda
