NE2000 driver updates
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 10 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | NE2000 driver updatesdrivers/ | +90 | 0 replies | |
| 2/4 | NE2000 driver updatesdrivers/ | +8 | 0 replies | |
| 3/4 | NE2000 driver updatesdrivers/ | +101 | 1 reply | |
| 4/4 | NE2000 driver updatesdrivers/ | +9 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] NE2000 driver updates
The first two patches are retransmits of the original PnP api patches updated to apply to a current tree.
The third patch is more of an RFC. It consolidates the creation/removal of the driver between the PnP code and the plain ISA code. In doing so it changes the net_device allocation from static to dynamic and allows PnP support when the driver is compiled in. This is probably how things will eventually have to be if there is ever driver model support for plain ISA devices.
The forth patch gets rid of the use of dev->mem_end as a bad flag.
Caveats:
It appears that the patch will break any autoprobe ordering because it no longer uses Space.c when compiled into the kernel.
Data size of object goes up about 100 bytes.
-Jeff