.\" This manpage has been automatically generated by docbook2man 
.\" from a DocBook document.  This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
.\" Please send any bug reports, improvements, comments, patches, 
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "WALK_NATIVE_BUS" "" "06 October 2005" "" ""

.SH NAME
walk_native_bus \- - Probe a bus for devices
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
void walk_native_bus  (unsigned long \fIio_io_low\fB, unsigned long \fIio_io_high\fB, struct parisc_device * \fIparent\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIio_io_low\fB\fR
Base address of this bus.
.TP
\fB\fIio_io_high\fB\fR
Last address of this bus.
.TP
\fB\fIparent\fB\fR
The parent bus device.
.SH "DESCRIPTION"
.PP
A native bus (eg Runway or GSC) may have up to 64 devices on it,
spaced at intervals of 0x1000 bytes.  PDC may not inform us of these
devices, so we have to probe for them.  Unfortunately, we may find
devices which are not physically connected (such as extra serial &
keyboard ports).  This problem is not yet solved.