From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: Francois Romieu <romieu@fr.zoreil.com>,
Martin Michlmayr <tbm@cyrius.com>,
Riku Voipio <riku.voipio@iki.fi>,
linux-kernel@vger.kernel.org
Subject: Re: r8169 on n2100 (was Re: r8169 mac address change (was Re: [0/3] 2.6.19-rc2: known regressions))
Date: Fri, 15 Dec 2006 21:14:35 +0000 [thread overview]
Message-ID: <20061215211435.GB10367@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20061215210329.GB14860@xi.wantstofly.org>
On Fri, Dec 15, 2006 at 10:03:29PM +0100, Lennert Buytenhek wrote:
> On Fri, Dec 15, 2006 at 09:15:22PM +0100, Francois Romieu wrote:
>
> > > Is there a way we can have this done by default on the n2100? I guess
> > > that since it's a PCI device, there isn't much hope for that..?
> >
> > Do you mean an automagically tuned default value based on CONFIG_ARM ?
>
> No, that wouldn't make sense, that's like making a workaround depend on
> arch == i386.
>
> I'm thinking that we should somehow enable this option on the n2100
> built-in r8169 ports by default only. Since the n2100 also has a mini-PCI
> slot, and it is in theory possible to put an r8169 on a mini-PCI card,
> the workaround probably shouldn't apply to those, so testing for
> CONFIG_MACH_N2100 also isn't the right thing to do.
There is dev->broken_parity_status ... although exactly what the sematics
of that flag actually are seems to be rather vague - there's code which
sets it for the Mellanox Tavor device, but it seems to only be exposed
via sysfs - no code in drivers/pci seems to take any action based upon
this flag being set.
That rather raises the question about the usefulness of that quirk.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2006-12-15 21:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061107115940.GA23954@unjust.cyrius.com>
2006-11-08 20:35 ` r8169 mac address change (was Re: [0/3] 2.6.19-rc2: known regressions)] Riku Voipio
2006-11-09 22:13 ` Francois Romieu
2006-11-09 23:14 ` Lennert Buytenhek
2006-11-10 18:59 ` Francois Romieu
2006-11-21 10:24 ` Martin Michlmayr
2006-11-21 20:45 ` Francois Romieu
2006-11-22 23:16 ` r8169 on n2100 (was Re: r8169 mac address change (was Re: [0/3] 2.6.19-rc2: known regressions)) Francois Romieu
2006-11-25 14:52 ` Martin Michlmayr
2006-11-25 16:02 ` Francois Romieu
2006-12-15 13:27 ` Lennert Buytenhek
2006-12-15 20:15 ` Francois Romieu
2006-12-15 21:03 ` Lennert Buytenhek
2006-12-15 21:14 ` Russell King [this message]
2006-12-16 23:09 ` Lennert Buytenhek
2006-12-16 23:31 ` Francois Romieu
2006-12-16 23:52 ` Lennert Buytenhek
2006-12-17 19:28 ` Martin Michlmayr
[not found] ` <20061217195635.GA10181@kos.to>
[not found] ` <20061217195728.GF23747@xi.wantstofly.org>
2006-12-17 21:02 ` Riku Voipio
2006-12-17 21:13 ` Lennert Buytenhek
2006-12-17 21:40 ` Riku Voipio
2006-12-17 21:48 ` Francois Romieu
2006-12-17 22:10 ` Martin Michlmayr
2006-12-16 0:54 ` Francois Romieu
2006-12-16 2:09 ` Lennert Buytenhek
2006-12-16 21:58 ` Francois Romieu
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=20061215211435.GB10367@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=buytenh@wantstofly.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riku.voipio@iki.fi \
--cc=romieu@fr.zoreil.com \
--cc=tbm@cyrius.com \
/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
Powered by JetHome