> On Wed, May 16, 2007 at 12:41:18PM -0500, Rolf Brudeseth wrote: > > > > > I tested the script with the console attached to serial port 1 and 2 (hvsi0 > > and hvsi1). > > > > I had to make some minor changes to the script to get it to work. > > > > I don't know, but you may want to implement the changes differently. > > Regardless, before you submit the final 90console script, I assume I need > > to figure out how to detect whether a graphics monitor is used as the > > console, as well as how the ATX workstation behaves. > > Hi Rolf, ... > > I have a question here. Is this a safe way to handle this ? The options > contain the variables of the OF, set by the user, but it is also > possible to boot directly from the OF command line, bypassing the values > found in options, or have special values passed from yaboot. On the > pegasos, but i suppose the same holds true for IBM power boxes, i know > it is even possible to pass these special values by the DHCP server. > > This would typically be done in a d-i install, where you want to > over-ride the defaults, without changing the real values. I know i have > done so myself. > > So, all in all, it is much better to do the same using the chosen > properties, which is what should be used on CHRP for this kind of > things, and is also said to be so in the CHRP spec. > > If you don't believe me, or otherwise ignore me, just ask someone with a > clue on this and they will tell you so.
I am not ignoring you, just slow at responding. I am getting input from folks that are not adding their comments to this bug, and I am no Open Firmware expert so it is taking me some time to wrap my head around this. But I am happy to change the script if you think I am not implenting the changes in the optimum way. $ ls -l /proc/device-tree/chosen/ total 16 -r--r--r-- 1 root root 19 2007-05-17 10:23 bootargs -r--r--r-- 1 root root 58 2007-05-17 10:23 bootpath -r--r--r-- 1 root root 4 2007-05-17 10:23 cpu -r--r--r-- 1 root root 40 2007-05-17 10:23 ibm,rpa-client-config -r--r--r-- 1 root root 8 2007-05-17 10:23 linux,initrd-end -r--r--r-- 1 root root 8 2007-05-17 10:23 linux,initrd-start -r--r--r-- 1 root root 8 2007-05-17 10:23 linux,kernel-end -r--r--r-- 1 root root 4 2007-05-17 10:23 linux,phandle -r--r--r-- 1 root root 4 2007-05-17 10:23 linux,stdout-package -r--r--r-- 1 root root 22 2007-05-17 10:23 linux,stdout-path -r--r--r-- 1 root root 4 2007-05-17 10:23 memory -r--r--r-- 1 root root 4 2007-05-17 10:23 mmu -r--r--r-- 1 root root 7 2007-05-17 10:23 name -r--r--r-- 1 root root 4 2007-05-17 10:23 nvram -r--r--r-- 1 root root 4 2007-05-17 10:23 stdin -r--r--r-- 1 root root 4 2007-05-17 10:23 stdout I see that the following two files report the node, so changing the script to use 'chosen' instead, and testing it on my hardware is no problem. $ cat /proc/device-tree/options/output-device /vdevice/[EMAIL PROTECTED] $ cat /proc/device-tree/chosen/linux,stdout-path /vdevice/[EMAIL PROTECTED] But I can not find an equivalent method in 'chosen' to determine whether the console is mapped to hvsi0 or hvc0. $ cat /proc/device-tree/vdevice/[EMAIL PROTECTED]/compatible hvterm-protocol Let me know what I should use. I can either modify the script myself or if you prefer you can send me a new one. Either way I can test it. > > Friendly, > > Sven Luther > > > >
