From: "Laurent Lagrange" <lagrange@fr.oleane.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: Questions about PCI resources in Linux 2.4.25 for MPC8260
Date: Thu, 25 Nov 2004 10:59:28 +0100 [thread overview]
Message-ID: <000001c4d2d5$758dc9b0$5201a8c0@GEG2400> (raw)
Hi,
I ported a MPC8260 custom LSP from Linux 2.4.18 to Linux 2.4.25 and
I discovered something strange in the last kernel.
In the file arch/ppc/kernel/setup.c, the function "setup_arch" runs this new
code :
code_resource.start = virt_to_bus((void *)PAGE_OFFSET);
code_resource.end = virt_to_bus(&_etext)-1;
data_resource.start = virt_to_bus(&_etext);
data_resource.end = virt_to_bus(&_edata)-1;
request_resource(&iomem_resource, &code_resource);
request_resource(&iomem_resource, &data_resource);
This code seems to reserve PCI resources for the kernel code and data.
Has anybody an idea why these resources are added and needed ?
To detect future PCI conflicts ? To preserve from external PCI accesses ?
If the board sdram is not mapped on PCI at 0x00000000, these resources
generate problems when scanning pci bus and discovering sdram space
in own pci bridge header space.
Is there a new rule to set sdram board to 0x00000000 instead of 0x80000000
while enumerating PCI.
Thanks for your ideas.
Laurent
reply other threads:[~2004-11-25 20:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000001c4d2d5$758dc9b0$5201a8c0@GEG2400' \
--to=lagrange@fr.oleane.com \
--cc=linuxppc-embedded@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox