Re: __BROKEN_CONFIG_UNIT_USAGE ?
David Young <dyoung <at> pobox.com>
2009-12-06 20:27:36 GMT
On Tue, Dec 01, 2009 at 05:52:44PM -0600, David Young wrote:
> On Tue, Dec 01, 2009 at 01:48:44PM -0800, Jason Thorpe wrote:
> > On Dec 1, 2009, at 12:46 PM, David Young wrote:
> > > On Tue, Dec 01, 2009 at 09:44:29PM +0100, Manuel Bouyer wrote:
> > >> On Mon, Nov 30, 2009 at 01:54:13PM -0600, David Young wrote:
> > >>> Only NetBSD/sun3 uses __BROKEN_CONFIG_UNIT_USAGE. The name of this
> > >>> mysterious #define, which affects which code in subr_autoconf.c is
> > >>> compiled, implies that sun3 is somehow "broken"? Will somebody fix it?
> > >>
> > >> So you know what is broken exactly ?
> > >
> > > No, I do not. I'm hoping that some NetBSD/sun3 developer knows.
> > The code makes assumptions about the behavior / relationships of
> > devices at fixed unit numbers. See sun3/sun3/vme.c:vme_match(),
> Can this magic in vme_match()
> #define VME_UNITS 6
> unit = cf->cf_unit;
> if (unit >= VME_UNITS)
> return 0;
> if (ca->ca_bustype != vme_info[unit].bustype)
> return 0;
> be avoided by creating a new locator, "bustype", and