From: "Mark A. Greer" <mgreer@mvista•com>
To: Dan Malek <dan@mvista•com>
Cc: linuxppc-dev@lists•linuxppc.org
Subject: Re: Sandpoint added to 2_5 tree
Date: Thu, 08 Mar 2001 11:12:00 -0700 [thread overview]
Message-ID: <3AA7CB70.DCF55576@mvista.com> (raw)
In-Reply-To: 3AA6F769.E9EE5931@mvista.com
Dan Malek wrote:
> "Mark A. Greer" wrote:
> >
> > For those of you with sandpoints, there has been sandpoint support
> > pushed out into the 2_5 tree. It requires the patch at:
> > ftp://ftp.mvista.com/pub/Area51/sandpoint/sp_patch_2_5
>
> This is a "don't touch yourself", right? Shouldn't this be generally
> useful (or required)? Why don't other architectures have this
> problem and can we create a generic solution (i.e. we shouldn't have
> to hard-code the device number)?
Yes, its the "don't touch yourself" problem with 824x & 107 bridges.
Most boards don't have the IDSEL wired up so its not an issue for them.
I expect more & more people to start wiring it up, though, so I think it
will become more of an issue.
Yes, there should be some general feature for skipping PCI slots, it
just doesn't exist yet. There are 2 places that this skip needs to be
put in, drivers/pci/pci.c and arch/ppc/kerner/pci_auto.c. I chose to
make a patch instead of cluttering up those files (plus the
drivers/pci/pci.c #ifdef would probably never be accepted into
kernel.org).
Matt Porter has a scheme for doing the skipping (plus other stuff), he
just hasn't had the time to do it yet.
Mark
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-03-08 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-06 0:03 Sandpoint added to 2_5 tree Mark A. Greer
2001-03-08 3:07 ` Dan Malek
2001-03-08 10:51 ` Matt Porter
2001-03-08 18:12 ` Mark A. Greer [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=3AA7CB70.DCF55576@mvista.com \
--to=mgreer@mvista$(echo .)com \
--cc=dan@mvista$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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