[PATCH Try#2] introduce-fiq-hdq.patch

[Michael 'Mickey' Lauer]

Hi Andy,

On Thursday 14 February 2008 10:37:30 Andy Green wrote:
> Maybe you can help explain another branding anomoly since it seems you
> have a system in mind.
>
> The Kconfig I made for HDQ and bq27000 drivers uses the branding names,
> which makes sense to me, and this was accepted.  Can you articulate how
> that situation differed from the MODULE_DESCRIPTION case?

It's not different.

> Or you think 
> we should use GTA02 there?

From my point of view, yes we should use GTA02 there as well. The point is 
that the whole deal with marketing names is that they inherently 
unpredictable as opposed to board codenames.

It's your call as the one writing the code, of course, but in general I'd 
rather stick with only the board codenames as everything else is likely to 
introduce confusion sooner or later.

Look at the present sitation, first it was only one device, the GTA01. Then 
the marketing name Neo1973 came. Then GTA02 was planned and it was supposed 
to have the same name. Then the name FreeRunner came and Neo1973 now no 
longer was the name for a class of devices, but just one. Who knows what 
comes next? At the end of the day, not even the board codenames are something 
to rely on but the probability of changes there are much less.

So, If it was my call, I'd use FIC GTA01 and FIC GTA02 everywhere.

:M: