From: Jason Straight <junfan@penguinfarm.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: (2.4.1-ac15) pcmcia irq conflict
Date: Fri, 16 Feb 2001 15:40:16 -0500 [thread overview]
Message-ID: <3A8D9030.9040503@penguinfarm.com> (raw)
In-Reply-To: <E14TrL9-00043y-00@the-village.bc.nu>
Any suggestions of things I could try to help pinpoint the problem and
let you know the results? Everything was fine before 2.4.1.
I've been using the pcmcia-cs without kernel pcmcia support up until it
didn't work with 2.4.1, then I tried using the kernel pcmcia and no deal
there either.
As soon as I try to start pcmcia my machine freezes. When using
yenta_socket I can see that the TI pcmcia and eth0 (intel eepro100) are
both on irq 11.
when using the pcmcia-cs way of it I tried "exclude irq 11" in
config.opts and /etc/sysconfig/pcmcia set "PCIC_OPTS="irq_list=9,10,15
pci_irq_list=9,10,15"
as was suggested in this post :
http://groups.google.com/groups?q=inspiron+8000+pcmcia+2.4.1&hl=en&lr=&safe=off&rnum=1&seld=929215370&ic=1
It didn't work for me - at least not with 2.4.1-ac13 to ac15
I didn't disable my minipci ethernet because I need it and if the IRQ's
for pcmcia didn't use 11 now I wouldn't think I would need to.
Alan Cox wrote:
>> I have a Dell Inspiron 8000. Trying to use pcmcia with kernel
>> (yenta_socket) or pcmcia-cs only causes pcmcia card to take irq 11,
>> which my eth device is on also. This didn't happen with 2.2 or 2.4.0
>> kernels.
>
>
> Sharing a PCI irq is legal, so that isnt the cause. It could be that the
> irq routing isnt getting handled correctly however.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
--
Jason Straight
prev parent reply other threads:[~2001-02-16 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-16 18:14 (2.4.1-ac15) pcmcia irq conflict Jason Straight
2001-02-16 20:18 ` Alan Cox
2001-02-16 20:40 ` Jason Straight [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=3A8D9030.9040503@penguinfarm.com \
--to=junfan@penguinfarm.com \
--cc=alan@lxorguk.ukuu.org.uk \
/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.