From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PCI MEM I/O space allocation
Date: Tue, 09 Jan 2007 10:53:34 -0600 [thread overview]
Message-ID: <1168361614.2903.24.camel@localhost.localdomain> (raw)
In-Reply-To: <20070109163921.0D57B352B26@atlas.denx.de>
On Tue, 2007-01-09 at 17:39 +0100, Wolfgang Denk wrote:
> In message <1168358761.2903.19.camel@localhost.localdomain> you wrote:
> >
> > > I wouldn't do this lightly...
> >
> > All right. I will do it in my branch and not to submit patch for this.
>
> This is definitely not the result I wanted to acchieve :-(
My first attempt was to find out if there was a particular reason to
allocate from bottom up. If changing it causes too much trouble, we can
keep it there until really necessary.
>
> > > 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.
>
> Maybe we can make this optional, so we can leave unaffected systems
> untouched, and/or give board maintainers time for a slower migration?
We can leave it untouched until all the fixing is done. We will decide
from there.
Regards,
York
next prev parent reply other threads:[~2007-01-09 16:53 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 [this message]
2007-01-13 9:41 ` Tolunay Orkun
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=1168361614.2903.24.camel@localhost.localdomain \
--to=yorksun@freescale.com \
--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