Date: Fri, 08 Aug 2003 09:44:08 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: John Birrell <jb@cimlogic.com.au> Cc: ticso@cicely.de Subject: Re: How to get a device_t Message-ID: <6421.1060328648@critter.freebsd.dk> In-Reply-To: Your message of "Fri, 08 Aug 2003 08:36:17 %2B1000." <20030808083617.E7321@freebsd1.cimlogic.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20030808083617.E7321@freebsd1.cimlogic.com.au>, John Birrell writes : >I'm not convinced that any hacking is required other than passing the >device_t parent to nexus_pcib_is_host_bridge (in STABLE) as Bernd says. >I traced the boot on my system and the MMCR is initialised early (when >the Timecounter "ELAN" output occurs). Immediately following that >initialisation, 'pcib' is added as a child of 'nexus'. I don't see why >'mmcr' couldn't be added as a child of 'nexus' too. At this point, >nexus isn't walking through it's children so there shouldn't be a problem. >Then the ELAN specific devices (like GPIO and flash) can attach to 'mmcr'. > >This seems straight forward. Maybe I'm missing something. 8-) That's my take too. And MMCR belongs on nexus not on legacy from an architectural point of view. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6421.1060328648>