Date: Sat, 12 Oct 2019 20:42:39 -0700 From: Scott Long <scottl@samsco.org> To: rgrimes@freebsd.org Cc: Scott Long <scottl@freebsd.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r353456 - head/usr.sbin/pciconf Message-ID: <33AA1D39-CA5B-4AE1-BD1F-A12D1F0DE508@samsco.org> In-Reply-To: <201910130210.x9D2AokR097894@gndrsh.dnsmgr.net> References: <201910130210.x9D2AokR097894@gndrsh.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Oct 12, 2019, at 7:10 PM, Rodney W. Grimes <freebsd@gndrsh.dnsmgr.net> wrote: > >> Author: scottl >> Date: Sat Oct 12 22:27:57 2019 >> New Revision: 353456 >> URL: https://svnweb.freebsd.org/changeset/base/353456 >> >> Log: >> Change from the non-standard nomenclature of "chip" and "card" to the >> standard nomenclature of "device" and "vendor" with the "sub" variants. >> This changes the printed format, so anything that scrapes and parses >> this will need to be adapted. No compatibility shims are provided, >> but this will not be MFC'd. > > I can not "adapt" google easily, seaching for these strings are > often very usefull in finding stuff like bug reports and ohers > with similiar issues. I am not sure the gain of this is positive > over the loss of that. It’s never too early to change bad habits =-) Every time I write a driver, or even just evaluate an existing driver against new hardware (which happens frequently for me now, you should have been at my talk yesterday), I stumble over the non-standard nomenclature. It doesn’t match the published spec, it doesn’t match the kernel API, and it doesn’t match any other OS. John, Warner, and I have been talking about this for at least 10 years, and it was time to rip off the band-aid and just do it. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?33AA1D39-CA5B-4AE1-BD1F-A12D1F0DE508>