Re: [Gumstix-users] Flashing Over Ethernet Fails Due to No 3rd Partition

[Craig H. <cr...@gu...>]

On Oct 12, 2007, at 11:34 AM, Eric Sorton wrote:

> On 10/8/07, Craig Hughes <cr...@gu...> wrote:
>> Doh!  I'm an idiot -- I was remembering the old flash partitioning,
>> where /dev/mtd0 was one giant partition which covered the whole of
>> flash, then /dev/mtd1, /dev/mtd2, etc were sub-partitions; I forgot
>> that linux had changed this at some point -- so you're right, you now
>> need a separate image for u-boot.bin and the rootfs+uImage needs to
>> be sized to remove that mtd0 space.  In other words, it must be at
>> most 32MB (32MB+4*64k-2*128k).
>
> Hi Craig,
>
> Should the wiki page be changed back to 0x1EC0000 then?
>
> I believe that 0x1EC0000 is the size of the partition as configured in
> the kernel (if I'm reading the code right in
> drives/mtd/maps/gumstik-flash.c).  Bootloader is 0x40000, kernel is
> 0x100000, rootfs is all that is left 0x1EC0000 (0x2000000 - 0x40000 -
> 0x100000). How does the kernel figure out the size of the flash
> partition?  WINDOW_SIZE/2 seems to work, not sure why you divide by 2,
> but I'm can't claim to understand the hardware.
>
> If I understand everything correctly discussed in this thread, the
> verdex has 32MB+4*64k but the kernel is only configured to use 32MB.
> Is that correct?

I actually was mis-remembering and misreading the datasheet.  Looks  
like in fact, there are 255*128kB sectors, and 4*32kB sectors.  (not  
256* and not *64k).  So the total *is* exactly 32MB.

C