Hello, I have on hand both the DM355EVM and a leopard Board. I would like to ask a few getting started questions. First I have already built a kernel from Kevin's tree for 2.6.29-davinci1 and patched it for support for the 2M pixel image sensor. I am currently using an Ubuntu rootfs which I had built originally for the Omap 3530 and it seems to work fine. The rootfs is on a 2G MMC card. I am using tftpboot to load my kernel just so I do not have to reflash the NAND every time I recompile. All is well. One weird caveat is that the dm9000 driver was not working until I replaced the dev_dbg to dev_info. I originally did it as a quick way to see all the output messages, as a starting point of why it was not working. Weird thing is the driver started working after that. I also found a patch that claimed to intialize the chipset properly. That did not fix it either until I did the dev_info replacement. I am not sure if that patch is relevant but now it seems to work. The dm9000 claims that the chip is rev E, but the soldered down component has DM9000BEP which I am assuming is revB. I may look more into this later. Also I added the platform_device __init for the davinci_fb to the board_dm355_evm (I just copied it from the 644x board file) and it appears that I have fb0-3 in the /dev folder. My questions are is their another rootfs that is recommend such as maemo or openembedded. Also and more importantly should I just start using Kevin's head which may have already tackled the fb and the dm9000 problems. I am throwing this message in the list as I start to search these answers myself with the hopes that I may get a jumpstart from somebody who has worked on the dm355 longer than 2 days :)
Thanks, John Sarman _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
