From: Greg KH <greg@kroah.com>
To: Marty Leisner <leisner@rochester.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_HOTPLUG, 2.4.x and ppc
Date: Thu, 26 May 2005 15:06:21 -0700 [thread overview]
Message-ID: <20050526220621.GD19628@kroah.com> (raw)
In-Reply-To: <200505250523.j4P5N5Xo012122@hp.home>
On Wed, May 25, 2005 at 01:23:04AM -0400, Marty Leisner wrote:
> Its a custom chip with bridge functionality...(its not hotplug,
> but the thought was "if hotplug can add a bridge at a later time,
> so can an arbitrary module". There's a number of minor problems
> in how BRIDGE_OTHER is handled (i.e. the first two bars should
> be filled in like any other bridge, but everything else ignored).
>
> The goal is to add a PCI bus behind the bridge (the bios
> and the kernel doesn't know about it).
>
> So I'm executing the sequence to add a new bus -- which
> needs CONFIG_HOTPLUG to export the symbols -- which causes the
> problem with PPC in the arch dependent part (it works fine
> on intel platforms).
>
> Looking at the hotplug drivers, it looks like its tied to
> intel architectures in places...but adding a PCI bus should be
> a PCI thing...
Yes it should be a pci thing, but for 2.4, a lot of the codepaths have
not been checked to see that they are all proper for a non-intel based
system. Your finding is one such proof :)
thanks,
greg k-h
prev parent reply other threads:[~2005-05-26 22:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 2:41 CONFIG_HOTPLUG, 2.4.x and ppc Marty Leisner
2005-05-25 4:26 ` Greg KH
2005-05-25 5:23 ` Marty Leisner
2005-05-26 22:06 ` Greg KH [this message]
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=20050526220621.GD19628@kroah.com \
--to=greg@kroah.com \
--cc=leisner@rochester.rr.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