From: Andrew Morton <akpm@linux-foundation.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: davej@redhat.com, netdev@vger.kernel.org
Subject: Re: odd RTL8139 quirk.
Date: Tue, 29 Apr 2008 15:32:40 -0700 [thread overview]
Message-ID: <20080429153240.7200e1a3.akpm@linux-foundation.org> (raw)
In-Reply-To: <48179B56.7000606@garzik.org>
On Tue, 29 Apr 2008 18:04:06 -0400
Jeff Garzik <jeff@garzik.org> wrote:
> Dave Jones wrote:
> > On Tue, Apr 29, 2008 at 03:37:41PM -0400, Jeff Garzik wrote:
> > > Dave Jones wrote:
> > > > I've just been playing with a model 2 OQO, which has an RTL8139.
> > > > It gets detected just fine, though it doesn't actually work..
> > > >
> > > > eth0: RealTek RTL8139 at 0xf8830000, 00:00:00:00:00:00, IRQ 18
> > > > eth0: Identified 8139 chip type 'RTL-8139'
> > > >
> > > > The null MAC address being one clue. Another oddity is that
> > > > ethtool reports that there's no link detected, even though there is.
> > > > (Enough for it to PXE boot a kernel from at least :)
> > > >
> > > > Futzing with the debug= modparam didn't yield anything extra at all.
> > > >
> > > > Any clues?
> > >
> > > Sounds like a broken EEPROM. Does supplying a MAC via ifconfig prior to
> > > 'ifconfig ... up' help?
> >
> > Ah. This sounds enlightening: http://www.oqotalk.com/index.php/topic,1511.0.html
> > Seems a shame to have to choose PIO vs MMIO for a distro kernel though.
> > Would there be any objection to turning that into a modparam ?
> > (If we wanted to get really fancy, we could even quirk around it automatically
> > when we detect broken hardware).
>
> Something like this? :)
>
> http://www.linux.sgi.com/archives/netdev/2004-11/msg00226.html
>
> It did not go upstream but it needed some init-time bug fixing, IIRC.
> Maybe akpm remembers more why my patch sucked... :)
Apart from its From: address you mean? ;)
I can find no record, sorry.
next prev parent reply other threads:[~2008-04-29 22:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 17:14 odd RTL8139 quirk Dave Jones
2008-04-29 19:37 ` Jeff Garzik
2008-04-29 19:47 ` Dave Jones
2008-04-29 21:56 ` Dave Jones
2008-04-29 22:04 ` Jeff Garzik
2008-04-29 22:10 ` Dave Jones
2008-04-29 22:19 ` Jeff Garzik
2008-04-29 22:28 ` Dave Jones
2008-04-29 22:33 ` Jeff Garzik
2008-04-29 22:32 ` Andrew Morton [this message]
2008-04-30 11:13 ` Jeff Garzik
2008-04-30 15:19 ` Stephen Hemminger
2008-05-29 15:06 ` Dave Jones
2008-05-29 15:07 ` [PATCH 1/2] 8139too: Make PIO/MMIO a modparam Dave Jones
2008-05-29 18:18 ` Jeff Garzik
2008-05-29 18:41 ` Dave Jones
2008-05-29 19:01 ` Jeff Garzik
2008-07-15 18:40 ` Dave Jones
2008-07-15 22:18 ` Jeff Garzik
2008-07-15 22:36 ` Dave Jones
2008-07-15 22:55 ` Jeff Garzik
2008-07-15 23:14 ` Dave Jones
2008-07-15 23:31 ` Jeff Garzik
2008-07-15 23:40 ` Dave Jones
2008-07-16 10:03 ` Peter Korsgaard
2008-07-15 22:54 ` Dave Jones
2008-07-15 23:03 ` Jeff Garzik
2008-07-15 23:15 ` Dave Jones
2008-05-29 15:08 ` [PATCH 2/2] 8139too: Make the OQO2 automatically use PIO mode Dave Jones
2008-05-29 18:21 ` Jeff Garzik
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=20080429153240.7200e1a3.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).