[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: dynamic LCD support for "embedded" systems

On Mon, Jul 25, 2011 at 1:40 PM, Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:

>  i have an idea.
>  devicetree LCD modules.  these could still be dynamically loaded,
> right?  i mean, it's a bit crazy, but you could have associated with a
> particular LCD panel a devicetree-compliant dynamic loaded module
> which had the correct LCD settings (including the required pre-tested
> hsync and vsync data), right?

 sorry to be following-up to my own posts: thought-continuation error,
Does Not Compute :)

 ok, the context is as follows:

 * plugnpray CPU module, de-facto standard interface(s), USB2, I2C,
Ethernet, LCD, GPIO, blah blah
 * Motherboards (conforming to de-facto standard interface), but apart
from that, can be any design.


 * CPU module Cortex A8, 1gb RAM
 * CPU module Cortex A9, 1gb RAM
 * CPU module MIPS Ingenic jz4770
 * Motherboard 7in tablet, 800x480 LCD
 * Motherboard 11in laptop, 1280x768 LCD
 * Desktop PC (VGA or DVI converter on LCD data)

 i.e. radically different CPU modules, and radically different motherboards.

 that's the context.

 question: how the bloody hell do you make sure that any of the CPU
modules can plug into any of the motherboards... *including* future
CPU modules and including *unknown* motherboards yet to be designed..
and actually boot up the LCD. correctly.

  i thought: yeah, yeah, make a devicetree-compliant dynamic module,
put it on some storage on the motherboard: CPU module boots up, mounts
the motherboard storage, loads the module, everything hunky-dory.

 except... then you're into "linux kernel upgrade hell".  and you'd
have to have, pre-loaded on the motherboard storage, a
devicetree-compliant LCD dynamic module for 2.6.N for MIPS, another
one for the 2.6.N Cortex A8 CPU(s) ... no, it's hell on earth.

 but then it occurred to me... well... why bother having that data in
a kernel module (esp. if it has to go on a filesystem anyway), why not
just have that LCD data in a text file?   somewhere in
/lib/firmware/edid_data or something like that?

 so, you go through the heuristics-process (arnaud's just kindly
described some of what is needed here:
http://lists.debian.org/debian-arm/2011/07/msg00054.html ) and then
you go look up the actual required LCD settings off of
/lib/firmware/{somewhere}, drop them into the one generic (and
statically-loaded, yaay!) devicetree-compliant module, everything's

 does that sound like a reasonable plan, or have i completely lost
everyone at this point? :)


Reply to: