Date: Thu, 18 Jan 2001 00:04:28 -0800 From: Julian Elischer <julian@elischer.org> To: Mark Santcroos <marks@ripe.net> Cc: "Michael C . Wu" <keichii@iteration.net>, freebsd-hackers@freebsd.org, benno@freebsd.org Subject: Re: [IrDA] adding new network stack Message-ID: <3A66A38C.310774FD@elischer.org> References: <20010116103212.C12906@ripe.net> <3A649154.B345C634@elischer.org> <20010116194307.A28087@ripe.net> <3A64B6C2.6D0ADF97@elischer.org> <20010116232326.A6513@ripe.net> <20010116233409.A9413@peorth.iteration.net> <20010117113949.A29173@ripe.net> <3A65A18C.B5529BA9@elischer.org> <20010117151421.B29173@ripe.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Santcroos wrote:
>
> On Wed, Jan 17, 2001 at 05:43:40AM -0800, Julian Elischer wrote:
>
> I've been looking alot at other drivers already.
> My device driver is heavily based on the scheme in the example. But I've
> made it a module so I can develop it outside the source tree.
the sample driver in -current already is a module :-)
>
> > If you want to send me your driver I'll even make a first attempt to bolt a
> > netgraph interface to it.
> > (or you can try and I'll check it for you)
>
> Thanks for the offer, I will do a first try myself, to learn more about
> it, but will certainly come to you when I can't work things out.
>
> > check the 'blueprints' article on netgraph in daemon-news
> > for a good run-down on what it all means (though it's abot out of date
> > and had a few small
> >
> > lastly, read netgraph(4)
>
> done (doing)
>
> > here is a list of existing netgraph drivers:
> >
> > sys/dev/lmc/if_lmc.c sys/dev/usb/udbp.c sys/i386/isa/if_ar.c
> > sys/i386/isa/if_sr.c sys/i4b/driver/i4b_ing.c sys/netgraph/ng_ether.c
> > sys/netgraph/ng_tty.c sys/pci/if_mn.c sys/dev/musycc/musycc.c
>
> *nods* already found them
>
> > maybe just old async IR.. we should try handle that too :-)
>
> *nods* for the driver part we can use ALOT from Linux
>
> > for a sample PCI driver do:
> > (on current)
> > cd /usr/share/examples/drivers
> > sh make_device_driver.sh irda
> > then examine the generated files..
> > :-)
>
> Like I said above, I've used the info in there but created my own module,
> to be able to develop outside the tree.
> (I'm fairly new to FreeBSD/CVS so I do not know an easy way to work on a
> cvstree and keep it up to date(when your changes don't get uploaded) at
> the same time)
> I don't know what is the normal behaviour, but maybe it's possible to get
> an early framework into -CURRENT sooner or later? (If it doesn't
> interfere with other code)
if it's completely independent of othe rcode it can be ssonner than later.
if it makes changes elsewhere, then it should be better developed.
it should at least do one thing before it is committed, whether that is
talk to palm-pilots or Philips TVs is up to you :-)
>
> Within a day or so I hope to release my first pieces of code.
> In the next day I will try to insert a little netgraph code into it.
great.
basically just bolt the sample netgraph node on the end and edit all
teh 'xxx' to something else.
>
> Mark
>
> --
> Mark Santcroos RIPE Network Coordination Centre
>
> PGP KeyID: 1024/0x3DCBEB8D
> PGP Fingerprint: BB1E D037 F29D 4B40 0B26 F152 795F FCAB 3DCB EB8D
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
--
__--_|\ Julian Elischer
/ \ julian@elischer.org
( OZ ) World tour 2000
---> X_.---._/ from Perth, presently in: Budapest
v
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A66A38C.310774FD>