On Fri, Feb 13, 2009 at 01:41:44PM +0100, Mitja Kleider wrote: > I would like to see native Debian running on the Letux400. The biggest > step forward would be a reliable 2.6 kernel.
:-) /me actually feels ashamed. > My missing success was to get wifi and Xserver running after installing > native Debian Etch. I flashed the 2008-12-18 version of 2.4 uImage-nand2 > [1]. If it's still a problem I can paste some of my configuration files. > I was thinking about the confusion with different models of very similar > hardware and different uboot versions. Not being sure if you are booting > or flashing and different keycombos for each version could scare users. > Maybe a unified bootloader which supports all models would help. The Qi > approach [2] of the Openmoko project sounds promising, I dont know if it > is applicable for the mipsbook hardware. This would probably also reduce > boot time. The waiting for keys takes at most 2s. The loading and decompressing of the kernel takes 1s or so. The moment you see the splash screen, the kernel is already started. It takes another 30s or so to finish booting this kernel. After it has finished booting, it takes another 3s. or so to present the login screen. It's absurd long, but I do not intend to fix that. I seldomly have to turn on the letux 400, since it can run about 5 hours with an active wifi connection. So it's long enough to go from outlet to outlet ;-). Going to 2.6 is a major fix to a lot of things. Anyway: changing the bootloader is very scary since we don't know of a way yet to recover from a broken bootloader. People will say to use jtag, but mips isn't into having a standardised jtag interface. -- .signature not found _______________________________________________ Mipsbook-devel mailing list Mipsbook-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/mipsbook-devel
