[Arm-netbook] [advice sought] EOMA68 kernel support

lkcl luke luke.leighton at gmail.com
Sat Mar 10 20:20:11 GMT 2012

On Sat, Mar 10, 2012 at 7:51 PM, Alan Cox <alan at lxorguk.ukuu.org.uk> wrote:

>>  of particular concern is that a CPU card could be running on (small!)
>> backup battery / supercapacitor whilst being hot-swapped, and thus
>> that means that the LCD module (drivers/eoma68/lcd.ko?) would need to
>> be loaded and unloaded from userspace (udev).  that's not going to be
>> a problem, is it?  i may just be imagining skeletons in the closet,
>> here.
> Your device tree describes devices. Your bus creates them when you
> hotplug and it removes them when you hot unplug. The rest is the drivers
> problem to behave properly, and refcount right.

>>  * it's the purposes to which the 16 GPIOs can be put that will be
>> radically different from one I/O board to the next.  GPIO 0 could be
>> "powerup for WIFI" on one I/O board, but "lid open/shut switch" on
>> another.
> It's "GPIO 0 of card X" and providing you remember that, watch your
> refcounting and don't remap a new device over the address space of an old
> one during a hotplug you should be fine.

 allright.  thanks alan.  that's clear.

honest opinion sought: is this something that would keep a (good) gsoc
student occupied full-time?  you or i could complete it in a week, 2
weeks, whatever, but i'm concerned that a gsoc student would go "um is
that it??"

yes we'll have by then one or two reference platforms, but that's not
going to be rocket science to get the device drivers for them
up-and-running [non-eoma-compliant].

i guess i'm talking myself out of the proposal, am looking for advocates :)


More information about the arm-netbook mailing list