Roman Zippel wrote:
Hi,
On Thu, 15 Jan 2004, David Brownell wrote:
> choice values can also be tristate symbols, so you wouldn't need the
> separate defines, unless you really always want to compile only a
> single controller (even as module).
That's it precisely. USB devices have only one (up
Hi,
On Thu, 15 Jan 2004, David Brownell wrote:
> choice values can also be tristate symbols, so you wouldn't need the
> separate defines, unless you really always want to compile only a single
> controller (even as module).
That's it precisely. USB devices have only one (upstream) link;
they're
Roman Zippel wrote:
Hi,
On Mon, 29 Dec 2003, David Brownell wrote:
How about using this approach instead? It simplifies the kconfig
for the gadget drivers ..
There are some strange things in there.
Some of it was to kick the menu layout heuristic into something
closer to sanity. There was also
Hi,
On Mon, 29 Dec 2003, David Brownell wrote:
How about using this approach instead? It simplifies the kconfig
for the gadget drivers by providing a boolean "which hardware"
symbol, so gadget drivers don't need to make their own. The symbol
that's synthetic is the one needed only by the Makef
Hi David,
first of all sorry for my late answer.
I'm currently wading through a bunch of mails in my INBOX that should
have been answered some time ago. :-(
On Mon, Dec 29, 2003 at 07:54:29PM -0800, David Brownell wrote:
> Adrian Bunk wrote:
> >The patch below contains small changes to the US
Adrian Bunk wrote:
The patch below contains small changes to the USB Gadget Kconfig.
The main change is that multiple modular peripheral controllers are no
longer allowed (currently only one is there, but this may change).
How about using this approach instead? It simplifies the kconfig
for the
