From owner-svn-src-all@FreeBSD.ORG Thu May 14 18:27:01 2009 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2524A106564A; Thu, 14 May 2009 18:27:00 +0000 (UTC) (envelope-from gonzo@freebsd.org) Received: from core.tav.kiev.ua (tavex.colocall.com [62.149.10.42]) by mx1.freebsd.org (Postfix) with ESMTP id 739068FC08; Thu, 14 May 2009 18:27:00 +0000 (UTC) (envelope-from gonzo@freebsd.org) Received: from [76.77.86.2] (helo=[10.80.5.136]) by core.tav.kiev.ua with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.52 (FreeBSD)) id 1M4f29-000CY5-NW; Thu, 14 May 2009 20:47:54 +0300 Message-ID: <4A0C5934.7060101@freebsd.org> Date: Thu, 14 May 2009 10:47:32 -0700 From: Oleksandr Tymoshenko User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Stanislav Sedov References: <200905131842.n4DIgnnu064429@svn.freebsd.org> <20090514002555.f56ba38b.stas@FreeBSD.org> In-Reply-To: <20090514002555.f56ba38b.stas@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Core-Spam-Level: / X-Core-Spam-Report: Spam detection software, running on the system "core.tav.kiev.ua", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Stanislav Sedov wrote: > On Wed, 13 May 2009 18:42:49 +0000 (UTC) > Oleksandr Tymoshenko 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. [...] Content analysis details: (-0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.0 BAYES_50 BODY: Bayesian spam probability is 40 to 60% [score: 0.5000] 1.8 AWL AWL: From: address is in the auto white-list 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 X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2009 18:27:01 -0000 Stanislav Sedov wrote: > On Wed, 13 May 2009 18:42:49 +0000 (UTC) > Oleksandr Tymoshenko 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.