From: "Kevin D. Kissell" <kevink@paralogos.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Linux MIPS org <linux-mips@linux-mips.org>, tsbogend@alpha.franken.de
Subject: Re: MIPS Malta and PCNet32 Driver
Date: Sat, 08 Jan 2011 15:23:26 -0800 [thread overview]
Message-ID: <4D28F1EE.8030609@paralogos.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1101082251440.31930@eddie.linux-mips.org>
On 1/8/2011 3:07 PM, Maciej W. Rozycki wrote:
> On Sat, 8 Jan 2011, Kevin D. Kissell wrote:
>
>> and, amusingly, from a stock 2.6.32.27 kernel that exhibits the problem,
>> I plugged in a PCI NIC and *both* interfaces came up happy. :o/ One
>> might suspect that PCNet32 now assumes some level of initialization that
>> isn't being done in the platform code, and lucks out if a more
>> thoroughly paranoid driver gets loaded first.
> Are you seeing the problem with a system controller other than the
> Bonito? That would be somewhat alarming, though easier to fix.
>
> With the Bonito I'd have assumed it was some low-level PCI code rewrite
> -- that seem to keep happening over and over again -- that missed a bit in
> the Bonito driver or the driver altogether. With the Bonito core cards
> limited to the MIPS 20Kc core and some exotic (for the Malta) QED CPU
> options that would be no surprise at all to me.
I don't think it's a "classic" Bonito, YAMON calls out:
MIPS SOC-it 101 OCP / 1.3 SDR-FW-1:1
Regards,
Kevin K.
next prev parent reply other threads:[~2011-01-08 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 18:40 MIPS Malta and PCNet32 Driver Kevin D. Kissell
2011-01-08 20:02 ` Kevin D. Kissell
2011-01-08 23:07 ` Maciej W. Rozycki
2011-01-08 23:23 ` Kevin D. Kissell [this message]
2011-01-09 0:01 ` Maciej W. Rozycki
2011-01-08 22:33 ` Thomas Bogendoerfer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D28F1EE.8030609@paralogos.com \
--to=kevink@paralogos.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=tsbogend@alpha.franken.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox