All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	<linuxppc-dev@lists.linuxppc.org>
Subject: Re: PReP and generic PCI resource assignment
Date: Fri, 10 Aug 2001 11:56:59 +0200	[thread overview]
Message-ID: <20010810095659.6588@smtp.adsl.oleane.com> (raw)
In-Reply-To: <Pine.LNX.4.05.10108101034110.2083-100000@callisto.of.borg>


>You should initialize the parent pointers in the PCI bus structure with
>pointers to resources containing the correct region.
>
>I once hardcoded the parents for the LongTrail, but that code is gone. Now it
>tries to set up the parents from information in the OF device, which works
>more or less. There are (or were, read as in `were the last time I tried
it, a
>few months ago) still some problems, though. One of them is that the
hardcoded
>ISA motherboard resources (i8259 and legacy stuff) are requested before PCI
>resources are done, and that the PCI bus parent resources were not requested
>and thus don't appear in the full resource tree.

Parent pointer should be set properly nowadays on bk _2_4_devel at least.

However, the generic PCI code still wants to add that PCIBIOS_MIN_MEM
value when assigning resources, I bet we should probably #define that
to 0 on PPC.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-08-10  9:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-08  5:11 PReP and generic PCI resource assignment Hollis
2001-08-08  5:43 ` ashish anand
2001-08-08 12:23   ` Benjamin Herrenschmidt
2001-08-08 10:27 ` Benjamin Herrenschmidt
2001-08-09  1:34   ` Hollis
2001-08-09 10:18     ` Benjamin Herrenschmidt
2001-08-09 16:14       ` Matt Porter
2001-08-10  8:38         ` Geert Uytterhoeven
2001-08-10  9:56           ` Benjamin Herrenschmidt [this message]
2001-08-10 10:51             ` Geert Uytterhoeven
2001-08-10 19:34           ` Hollis Blanchard
2001-08-11 17:43             ` Geert Uytterhoeven

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=20010810095659.6588@smtp.adsl.oleane.com \
    --to=benh@kernel.crashing.org \
    --cc=geert@linux-m68k.org \
    --cc=linuxppc-dev@lists.linuxppc.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.