Rockbox Development > New Ports

SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2

<< < (177/386) > >>

saratoga:
One thing I want to double check:  mkamsboot's output will only take on the target its made for right?  So you can't accidentally flash a V1 clip bootloader onto a V2?

Additionally, i've ordered an e200v2, which has easy access to the battery terminals, so I can make whatever power measurements people are interested in seeing once I get it.

funman:

--- Quote from: funman ---mkamsboot should be made more intolerant.
I think if you're not using the correct target, only a warning will be issued while it should abort.

I also plan to make modifications of untested firmwares (unknown md5sum) fail, and if people want to test a new firmware they would have to modify the source.

--- End quote ---
EDIT: committed

Here are the plots (almost no difference for Fuze, except longer battery life with lower pclk)
For one test, my Clip wasn't fully loaded, but you can still see the difference.

kugel.:
So, the difference between DBOP @62MHz and DBOP @15MHz (lower was not possible) is non-existent. Both give me 9h in my heavy test.

I opt for removing the divider.

funman:

--- Quote from: kugel. on May 25, 2009, 08:02:35 AM ---I opt for removing the divider.
--- End quote ---

Please just let me test on my Clip as well since the screen is different. That way we can make the change for all models.

kugel.:
I also tested CPU @ 192/64 and PCLK@64 (just by changing clock-target.h for now) and get major speed ups in decoding and test_fps.

Navigation

[0] Message Index

[#] Next page

[*] Previous page