[openbeosnetteam] Re: Realtek 8139 Driver
- From: "Niels Reedijk" <n.reedijk@xxxxxxxxx>
- To: <openbeosnetteam@xxxxxxxxxxxxx>
- Date: Tue, 10 Jun 2003 21:48:26 +0200
> Sounds like Interrupt handler and/or read hook issue there.
> But we'll try to see why looking at code, much easer.
I'm not too sure about that. My first take on the interrupt handler/read
hook would allow that possibility, but I've rewritten the beast and it
'should' not skip any packets. (The rewrite does bring up a kernel panic
sometimes :-(
> If you've write access to OBOS CVS repository, feel free to create a
> new "rtl8139" directory under
> current/src/add-ons/kernel/drivers/network, right next to Axel's
sis900
> one ;-)
>
> If you don't, send me your driver in a zipfile, I'll commit for you.
I'll have a nice zipfile within the hour. (I'll include a nice todo
list).
> Then, I'll ask contributor access for you to continue working on it
> using the CVS repository (always a pleasure, always :-) ).
Hehe, I sort of hate CVS, and I'm currently testing arch to see if it
is any better (but it won't be without a good frontend and proper
documentation - BitKeeper is better in this respect). My SF ID is nielx.
> Do you have already wrote the userland add-on to interface your driver
> with net_server?
Yes I have. I figured that it most probably would be compatible with the
current add-on if I would only follow the etherpci example, but it
isn't. (I believe the add-on of Be is probably designed differently to
accommodate the 'nice' design of the rtl8139).
> > Further on, I thought that this
> > > driver could probably be one of the first to be adapted to the new
> > > interface api.
>
> (...)
>
> But...
>
> But I'll hard suggest you to B_DONT_DO_THAT!
>
> First, it's too soon to consider our network interface module API
> stable, nor even finish.
>
> Second, by choosing it, you'll make far harder to have both OBOS and
R5
> (BONE & net_server) code shared,
> Which, I think, is bad, as R5, net_server and BONE exists, OBOS
network
> stack replacment don't (yet).
> And last but not least, rewriting to new interface will not give you
> any huge gain, I think it's not worth it...
Then I won't do that. Perhaps there's a nice task for me there ;-)
> PS: hope you'll pardon constant baby cries while I wrote this message
;
> -)
Don't sweat it, I like a little background noise.
Niels Reedijk
- Follow-Ups:
- [openbeosnetteam] Re: Realtek 8139 Driver
- From: Philippe Houdoin
- References:
- [openbeosnetteam] Re: Realtek 8139 Driver
- From: Philippe Houdoin
Other related posts:
- » [openbeosnetteam] Realtek 8139 Driver
- » [openbeosnetteam] Re: Realtek 8139 Driver
- » [openbeosnetteam] Re: Realtek 8139 Driver
- » [openbeosnetteam] Re: Realtek 8139 Driver
- » [openbeosnetteam] Re: Realtek 8139 Driver
- » [openbeosnetteam] Re: Realtek 8139 Driver
- » [openbeosnetteam] Re: Realtek 8139 Driver
- » [openbeosnetteam] Re: Realtek 8139 Driver
- » [openbeosnetteam] Re: Realtek 8139 Driver
- » [openbeosnetteam] Re: Realtek 8139 Driver
- » [openbeosnetteam] Re: Realtek 8139 Driver
- » [openbeosnetteam] Re: Realtek 8139 Driver
- » [openbeosnetteam] Re: Realtek 8139 Driver
- » [openbeosnetteam] Re: Realtek 8139 Driver
- » [openbeosnetteam] Re: Realtek 8139 Driver
- » [openbeosnetteam] Re: Realtek 8139 Driver
- » [openbeosnetteam] Re: Realtek 8139 Driver
- » [openbeosnetteam] Re: Realtek 8139 Driver
- » [openbeosnetteam] Re: Realtek 8139 Driver
- » [openbeosnetteam] Re: Realtek 8139 Driver
- » [openbeosnetteam] Re: Realtek 8139 Driver
- » [openbeosnetteam] Re: Realtek 8139 Driver
- [openbeosnetteam] Re: Realtek 8139 Driver
- From: Philippe Houdoin
- [openbeosnetteam] Re: Realtek 8139 Driver
- From: Philippe Houdoin