Support and General Use > Hardware
X5: Any news about remote support? (RaeNye maybe?)
RaeNye:
>:( I think I stated clearly that
--- Quote ---It has nothing to do with buttons (ADC driver already handles them)
--- End quote ---
However, the problem is that there's no #define HAVE_REMOTE in config-iaudiox5.h.
Try to add this and check what goes wrong (something should, since the remote LCD is not defined)
Eriol:
--- Quote from: RaeNye on July 10, 2006, 06:02:35 AM --->:( I think I stated clearly that
--- Quote ---It has nothing to do with buttons (ADC driver already handles them)
--- End quote ---
However, the problem is that there's no #define HAVE_REMOTE in config-iaudiox5.h.
Try to add this and check what goes wrong (something should, since the remote LCD is not defined)
--- End quote ---
From taking a cursory look at the code affected by HAVE_REMOTE and the h100 lcd driver... yikes. I'll admit I don't know the source tree worth crap (I haven't even bothered to set up my own environment to compile it yet), but (some) of the issues appear to be in converting the h100 lcd driver:
[*]They defined the global LCD framebuffer as a 1-bit color. I'm pretty sure my X5 remote has a few monochrome tones (virtually certain in fact, from looking at it REALLY f'n close, they're not doing on/off adjacent pixels, though who knows if they're switching on/off rapidly, though I doubt it). And the define for allocation has it hard-coded to be a bit, rather than using some type of definition for LCD color depth (which I'm pretty sure DOES exist for the remotes already in one of the config .h files). I'm thinking either we'll be duplicating most of the driver file for the X5 specifically, with MOSTLY identical functions, or we "generify" it into one driver file, with define blocks for each specific remote model. As I'm a neophyte here, I have no idea which approach is preferred by the style of the developers.
[*]They have this weird "tick" define hanging around that seems to be an anti-flicker delay... or something. This was a cursory look, so I'll admit I don't understand a lot of what's happening there.
[*]I'm probably missing a host of other issues, since as I said, this is a super-quick look from somebody who doesn't know the project at all. Layout issues (different resolution remotes) I'm sure also abound, and how to handle them.
[*]How would I go about testing that patch mentioned above RaeNye? I assume patching instructions are around (once I set up an environment), but what should I be looking for on the remote to know success/failure?[/list]
.
And this is seperate from getting the BUTTONS to work. The power on delay/not for choosing dual boot works, though after initial boot, all of the buttons are completely non-functional. You mentioned that the ADC driver handles them, so does anybody know where to start to fully enable them for every part of rockbox? I said I'm a neophyte, so it's probably pretty obvious to people that know the code, but hey, I wanna use my remote! ;) And I have background in programming (I do C/C++ as the main part of my job, though I haven't done integrated systems since University) so I'd like to help out once I get off my lazy ass and set up the build on my own box.
RaeNye:
--- Quote from: Eriol on July 18, 2006, 03:21:17 PM ---From taking a cursory look at the code affected by HAVE_REMOTE and the h100 lcd driver... yikes. I'll admit I don't know the source tree worth crap (I haven't even bothered to set up my own environment to compile it yet), but (some) of the issues appear to be in converting the h100 lcd driver
--- End quote ---
My initial attempt (the patch has already been deleted) was to convert the h100-remote, but X5 remote is 2-bit.
The correct code should be some kind of cross breeding the h100 main lcd (for 2-bit grayscale) and remote lcd driver.
--- Quote ---I'm thinking either we'll be duplicating most of the driver file for the X5 specifically, with MOSTLY identical functions, or we "generify" it into one driver file, with define blocks for each specific remote model. As I'm a neophyte here, I have no idea which approach is preferred by the style of the developers.
--- End quote ---
I pointed out the same thing as well. In fact, this is the main reason I didn't do any high-level code.
--- Quote ---How would I go about testing that patch mentioned above RaeNye? I assume patching instructions are around (once I set up an environment), but what should I be looking for on the remote to know success/failure?
--- End quote ---
First step: convert the code into a plugin and see if the sample image works.
--- Quote ---And this is seperate from getting the BUTTONS to work. The power on delay/not for choosing dual boot works, though after initial boot, all of the buttons are completely non-functional. You mentioned that the ADC driver handles them, so does anybody know where to start to fully enable them for every part of rockbox?
--- End quote ---
The dual boot is written specifically to do that, since the decision occurs much before anything is initialized in RB.
The #define HAVE_REMOTE (once compiles) will fix the ADC as well.
--- Quote ---I said I'm a neophyte, so it's probably pretty obvious to people that know the code, but hey, I wanna use my remote! ;) And I have background in programming (I do C/C++ as the main part of my job, though I haven't done integrated systems since University) so I'd like to help out once I get off my lazy ass and set up the build on my own box.
--- End quote ---
What are you waiting for?
Navigation
[0] Message Index
[*] Previous page
Go to full version