I agree. While the relevance of the USB spec to most people is exactly
0%, the relevance to the USB portion of the kernel is almost exactly 0%
as well. I'd much rather cater to the USB developers since they're the
people who will be looking at those names, not anyone else.
Nonetheless, the current naming is a bit confusing.
> > Since we're talking about the other end of a "host" driver, "client" makes
> > sense - in computers, I've always seen "client" as the reverse of the
> > "host", but maybe that's just me.
>
> Another overloaded word. I've always seen it as the requestor,
> in all contexts (restaurants, stores, networking ... :) and in USB
> it's the "host" that requests.
Hmm, good point.
> > What were the other suggestions?
>
> Of the two I saw coming by this morning ("target" from Larry,
> and "gadget" from Stephen) I confess I liked "target" best.
> It captures the initating/responding roles quite well.
I agree too.
> I don't recall many other suggestions that were forthcoming.
>
> But I'll also toss out "firmware", which is often used in such
> contexts: firmware revision for a network adapter, and so on.
> "USB firmware" is not likely to be expected on the host side.
> "USB target firmware", and so on.
This can also be used too, although I typically picture smaller
controllers when it comes to firmware, whereas software runs on more
general purpose controllers, like the ones people would find running
embedded devices and thusly this software.
Anyway, my opinion is that "target" is the best term to use.
JE
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/