Date: Fri, 12 Sep 2008 19:43:33 +0100 From: "Bruce M. Simpson" <bms@FreeBSD.org> To: Jeremy Chadwick <koitsu@FreeBSD.org> Cc: Chris Ruiz <chris@young-alumni.com>, FreeBSD stable <freebsd-stable@freebsd.org> Subject: Re: Any working ichsmb(4) platforms out there? Message-ID: <48CAB855.2020200@FreeBSD.org> In-Reply-To: <20080912183233.GA63271@icarus.home.lan> References: <48C927DC.6000202@incunabulum.net> <1EDB9C24-8E69-43D3-8082-2379955FF8FF@young-alumni.com> <20080912175749.GA62725@icarus.home.lan> <F2585A4F-9EC0-463E-9815-180BCED980B5@young-alumni.com> <20080912183233.GA63271@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeremy Chadwick wrote: > I don't consider this a "dependency issue" at all. These are all > literally separate things; you do not meed smbus(4) and smb(4) if you > just simply want to tie a driver to a feature/device that's on the PCI > bus (e.g. ichsmb(4)). > > Besides, does kldload or kernel modules in general have *any* sort > of dependency tree code? I didn't think they did. > Some modules do, some modules don't. One of the issues here is that there is sometimes a diamond-like dependency graph between kernel modules, or there is no way to establish dependency at all. For example, smb(4) has no idea that ichsmb(4) should be loaded, for the very reason you point out that smb(4) isn't needed by ichsmb(4); whilst ichsmb(4) presents an smbus(4) interface in the kernel, which smb(4) will recognise and attach to, it has no idea that it should get loaded. Having said that, I thought your plain language explanation of how things are was excellent and clear. cheers BMS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48CAB855.2020200>