ada(4) and ahci(4) quirk printing

Jeremy Chadwick jdc at
Tue Apr 23 13:49:55 UTC 2013

On Tue, Apr 23, 2013 at 02:15:31PM +0100, Tom Evans wrote:
> On Tue, Apr 23, 2013 at 1:51 PM, Jeremy Chadwick <jdc at> wrote:
> > On Tue, Apr 23, 2013 at 01:20:31PM +0100, Steven Hartland wrote:
> >> >4) camcontrol wouldn't address the need/interest for ahci(4) quirks to
> >> >be made available.
> >>
> >> Why?
> >
> > Because camcontrol is for CAM.  ahci(4) is not part of CAM.  The last
> > place I'd look for "poking at AHCI" (as in *actual AHCI*) is camcontrol.
> >
> > This is one of the reasons sysctl exists -- it's a sort of "covers
> > everything" tree, on a per-device basis.
> Just on this point, these quirks aren't actually quirks of ahci(4) are
> they? They are quirks of the disks that are attached to ahci(4), and
> presumably should apply regardless of whether the disk in question is
> hooked up to ahci(4), siis(4) or even mps(4).

There are two patches: one prints ada(4) (disk) quirks, the other prints
ahci(4) (controller) quirks.  These are two separate/unrelated things.

> To my mind, this means the quirks should belong to da(4), or at the
> very least ada(4). ada(4) and da(4) are both manipulated by CAM, so
> having this in camcontrol seems logical to me. To clarify, my mind is
> completely oblivious of how all this is implemented in software, so
> perhaps my mind needs to be changed rather than the code!

| Jeremy Chadwick                                   jdc at |
| UNIX Systems Administrator       |
| Mountain View, CA, US                                            |
| Making life hard for others since 1977.             PGP 4BD6C0CB |

More information about the freebsd-stable mailing list