linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sean MacLennan <smaclennan@pikatech.com>
To: LinuxPPC-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Could the DTS experts look at this?
Date: Sun, 10 Feb 2008 22:49:55 -0500	[thread overview]
Message-ID: <47AFC5E3.20101@pikatech.com> (raw)
In-Reply-To: <20080211031110.GD11572@localhost.localdomain>

David Gibson wrote:
> On Sun, Feb 10, 2008 at 09:40:19PM -0500, Sean MacLennan wrote:
>   
>> David Gibson wrote:
>>     
>>> This doesn't seem right.  warp_fixup_one_nor() changes only the
>>> partition's offset, so you're not changing the size of any
>>> partitions.  If you're not going to actually use any of the extra
>>> flash space with 64M, I can't see why you'd bother moving around the
>>> partitions you have.
>>>   
>>>       
>> u-boot must be at the bottom of the flash. Also, for the 64M NOR flash 
>> you can put everything in the NOR flash, I just don't show the 
>> partitions. Booting from NOR is *much* faster than  booting from
>> NAND.
>>     
>
> Sorry, still not really following what's going on.  Without worrying
> about the dts formatting or fixup code, can you summarise what the two
> flash maps look like?
>
>   
I guess what is confusing is that I am actually working with 3 flash 
maps right now, although there will only be one map in the final version.

Map1:

NOR:
  Kernel @ 0
  Ramdisk
  User
  FPGA
  Env
  U-boot @ 63.5M

Map 2:

NOR:
  FPGA
  Env
  U-boot @ 63.5M
NAND:
  Kernel @ 0
  Ramdisk
  User

Map 3:
  Same as Map 2 only 4M NOR rather than 64M, so u-boot @ 3.5M.


The u-boot, env, and FPGA are anchored at the bottom of the flash. 
Kernel is anchored at the top. Everything else goes in the middle.

The FPGA partition contains the FPGA image. The user partition contains 
a persistent JFFS2 file system. I don't use the user partition, so it 
doesn't show up in the map I sent.

So map 1 was used until we got the NAND working. Map 2 is an interim 
solution until we get the 4M flash. Map 3 is the final version.

Cheers,
   Sean

  reply	other threads:[~2008-02-11  3:49 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08 23:30 Could the DTS experts look at this? Sean MacLennan
2008-02-10  5:47 ` Arnd Bergmann
2008-02-10  6:05   ` Sean MacLennan
2008-02-11 17:57   ` Timur Tabi
2008-02-11 23:54     ` David Gibson
2008-02-11 23:56       ` David Gibson
2008-02-12  0:21         ` Arnd Bergmann
2008-02-12  0:36           ` David Gibson
2008-02-12 18:51             ` Scott Wood
2008-02-12 23:17               ` David Gibson
2008-02-12 23:41                 ` Timur Tabi
2008-02-12 23:50                   ` David Gibson
2008-02-12 15:44           ` Timur Tabi
2008-02-12 18:58             ` Grant Likely
2008-02-12 19:08               ` Timur Tabi
2008-02-12 19:34                 ` Grant Likely
2008-02-12 19:45                   ` Timur Tabi
2008-02-12 20:43                     ` Grant Likely
2008-02-12 23:35                     ` David Gibson
2008-02-12 23:50                       ` Timur Tabi
2008-02-13  0:10                       ` Grant Likely
2008-02-12 23:26                 ` David Gibson
2008-02-12 23:47                   ` Timur Tabi
2008-02-13  0:08                     ` David Gibson
2008-02-13  0:15                     ` Grant Likely
2008-02-12 23:21             ` David Gibson
2008-02-11  0:14 ` David Gibson
2008-02-11  2:40   ` Sean MacLennan
2008-02-11  3:11     ` David Gibson
2008-02-11  3:49       ` Sean MacLennan [this message]
2008-02-11 23:59         ` David Gibson
2008-02-12  1:07           ` Sean MacLennan
2008-02-12  0:20             ` David Gibson
2008-02-12  0:41               ` Sean MacLennan
2008-02-12  0:48                 ` David Gibson
2008-02-12 18:52                 ` Scott Wood
2008-02-12 19:03                   ` Grant Likely
2008-02-12 19:10                     ` Scott Wood
2008-02-17 10:22                       ` David Woodhouse

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=47AFC5E3.20101@pikatech.com \
    --to=smaclennan@pikatech.com \
    --cc=linuxppc-dev@ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).