Subject: Re: OF and ethernet problems with 9600 upgrade
To: Daniel Eggert <firstname.lastname@example.org>
From: Patrick Welche <email@example.com>
Date: 04/25/2004 13:25:54
On Sun, Apr 25, 2004 at 12:35:14AM +0200, Daniel Eggert wrote:
> On 24. apr 2004, at 19:42, Riccardo Mottola wrote:
> >- OF acts stupidly and falls alwas to serial console! Annoying, to have
> >always a TE attached to the seral console.
> >output-device and input-device are correctly written inside nvram, as
> >"printenv" shows.
> >In fact making printenv and using those parameters with
> >" screen" output
> >" kbd" input
> >works. SO I don't understand what could go wrong...
> It resets back to ttya. Makes you wonder. You could set up your
> output-device and input-device in nvram, but i can't remember how that
At least you (Riccardo) have a TE to attach to the serial console.
I'm finding it harder and harder to find macs with serial ports for this,
which makes me wonder about how one could make a bootable CD which sets
OFW variables. In fact, why are those variables necessary?
Can someone clarify what happens when one boots from CD?
- we make a bootable cd with mkisofs -boot-hfs-file macppcboot.raw
? does this mean that the mac will run macppcboot.raw when it starts ?
? does ofw get a look in first and set bootpath to the CD ?
- macppcboot.raw means stand/bootxx/bootxx.c is run which reads the
/chosen/bootpath, or /options/boot-device variable
- so that it can read the 2nd stage boot
? is the 2nd stage ofwboot.xcf ?
- ofwboot.xcf in turn reads /chosen/bootpath and /chosen/bootargs,
Now the tantalising bit in stand/ofwboot/Locore.c:
#ifdef __notyet__ /* Has a bug on FirePower */
OF_setprop(int handle, char *prop, void *buf, int len)
A way of setting OFW variables?