Date: Thu, 8 Aug 2019 15:12:52 -0600 From: Warner Losh <imp@bsdimp.com> To: Ed Maste <emaste@freebsd.org> Cc: Warner Losh <imp@freebsd.org>, src-committers <src-committers@freebsd.org>, svn-src-all <svn-src-all@freebsd.org>, svn-src-head <svn-src-head@freebsd.org> Subject: Re: svn commit: r350678 - head/share/mk Message-ID: <CANCZdfoe2EabZ6shNToU1BmPV15KUNNnWt=TAbB7bysUx9FU=w@mail.gmail.com> In-Reply-To: <CAPyFy2DRtMRs7xTYFPPYhp7OFQHA5eADPrRaLW__=smotkQ7Tw@mail.gmail.com> References: <201908071619.x77GJ6qq067924@repo.freebsd.org> <CAPyFy2DRtMRs7xTYFPPYhp7OFQHA5eADPrRaLW__=smotkQ7Tw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 8, 2019 at 1:49 PM Ed Maste <emaste@freebsd.org> wrote: > On Wed, 7 Aug 2019 at 12:19, Warner Losh <imp@freebsd.org> wrote: > > > > Author: imp > > Date: Wed Aug 7 16:19:06 2019 > > New Revision: 350678 > > URL: https://svnweb.freebsd.org/changeset/base/350678 > > > > Log: > > Enable nvme on aarch64 > > > > Don't mark nvme as broken on aarch64. It compiles, at least, and > people are > > testing it out. This only enables the userland parts of the nvme stack. > > For BROKEN_OPTIONS we should probably list the archs where it is known > to be broken instead? > Generally. At first, this was known working only on x86 due to how the driver was written, so it made sense to whitelist. We're likely getting close to black-listing in this case. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfoe2EabZ6shNToU1BmPV15KUNNnWt=TAbB7bysUx9FU=w>