Rockbox mail archiveSubject: Re: supported targets : which ones to add
Re: supported targets : which ones to add
From: Thomas Martitz <thomas.martitz_at_student.htw-berlin.de>
Date: Tue, 14 Jul 2009 23:16:28 +0200
Frank Gevaerts schrieb:
> Since I've been accused on irc of only sending non-controversial mails,
> here's my attempt at a controversial one.
> Here are the targets from the "New Platforms Currently Under
> Development" section on the TargetStatus page, together with my opinion
> on whether they should move on to the supported list:
> The following work more or less well:
> * Cowon D2
> Installation works well, no write support to NAND, not always well
> integrated touchscreen, SD driver nearly ready. A lot of people seem
> to use it. I think it should be supported.
I think so too. It may be a bit unusual, but that isn't bad by any means.
Isn't the D2 still in production also? Supporting it might also get us a
boost with general touchscreen support (hoping it will attract developers).
> * Olympus M:Robe 500
> Installation requires a "magic" svg file (but it is easy), starting
> rockbox requires doing some things in the OF. Once running, rockbox
> seems to work fine, with the same touchscreen caveat as the D2. If the
> magic SVG file is not seen as a problem, I think it can be supported.
I have no opinion here, I'm not into that target at all.
> * Sansa AMS devices (e200v2, m200v4, c200v2, Clip, and Fuze)
> Some of these are very close to working perfectly (fuze, clip, e200?).
> There is talk about data corruption on the sd card. If that is still
> there, we should probably wait until it's fixed and then move them to
We still have some issues with the SD driver. The low memory have
buffering problems also. It might be too early to support them, but
having them in the testing builds forum was a good move IMO. Although, I
still think that's mostly the same (read as: I'd love to have them
supported if I wasn't a bit responsible for bug reports :D ).
> * Toshiba Gigabeat S
> I'm not sure about this one. There seem to be three cases here:
> * for some people it works fine
> * some are picky about dualboot vs single boot (i.e. only one of the
> options works, which one depends on the exact player)
> * some people suffer from the OF boot code wiping the data partition
> every now and then
> * for some people, magic is needed before the bootloader manages to
> find rockbox.gigabeat (special mkfs.vfat options, booting the OF
> once, ...). It's possible to lose lots of time with this.
> I think that if we call it supported, there should be lots of
It works fine, but the installation is flawed, so I don't think it
should be supported.
> I don't have enough informsation about these, so I won't say anything:
> * Philips GoGear HDD16X0/18X0
> * Philips GoGear HDD63X0
> * Philips GoGear SA9200
> * Samsung YH82X/YH92X
The Samsungs YH820 and YH925 could be supported right now. They're PP
based and have much code imported that worked for ages on other targets,
even USB. My only concern is the battery life. It seems very low, BUT I
haven't done a battery_bench, and I have no idea how much the OF does.
Part of the problem is that the backlight can't be turned of completely
(on the 925 at least), so that could explain the battery life. The
battery is also rather weak (750mAh only, for a HDD-based player IIRC).
The disk transfer speed is also rather low. They don't have plugins yet too.
But again, these not blockers IMO. We could support them, but we talk to
> The following are definitely not ready. Most don't even run a full build
> * Cowon iAudio 7
> * Creative ZVM
> * Onda VX747(+)/VX777
> * Onda VX767
> * Sansa m200 v1/v2/v3
> * Tatung Elio TPJ-1022
> * Sansa c100
> * Logik Dax 1GB DAB/MP3 player
> * Meizu M6
Most of them aren't even actively being worked on, actually. I agree.
Received on 2009-07-14