Skip to contentSkip to conversation

Static partitions

DISCUSSION Justin Clacherty 2 participants 3 messages Sep 3, 2006 – Sep 6, 2006 Memory technology devices (MTD)

lore
Share & tools
lore
#0 lore raw

Hi,

I've managed to get mtd working on my PXA270 board. I've used the mainstone port as a template for my board port and was wondering why the static partitions need to be defined twice. Mainstone has it defined in arch/arm/mach-pxa/mainstone.c and in drivers/mt d/maps/mainstone-flash.c.

Regards,
Justin.

#1 lore raw
Quoted 7 lines · Justin Clacherty

Hi,

I've managed to get mtd working on my PXA270 board. I've used the mainstone port as a template for my board port and was wondering why the static partitions need to be defined twice. Mainstone has it defined in arch/arm/mach-pxa/mainstone.c and in drivers/mt d/maps/mainstone-flash.c.

Regards,
Justin.

Asking again due to lack of interest :)

Nicolas, you wouldn't happen to know the answer to this would you?

#2 lore raw
Quoted 8 lines · Justin Clacherty
Quoted 7 lines · Justin Clacherty

Hi,

I've managed to get mtd working on my PXA270 board. I've used the mainstone port as a template for my board port and was wondering why the static partitions need to be defined twice. Mainstone has it defined in arch/arm/mach-pxa/mainstone.c and in drivers/mt d/maps/mainstone-flash.c.

Quoted 7 lines
Quoted 3 lines

Regards,
Justin.

Asking again due to lack of interest :)

Nicolas, you wouldn't happen to know the answer to this would you?

There was a patch in the CVS to remove any partition definitions from mainstone-flash.c and lubbock-flash.c, merge those two into a generic pxa-flash.c and have it get the partition information in a generic way from each board specific file.

The board specific file part is in mainline now. Somehow the other part hasn't been carried over to the MTD GIT tree yet.

Nicolas