removing hardcoded uart vbase

John Hay jhay at meraka.org.za
Mon May 28 20:16:54 UTC 2007


On Mon, May 28, 2007 at 12:10:58PM -0700, Marcel Moolenaar wrote:
> 
> On May 28, 2007, at 6:46 AM, John Hay wrote:
> 
> >To find the console, I just check for uart 0 in the hints. Is that
> >good enough or should one also check for flags 0x10 like on sio
> >devices?
> 
> Typically, you set uart.hw.console to point to the console. Since
> device numbers don't make sense, you define the console in terms of
> hardware I/O location. For example:
> 	uart.hw.console=io:0x3f8
> or
> 	uart.hw.console=mm:0xfef04500
> 
> The uart.hw.console variable also allows you to specify baudrate,
> stopbits, parity and the device class (ns8250, z8530, etc), which
> hints do not.
> 
> Hints are not recommended, unless you already have hints to
> describe the hardware. In that case you can simply add:
> 	hint.uart.0.flags=0x10

Well on the ixp425/avila we are moving to hints so that we can support
different boards easier. For instance both the Avila and Pronghorn Metro
boards use the same ixp425 cpu, which has 2 serial ports, but on the Avila
they decided to bring one serial port out and on the Pronghorn, the other.
:-)

So shall I then just run through the hints of the known number of serial
ports and look for the flags?

> The patch looks good to me.

Thanks.

John
-- 
John Hay -- John.Hay at meraka.csir.co.za / jhay at FreeBSD.org


More information about the freebsd-arm mailing list