linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frank_rowand@mvista.com>
To: Benjamin Herrenschmidt <bh40@calva.net>
Cc: mgreer@mvista.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: Early PCI auto-configuration
Date: Thu, 26 Oct 2000 20:01:32 -0700	[thread overview]
Message-ID: <39F8F00C.C6DF5AF4@mvista.com> (raw)
In-Reply-To: 19340920165843.29028@192.168.1.10


Benjamin Herrenschmidt wrote:
>
> >
> >[The discussion below is based on the latest fsmlabs 5005 repository
> >code]
>
> You mean linuxppc_2_5, I guess ?
>
> >My problem:  The firmware on a couple platform I need to support do
> >absolutely _no_ PCI device initialization.

< stuff deleted >

> You may also want to look at pci_assign_unassigned_resources() (in
> drivers/pci/setup-res.c) and friends. They do things a bit differently,
> but it might match more closely what you want.

Note that pci_assign_unassigned_resources() gets called by the Alpha, MIPS,
and ARM kernels for this purpose, if I understand correctly...


--
Frank Rowand <frank_rowand@mvista.com>
MontaVista Software, Inc

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

  parent reply	other threads:[~2000-10-27  3:01 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 [this message]
2000-10-27 17:24   ` Geert Uytterhoeven
2000-10-27 19:06     ` Mark A. Greer
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=39F8F00C.C6DF5AF4@mvista.com \
    --to=frank_rowand@mvista.com \
    --cc=bh40@calva.net \
    --cc=frowand@mvista.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mgreer@mvista.com \
    /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;
as well as URLs for NNTP newsgroup(s).