Date: Thu, 14 May 2009 10:47:32 -0700 From: Oleksandr Tymoshenko <gonzo@freebsd.org> To: Stanislav Sedov <stas@FreeBSD.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r192059 - in head/sys: arm/at91 dev/spibus Message-ID: <4A0C5934.7060101@freebsd.org> In-Reply-To: <20090514002555.f56ba38b.stas@FreeBSD.org> References: <200905131842.n4DIgnnu064429@svn.freebsd.org> <20090514002555.f56ba38b.stas@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Stanislav Sedov wrote:
> On Wed, 13 May 2009 18:42:49 +0000 (UTC)
> Oleksandr Tymoshenko <gonzo@FreeBSD.org> mentioned:
>
.. skipped ..
>>
>
> On the other hand this driver appears to be machine-specific.
> What if one
> would like to have a kernel with several SPI bus drivers included for devices
> that doesn't support enumeration? In this case it will be impossible to
> diffirentiate these drivers in the hints file.
Could you elaborate on this? Completely different drivers
or several instances of the same driver? Use case is welcome.
dev/spibus is just abstraction that provides interface to child
devices. It can't be machine-specific. Bridge implementation
(at91_spi) is machine specific and implements actual hardware
access.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A0C5934.7060101>