hi,
i'm using linux kernel v2.6.34 and porting to a omapl137 (da830) board..
the kernel seems to be running well and mounts the NFS rootfs well just like
the previous one(2.6.18_pro500) i used...
BUT when i set a PINMUX register or write a common register of omapl137, for
example the USB configuration register CFGCHIP2, it seems to be failed...
why i said it failed..becoz i checked the value of the register after writing,
it was not the value i had written...and it was the same as the original
value...
[ 0.260000] MUX: initialized GPIO2_11
[ 0.260000] MUX: Setting register GPIO2_11
[ 0.260000] PINMUX9 (0x00000024) = 0x00000000 -> 0x00000800
[ 0.260000] MUX:now register(0xfec14144) is 0x00000000
the log above can obviously show the problem i said...it used the function
'davinci_cfg_reg' in mux.c to set the PINMUX9 register
when i use this kernel, it seems that i can read a register but i can't write
or set it....
i don't know why and when i use linux v2.6.18_pro500 kernel again, there is no
this kind of problem...
therefore, it would not be a hardware issue..
AND i checkout the linux-davinci mainline based on v2.6.34...and also git-clone
a snapshot kernel based on v2.6.35rc3.
but it doesn't make any sense...this problem also exists....
i am not sure whether it's a bug in the kernel...
can anyone give me some idea to solve the problem...
Best regards,
Nicole
_________________________________________________________________
MSN十年回馈，每位用户可免费获得价值25元的卡巴斯基反病毒软件2010激活码，快来领取！
http://kaba.msn.com.cn/?k=1_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
