Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
fragilematter:
It's fat16 in fact, so we can get rid of the fat32 support and make a smaller driver ;)
kugel.:
Are you sure it's fat16 for all v2s? I have a doubt that a 8GB Fuze uses fat16.
Also, I seem to remember that for the e200v1, fat16 was possible for <= 4GB versions, but 6 and 8GB ones used (of course) fat32.
As for the minimalistic fat driver: I think it's worth looking into existing code for already supported targets, especially if the SD interface is to be used, just like e/c200v1 series.
funman:
--- Quote from: Bagder on September 18, 2008, 01:53:17 PM ---Rockbox already has all the fat32 filesystem code you need of course...
--- End quote ---
I am not sure it fits in the 1kB of our code segment, aside with the sd driver, so I think we must go we the minimum.
I don't know filesystems but I think we can remote at least write support, recursive directories traversal, and maybe more ..
I built rockbox bootloaders for other targets and they are not very smaller than the rockbox code (without applications) and are definitely too big for the actual room.
By the way do you know if MMC (SD) and NAND flash are driven by the same driver with different base addreses for the registers in SansaV1 ?
caladan:
Atomikpunk must be right with that SD driver. We should have thought about it earlier, texts in sw indicate clearly that all directories are seen in mmc:\
I wonder how dangerous it would be, but maybe we should try to use the same values as those used in v1 to access registers.
funman:
--- Quote from: caladan on September 18, 2008, 03:25:10 PM ---I wonder how dangerous it would be, but maybe we should try to use the same values as those used in v1 to access registers.
--- End quote ---
The OF clearly show different values: it shows that the SD controller is the ARM PL180
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version