View Single Post
Posts: 2,154 | Thanked: 8,464 times | Joined on May 2010
#167
Originally Posted by Mentalist Traceur View Post
Anyone know a good safe way to get the framebuffer console that isn't as risky as my random experimental insertion of the modprobe line? Also, how do you go from console to an actual shell, or is something else required before that's doable?
Instead /sbin/preinit edit file /bootmenu.sh
/sbin/preinit run /bootmenu.sh only when keyboard are open. So if your /bootmenu.sh will break booting, you can close keayboard and this file will not be loaded.

Multiboot and Bootmenu are using this file too. (it does not break system with closed keyboard)

Originally Posted by Mentalist Traceur View Post
Still want to know what steps have to be taken to get from here to a an accessible command-line at boot time, and my web searching has turned up naught so far, so perhaps I'm looking in the entirely wrong direction...
I'm prepairing special entry for bootmenu for booting recovery console mode.


Originally Posted by freemangordon View Post
@pali - Where patches should go, I have updated dspbridge driver to this http://dev.omapzoom.org/?p=integrati...7d1783f6606763 commit, does not make sense do go any further for now as first 720p mpeg4 was played successfully on my N900 . When I have time I will go through newer patches to check for something critical, but for now this is it.
First, all patches must be applied on power-kernel 2.6.28.10 tree. And all patches mustn't break some parts of system/kernel.

Put patches in debian/patches, add patch file names to debian/pacthes/series and generate diff agains my power-kernel git repository.
 

The Following 9 Users Say Thank You to pali For This Useful Post: