public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 8/9] mpc8641: Change 32-bit memory map
Date: Thu, 06 Nov 2008 16:16:22 -0600	[thread overview]
Message-ID: <49136CB6.3000309@freescale.com> (raw)
In-Reply-To: <2AC2C69E-E99C-45E4-9485-7BDEDC263BDA@freescale.com>

Becky Bruce wrote:
> We *do* need a comment in the release notes for this revision of u-boot 
> that the map for 8641 has changed so it doesn't catch anyone by surprise.

How about a runtime check in the board fdt code to print a warning if it 
finds an old device tree?  Unfortunately, using new dts with old u-boot 
isn't as easy to detect.

-Scott

  reply	other threads:[~2008-11-06 22:16 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-05 20:55 [U-Boot] [PATCH 0/9] MPC8641 memory map changes/cleanup/36-bit Becky Bruce
2008-11-05 20:55 ` [U-Boot] [PATCH 1/9] mpc8641: Remove extra "0" from BR2 define Becky Bruce
2008-11-05 20:55   ` [U-Boot] [PATCH 2/9] mpc86xx: Move setup_bats into cpu_init_f Becky Bruce
2008-11-05 20:55     ` [U-Boot] [PATCH 3/9] mpc8641: only define CONFIG_ENV_SIZE once Becky Bruce
2008-11-05 20:55       ` [U-Boot] [PATCH 4/9] mpc8641: Drop imaginary second flash bank, map 8MB Becky Bruce
2008-11-05 20:55         ` [U-Boot] [PATCH 5/9] mpc8641: make DIAG_ADDR == FLASH_BASE Becky Bruce
2008-11-05 20:55           ` [U-Boot] [PATCH 6/9] mpc86xx: Use SRR0/1/rfi to enable address translation, not blr Becky Bruce
2008-11-05 20:55             ` [U-Boot] [PATCH 7/9] mpc86xx: Change early FLASH mapping to 1M at CONFIG_MONITOR_BASE_EARLY Becky Bruce
2008-11-05 20:55               ` [U-Boot] [PATCH 8/9] mpc8641: Change 32-bit memory map Becky Bruce
2008-11-05 20:55                 ` [U-Boot] [PATCH 9/9] mpc8641: Support 36-bit physical addressing Becky Bruce
2008-11-05 21:42                   ` Kumar Gala
2008-11-06 19:04                     ` [U-Boot] [PATCH] toplevel Makefile: Add MPC8641HPCN_36BIT target Becky Bruce
2008-11-06 21:06                       ` Scott Wood
2008-11-06 21:40                         ` Becky Bruce
2008-11-06 21:59                           ` Scott Wood
2008-11-06 22:07                             ` Becky Bruce
2008-11-06 23:37                   ` [U-Boot] [PATCH 9/9 V2] mpc8641: Support 36-bit physical addressing Becky Bruce
2008-11-06 19:28                 ` [U-Boot] [PATCH 8/9] mpc8641: Change 32-bit memory map Scott Wood
2008-11-06 22:12                   ` Becky Bruce
2008-11-06 22:16                     ` Scott Wood [this message]
2008-11-06 22:24                       ` Becky Bruce
2008-11-06 22:26                         ` Scott Wood
2008-11-07 19:45                           ` [U-Boot] [PATCH] mpc8641: Try to detect old .dts files Becky Bruce
2008-11-10 22:58                             ` Scott Wood
2008-11-10 23:09                               ` Becky Bruce
2008-11-06 22:30                       ` [U-Boot] [PATCH 8/9] mpc8641: Change 32-bit memory map Jon Loeliger
2008-11-06 22:39                         ` Becky Bruce
2008-11-06 23:36                           ` [U-Boot] [PATCH 8/9 V2] " Becky Bruce
2008-11-06 20:04                 ` [U-Boot] [PATCH 8/9] " Jon Loeliger
2008-11-06 22:14                   ` Becky Bruce
2008-11-06 23:41                   ` Becky Bruce

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=49136CB6.3000309@freescale.com \
    --to=scottwood@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