From: David Woodhouse <dwmw2@infradead.org>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Russell King <rmk@arm.linux.org.uk>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
David Hinds <dhinds@valinux.com>,
tytso@valinux.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pcmcia event thread. (fwd)
Date: Fri, 17 Nov 2000 16:43:49 +0000 [thread overview]
Message-ID: <5997.974479429@redhat.com> (raw)
In-Reply-To: <3A155F6A.28783D4A@mandrakesoft.com>
In-Reply-To: <3A155F6A.28783D4A@mandrakesoft.com> <Pine.LNX.4.10.10011170814440.2272-100000@penguin.transmeta.com> <5178.974478881@redhat.com>
jgarzik@mandrakesoft.com said:
> For these two, it sounds to me like you need to be doing a PCI probe,
> and getting the irq and I/O port info from pci_dev. And calling
> pci_enable_device, which may or may not be a showstopper here...
Yep. The same code is already present in David Hinds' i82365.c, but appears
to have been stripped out when CardBus sockets started to be supported
elsewhere.
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-17 17:14 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-13 13:08 [PATCH] pcmcia event thread. (fwd) David Woodhouse
2000-11-13 13:48 ` Jeff Garzik
2000-11-16 13:28 ` Alan Cox
2000-11-13 14:37 ` David Woodhouse
2000-11-13 15:04 ` Jeff Garzik
2000-11-13 15:14 ` David Woodhouse
2000-11-13 15:33 ` Jeff Garzik
2000-11-16 13:39 ` Alan Cox
2000-11-16 14:14 ` David Woodhouse
2000-11-16 16:28 ` Tobias Ringstrom
2000-11-18 11:24 ` Pavel Machek
2000-11-13 15:42 ` David Woodhouse
2000-11-13 18:59 ` David Hinds
2000-11-13 21:52 ` David Woodhouse
2000-11-13 21:57 ` David Hinds
2000-11-13 22:30 ` David Woodhouse
2000-11-13 22:47 ` Jeff Garzik
2000-01-01 2:54 ` Pavel Machek
2000-11-16 21:26 ` tytso
2000-11-16 21:42 ` David Hinds
2000-11-13 23:04 ` David Woodhouse
2000-11-16 16:08 ` Alan Cox
2000-11-16 16:15 ` Jeff Garzik
2000-11-16 16:20 ` Alan Cox
2000-11-17 0:51 ` Russell King
2000-11-17 10:54 ` Alan Cox
2000-11-17 16:21 ` Linus Torvalds
2000-11-17 16:29 ` Alan Cox
2000-11-17 16:35 ` Linus Torvalds
2000-11-17 16:39 ` Alan Cox
2000-11-17 16:34 ` Russell King
2000-11-17 16:17 ` Linus Torvalds
2000-11-17 16:34 ` David Woodhouse
2000-11-17 16:40 ` Jeff Garzik
2000-11-17 16:47 ` Linus Torvalds
2000-11-17 16:49 ` David Woodhouse
2000-11-17 20:01 ` David Hinds
2000-11-17 16:43 ` David Woodhouse [this message]
2000-11-17 20:30 ` 2.4's internal PCMCIA works for me (was Re: [PATCH] pcmcia event thread) Barry K. Nathan
2000-11-17 21:07 ` David Hinds
2000-11-18 9:55 ` [PATCH] pcmcia event thread. (fwd) David Ford
2000-11-18 16:03 ` Linus Torvalds
2000-11-18 22:16 ` David Hinds
2000-11-19 5:32 ` David Ford
2000-11-19 5:36 ` Linus Torvalds
2000-11-19 6:30 ` [FIXED!] " David Ford
2000-11-19 7:03 ` neighbour table? Andrew Park
2000-11-19 6:57 ` David Ford
2000-11-19 7:45 ` Eric W. Biederman
2000-11-19 10:40 ` David Ford
2000-11-16 13:40 ` [PATCH] pcmcia event thread. (fwd) Alan Cox
2000-11-15 0:01 ` Russell King
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=5997.974479429@redhat.com \
--to=dwmw2@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dhinds@valinux.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=torvalds@transmeta.com \
--cc=tytso@valinux.com \
/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.