irda devices support

Martin Roos kulminaator at gmail.com
Sat Apr 9 01:25:51 PDT 2005


i certainly dont think that every userlevel application should worry
about implementing the irda stack itself ... this is kindof wierd
(would you develope an ufs for each application that wants to use your
data on your ufs formatted disk ? or would every network application
have to own their own implementation of tcp stack ? i don't think so
...)

besides, if there are certain hardware pieces like this usb dongle,
then implementing a device on a framework in the kernel is certainly
easier than inventing the whole wheel again. the linux driver for my
irda dongle is pretty small. but writing all it by myself for freebsd
wont probably be worth the result.

birda seems to be a quite shallow solution with even shallower docs,
and it doesn't seem to have a clue how to use an usb dongle as an irda
device. (you can't just handle the ugen device as an infrared port, it
behaves pretty much differently :) )

i am looking at it's code hoping to find some way to modify it to make
it interact with the usb device ... but since the application wasn't
designed for such hacks this can take quite a while.


On Fri, 08 Apr 2005 22:46:44 +0200, Eric Masson
<e-masson at kisoft-services.com> wrote:
> Martin Roos <kulminaator at gmail.com> writes:
> 
> > imho freebsd's kernel couldn't possible really recognize any usb irda
> > dongle because it really wouldn't have any idea what to 'do' with the
> > device without an implementation of irda stack.
> 
> What makes you think that the irda protocol stack should be implemented
> in kernel ?
> 
> Birda is a userland irda stack that uses a serial device as transport
> media.
> 
> Éric Masson
> 
> -- 
>  AB> Comment cela peut-il se débloquer ?
>  AT> Fuca.
>  Excusez-moi, je n'ai pas compris. Merci de répondre plus clairement.
>  -+- AB in Guide du Neuneu Usenet - Il est con c'type, hé ! -+-
> 

-- 
##########
Martin Roos


More information about the freebsd-hardware mailing list