David Basden | 14 Mar 2008 14:15
Picon
Picon

Re: Raw IR read/write with Actisys 220L+

Hi,

If you're comfortable looking at the kernel drivers, maybe take a look
at sirdev_raw_read and sirdev_raw_write (and nearby) in 
drivers/net/irda/sir_dev.c

I doubt that the hooks there were at all intended for what you are
trying to do, but the calls are at least aware of the rest of the stack,
while still allowing raw reads and writes. (This may not work without
modification, but I suspect it would be the best place to start if you want to
coexist with the irda stack, or at least use the hardware drivers)

Most of what the actisys dongle driver itself (actisys-sir.c) does is just to
reset the dongle, bring it up into a known state, and then set the
line speed. If you really want to avoid the irda stack altogether,
it should be trivial to do this in userspace and avoid having to write
a totally new kernel driver.

David

On Fri, Mar 14, 2008 at 01:42:34PM +0100, Pascal Henck wrote:
> Hello,
> 
> I'm new in Linux and IrDA drivers so maybe my question is stupid. :)
> 
> We have developped medical devices with Infra-red communicationand our
> own OS. Our communication layer is more or less the IrPhy layer (SIR)
> with a receiver frequency shorter (~100?s). It works fine.
> 
> Now, we want to develop a new device with a backward compatibility. I
(Continue reading)

Pascal Henck | 14 Mar 2008 14:50
Picon

Re: Raw IR read/write with Actisys 220L+

Thank you for this quick answer.
I understand that you advice me to do initialise the dongle in user
space and then open /dev/ttyS0 (if dongle on commport 1) as a normal
serial port. I'm going to analyse the actisys-sir.c driver.

I like your proposal. I try!

Best Regards
P. Henck

2008/3/14, David Basden <davidb-irda@...>:
> Hi,
>
>  If you're comfortable looking at the kernel drivers, maybe take a look
>  at sirdev_raw_read and sirdev_raw_write (and nearby) in
>  drivers/net/irda/sir_dev.c
>
>  I doubt that the hooks there were at all intended for what you are
>  trying to do, but the calls are at least aware of the rest of the stack,
>  while still allowing raw reads and writes. (This may not work without
>  modification, but I suspect it would be the best place to start if you want to
>  coexist with the irda stack, or at least use the hardware drivers)
>
>  Most of what the actisys dongle driver itself (actisys-sir.c) does is just to
>  reset the dongle, bring it up into a known state, and then set the
>  line speed. If you really want to avoid the irda stack altogether,
>  it should be trivial to do this in userspace and avoid having to write
>  a totally new kernel driver.
>
>  David
(Continue reading)


Gmane