<larsc>
ili8960 is the controller inside the GPM940B0
<roh>
is that the one on the NN?
<larsc>
yes
<kyak>
larsc: i'm trying to refrsh kernel config, enabling battery and backlight support (they don't seem to be present in openwrt trunk kernel config)
<kyak>
i'm not sure if there is a special reason why they were not enabled, or maybe they just were not present at that time?..
<larsc>
kyak: they should be enabled
<larsc>
if they are not thats a bug
<larsc>
CONFIG_LCD_ILI8960=y
<kyak>
for example, ili8960 was not enabled because SPI support was switched off.. And then battery wasn't enabled because of some other dependency
<larsc>
hm, i see
<kyak>
i'm now fighting with make kernel_menuconfig :)
<larsc>
but there is CONFIG_SPI=y
<larsc>
as well
<kyak>
hm..
<kyak>
CONFIG_SPI=y is in target/linux/xburst/qi_lb60/config-2.6.37.. make kernel_menuconfig puts it into target/linux/xburst/config-2.6.37
<kyak>
maybe i'll just start from scratch..
<xMff>
that is expected
<xMff>
better do it by hand
<kyak>
if i do it by hand, then following kernel_menuconfig would overwrite these changes..
<xMff>
yes
<kyak>
or is it ok?
<xMff>
I mean do not use kernel_menuconfig
<kyak>
oh ok
<xMff>
it has no way to know how symbols should be distributed
<xMff>
so it just stuffs them into the target config
<xMff>
xou could use the diff to fill up the subtarget config though
<xMff>
*you
<larsc>
but it should only modify the last config which is the board config and not the target config in this case
<xMff>
larsc: I suppose it is bugged then, but that'd only shift the problem, generic symbols would end up in the wrong config, too
<larsc>
yes
<larsc>
so far i've moved those symbols by hand to the target config
<larsc>
kyak: btw. my plan was to add the 2.6.39 patch today or tomorrow