From: David Brownell <david-b@pacbell.net>
To: Miles Lane <miles@megapathdsl.net>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Andrew Morton <andrewm@uow.edu.au>,
linux-kernel@vger.kernel.org
Subject: Re: Prerelease kernel will not hotplug a USB host-controller when itisinserted into a Cardbus slot.
Date: Wed, 03 Jan 2001 18:25:56 -0800 [thread overview]
Message-ID: <047301c075f5$ac01a480$6600000a@brownell.org> (raw)
In-Reply-To: <3A53187B.9030601@megapathdsl.net> <032e01c07595$7be8b8c0$6600000a@brownell.org> <3A53C8AA.8060103@megapathdsl.net>
Hi Miles,
> The whole
> "Bad PCI invocation" error was a red herring, sorry.
Not an endangered species ... even if Tux does like to
snack on them! :-)
> I have since gone in a tested test12-pre5, test12-pre6 and
> test12-pre8. test12-pre5 works. test12-pre6 fails utterly.
That's for "Cardbus hotplug". I've had USB hotplugging fine,
with the iffy bits being when it combines with the network
hotplugging ... those async changes seem to have created some
deadlocking paths (while removing some others).
> It looks like Cardbus was just completely hosed in that
> tree, because I can't get my network card (3c575) to be recognized
> by that kernel, either. I checked the patches and Andrew's
> "04X" change went into test12-pre8. I just tested test12-pre8
> with both your latest hotplug script, David, and with the
> pertinent "0x" locations changed to "04x". Both scripts fail
> to load usb-ohci.
The root cause seems to be the Cardbus/PCI hotplug invocation not
happening for you.
Was this with or without the "pcmcia_cs" package installed? My
own take on it is that 2.4 _should_ hotplug that controller
just fine if "pcmcia_cs" isn't installed. Otherwise, I'd be
pleasantly surprised to know it works properly.
> For the Cardbus hotplug event, is it expected that the hotplug
> debug info would be dumped after the insert event is processed
> and the required driver is loaded?
No -- you were seeing the USB hotplug event, not the cardbus one.
Plugging a cardbus OHCI into your machine should cause two hotplug
events ... first for PCI, eventually modprobing "usb-ohci", and
then as that module initializes you'll get a second one for USB,
reporting a new (root) hub.
So you should see an invocation "arguments (pci) env (...)"
followed by "arguments (usb) env (...)"; but you reported the
second one.
- Dave
-
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:[~2001-01-04 2:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 12:18 Prerelease kernel will not hotplug a USB host-controller when it is inserted into a Cardbus slot Miles Lane
2001-01-03 12:40 ` Andrew Morton
2001-01-03 14:57 ` Prerelease kernel will not hotplug a USB host-controller when it isinserted " David Brownell
2001-01-04 0:49 ` Miles Lane
2001-01-04 1:43 ` Miles Lane
2001-01-04 1:48 ` Miles Lane
2001-01-04 2:25 ` David Brownell [this message]
2001-01-04 5:49 ` Prerelease kernel will not hotplug a USB host-controller when it is inserted " Miles Lane
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='047301c075f5$ac01a480$6600000a@brownell.org' \
--to=david-b@pacbell.net \
--cc=andrewm@uow.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@megapathdsl.net \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox