Just for the record, in order to make musb_hdrc as module, you have to set:
CONFIG_USB_MUSB_HDRC=m (obviously ...) and CONFIG_USB_GADGET=m and it compiles.
If you want to add a gadget module, you get
error: implicit declaration of function ‘msleep’
Just "#include <linux/delay.h>" into the .c file that generate the error and it compiles fine
But even in module, the HOST port doesn't work
I don't know were to search anymore...
If you have some specific questions, just join irc://irc.freenode.net/openpma or use the webclient http://www.openaos.org/chat there are some archos and other skilled people around. They mostly don't read forum posts.
Originally Posted by grim-a101
BTW divx118, the option to change the language of an external keyboard is not there on your rom
Awesome find, I might try playing with that on A43, should only be a matter of forward-porting the A43 board file and LCD files to get basic support. The downside is the LCD uses DSI instead of DPI, but the new omapdss driver should support DSI natively if I could figure out how it works.
The newer the kernel, the better in my opinion, as long as everything works.
EDIT: That's a very clean board file! Hopefully it will be relatively easy to port, most of the GPIO's are the same between different gen8's but some aren't I think.
EDIT 2: I've started forward-porting the A43 board file to the new format. The big issue here is the LCD panel, hopefully I can get the board file itself working before I take on porting the driver itself
On the A101, does the Power LED flash with this kernel? The board file initializes the LED to "heartbeat" mode which should cause it to blink, indicating that the system is functional. This would be highly useful with the LCD unavailable.
As I reply to you on irc, no, the led doesn't blink, it just stay "on".
I've tried lots of things to get this USB host port working, but still no luck.
I've tried forcing the plat->mode to 1 (and the musb->board_mode to 1), forcing the extvbus to 1 also, adding lot's of debug to see where the initialisation goes (and doesn't) and I still have no idea why it still doesn't work.
I have no vbus, no power is transmited to the USB port whatever I change.
I tried to plug a powered usb hub, just to be sure that it is not only a vbus issue, but even with the external power, no syslog reaction when I plug anything to it.
I have to say, i'm a bit lost and don't know where to search anymore
Could you recompile the 3.0 kernel with CONFIG_LED_TRIGGERS enabled? I think it was disabled in the default config. Also CONFIG_LED_TRIGGER_HEARTBEAT (or something like that, might be CONFIG_TRIGGER_HEARTBEAT) enabled. Then see if the power LED blinks. I'd really like to have this running on the A43 and the power LED blinking is probably an important step as I want to make sure it's booting before I try messing with the LCD.
Already tried, with no changes. I'll try to make it blink, and let you know.
For the LCD, if I have well looked, there is only the 101 LCD (BOE something) that is available within this firmware. I don't know what is the 43 LCD but if I remember well, it is not the same.
The A43 LCD is an LG FWVGA 4.3" display, the driver is lg_fwvga_43 or something like that. I figured I'd have to port the driver myself, which is going to be tricky as it's a MIPI DSI video mode display. Support for this display type was hacked in to 2.6.29 by Archos, though with 3.0 it should be supported officially, though the API is quite different and the driver will need modification.
It’s been a while since Android 4.4KitKat wasreleased, and we’re slowly … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?