public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed

From: "Mark A. Greer" <mgreer@mvista•com>
To: Geert Uytterhoeven <geert@linux-m68k•org>
Cc: Benjamin Herrenschmidt <bh40@calva•net>, linuxppc-dev@lists•linuxppc.org
Subject: Re: Early PCI auto-configuration
Date: Fri, 27 Oct 2000 12:06:19 -0700	[thread overview]
Message-ID: <39F9D22B.23BDE8E9@mvista.com> (raw)
In-Reply-To: Pine.LNX.4.10.10010271921050.390-100000@cassiopeia.home


Geert Uytterhoeven wrote:

> <cut>
>
> > cards, the pcibios_assign_resources() function will assign bases
> > addresses to unassigned devices. This is done by the call to
> > pcibios_assign_resources(), and works if your bus resources & ranges have
> > been setup properly.
>
> Yep. If you set up the bus resources correctly, that code will assign all
> unassigned resources automatically (and reassign conflicting resources) from
> the ranges specified by the bus resources.
>
> BTW, before I did this on PPC, I played with PCI resource assignment on a MIPS
> board, where the firmware didn't do any PCI assignments (except for Ethernet,
> to boot images using TFTP), which is exactly what you want. For reference, that
> code is in arch/mips/ddb5074/pci.c.

Geert, Ben, Matt,

Thanks for the feedback.  I've looked through much of the code you guys pointed
out and it does look like it will do what I want.  I'll hook it up and see how it
goes.

Mark


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

next prev parent reply	other threads:[~2000-10-27 19:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-26 22:46 Early PCI auto-configuration Mark A. Greer
2000-10-26 23:26 ` Benjamin Herrenschmidt
2000-10-27  2:23   ` Matt Porter
2000-10-27  3:01   ` Frank Rowand
2000-10-27 17:24   ` Geert Uytterhoeven
2000-10-27 19:06     ` Mark A. Greer [this message]
2000-11-16 23:05     ` header file location Frank Rowand
2000-11-17  6:52       ` 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=39F9D22B.23BDE8E9@mvista.com \
    --to=mgreer@mvista$(echo .)com \
    --cc=bh40@calva$(echo .)net \
    --cc=geert@linux-m68k$(echo .)org \
    --cc=linuxppc-dev@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox