From: Timothy L. <tl...@ro...> - 2003-04-01 02:10:17
Hi
I am going to update the 3c515 driver in 5.1 with the changes that I
have done in 5.0 (separating out the ISAPNP code to isapnp.c and
isapnp.h and other updates). Where in the directory structure should
they go? Should I leave them in drivers/net or move them to somewhere
like core/ or arch/i386/core/
Tim
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.465 / Virus Database: 263 - Release Date: 3/25/2003
From: Timothy L. <tl...@ro...> - 2003-04-01 02:33:22
Sorry for the html format, here is the text
Hi=20
=A0
I am going to update the 3c515 driver in 5.1 with the changes that I
have done in 5.0 (separating out the ISAPNP code to isapnp.c and
isapnp.h and other updates).=A0 Where in the directory structure should
they go?=A0 Should I leave them in drivers/net or move them to somewhere
like core/ or arch/i386/core/
=A0
Tim
"Timothy Legge" <tl...@ro...> writes:
> Sorry for the html format, here is the text
>=20
> Hi=20
> =A0
> I am going to update the 3c515 driver in 5.1 with the changes that I
> have done in 5.0 (separating out the ISAPNP code to isapnp.c and
> isapnp.h and other updates).=A0 Where in the directory structure should
> they go?=A0 Should I leave them in drivers/net or move them to somewhere
> like core/ or arch/i386/core/
I would place the in:
core/isapnp.c
include/isapnp.h
And if there is something that is demonstrably x86 specific
the code can code in arch/i386/core. But isapnp primarily depends
on the isa bus and inb/outb none of which are x86 specific. And
inb/outb already have arch dependent implementations.
Eric