cvs commit: src/sys/conf files src/sys/dev/uart uart_cpu.h
uart_cpu_alpha.c uart_cpu_amd64.c uart_cpu_i386.c uart_cpu_ia64.c
uart_cpu_pc98.c uart_cpu_sparc64.c uart_subr.c
marcel at xcllnt.net
Sat Mar 20 12:16:16 PST 2004
On Sat, Mar 20, 2004 at 10:56:40AM -0800, John-Mark Gurney wrote:
> > > > The hw.uart.console and hw.uart.dbgport variables specify a list of
> > > > attributes. An attribute is a tag-value pair, seperated by a colon.
> > > > Attributes are seperated by a comma. Where possible, tags are the
> > > > same as those in /etc/remote (only br and pa in practice). Details
> > > > can be found in the manpage (not part of this commit).
> > >
> > > I don't see how this prevents problems with probe order suddenly changing
> > > and you don't have the same console you thought you had... also, how
> > > do you handle this before devfs is up?
> > Probe order is irrelevant if you specify the device by its I/O port
> > or memory mapped I/O address. When you need to pinpoint a device
> > prior to any form of bus enumeration, the unit number is meaningless
> > and any mechanism that includes a unit number is bogus. That's why
> > hints are the wrong tool for pinpointing a console or debug port.
> I hope that you don't have to specify the console via io/memory port..
Yes you have. This is no different than hints, except that you set
flags in that case to tell uart(4) that the device is to be used as
a console or debug port. But you still need to specify the I/O port
because without it your hint is bogus.
Marcel Moolenaar USPA: A-39004 marcel at xcllnt.net
More information about the cvs-all