From: "Miles Lane" <miles.lane@gmail.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Arjan van de Ven" <arjan@infradead.org>,
mingo@elte.hu, "Andrew Morton" <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.17-mm5 + pcmcia/hostap/8139too patches -- inconsistent {hardirq-on-W} -> {in-hardirq-W} usage
Date: Tue, 4 Jul 2006 19:20:16 -0700 [thread overview]
Message-ID: <a44ae5cd0607041920p691a1998w8b3fb844cab6b706@mail.gmail.com> (raw)
In-Reply-To: <1152005201.28597.14.camel@localhost.localdomain>
On 7/4/06, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> Ar Llu, 2006-07-03 am 16:14 -0700, ysgrifennodd Miles Lane:
> > eth2: NE2000 (DL10022 rev 30): io 0x300, irq 11, hw_addr 00:50:BA:73:92:3D
> > Which seems to indicate I need to tweak the PCMCIA settings to get this card
> > working. I wonder if anyone is going to follow up on enabling shared IRQ
> > support.
>
>
> Try this. Note the SMP locking in this driver appears iffy and looks
> like it was never SMP sane.
The patch corrects the messages about shared interrupts:
pccard: PCMCIA card inserted into slot 0
cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xcffff 0xdc000-0xfffff
cs: memory probe 0x50000000-0x51ffffff: excluding 0x50000000-0x51ffffff
cs: memory probe 0x60000000-0x60ffffff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.
cs: memory probe 0xe0200000-0xe02fffff: excluding 0xe0200000-0xe020ffff
pcmcia: registering new device pcmcia0.0
PM: Adding info for pcmcia:0.0
eth2: NE2000 (DL10022 rev 30): io 0x300, irq 11, hw_addr 00:50:BA:73:92:3D
I have lost the connector cable that attaches the card to an ethernet
cable, so I have been using a cable labelled 3COM instead. It has
LEDs for 10 and 100 Kbps connections.
Neither LED is lighting up. On the other hand, NetworkManager
seems aware when I have an ethernet cable attached. I now
suspect that I need a new cable. The card is a D-Link DFE-650
Fast Ethernet PCMCIA adapter. Maybe I should order one of these:
http://shopping.yahoo.com/p:QVS%20CPN-GN100T%20:1991447348;_ylt=Ap_SzM9pNc5eVJDZKVqsYd5tpcsE;_ylu=X3oDMTBuZDl1N2RxBF9zAzU5MDk4NTIxBGx0AzQEc2VjA3Ny?clink=dmss//ctx=sc:cnetwork_adapter,c:cnetwork_adapter,mid:57,pid:1991447348,pdid:57,pos:6
What do you think?
Miles
prev parent reply other threads:[~2006-07-05 2:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 21:31 Miles Lane
2006-07-03 21:43 ` Arjan van de Ven
2006-07-03 22:25 ` Alan Cox
2006-07-03 23:14 ` Miles Lane
2006-07-04 7:36 ` Ingo Molnar
2006-07-04 8:18 ` Alan Cox
2006-07-04 9:26 ` Alan Cox
2006-07-05 2:20 ` Miles Lane [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=a44ae5cd0607041920p691a1998w8b3fb844cab6b706@mail.gmail.com \
--to=miles.lane@gmail.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®