From: Tolunay Orkun <listmember@orkun.us>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PCI MEM I/O space allocation
Date: Sat, 13 Jan 2007 03:41:20 -0600 [thread overview]
Message-ID: <45A8A940.70107@orkun.us> (raw)
In-Reply-To: <1168361614.2903.24.camel@localhost.localdomain>
York Sun wrote:
>>>> What exactly is the problem you're trying to fix? The fact that it's
>>>> different is IMHO not enough of a reason to change it.
>>>>
>>> The problem is some bridges have 64K limitation on I/O space, which
>>> requires special care in allocation. I am fixing it in the kernel.
>>>
May I remined that U-Boot is not solely booting Linux kernel while Linux
is probably the most popular one. How will such change affect other OS
booting?
Tolunay
next prev parent reply other threads:[~2007-01-13 9:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-27 19:07 [U-Boot-Users] [PATCH] Fix PCI I/O space mapping on Freescale MPC85x0ADS Sergei Shtylyov
2007-01-08 21:40 ` [U-Boot-Users] PCI MEM I/O space allocation York Sun
2007-01-08 23:04 ` Wolfgang Denk
2007-01-08 23:08 ` York Sun
2007-01-09 0:55 ` Wolfgang Denk
2007-01-09 15:16 ` York Sun
2007-01-09 15:48 ` Wolfgang Denk
2007-01-09 16:06 ` York Sun
2007-01-09 16:39 ` Wolfgang Denk
2007-01-09 16:53 ` York Sun
2007-01-13 9:41 ` Tolunay Orkun [this message]
2007-01-09 16:55 ` Timur Tabi
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=45A8A940.70107@orkun.us \
--to=listmember@orkun.us \
--cc=u-boot@lists.denx.de \
/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