09:22 <megi> unlikely. you need to at least powerup the panel to be able to read ID from it (and that is now implemented as a panel specific function), so the kernel would have to cycle through various panel drivers just to be able to enumerate which one may connected (if this was to be generic)

09:26 <mripard> MoeIcenowy: if the design isn't final yet, you can probably claim a bunch of GPIOs then and make that your version detection mecanism

09:27 <mripard> (ie, have something like 4 GPIOs all set to the ground on v1, and 1 set to 3.3v on v2 or something)

09:41 <wens> that reminds me, I still need to do a fix for the gpio driver

20:47 <Ashleee> wow *really*? The *one* time I actually manage to not forget to run dmesg -wH in a console it will *not* freeze on IO?

20:47 <Ashleee> how rude!

20:51 <Ashleee> oh I spoke too soon. "data error, sending stop command; send stop command failed"

21:07 <Ashleee> ah well, don§t see any obvious easy way to try slowing down the eMMC, gonna use the box with sd card apparently :P.

21:11 <jernej> Ashleee: Just check eMMC datasheet and put correct property in DT. Accepted properties: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Documentation/devicetree/bindings/mmc/mmc-controller.yaml#n127

21:11 <jernej> usually "mmc-hs200-1_8v;" helps

21:12 <jernej> but that really depends on eMMC features