All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Updegraff <dave@cray.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: [PATCH] Make System IO Config Registers board configurable on MPC83xx
Date: Mon, 28 Nov 2005 08:47:01 -0600	[thread overview]
Message-ID: <438B1865.100@cray.com> (raw)
In-Reply-To: <20051127215106.847CA352616@atlas.denx.de>

Wolfgang.

That is very  convincing. So for the special case of setting RCW to boot 
from lowmem vector, all is well.  And I guess there is no great harm in 
that restriction.

When RCW set to boot from himem vector though, the 83xx maps in the 
_last_ 8M of the flash chip, not the first, so the remap_flash_by_law* 
routines end up mapping u-boot out from under us.  But OK; we just won't 
do that then.

I still stand by by compaint though: if you're going to remap flash 
according to CFG_FLASH_BASE in start.S,  then the 8M hardcoded size is 
annoying.

>>back to LAW0 on a builtin assumption of 8M size, placing the starting 
>>address thereof to the CFG_FLASH_BASE location (in their case, 
>>0xfe00_0000); then do jumping arithmetic based on that value and TEXT_BASE.
>>
>>Which works in the Freescale-ADS case, as they have an 8M flash chip.
> 
> 
> It also works in case of the TQM8349 board, which uses 32 MB:
> 
> U-Boot 1.1.4 (Nov 17 2005 - 00:14:36) MPC83XX
> 
> Clock configuration:
>   Coherent System Bus:  266 MHz
>   Core:                 533 MHz
>   Local Bus:             33 MHz
> CPU:   MPC83xx, Rev: 1.1 at 533.328 MHz
> Board: TQM834x
> PCI1:  32 bit, 33 MHz
> I2C:   ready
> DTT:   1 is 28 C
> DRAM:  256 MB
> FLASH: 32 MB
> PCI:   Bus Dev VenId DevId Class Int
> In:    serial
> Out:   serial
> Err:   serial
> Net:   TSEC0, TSEC1
> 
> Type "run flash_nfs" to mount root filesystem over NFS
> 
> Hit any key to stop autoboot:  0 
> => fli
> 
> Bank # 1: CFI conformant FLASH (32 x 16)  Size: 32 MB in 256 Sectors
>  Erase timeout 16384 ms, write timeout 0 ms, buffer write timeout 4096 ms, buffer size 32
>   Sector Start Addresses:
>     80000000 (RO) 80020000 (RO) 80040000 (RO) 80060000      80080000     
>     800A0000      800C0000      800E0000      80100000      80120000     
>     80140000      80160000      80180000      801A0000      801C0000     
> ...
> 
> Best regards,
> 
> Wolfgang Denk
> 

       reply	other threads:[~2005-11-28 14:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051127215106.847CA352616@atlas.denx.de>
2005-11-28 14:47 ` David Updegraff [this message]
2005-11-23 20:31 [U-Boot-Users] [PATCH] Make System IO Config Registers board configurable on MPC83xx Kumar Gala
2005-11-23 20:47 ` [U-Boot-Users] " David Updegraff
2005-11-25 20:10   ` Wolfgang Denk
2006-03-12 17:52 ` 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=438B1865.100@cray.com \
    --to=dave@cray.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.