Hi,
----- Stefan Seyfried <[email protected]> a écrit : > Hi all, > > after Andreas' and Guillaume's great HOWTO, I finally pulled out my > raspi over the weekend and played with it. > > It works pretty well. > However, the system is pretty unstable with the 3.1 kernel. > I noticed when trying to build ffmpeg from source. Lots of strange > errors, from ext4 complaining about delayed allocation to spurios > "ENOPERM" when closing temporary files during compilation etc. > Also, the raspberrypi-gfx demo/test tools did not work, erroring with > messages about "vcihq not connected" in dmesg. > > Additionally, my 512MB Raspi only had 256MB available, no matter what > amount of gpu_mem I put into config.txt. > > Then I simply grabbed the binary kernel and modules from > https://github.com/raspberrypi/linux and new firmware from > https://github.com/raspberrypi/firmware and voila -- the little box was > running stable. > > So I took the kernel from > devel:ARM:Factory:Contrib:RaspberryPi:kernel-3.6 and updated the patch > set to yesterdays git and changed the configuration to be pretty similar > to what is in the "upstream" git. Sounds good. :) > > I also updated the firmware package. > > Both together run very fine for me. I have all RAM available, the test > tools work, etc.pp. > > So maybe it would make sense to use the 3.6.11 kernel as "upstream" > Raspberry Pi also does? Make sense to me. > > I created SRs 198076 (raspberrypi-firmware) and 198080 > (kernel-raspberrypi) and maybe we should use > devel:ARM:Factory:Contrib:RaspberryPi:kernel-3.6 as the default raspi > kernel? I accepted your firmware patch but I have not the rigths to accept kernel SR. Thanks for your help. Guillaume > > Best regards, > > Stefan > -- > Stefan Seyfried > "If your lighter runs out of fluid or flint and stops making > fire, and you can't be bothered to figure out about lighter > fluid or flint, that is not Zippo's fault." -- bkw > -- > To unsubscribe, e-mail: [email protected] > To contact the owner, e-mail: [email protected] > -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
