From owner-freebsd-questions@freebsd.org  Thu Dec 29 16:35:35 2016
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id B48C4C95701
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Thu, 29 Dec 2016 16:35:35 +0000 (UTC)
 (envelope-from freebsd@omnilan.de)
Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 3C18918A8;
 Thu, 29 Dec 2016 16:35:35 +0000 (UTC)
 (envelope-from freebsd@omnilan.de)
Received: from mh0.gentlemail.de (ezra.dcm1.omnilan.net
 [IPv6:2a00:e10:2800::a135])
 by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id uBTGZWR2086449;
 Thu, 29 Dec 2016 17:35:32 +0100 (CET)
 (envelope-from freebsd@omnilan.de)
Received: from titan.inop.mo1.omnilan.net (titan.inop.mo1.omnilan.net
 [IPv6:2001:a60:f0bb:1::3:1])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mh0.gentlemail.de (Postfix) with ESMTPSA id 4748B423;
 Thu, 29 Dec 2016 17:35:32 +0100 (CET)
Message-ID: <58653B53.9000503@omnilan.de>
Date: Thu, 29 Dec 2016 17:35:31 +0100
From: Harry Schmalzbauer <freebsd@omnilan.de>
Organization: OmniLAN
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE;
 rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2
MIME-Version: 1.0
To: freebsd-questions@freebsd.org
Subject: Disable driver attaching by PCI slot
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7
 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]);
 Thu, 29 Dec 2016 17:35:32 +0100 (CET)
X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: ;
 Sender-helo: mh0.gentlemail.de; )
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Dec 2016 16:35:35 -0000

 Hello,

I have machines where an additional SATA controller is populated.
Unfortunately, ahcich numbering violates private conventions, since the
addon card is detected first and occupies ahci0 (the onboard controller
will become ahci1 and hard wired [local default] device numbering via
device.hints fails on these machines – there are several reasons not to
alter local standard device.hints...)
Setting hint.ahci.0.disabled="1" obviously is no good idea. Haven't
tried, but I guess this will disable both controllers...

One suitable way is to attach ppt to the card in question (like
pptdevs="0/25/0").
But that means vmm must be loaded/available.
And requires detaching ppt from the device before assigning the ahci
driver (by devctl(8)).

Is there a way to influence probing order by PCI slot?
Or at least disabling driver attachment by PCI slot?

Thanks,

-harry