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 09:16:04 -0600 [thread overview]
Message-ID: <1168355764.2903.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20070109005507.99232353C3A@atlas.denx.de>
On Tue, 2007-01-09 at 01:55 +0100, Wolfgang Denk wrote:
> In message <1168297700.2883.18.camel@localhost.localdomain> you wrote:
> >
> > I am trying to fix the resource allocation bugs, but found things
> > unexpected. I want to know if there is particular reason to allocate
> > from bottom up. If not, I would change it back to kernel's way.
>
> What do you mean by "change it back"?
To allocate resources from the top.
> When has this been changed before?
There isn't one. I mean back to kernel's way. Why should U-boot use
different way from kernel to allocate resources since most PCI parts are
similar (equivalent) to kernel?
>
> You are aware that you will cause LOT of regression testings with
> such a change?
Yes, I know. Hopefully not too much. This change will only change the
allocation direction. Once U-boot has same algorithm with kernel, it is
easier to maintain in the future.
Regards,
York
next prev parent reply other threads:[~2007-01-09 15:16 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 [this message]
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
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=1168355764.2903.10.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