From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: multiple devices behind a cardbus bridge (adding magma pci extender support)
Date: Thu, 04 Oct 2001 15:24:05 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100220947519123@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100215517923775@msgid-missing>
On Wed, Oct 03, 2001 at 09:18:54PM -0700, David Hinds wrote:
> On Wed, Oct 03, 2001 at 06:10:42PM -0700, David Brownell wrote:
> >
> > Is the root problem that drivers/pcmcia/cardbus.c
> > doesn't set up bridge devices when they're connected
> > to the Cardbus bridge?
>
> This is it. The cardbus code will configure a single normal device on
> the far side of the cardbus bridge, not (potentially) a whole tree of
> things. It is similar to the hot plug PCI situation.
But for hotplug PCI, you need a hotplug pci controller that handles the
initialization of that pci tree (among other things). For this device,
does it have a controller that can be addressed to do these things?
thanks,
greg k-h
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-10-04 15:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-04 0:24 multiple devices behind a cardbus bridge (adding magma pci extender support) Mark Krischer
2001-10-04 1:10 ` multiple devices behind a cardbus bridge (adding magma pci David Brownell
2001-10-04 2:55 ` multiple devices behind a cardbus bridge (adding magma pci extender support) Mark Krischer
2001-10-04 4:18 ` David Hinds
2001-10-04 15:24 ` Greg KH [this message]
2001-10-04 15:37 ` David Hinds
2001-10-04 15:45 ` Greg KH
2001-10-04 17:40 ` multiple devices behind a cardbus bridge (adding magma pci David Brownell
2001-10-05 3:55 ` multiple devices behind a cardbus bridge (adding magma pci extender support) David Hinds
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=marc-linux-hotplug-100220947519123@msgid-missing \
--to=greg@kroah.com \
--cc=linux-hotplug@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 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.