From: "Krzysztof Helt" <krzysztof.h1@wp.pl>
To: sparclinux@vger.kernel.org
Subject: [PATCH] sunlance probing problem
Date: Fri, 11 Aug 2006 22:03:16 +0000 [thread overview]
Message-ID: <44dcfea4406f9@wp.pl> (raw)
[-- Attachment #1: Type: text/plain, Size: 660 bytes --]
From: Krzysztof Helt (krzysztof.h1@wp.pl)
The patch removes the "le" device from matching list of probed
devices.
Signed-off-by: Krzysztof Helt (krzysztof.h1@wp.pl)
---
The sunlance driver allows probing of three devices: le, ledma
and lebuffer. The "le" device is a child entry for either ledma
or lebuffer devices. Thus, each Ethernet adapter is probed twice
and registered as two Ethernet adapters.
I tested it on SS20 and 2.6.18-rc4 kernel.
----------------------------------------------------
Czy 10 minut rozmowy = ponad 11 zł oszczędności ?
Sprawdź: http://klik.wp.pl/?adr=http%3A%2F%2Ftelefon.wp.pl%2Foszczednosci.html&sid=842
[-- Attachment #2: lance-id.patch --]
[-- Type: application/octet-stream, Size: 705 bytes --]
diff -ur linux-2.6.17/drivers/net/sunlance.c linux-new/drivers/net/sunlance.c
--- linux-2.6.17/drivers/net/sunlance.c 2006-08-10 08:58:34.000000000 +0200
+++ linux-new/drivers/net/sunlance.c 2006-08-11 23:33:11.000000000 +0200
@@ -1569,9 +1569,7 @@
struct device_node *dp = dev->node;
int err;
- if (!strcmp(dp->name, "le")) {
- err = sparc_lance_probe_one(sdev, NULL, NULL);
- } else if (!strcmp(dp->name, "ledma")) {
+ if (!strcmp(dp->name, "ledma")) {
struct sbus_dma *ledma = find_ledma(sdev);
err = sparc_lance_probe_one(sdev->child, ledma, NULL);
@@ -1602,9 +1600,6 @@
static struct of_device_id sunlance_sbus_match[] = {
{
- .name = "le",
- },
- {
.name = "ledma",
},
{
next reply other threads:[~2006-08-11 22:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 22:03 Krzysztof Helt [this message]
2006-08-11 23:11 ` [PATCH] sunlance probing problem Eric Brower
2006-08-11 23:27 ` David Miller
2006-08-12 13:20 ` Krzysztof Helt
2006-08-18 1:10 ` David Miller
2006-08-18 17:32 ` Krzysztof Helt
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=44dcfea4406f9@wp.pl \
--to=krzysztof.h1@wp.pl \
--cc=sparclinux@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 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.