AHCI support in 6.1-RELEASE?

[Juha Saarinen]

On 10/10/06, Antony Mawer <fbsd-questions at mawer.org> wrote:
> Usually I find that ad0/ad1 = primary IDE (master/slave), ad2/3 =
> secondary IDE (master/slave), and then the SATA connectors pick up from
> ad4 onwards...
>
> The SATA ports seem to be numbered in increments of 2, presumably
> because every SATA port is a "master", so the usual "slave" position is
> unused... ie:
>
>      SATA 0 -> ad4
>      SATA 1 -> ad6
>      SATA 2 -> ad8
>      SATA 3 -> ad10

This is how it looks in dmesg now:

atapci0: <Intel ICH7 UDMA100 controller> port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f
at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0

atapci1: <Intel ICH7 SATA300 controller> port
0xd000-0xd007,0xd400-0xd403,0xd800-0xd807,0xdc00-0
xdc03,0xe000-0xe00f mem 0xe2307000-0xe23073ff irq 19 at device 31.2 on pci0
ata2: <ATA channel 0> on atapci1
ata3: <ATA channel 1> on atapci1
ata4: <ATA channel 2> on atapci1
ata5: <ATA channel 3> on atapci1

> Presumably turning off ATA_STATIC_ID would just number them in the
> sequential order (ad0, ad1, ad2, ...) based on the devices that are
> actually connected... but this can mess things up when you connect
> additional drives at a later date somewhere in the middle of the chain!
>
> I have a patch I wrote for sysinstall somewhere that allows you to do
> disk=auto in an install.cfg, and it picks the first device it comes
> across (eg. if ad4 is the first IDE disk, it picks it over ad10)...
> we've found this very handy for installation/deployment scenarios that
> are automated via install.cfg but may have different disk configurations...
>
> If there's enough interest I might look at submitting it for inclusion...

Could be useful...

-- 

Juha