public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Matt Sealey <matt@genesi-usa•com>
To: Becky Bruce <beckyb@kernel•crashing.org>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: [PATCH] powerpc: Update 8641hpcn dts file to match latest u-boot
Date: Tue, 30 Dec 2008 16:27:32 -0600	[thread overview]
Message-ID: <495AA054.7090903@genesi-usa.com> (raw)
In-Reply-To: <1229724312-20406-1-git-send-email-beckyb@kernel.crashing.org>

Becky Bruce wrote:
> The newest revision of uboot reworks the memory map for this
> board to look more like the 85xx boards.  Also, some regions
> which were far larger than the actual hardware have been scaled
> back to match the board, and the imaginary second flash bank has
> been removed. Rapidio and PCI are mutually exclusive in the hardware,
> and they now are occupying the same space in the address map.
> The Rapidio node is commented out of the .dts since PCI is the
> common use case.

Hi Becky,

What would be the "newest revision of U-Boot" that implements this 
memory map? We're entering into moving-target territory again here where 
we have no real idea which kernels are required or work or are even 
supported on which versions of the firmware.. and of course this device
tree committed to mainline means that the next set of kernel.org won't
have the right data to boot what could be a perfectly workable kernel
on previous U-Boot versions.

Isn't there any documentation on this apart from git changesets hidden 
behind obscure many-digit hashes?

--
Matt Sealey <matt@genesi-usa•com>

      parent reply	other threads:[~2008-12-30 22:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-19 22:05 [PATCH] powerpc: Update 8641hpcn dts file to match latest u-boot Becky Bruce
2008-12-21  3:27 ` Timur Tabi
2008-12-30 17:24   ` Kumar Gala
2008-12-30 17:27 ` Kumar Gala
2008-12-30 22:27 ` Matt Sealey [this message]

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=495AA054.7090903@genesi-usa.com \
    --to=matt@genesi-usa$(echo .)com \
    --cc=beckyb@kernel$(echo .)crashing.org \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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