From: Komuro <komurojun-mbn@nifty.com>
To: Cord Walter <cord.walter@gmx.de>
Cc: netdev@vger.kernel.org, linux-pcmcia@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: axnet_cs / pcnet_cs: moving PCMCIA_DEVICE_PROD_ID for Netgear FA411
Date: Fri, 21 Nov 2008 21:48:12 +0900 [thread overview]
Message-ID: <20081121214812.b03d7166.komurojun-mbn@nifty.com> (raw)
In-Reply-To: <4925F6F1.9010305@gmx.de>
On Fri, 21 Nov 2008 00:46:57 +0100
Cord Walter <cord.walter@gmx.de> wrote:
> after noticing that my Netgear FA411 (PCMCIA-NIC) [1] stopped working with
> the release of the 2.6.25 kernel (sidux-version),
You are right. My patch has a bug.
The patch below fixes this problem.
By the way,
(1) Does your FA411 work properly with the pcnet_cs driver before?
(2) Please post the full-dmesg (axnet_cs).
--- linux-2.6.28-rc6/drivers/net/pcmcia/pcnet_cs.c.orig 2008-11-21 21:39:08.000000000 +0900
+++ linux-2.6.28-rc6/drivers/net/pcmcia/pcnet_cs.c 2008-11-21 21:39:24.000000000 +0900
@@ -587,7 +587,7 @@ static int pcnet_config(struct pcmcia_de
}
if ((link->conf.ConfigBase == 0x03c0)
- && (link->manf_id == 0x149) && (link->card_id = 0xc1ab)) {
+ && (link->manf_id == 0x149) && (link->card_id == 0xc1ab)) {
printk(KERN_INFO "pcnet_cs: this is an AX88190 card!\n");
printk(KERN_INFO "pcnet_cs: use axnet_cs instead.\n");
goto failed;
Best Regards
Komuro
> Hi,
>
> after noticing that my Netgear FA411 (PCMCIA-NIC) [1] stopped working with
> the release of the 2.6.25 kernel (sidux-version), I checked the
> respective driver sources and noticed that the pcnet_cs driver bailed
> out with "use axnet_cs instead" for the Netgear FA411, but axnet_cs
> doesn't claim this ID.
>
> I compiled a kernel with the PCMCIA-ID for the netgear card moved to
> axnet_cs from pcnet_cs which worked. I then contacted sidux-kernel
> maintainer Stefan Lippers-Hollmann who turned the info into this patch
> and integrated it into the kernel:
>
> <http://svn.berlios.de/svnroot/repos/fullstory/linux-sidux-2.6/trunk/debian/patches/features/2.6.27.4_PCMCIA_move-PCMCIA-ID-for-Netgear-FA411-from-pcnet_cs-to-axnet_cs.patch>
>
> This works for me and AFAIK there were no reports of any breakage for
> other devices on sidux-support.
>
> This looks like a trivial patch, but since I have very limited
> experience with kernel modifications I might be woefully wrong there.
> But if there are no side effects of this patch, is it possible to get it
> into the official kernel?
>
> I can provide more detailed information on the affected hardware if
> necessary.
>
> -cord
>
>
> [1]
> Socket 1 Device 0: [axnet_cs] (bus ID: 1.0)
> Configuration: state: on
> Product Name: NETGEAR FA411 Fast Ethernet
> Identification: manf_id: 0x0149 card_id: 0x0411
> function: 6 (network)
> prod_id(1): "NETGEAR" (0x9aa79dc3)
> prod_id(2): "FA411" (0x40fad875)
> prod_id(3): "Fast Ethernet" (0xb4be14e3)
> prod_id(4): --- (---)
> --
> Cord Walter
> email: cord.walter@gmx.de
>
> Weil es niemanden etwas angeht, dass ich nichts zu verbergen habe:
> http://www.gnupg.org/
> http://www.truecrypt.org/
> ...und überhaupt: http://www.FreiheitstattAngst.de
>
>
>
--
Komuro <komurojun-mbn@nifty.com>
next parent reply other threads:[~2008-11-21 12:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4925F6F1.9010305@gmx.de>
2008-11-21 12:48 ` Komuro [this message]
2008-11-21 14:10 ` Cord Walter
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=20081121214812.b03d7166.komurojun-mbn@nifty.com \
--to=komurojun-mbn@nifty.com \
--cc=cord.walter@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.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
all inboxes | Powered by JetHome®