This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DaVinci Linux - How to add missing functionality?

Other Parts Discussed in Thread: AM1808

Hi - I am currently "playing" with an AM1808 experimenter kit setup and I have been tasked with trying to capture keyboard and mouse user input.  I am currently running the recommended version of linux (v. 2.6.34) on the board and I have been through the documentation regarding Kernel configuration and rebuilding of the kernel using CROSS_COMPILATION (using CodeSourcery as my ToolChain). The OS works fine when downloaded to the board and I can plug a mouse and keyboard in and all is good. In attempting to meet my goal of capturing keyboard and mouse input, I have downloaded the logkeys project posted on google.code website (http://code.google.com/p/logkeys/) - this only helps solve the keyboard capture .. but it would be a great start. I built this project on my UBUNTU 10.4 linux development system and tested it on the UBUNTU system and all works well.  I have then CROSS_COMPILED this project for my AM1808 and copied the resulting binaries to the board.  Now when I try to invoke the application, the apps usage description always is printed regardless of what parameters I provide. Reading up more on the logkeys project I notice it is dependent on "dumpkeys" and it also expects locale information - (expects entries to be in the /usr/lib/locale) - both of which apparently do not exist in the DaVinci (ARM9) PSP Release.  I have checked the kernel configuration options and apparently there is nothing governing either of these topics.  So now I am not sure where I go.  Is there a linux package I can download that is compatible with the DaVinci flavor of linux that would allow me to CROSS_COMPILE and be included in my kernel ?  Anybody have any suggestions on where I should go from here? 
(BTW - I do realize logkeys is a keylogger and very often may be leveraged for nefarious goals...my goal here is on the up-and-up where a customer would like a custom board solution where they can plug in various USB devices and have the input from those devices be sent to some centrally managed location over ethernet....well that does not sound any less nefarious to me...but I am told the intentions are good) Thanks for any help!

  • Update - as it turns out...I can get by without having the dumpkeys (apparently this may have been built into the tool chain??) After fixing the fact that the code kept on trying to parse more arguments off of the cmd line than what was actually supplied...I was able to make it to a point in the code where it was trying to set the Locale.  This of course failed since there apparently is no Locale info installed on this version of linux.  However, commenting out the check...allowed for the assumption of a US keyboard and apparently all works now as expected.  So I have solved this set of problems.  On to finding the next set of issues.