From: David Ford <david@linux.com>
To: David Hinds <dhinds@valinux.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: current snapshots of pcmcia
Date: Mon, 06 Nov 2000 16:39:43 -0800 [thread overview]
Message-ID: <3A074F4F.DACD7ABA@linux.com> (raw)
In-Reply-To: <3A06757F.3C63F1A8@linux.com> <20001106104927.A19573@valinux.com> <3A073C8D.B6511746@linux.com> <20001106154039.A19860@valinux.com> <3A074AAC.1F88DB3@linux.com> <20001106163154.A20457@valinux.com>
[-- Attachment #1: Type: text/plain, Size: 519 bytes --]
David Hinds wrote:
> Incidentally, the i82365 module should work ok (using ISA interrupts)
> despite the "No IRQ known" messages. The Yenta driver won't work at
> all if PCI interrupts aren't set up. So I guess another question
> would be, what card(s) are you using and how are they misbehaving?
I'm using tulip based cards and a linksys PC 10/100 + 56K mdm.
-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 prev parent reply other threads:[~2000-11-07 0:40 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 ` current snapshots of pcmcia David Ford
2000-11-06 23:40 ` 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 [this message]
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=3A074F4F.DACD7ABA@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