linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johnny Hung <johnny.hacking@gmail.com>
To: Marco Stornelli <marco.stornelli@gmail.com>,
	linux-embedded@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: PCI device support in Open Firmware (device tree syntax)
Date: Tue, 30 Jun 2009 15:33:11 +0800	[thread overview]
Message-ID: <cb9ecdfa0906300033x4dfcc315gfd67522b77f6004a@mail.gmail.com> (raw)
In-Reply-To: <2ea1731b0906292329t30cdc9a6q1fc36dc2273a2931@mail.gmail.com>

2009/6/30 Marco Stornelli <marco.stornelli@gmail.com>:
> 2009/6/30 Johnny Hung <johnny.hacking@gmail.com>:
>> Thanks for your reply. So there are no PCI device resource info in
>> flat device tree.
>> How do PCI device resources be assign in general case or is there any example?
>> I am so confusing, would you please give me detailed describle?
>>
>> BRs, H. Johnny
>>>
>
> You should look at your bootloader about the initial configuration of
> the pci device, in general it should (more or less) do the work of
> BIOS as you said. After that the kernel can probe them.
>
> Marco
>
You are right. u-boot do PCI device BAR resources assign and flat
device tree describe PCI device interrupt-map. I use "lspci -s xxx -x"
for the PCI device, the resources was assigned properly.
Thanks.

BRs, H. Johnny

  parent reply	other threads:[~2009-06-30  7:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29 15:58 PCI device support in Open Firmware (device tree syntax) Johnny Hung
2009-06-29 16:51 ` Scott Wood
2009-06-30  1:36   ` Johnny Hung
     [not found]     ` <2ea1731b0906292329t30cdc9a6q1fc36dc2273a2931@mail.gmail.com>
2009-06-30  7:33       ` Johnny Hung [this message]
2009-07-01 22:15         ` Benjamin Herrenschmidt
2009-06-30 15:32     ` Scott Wood

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=cb9ecdfa0906300033x4dfcc315gfd67522b77f6004a@mail.gmail.com \
    --to=johnny.hacking@gmail.com \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=marco.stornelli@gmail.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).