HEADSUP usb2/usb4bsd to become default in GENERIC

[Hans Petter Selasky]

On Monday 09 February 2009, Garrett Cooper wrote:
> On Sun, Feb 8, 2009 at 7:17 PM, Maksim Yevmenkin
>
> <maksim.yevmenkin at gmail.com> wrote:
> > On Sun, Feb 8, 2009 at 11:12 AM, Sam Leffler <sam at freebsd.org> 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 the
> >>>>> list.
> >>>>
> >>>> Probably, although coming from the other side as a user I find it
> >>>> pretty annoying when there's somewhat gratuitous changes to the kernel
> >>>> 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

From what I understand the "conf/files" syntax allows this. Not sure about 
KMODs, if there is a LINK option.

--HPS