On Sun, 12 Nov 2000, Al B. Snell wrote:

> > > 2) How do I force the boot loader to not be confused by the BIOS claiming
> > > the serial port it's using for redirection is nonexistent? It's not a
> > > problem that I'm using bot serial ports (one for the BIOS, one for NetBSD)
> > > right now, but it'd be nice to be more gadget-efficient.
> > >
> > 	I think you need to hard code the probe for the first serial port.
>
> Yup. How? -DDIRECT_SERIAL?
>
	Uh, pass - see
	http://mail-index.netbsd.org/port-i386/2000/09/27/0011.html

> > 	The sparc port has a simple driver for an LED - it can blink it
> > 	to indicate machine load. It would be nice to have a more general
> > 	driver....
>
> Yeah, did you see my post about /dev/panel ideas? I'd use /dev/panel as
> the low level control for a front panel of any description, and then
> define an interface mapping machine states/variables to the particular
> lights on the panel - things like init would call "/sbin/panelctl --state
> running", and panel_state would look in /etc/panel.conf and find:
>
> state running {
> 	set_led status = power_on
> }
>
> /etc/panel.conf would also contain such gems as:
>
> kernel {
> 	sched_runq_led = u1
> }
>
> ...so the scheduler would light u1 whenever a process other than the ideal
> process was running, say. /etc/rc would run "/sbin/panelctl --config" to
> get panelctl to ioctl() /dev/panel to set up the kernel LED mappings,
> which would include states such as "kernel_panic"...

	Sound sinteresting - I assume that would be /dev/panel0 for the
	first panel and so on :)

	The best place to post such a suggestion would be on tech-kern.

                David/absolute
			       -- www.netbsd.org: A pmap for every occasion --