From: Ben Hutchings <ben@decadent.org.uk>
To: Brandon Philips <brandon@ifup.org>
Cc: netdev@vger.kernel.org, Tobias Ringstrom <tori@unhappy.mine.nu>,
Grant Grundler <grundler@parisc-linux.org>,
Kyle McMartin <kyle@mcmartin.ca>,
davem@davemloft.net
Subject: Re: dmfe/tulip device id overlap
Date: Wed, 25 Nov 2009 13:08:22 +0000 [thread overview]
Message-ID: <1259154502.16258.36.camel@localhost> (raw)
In-Reply-To: <20091125043603.GK14043@jenkins.home.ifup.org>
[-- Attachment #1: Type: text/plain, Size: 666 bytes --]
On Tue, 2009-11-24 at 20:36 -0800, Brandon Philips wrote:
> Hello All-
>
> dmfe and tulip have an overlap of device IDs and it has been discussed
> before without resolution[1][2].
>
> The device ID in particular is:
>
> { 0x1282, 0x9100, PCI_ANY_ID, PCI_ANY_ID, 0, 0, DM910X },
> { 0x1282, 0x9102, PCI_ANY_ID, PCI_ANY_ID, 0, 0, DM910X },
>
> Users of Fedora[3] and openSUSE[4] are feeling pain from this but
> Ubuntu users are avoiding the issue do to the patch below.
[...]
Also an open bug in Debian (#515533). Thanks for pushing this issue.
Ben.
--
Ben Hutchings
Beware of programmers who carry screwdrivers. - Leonard Brandwein
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2009-11-25 13:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 4:36 dmfe/tulip device id overlap Brandon Philips
2009-11-25 4:49 ` Brandon Philips
2009-11-25 17:24 ` Grant Grundler
2009-11-29 8:30 ` David Miller
2009-11-30 6:55 ` Brandon Philips
2009-11-30 7:07 ` David Miller
2009-11-30 12:46 ` Ben Hutchings
2009-11-30 20:21 ` David Miller
2009-11-30 17:14 ` Grant Grundler
2009-11-30 20:26 ` David Miller
2009-11-30 22:22 ` Brandon Philips
2009-11-30 22:29 ` David Miller
2009-12-29 18:22 ` [PATCH] dmfe/tulip: Let dmfe handle DM910x except for SPARC on-board chips Ben Hutchings
2009-12-29 18:41 ` Grant Grundler
2010-01-04 5:36 ` David Miller
2009-11-25 13:08 ` Ben Hutchings [this message]
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=1259154502.16258.36.camel@localhost \
--to=ben@decadent.org.uk \
--cc=brandon@ifup.org \
--cc=davem@davemloft.net \
--cc=grundler@parisc-linux.org \
--cc=kyle@mcmartin.ca \
--cc=netdev@vger.kernel.org \
--cc=tori@unhappy.mine.nu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.