Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 3 Dec 2015 11:40:57 -0700
From:      Warner Losh <imp@bsdimp.com>
To:        Andrew Turner <andrew@freebsd.org>
Cc:        src-committers <src-committers@freebsd.org>,  "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>,  "svn-src-head@freebsd.org" <svn-src-head@freebsd.org>
Subject:   Re: svn commit: r291689 - in head/sys: conf dev/ahci
Message-ID:  <CANCZdfochAv%2BDMBs3kAc9s034HP1eUQ9JY1BWuw7jMA1ba-98w@mail.gmail.com>
In-Reply-To: <201512031124.tB3BOBRu070023@repo.freebsd.org>
References:  <201512031124.tB3BOBRu070023@repo.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 3, 2015 at 4:24 AM, Andrew Turner <andrew@freebsd.org> wrote:

> Author: andrew
> Date: Thu Dec  3 11:24:11 2015
> New Revision: 291689
> URL: https://svnweb.freebsd.org/changeset/base/291689
>
> Log:
>   Add support for a generic AHCI attachment. This allows us to attach to a
>   typically memory mapped bus, for example on the AMD Opteron A1100 the
> AHCI
>   device is mapped in the CPUs address space, and not through a PCI
>   controller.
>
>   Further work is needed for this to work with ACPI as this is expected to
> be
>   common on ARMv8 servers.
>

We've created a few front ends for a10 and imx6 already. These require
special
handling of the environment to setup things properly based on implementation
specific registers, clocks, gpios, etc. In the arm64 world, is it
anticipated that
we won't need to do those things?

Would it be better to name this ahci_acpi.c instead then? I'd exepect with
an
acpi attachment, there'd be some ACPI-specific things needed.

Warner



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfochAv%2BDMBs3kAc9s034HP1eUQ9JY1BWuw7jMA1ba-98w>