ocpbus(4)

M. Warner Losh imp at bsdimp.com
Fri Dec 28 12:10:00 PST 2007


In message: <20071228.130329.43010549.imp at bsdimp.com>
            "M. Warner Losh" <imp at bsdimp.com> writes:
: In message: <C95AFF48-2C06-40FA-BDB4-C46011EECCF3 at juniper.net>
:             Marcel Moolenaar <marcelm at juniper.net> writes:
: : On Dec 28, 2007, at 11:12 AM, M. Warner Losh wrote:
: : 
: : > If the ocpbus has a table of bus types, what's wrong with having it
: : > directly assign the driver when it ads its children?
: : 
: : It violates newbus in that drivers compete for a device.
: : If the bus assigns the driver, then there's no competition
: : possible. The fact that the bus is abstract should not
: : mean that we should change its paradigm.
: 
: No it doesn't.  There's two kinds of busses in newbus.  Those that
: self enumerate based on the hardware present (ie pccard, pci, usb,
: firewire) and then those that are told what's there (oldcard-style
: pccard, pure ISA, I2C, etc).  The busses on the SoC more strongly
: resemble the latter than the former.  The former busses already are
: enumerated with hints, but the actual mechanism is just a few calls
: that could be replaced with something better.

Just a correction... 'The latter busses already are already..."



More information about the freebsd-embedded mailing list