[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] Flatfsd, partitions and MTD
>>> On 23 September 2009 at 17:14, in message <4ABA5759.E5F9.0050.0@xxxxxxx>,
"Martin.J Thompson" <Martin.J.Thompson@xxxxxxx> wrote:
> Hi all,
>
> I thought this would be simple, but I can't find the info I need - can anyone
> help?
>
Heh - always write the message, then cycle home if you need answers :)
> 2) If I use a "standard uclinux ROMFS moved to EBSS" configuration, it
> creates an MTD for it during boot at mtd0. This seems to mean that the minor
> numbers associated with the /dev/flash/* mtd references are out by 2 (ie by 1
> mtd device). Is that right, or have a messed something else up?
> Example - my kernel image is at /dev/mtd2
> I defined this as as CONFIG_SYSTEM_PARTITION2_NAME="kernel", which I would
> expect to be at node 90,4... but my rootfs has it at 90,2
I think this difference is because my spi flashes are "enumerated" way after the ROMFS, whereas in the parallel flash case, they are enumerated before the ROMFS. This means that usually the romfs mtd partition comes at the *end* and the parallel flash mtds start at mtd0 (which is SYSTEM_PARTITION1, node 90,0)
In my case the spi flashes come later, so start from mtd1.
Hence I need to customise my vendor makefile to setup the /dev/flash/ devices.
Cheers,
Martin (hoping his .sig goes in the right place...)
--
Martin Thompson CEng MIET
TRW Conekt, Stratford Road, Solihull, B90 4GW. UK
+44 (0)121-627-3569 : martin.j.thompson@xxxxxxx
http://www.conekt.net/
Conekt is a trading division of TRW Limited
Registered in England, No. 872948
Registered Office Address: Stratford Road, Solihull B90 4AX
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/