I've been working with the Kernel's Displaylink (udlfb) driver for a few days now. After some trouble I was able to get initial support for the legacy 2.0 USB devices working. Lucky, this early work was possible due to a few earlier projects. I had to work out a few power issues as our chosen device does not have enough power to run the display with out being chained to a powered hub.
So, currently I have an active framebuffer /dev/graphics/fb13 which I can push static frames to, but the display stack for the OS is not aware of the devices existence and so it can not be used with any of the API calls. I am looking for documentation or help on where to start. From reading the source pages on android.com I believe the extensions to the framebuffer need to be done in the Display HAL, but I'm not even sure where in the source tree those files exist. Its also possible that the display driver itself needs to be extended to report itself as an available display. If anyone has any insight I would be very grateful.
Link up and running.
References:
So, currently I have an active framebuffer /dev/graphics/fb13 which I can push static frames to, but the display stack for the OS is not aware of the devices existence and so it can not be used with any of the API calls. I am looking for documentation or help on where to start. From reading the source pages on android.com I believe the extensions to the framebuffer need to be done in the Display HAL, but I'm not even sure where in the source tree those files exist. Its also possible that the display driver itself needs to be extended to report itself as an available display. If anyone has any insight I would be very grateful.
Link up and running.
References:
