From: David Ford <david@linux.com>
To: David Hinds <dhinds@valinux.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: current snapshots of pcmcia
Date: Mon, 06 Nov 2000 15:19:41 -0800 [thread overview]
Message-ID: <3A073C8D.B6511746@linux.com> (raw)
In-Reply-To: <3A06757F.3C63F1A8@linux.com> <20001106104927.A19573@valinux.com>
[-- Attachment #1: Type: text/plain, Size: 2390 bytes --]
(cc: lkml)
David Hinds wrote:
> On Mon, Nov 06, 2000 at 01:10:24AM -0800, David Ford wrote:
> > :(
> >
> > Ok. Here's the story. 2.3/2.4 kernel pcmcia gave up the ghost on my
> > socket controller several versions back. It is unable to assign an irq.
>
> PCMCIA in 2.4 (whether you build the modules in the kernel, or build
> the modules in the standalone package) is completely dependent on the
> kernel PCI layer to assign PCI interrupts (I assume that's what you
> mean by "an irq"? without system log messages I can't be sure).
> There has been no change in this in recent months; there may have been
> changes in the PCI layer that broke your setup.
>
> > What changed in the last ~two weeks? I notice that the current snapshot
> > also loads pci fixup.
>
> I don't understand the second sentence. Please explain.
Undoubtedly :( But it used to work when I used your i82365 module instead of
the kernel's yenta module. The i82365 module now gives the same failure
output as the yenta module.
I modprobed the following to get things up and running, (all your pkg)
pcmcia_core, i82365, and ds. Then ran cardmgr. All was well. Now when I
load i82365, it yields the pci irq failure and the irq type is changed.
2nd sentc: What changed in the last two-three weeks? I notice that the
current pcmcia (yours) code loads a new module called pci_fixup.
The dmesg output from loading i82365 is:
Intel PCIC probe: <4>PCI: No IRQ known for interrupt pin A of device 00:03.0.
PCI: No IRQ known for interrupt pin B of device 00:03.1.
Ricoh RL5C478 rev 03 PCI-to-CardBus at slot 00:03, mem 0x10000000
host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1] [no pci irq] [lat
168/176] [bus 2/5]
host opts [1]: [serial irq] [io 3/6/1] [mem 3/6/1] [no pci irq] [lat
168/176] [bus 6/9]
ISA irqs (default) = 3,4,7,11 polling interval = 1000 ms
Previous output was:
Ricoh RL5C478 rev 03 PCI-to-CardBus at slot 00:03, mem 0x10000000
host opts [0]: [serial irq] [io 3/6/1] [mem 3/6/1] [no pci irq] [lat
168/176] [bus 2/5]
host opts [1]: [serial irq] [io 3/6/1] [mem 3/6/1] [no pci irq] [lat
168/176] [bus 6/9]
ISA irqs (default) = 3,4,7,11 polling interval = 1000 ms
Notice the change from serial irq to isa irq.
-d
--
"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken was 'involved' - the pig was
'committed'."
[-- Attachment #2: Card for David Ford --]
[-- Type: text/x-vcard, Size: 176 bytes --]
begin:vcard
n:Ford;David
x-mozilla-html:TRUE
adr:;;;;;;
version:2.1
email;internet:david@kalifornia.com
title:Blue Labs Developer
x-mozilla-cpt:;14688
fn:David Ford
end:vcard
next parent reply other threads:[~2000-11-06 23:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3A06757F.3C63F1A8@linux.com>
[not found] ` <20001106104927.A19573@valinux.com>
2000-11-06 23:19 ` David Ford [this message]
2000-11-06 23:40 ` current snapshots of pcmcia David Hinds
2000-11-06 23:45 ` Jeff V. Merkey
2000-11-06 23:54 ` David Hinds
2000-11-07 0:16 ` Jeff V. Merkey
2000-11-07 0:19 ` David Ford
2000-11-07 0:31 ` David Hinds
2000-11-07 0:39 ` David Ford
2000-11-08 20:21 ` PCMCIA versioning Simon Huggins
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=3A073C8D.B6511746@linux.com \
--to=david@linux.com \
--cc=dhinds@valinux.com \
--cc=linux-kernel@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