On Saturday 22 December 2007, Al Boldi wrote:
> Provided there is agreement, and we go with < >, it would mean a slight
> change to Host side USB, like this (note new USB Core Config sub-menu):
>
> --- Support for Host-side USB
> [ ] USB Core Config --->
Maybe. Let's see what you
David Brownell wrote:
> > > Which is why my suggestion was to have them both move up a level, with
> > > host and peripheral side menus nested normally:
> > >
> > > Device Drivers:
> > > ...
> > > [ ] HID devices
> > > < > Host side USB
> > > < > Peripheral
> > Which is why my suggestion was to have them both move up a level, with
> > host and peripheral side menus nested normally:
> >
> > Device Drivers:
> > ...
> > [ ] HID devices
> > < > Host side USB
> > < > Peripheral side USB
> > <
David Brownell wrote:
> > > The driver stacks are independent of each other, except for common
> > > data structures like what's in the header file. I
> > > think there's no real point, other than history, to having both sides
> > > share the same menu.
> >
> > They aren't.
>
> How can you say th
> > Notice that this whole menu is for "Host-side USB", except for that
> > gadget stuff. That might usefully be labeled as "Peripheral-side USB".
> >
> > For that matter, it could be moved up a level in the menu, so the top
> > level driver menu has two USB entries: Host side, and Peripheral sid
> >Propose new layout as follows:
>
> Yes, this has been done before in a lot of places, and attempts to
> clean up more menus is always welcome.
>
> Try to use 'menuconfig' objects so people can disable a whole menu
> at once without having to enter it, e.g. that USB Gadget thing down
> there.
No
On Dec 21 2007 16:30, Al Boldi wrote:
>
>The current USB Kconfig menu is rather cluttered and unorganized.
>
>Propose new layout as follows:
>
Yes, this has been done before in a lot of places, and attempts to
clean up more menus is always welcome.
Try to use 'menuconfig' objects so people can d
