ts-7000
[Top] [All Lists]

[ts-7000] Re: Kernel 2.6.29 on TS-72XX

To:
Subject: [ts-7000] Re: Kernel 2.6.29 on TS-72XX
From: "charliem_1216" <>
Date: Tue, 07 Apr 2009 02:31:02 -0000
Hi Stefan --

--- In  Stefan Agner <> wrote:
>
> 
> From: charliem_1216 <>
> >But that patch is for the static layout;  I think it would be better to use 
> >the 
> > code in drivers/mtd/ redboot.c to parse the FIS tables at boot.  Is that 
> > not 
> > working already?
> 
> I applied Matthieu's patchs to 2.6.29 and tried to boot without the changed 
> partition table, then he complained about wrong partition size according to 
> erease size... 
> 
> I just had a look in my kernel config, there is an option 
> CONFIG_MTD_REDBOOT_PARTS, it might be that this works (and if enabled, the 
> patch wouldn't be necessary...) But I didn't tried that...

Yes, try to enable that, and then also you must choose a block number that 
holds the redboot directory block (MTD_REDBOOT_DIRECTORY_BLOCK).  I used '-1', 
which means last block.  

But I just tried it, and now it fails for me, falling back to the wrong static 
partition info.  (I *thought* it worked before....).  Here is a dmesg snippet 
(2.6.29-rc6):

Searching for NAND flash...                                                     
                                       
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 
8-bit)
Scanning device for bad blocks
Bad eraseblock 0 at 0x000000000000
Bad eraseblock 1 at 0x000000020000
Bad eraseblock 1009 at 0x000007e20000       
Bad eraseblock 1010 at 0x000007e40000
Bad eraseblock 1011 at 0x000007e60000
Bad eraseblock 1012 at 0x000007e80000
cmdlinepart partition parsing not available
Using static partition definition
Creating 3 MTD partitions on "ts7250-nand":0x000000000000-0x000000004000 : 
"TS-BOOTROM"
mtd: partition "TS-BOOTROM" doesn't end on an erase block -- force read-only
0x000000004000-0x000007d04000 : "Linux"
mtd: partition "Linux" doesn't start on an erase block boundary -- force 
read-only
0x000007d04000-0x000008000000 : "RedBoot"
mtd: partition "RedBoot" doesn't start on an erase block boundary -- force 
read-only

And here is a snippet from my redboot:

RedBoot> fis list
Name              FLASH addr  Mem addr    Length      Entry point
(reserved)        0x60000000  0x60000000  0x07D20000  0x00000000
RedBoot           0x67D20000  0x67D20000  0x00040000  0x00000000
vmlinux           0x67D60000  0x00218000  0x00140000  0x00218000
(bad block)       0x67E20000  0x67E20000  0x00020000  0xFFFFFFFF
(bad block)       0x67E40000  0x67E40000  0x00020000  0xFFFFFFFF
(bad block)       0x67E60000  0x67E6x00020000  0xFFFFFFFF
(bad block)       0x67E80000  0x67E80000  0x00020000  0xFFFFFFFF
FIS directory     0x67FE0000  0x67FE0000  0x00003000  0x00000000
RedBoot config    0x67FFF000  0x67FFF000  0x00001000  0x00000000


regards, ........... Charlie
> 
> Bye
> Stefan
>




------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/ts-7000/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/ts-7000/join
    (Yahoo! ID required)

<*> To change settings via email:
     
    

<*> To unsubscribe from this group, send an email to:
    

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

<Prev in Thread] Current Thread [Next in Thread>
Admin

Disclaimer: Neither Andrew Taylor nor the University of NSW School of Computer and Engineering take any responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the birding-aus mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU