Date: Tue, 23 Apr 2013 09:33:19 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Jeremy Chadwick <jdc@koitsu.org> Cc: Tom Evans <tevans.uk@googlemail.com>, freebsd-stable@freebsd.org Subject: Re: ada(4) and ahci(4) quirk printing Message-ID: <CAJ-VmomN27_XTc9Zg-otcL1rsn0Ka08erwsuxRn38F=cox6_Zg@mail.gmail.com> In-Reply-To: <20130423134953.GA64010@icarus.home.lan> References: <20130422051452.GA2148@icarus.home.lan> <51763BF9.2000506@FreeBSD.org> <20130423092602.GA58831@icarus.home.lan> <51765466.4040209@FreeBSD.org> <4D28DBAE46424C268AA22FCDD8657946@multiplay.co.uk> <20130423114722.GA61919@icarus.home.lan> <CC7BB743D5AB4312BB3A0FE37AC1C566@multiplay.co.uk> <20130423125144.GA62949@icarus.home.lan> <CAFHbX1JPhfeZMv5t=jLr_2xHVz5XSrhq7Nipd-Qg7xfT%2Boo7nA@mail.gmail.com> <20130423134953.GA64010@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
.. are we really debating this? Stop calling them quirks. That sounds like something that won't mess up your actual runtime. It's not giving them enough "weight". They're more "device behaviours" or "device flags" or something. Print them out like that. I think that _not_ printing them out at boot time is insane. Doubly so if it could cause issues before you can actually run commands. So if it were me, I'd print out the device quirks like we print out CPU flags. Ie, all the time. Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomN27_XTc9Zg-otcL1rsn0Ka08erwsuxRn38F=cox6_Zg>