This is the bug/patch tracker for Rockbox. Click here for more information.
Quick links: Bugs · Patches · Rockbox frontpage
FS#9933 - Sansa Fuze & e200v2: Unify drivers
Attached to Project:
Rockbox
Opened by Thomas Martitz (kugel.) - Friday, 20 February 2009, 19:14 GMT+2
Last edited by Rafaël Carré (funman) - Saturday, 06 March 2010, 00:55 GMT+2
Opened by Thomas Martitz (kugel.) - Friday, 20 February 2009, 19:14 GMT+2
Last edited by Rafaël Carré (funman) - Saturday, 06 March 2010, 00:55 GMT+2
|
DetailsThis patch unifies much of the now duplicated code for e200v2 and fuze in several new files (dbop-e200v2-fuze.c, lcd-e200v2-fuze.c, button-e200v2-fuze.c).
As far as my experience goes, this two targets have too much in common to have the code split and duplicated. Needs testing on the e200v2. Also, I'm wondering if this good at all, since the other ams sansas are still split, and most functions cannot be static anymore. |
This task depends upon
Closed by Rafaël Carré (funman)
Saturday, 06 March 2010, 00:55 GMT+2
Reason for closing: Out of Date
Saturday, 06 March 2010, 00:55 GMT+2
Reason for closing: Out of Date
I really want to unify the driver, and I hope going from the e200v2 side, it could work.
You probably understood the code: If you repeatedly turn the wheel, say every tick task, then BUTTON_REPEAT is generated. And when BUTTON_REPEAT is true, then you don't wrap, else you wrap.
But in my code, it is just *highly unlikely to not have BUTTON_REPEAT*, since already two tick tasks in a row with scroll action will have the repeat.
So I ask you again, just to make sure: Does it always wrap or only if you're turning it slowly towards end of the list?
Another question, am I correct that the current e200v2 driver (in svn) does *never* wrap? If yes, that would certainly wrong, as other targets don't do that.