-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: | | Carsten Haitzler (The Rasterman) wrote: |> ok 2 things. |> |> 1. uboot env needs to get rid of "console=tty0" from any boot parames |> preferably something like:
| So clearly this will not work for the GTA01. Someone needs to verify | that on the GTA02, this output will be directed to the tty associated | with ttySAC2 (which is harmless on the GTA02), and not ttySAC0 (where it | will be sent to the GSM just like the GTA01). Its probably OK to set loglevel to something low (from Documentation/kernel-parameters.txt) ~ loglevel= All Kernel Messages with a loglevel smaller than the ~ console loglevel will be printed to the console. It can ~ also be changed with klogd or other programs. The ~ loglevels are defined as follows: ~ 0 (KERN_EMERG) system is unusable ~ 1 (KERN_ALERT) action must be taken immediately ~ 2 (KERN_CRIT) critical conditions ~ 3 (KERN_ERR) error conditions ~ 4 (KERN_WARNING) warning conditions ~ 5 (KERN_NOTICE) normal but significant condition ~ 6 (KERN_INFO) informational ~ 7 (KERN_DEBUG) debug-level messages If the error is "device on fire" then you probably don't mind it interrupted the flow of beautiful graphics. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkgsUY4ACgkQOjLpvpq7dMqVzQCfQNqI5fvTxqfBNTvdLFjmzTWy yzYAnRQG/Ng8tKDxodf2wsSW7M9Cl4CT =Kds0 -----END PGP SIGNATURE-----
