**** BEGIN LOGGING AT Fri Nov 15 02:59:59 2013
Nov 15 08:46:57 <ant_work> lumag: as of yesterday one user asked me about repartitioning zaurus poodle
Nov 15 08:47:30 <ant_work> we have talked about copying the code in kexecboot in kernel and I have found a very good example
Nov 15 08:47:43 <ant_work> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/mtd/bcm47xxpart.c
Nov 15 08:48:20 <ant_work> what I don't remember is, how would the kernel read these bytes? does it need the nandlogical oob stuff?
Nov 15 09:01:32 <ant_work> Sharp 'nandlogical' flash translation layer
Nov 15 09:01:32 <ant_work> The boot partition from 0x000000 to 0x6fffff is managed using the Sharp 'nandlogical' FTL. This FTL reserves 24 erase blocks for wear leveling (so the logical address space is only 0x000000 to 0x69ffff. Flash erase block size is 0x4000, 24*0x4000 == 0x60000).
Nov 15 10:48:08 <ant_work> hmm, seems we can read our 36 bytes without much hassle
Nov 15 10:48:21 <ant_work> today I'll send the repartition tool for MTD
**** ENDING LOGGING AT Sat Nov 16 02:59:59 2013