On Sun, 17 Oct 1999, Avery Pennarun wrote:
> On Sat, Oct 16, 1999 at 12:32:04PM -0400, Donald Becker wrote:
>
> > You should always use the 'ne2k-pci' driver for PCI cards:
> > The PCI driver automatically detects all cards and reads the proper IRQ.
>
> Doesn't the 'ne' driver do this? (Well, it automatically detects at least
> one PCI card...)
The 'ne' driver was updated to detect PCI cards. But that was not the best
approach.
> > The PCI driver accepts the standard set of PCI driver options
The goal is for all of the PCI network drivers to act identically. They
should
Detect all available cards with no parameters needed
Share interrupts properly (never with SA_INTERRUPT)
Take the same basic set of module parameters.
Work on all popular architectures (Alpha, MIPS, PPC, Sparc)
Eventually they should all
Support cards with ACPI
Support PCI hot-swap
Support MII ioctl() call if the chip has a MII transceiver.
(Faking a MII transceiver at address 32 is best, if possible.)
> I'm kind of interested to know the actual set of differences between ne and
> ne2k-pci (other than that ne2k-pci obviously can't do ISA) since I've
> recently run into some PCI arcnet cards and I don't _think_ I need to do a
> separate driver to support them fully.
You should do a separate driver.
- People with PCI-only machines should have safe, automatic hardware, and
should never have to see ISA work-arounds.
- The PCI driver should support all architectures (Sparc, MIPs, Alpha, PPC)
Donald Becker
Scyld Computing Corporation, and
USRA-CESDIS, [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
