From owner-freebsd-current@FreeBSD.ORG Mon Feb 9 08:24:40 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1B640106564A; Mon, 9 Feb 2009 08:24:40 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.swip.net [212.247.154.193]) by mx1.freebsd.org (Postfix) with ESMTP id BF4988FC19; Mon, 9 Feb 2009 08:24:38 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=8UcZu9N6atoA:10 a=rZF0ZLlPMY8A:10 a=OnW5LBC3fXBS4YDd7W4A:9 a=vU1u5jrEdvucmjNbPeMWpbf5_YMA:4 a=WY4ZyggBrbsA:10 a=MSl-tDqOz04A:10 a=SV7veod9ZcQA:10 a=LY0hPdMaydYA:10 Received: from [193.217.167.198] (account mc467741@c2i.net HELO [10.0.0.249]) by mailfe07.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 1191090215; Mon, 09 Feb 2009 09:24:37 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Mon, 9 Feb 2009 09:27:03 +0100 User-Agent: KMail/1.9.7 References: <20090206045349.GQ78804@elvis.mu.org> <7d6fde3d0902081940o3ffd8ea1m6f59d65ee59d57ff@mail.gmail.com> In-Reply-To: <7d6fde3d0902081940o3ffd8ea1m6f59d65ee59d57ff@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200902090927.04378.hselasky@c2i.net> Cc: current@freebsd.org, usb@freebsd.org, Sam Leffler , Maksim Yevmenkin , Garrett Cooper , Gavin Atkinson Subject: Re: HEADSUP usb2/usb4bsd to become default in GENERIC X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2009 08:24:40 -0000 On Monday 09 February 2009, Garrett Cooper wrote: > On Sun, Feb 8, 2009 at 7:17 PM, Maksim Yevmenkin > > wrote: > > On Sun, Feb 8, 2009 at 11:12 AM, Sam Leffler wrote: > > > > [...] > > > >>>>>> - Update GENERIC to use usb2 device names. > >>>>> > >>>>> Wasn't there a plan to rename usb2 devices to match oldusb names > >>>>> (where applicable) once oldusb had been killed? I don't see it in t= he > >>>>> list. > >>>> > >>>> Probably, although coming from the other side as a user I find it > >>>> pretty annoying when there's somewhat gratuitous changes to the kern= el > >>>> config files that I don't really care about that cause my kernels to > >>>> break. > >>> > >>> The vast majority of our users do not run -CURRENT, and so haven't had > >>> to change config files yet. > >>> > >>> One day, those users will be migrating from 7.x to 8.x, and shouldn't > >>> need to change their kernel config for a "somewhat gratuitous change". > >>> > >>> Your argument only works if people had already had to change their > >>> config files once (usb -> usb2), and that by renaming these back they > >>> will have to change their kernel config back. Only people running > >>> -CURRENT will end up having to do this twice (or indeed at all) if the > >>> rename takes place, end users will not need to do it at all. > >>> > >>>> Basically, calling it usb2 isn't as bad as renaming it back to "usb" > >>>> as it's less disruptive in my book. > >>> > >>> Again, I disagree. > >> > >> I agree with your comments. And, as I've said previously, any name > >> changes from usb1 will require _all_ documentation (manual pages, > >> handbook, etc) to change; not a good idea. > > > > i second that. i would really like to see old module names to be > > preserved as much as possible. > > > > thanks, > > max > > In some cases I find the new module names to be more intuitive > (uplcom -> usb2_serial_plcom), but I find having to add the additional > modules required for USB4BSD (usb2_core, etc) to be a bit more > annoying. > Also, there's an issue with the example USB2 kernel config -- you > need to have double-quotes around the include file otherwise config > says `syntax error' and pukes. How about symlinking the old module names with the new ones? And the same in the kernel, so that device uplcom Is equivalent to device usb2_serial_plcom =46rom what I understand the "conf/files" syntax allows this. Not sure abou= t=20 KMODs, if there is a LINK option. =2D-HPS