Date: Mon, 20 Jul 2009 14:05:34 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Andre Albsmeier <Andre.Albsmeier@siemens.com> Cc: freebsd-hackers@freebsd.org, Rui Paulo <rpaulo@freebsd.org>, Julian Elischer <julian@elischer.org> Subject: Re: Reading acpi memory from a driver attached to hostb Message-ID: <4A644F7E.2000107@icyb.net.ua> In-Reply-To: <4A61D6FB.2090904@elischer.org> References: <20090717190450.GA4697@curry.mchp.siemens.de> <4A60D6D1.3050703@elischer.org> <20090718081011.GA6920@curry.mchp.siemens.de> <4A61D6FB.2090904@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
on 18/07/2009 17:06 Julian Elischer said the following: > Andre Albsmeier wrote: >> But in order to attach to acpi0, I need to say >> >> DRIVER_MODULE( eccmon, acpi, eccmon_driver, eccmon_devclass, NULL, >> NULL ); >> >> instead of >> >> DRIVER_MODULE( eccmon, hostb, eccmon_driver, eccmon_devclass, NULL, >> NULL ); > > try both with different devclass and other args. Just to expand on Julian's words. You can create eccmon and e.g. eccmon_acpi such that they are different drivers (on different buses) in newbus sense, but logically they can share data or otherwise cooperate. /sys/dev/cpufreq/ichss.c prior to rev. 177041 used to be like that. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A644F7E.2000107>