From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Please pull u-boot-83xx.git
Date: Mon, 27 Nov 2006 10:41:39 -0600 [thread overview]
Message-ID: <456B1543.2040006@freescale.com> (raw)
In-Reply-To: <20061126200244.5E849353C30@atlas.denx.de>
Wolfgang Denk wrote:
> In message <200611261446.24607.sr@denx.de> you wrote:
>>> mpc83xx: fix TQM build by defining a CFG_FLASH_SIZE for it
>>>
>>> -------------------------- include/configs/TQM834x.h --------------------------
>>> index b1f033d..f0e4900 100644
>>> @@ -95,6 +95,7 @@
>>> #define CFG_FLASH_CFI_DRIVER /* use the CFI driver */
>>> #undef CFG_FLASH_CHECKSUM
>>> #define CFG_FLASH_BASE 0x80000000 /* start of FLASH */
>>> +#define CFG_FLASH_SIZE 8 /* FLASH size in MB */
>> Do you only support sizes bigger or equal to 1 MByte? What if a board
>> only has 512kBytes?
>
> I object against such changes which have not been discussed with
> the maintainer of the board, and most probably have not been tested
> either.
>
> TQ has a pretty long list of configuration options for their modules,
> and the change above will probably break quite a few, or most.
The above change is necessary to make the board compatible with the flash-size
code in mpc83xx/start.S:
/* Store 0x80000012 + log2(CFG_FLASH_SIZE) into LBLAWAR1 */
lis r4, (0x80000012)@h
ori r4, r4, (0x80000012)@l
li r5, CFG_FLASH_SIZE
1: srawi. r5, r5, 1 /* r5 = r5 >> 1 */
addi r4, r4, 1
bne 1b
Previously, this code just assumed that flash was 8MB. However, the 8349ITX has
16MB of flash. Rather than have #ifdefs in start.S, this code was changed to
calculate the correct value for LBLAWAR1 based on CFG_FLASH_SIZE.
I believe that this code is the most elegant solution to the problem, however it
does require that each board header file define a value for CFG_FLASH_SIZE. The
alternative would be to add these lines above the new code:
#ifndef CFG_FLASH_SIZE
#define CFG_FLASH_SIZE 8
#endif
If you prefer that we use this approach, then we can make that change. However,
I think our approach makes more sense.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2006-11-27 16:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-04 2:11 [U-Boot-Users] Please pull u-boot-83xx.git Kim Phillips
2006-11-16 23:55 ` Joakim Tjernlund
2006-11-26 13:46 ` Stefan Roese
2006-11-26 20:02 ` Wolfgang Denk
2006-11-27 16:41 ` Timur Tabi [this message]
2006-11-27 21:10 ` Wolfgang Denk
2006-11-27 21:26 ` Timur Tabi
2006-11-27 21:36 ` Wolfgang Denk
2006-11-27 21:48 ` Timur Tabi
2006-11-27 21:53 ` Wolfgang Denk
2006-11-27 21:55 ` Timur Tabi
2006-11-27 22:56 ` Wolfgang Denk
2006-11-28 0:25 ` Dan Malek
2006-11-28 15:18 ` Timur Tabi
2006-11-27 16:55 ` Timur Tabi
2006-11-27 22:45 ` Timur Tabi
2006-11-27 22:59 ` Wolfgang Denk
2006-11-29 7:18 ` Kim Phillips
2006-11-30 17:07 ` Wolfgang Denk
2006-11-30 17:49 ` Kim Phillips
2006-11-30 18:13 ` Timur Tabi
2006-11-30 21:14 ` [U-Boot-Users] ERROR: Cannot determine a common read delay k b
2006-12-02 12:02 ` Stefan Roese
2006-11-30 23:09 ` [U-Boot-Users] Please pull u-boot-83xx.git Wolfgang Denk
2006-11-26 13:49 ` [U-Boot-Users] Please pull u-boot-83xx.git (I2C rework) Stefan Roese
2006-11-27 2:45 ` Ben Warren
2006-11-27 6:22 ` Stefan Roese
2006-11-27 17:28 ` Timur Tabi
-- strict thread matches above, loose matches on Subject: below --
2008-01-29 18:10 [U-Boot-Users] Please pull u-boot-83xx.git Kim Phillips
2008-02-11 23:57 ` Wolfgang Denk
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=456B1543.2040006@freescale.com \
--to=timur@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