Message-ID: <3ADC798E.35236DBE@tac.ch>
Date: Tue, 17 Apr 2001 19:12:46 +0200
From: Roberto Nibali <ratz@tac.ch>
Organization: terreActive
MIME-Version: 1.0
To: Steve Hill <steve@navaho.co.uk>
CC: linux-kernel@vger.kernel.org, Donald Becker <becker@scyld.com>
Subject: Re: Fix for Donald Becker's DP83815 network driver (v1.07)
In-Reply-To: <Pine.LNX.4.21.0104171727300.4446-100000@sorbus.navaho>
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org

> I have no idea - I haven't been able to get in touch with him :(
> (The fix was urgently required, and this did the job).

I just realized I had this old patch for 2.2.17 and that in 2.2.19
series this problem is addressed correctly by Donald. Apologies to
him and sorry about the confusion. His or Ion's code from the starfire.c:

int __init starfire_probe(struct net_device *dev)
{
        static int __initdata probed = 0;

        if (probed)
                return -ENODEV;
        probed++;

        return pci_module_init(&starfire_driver);
}

> Not sure - I've never tried initing more than 3 of the DP83815 cards in a
> single machine.  (I am using Cobalt Qube 3's, which have 2 DP83815's on
> the motherboard, and a single PCI slot which I have installed a DP38315 in
> for testing purposes).

I think this is not the problem of the driver specifically but more of the
limitation of Space.c. I haven't yet found a clean way around it. I always
get "early initialization of device eth14 is deferred" messages.

Regards,
Roberto Nibali, ratz

-- 
mailto: `echo NrOatSz@tPacA.cMh | sed 's/[NOSPAM]//g'`
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/