From: Andrew May <acmay@acmay•homeip.net>
To: Matt Porter <porter@cox•net>, linuxppc-embedded@lists•linuxppc.org
Subject: Re: very minor 405GP and 405GPr PCI difference
Date: Fri, 11 Oct 2002 12:37:20 -0700 [thread overview]
Message-ID: <20021011193720.GA9039@acmay.homeip.net> (raw)
In-Reply-To: <20021009015828.GO32555@zax>
Sorry about the late reply but I wanted to check the 2.5 tree and I haven't
been looking at it before.
On Wed, Oct 09, 2002 at 11:58:28AM +1000, David Gibson wrote:
>
> On Mon, Oct 07, 2002 at 10:21:36PM -0700, Andrew May wrote:
> >
> > A full featured bootloader like PPCboot will need to setup the PCI bus
> > to work with PCI devices, so it is not like it is always an extra burden
> > on the bootloader or useless work.
>
> That's all very well if you've got PPCboot, but lots of boards have
> firmware which is, lets face it, shite. The kernel has to be able to
> deal with this case. And since it has to deal with it for the case of
> crappy firmware, is there any point turning it off for the case of
> decent firmware?
Yes there is a point. I am working on a new custum PCI device and the
hardware guy gives me silly requests to try differnt PCI bus settings.
And I would much rather make the changes in my small quick PPCBoot build
rather than a full kernel build.
> > So I just want you to keep in mind the PCI bus fixup can be a config
> > option that can be built out if desired. It really shouldn't be tied
> > to the board itself, since it is also common to load in PPCboot into
> > Walnut boards.
>
> That's easy - in fact the patch I posted before allows this (it won't
> do anything if CONFIG_BIOS_FIXUP is not defined).
Well you patch is only part of the issue, it is the rest of
arch/ppc/kernel/4xx/ppc405_pci.c that gets pulled in every build with PCI,
that remapps everything in _find_bridges.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-10-11 19:37 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-27 12:27 very minor 405GP and 405GPr PCI difference Ralph Blach
2002-09-30 4:01 ` David Gibson
2002-10-01 5:21 ` David Gibson
2002-10-01 8:37 ` "David Müller (ELSOFT AG)"
2002-10-02 1:42 ` David Gibson
2002-10-02 4:26 ` Allen Curtis
2002-10-02 5:34 ` David Gibson
2002-10-02 17:03 ` Matt Porter
2002-10-03 1:10 ` David Gibson
2002-10-03 15:14 ` Matt Porter
2002-10-04 2:48 ` David Gibson
2002-10-04 18:33 ` Todd Poynor
2002-10-08 4:17 ` David Gibson
2002-10-08 19:39 ` Todd Poynor
2002-10-09 2:14 ` David Gibson
[not found] ` <20021 <20021023040850.GC1198@zax>
2002-10-24 23:50 ` Ralph Blach
2002-10-25 1:19 ` David Gibson
2002-10-02 7:46 ` "David Müller (ELSOFT AG)"
2002-10-03 1:12 ` David Gibson
2002-10-03 8:28 ` "David Müller (ELSOFT AG)"
2002-10-06 5:23 ` Andrew May
2002-10-07 1:31 ` Matt Porter
2002-10-08 4:14 ` David Gibson
2002-10-08 5:21 ` Andrew May
2002-10-08 14:56 ` Matt Porter
2002-10-08 17:31 ` Andrew May
2002-10-08 18:20 ` Matt Porter
2002-10-09 1:58 ` David Gibson
2002-10-09 10:35 ` Kenneth Johansson
2002-10-09 15:21 ` Allen Curtis
2002-10-11 19:37 ` Andrew May [this message]
2002-10-14 1:20 ` David Gibson
2002-10-08 6:19 ` Allen Curtis
2002-10-08 15:18 ` Matt Porter
2002-10-09 2:10 ` David Gibson
2002-10-22 21:55 ` Todd Poynor
2002-10-23 4:08 ` David Gibson
-- strict thread matches above, loose matches on Subject: below --
2002-10-23 13:10 Ralph Blach
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=20021011193720.GA9039@acmay.homeip.net \
--to=acmay@acmay$(echo .)homeip.net \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=porter@cox$(echo .)net \
/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