Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 May 2005 14:47:31 +0000 (UTC)
From:      Marius Strobl <marius@FreeBSD.org>
To:        src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   cvs commit: src/sys/sparc64/sbus sbus.c sbusvar.h
Message-ID:  <200505191447.j4JElVMA041756@repoman.freebsd.org>

next in thread | raw e-mail | index | archive | help
marius      2005-05-19 14:47:31 UTC

  FreeBSD src repository

  Modified files:
    sys/sparc64/sbus     sbus.c sbusvar.h 
  Log:
  - Add an IVAR for retrieving the interrupt group number of the parent Sbus
    device and which also applies to the children. This is very usefull for
    drivers for the various subordinate busses so they don't need to fiddle
    with the OFW node of their parent themselves. As SBus busses hang of the
    nexus and we don't use the ofw_bus interface for nexus devices, yet, this
    would also require special knowledge about this in the drivers for the
    SBus children which these shouldn't need to have.
    This includes switching to use an unshifted IGN in the sc_ign member of
    the sbus(4) softc internally.
  - For SBus child devices where there are variants that are actually split
    split into two SBus devices (as opposed to the first half of the device
    being a SBus device and the second half hanging off of the first one)
    like 'auxio' and 'SUNW,fdtwo' or 'dma' and 'esp' probe the SBus device
    which is a prerequisite to the driver attaching to the second one with
    a lower order. This saves us from dealing with different probe orders
    in the respective device drivers which generally is more hackish.
  - Remove a stale comment about the 'specials' array above the attaching
    of the child devices. This is a remnant of the NetBSD/sparc origin of
    this code. There the 'specials' array is also used to probe certain
    devices which are prerequisites to others first. Why NetBSD soley
    relies on the devices having the expected order in the OFW tree on
    sparc64 isn't clear to me, as far as I can tell OFW doesn't guaranteed
    such things.
  
  Revision  Changes    Path
  1.35      +47 -9     src/sys/sparc64/sbus/sbus.c
  1.6       +8 -0      src/sys/sparc64/sbus/sbusvar.h



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200505191447.j4JElVMA041756>