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

[Andy Green]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:
> 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.

Completely agree.

>> Or you think 
>> we should use GTA02 there?
> 
> From my point of view, yes we should use GTA02 there as well. The point is 

I certainly agree if we use GTA02 for the MODULE_DESCRIPTION case, we
must logically use it in the Kconfig case.  So what's everyone else doing?

$ for i in `find . -name Kconfig` ; do cat $i >>/tmp/allconfig ; done

Marketing names I recognized:

h8300
Linux/SH64
config SUPERH
config SUPERH64
prompt "SuperH system type"
config SH64_USER_MISALIGNED_FIXUP
config S390_SWITCH_AMODE
<snip large number of *S390*>
config MARCH_G5
config AVR32
        def_bool y
        # With EMBEDDED=n, we get lots of stuff automatically selected
        # that we usually don't need on AVR32.
        select EMBEDDED
        help
          AVR32 is a high-performance 32-bit RISC microprocessor core,
          designed for cost-sensitive embedded applications, with particular
          emphasis on low power consumption and high code density.

          There is an AVR32 Linux project with a web page at
          http://avr32linux.org/.
config CPU_AT32AP7000
<snip *PARISC* >
config HPUX
config SPARC
config SPARC32
config ISA
config EISA
config MCA
config PCMCIA
config SBUS
config PPC_BESTCOMM
          BestComm is the name of the communication coprocessor found
<snipped more>
mainmenu "Linux/PowerPC Kernel Configuration"
config LINKSTATION
        bool "Linkstation / Kurobox(HG) from Buffalo"
        depends on EMBEDDED6xx
        select MPIC
        select FSL_SOC
        select PPC_UDBG_16550 if SERIAL_8250
        select DEFAULT_UIMAGE
        help
          Select LINKSTATION if configuring for one of PPC- (MPC8241)
          based NAS systems from Buffalo Technology. So far only
          KuroboxHG has been tested. In the future classical Kurobox,
          Linkstation-I HD-HLAN and HD-HGLAN versions, and PPC-based
          Terastation systems should be supported too.
config MPC7448HPC2
        bool "Freescale MPC7448HPC2(Taiga)"
config XILINX_VIRTEX_GENERIC_BOARD
        bool "Generic Xilinx Virtex board"
config PPC_IBM_CELL_BLADE
        bool "IBM Cell Blade"
        depends on PPC_MULTIPLATFORM && PPC64
mainmenu "Linux/UltraSPARC Kernel Configuration"
config SPARC64
        bool
        default y
        help
          SPARC is a family of RISC microprocessors designed and marketed by
          Sun Microsystems, incorporated.  This port covers the newer 64-bit
          UltraSPARC.  The UltraLinux project maintains both the SPARC32 and
          SPARC64 ports; its web page is available at
          <http://www.ultralinux.org/>.
config ALTIVEC
        bool "AltiVec Support"
        depends on 6xx
        depends on !8260 && !83xx
        ---help---
          This option enables kernel support for the Altivec extensions
to the
          PowerPC processor. The kernel currently supports saving and
restoring
          altivec registers, and turning on the 'altivec enable' bit so user
          processes can execute altivec instructions.
config RPXLITE
        bool "RPX-Lite"
        ---help---
          Single-board computers based around the PowerPC MPC8xx chips and
          intended for embedded applications.  The following types are
          supported:

          RPX-Lite:
          Embedded Planet RPX Lite. PC104 form-factor SBC based on the
MPC823.

          RPX-Classic:
          Embedded Planet RPX Classic Low-fat. Credit-card-size SBC based on
          the MPC 860

          BSE-IP:
          Bright Star Engineering ip-Engine.
<got bored here, jumped ahead to the drivers section oh no wait>
config AMIGA
config ATARI
        bool "Atari support"
        depends on !MMU_SUN3
        help
          This option enables support for the 68000-based Atari series of
          computers (including the TT, Falcon and Medusa). If you plan
to use
config MAC
        bool "Macintosh support"
        depends on !MMU_SUN3
        help
          This option enables support for the Apple Macintosh series of
          computers (yes, there is experimental support now, at least
for part
config WR_PPMC
        bool "Wind River PPMC board"
<manfully ignore MIPS* stuff>
config MACH_POODLE
        bool "Enable Sharp SL-5600 (Poodle) Support"
config MACH_CORGI
        bool "Enable Sharp SL-C700 (Corgi) Support"
config MACH_SHEPHERD
        bool "Enable Sharp SL-C750 (Shepherd) Support"
config MACH_HUSKY
        bool "Enable Sharp SL-C760 (Husky) Support"
config MACH_AKITA
        bool "Enable Sharp SL-1000 (Akita) Support"
config MACH_SPITZ
        bool "Enable Sharp Zaurus SL-3000 (Spitz) Support"
config MACH_BORZOI
        bool "Enable Sharp Zaurus SL-3100 (Borzoi) Support"
config MACH_TOSA
        bool "Enable Sharp SL-6000x (Tosa) Support"

LOL


  config MACH_HXD8
        bool "FIC HXD8"
        select CPU_S3C2440
        select SENSORS_PCF50606
        help
           Say Y here if you are using the FIC Neo1973 GSM Phone

config MACH_NEO1973_GTA02
        bool "FIC Neo1973 GSM Phone (GTA02 Hardware)"
        select CPU_S3C2442
        select SENSORS_PCF50633
        select POWER_SUPPLY
        select GTA02_HDQ
        help
           Say Y here if you are using the FIC Neo1973 GSM Phone

config NEO1973_GTA02_2440
        bool "Old FIC Neo1973 GTA02 hardware using S3C2440 CPU"
        depends on MACH_NEO1973_GTA02
        select CPU_S3C2440
        help
           Say Y here if you are using an early hardware revision
           of the FIC/OpenMoko Neo1973 GTA02 GSM Phone.


Oh well I got up to about 30% of it and I didn't find "Diamond RIO" I
was looking for.  Oh yeah

config USB_RIO500
        tristate "USB Diamond Rio500 support (EXPERIMENTAL)"
        depends on USB && EXPERIMENTAL
        help
          Say Y here if you want to connect a USB Rio500 mp3 player to your
          computer's USB port. Please read <file:Documentation/usb/rio.txt>
          for more information.

          To compile this driver as a module, choose M here: the
          module will be called rio500.

The point is once you *start* marketing something the name is sticky and
you can use it where you like.  Now they decided this thing is "Neo
Freerunner" and publish the name, we can go ahead and use it and GTAxx
buys us NOTHING.

> that the whole deal with marketing names is that they inherently 
> unpredictable as opposed to board codenames.

> 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.

No its much more irretrievably messed up than that, because if we
introduce a feature at GTAxx it gets tagged as GTAxx forever even when
it turns out it exists in GTA(xx+1), etc and so on.

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

I appreciate consistency!  But in fact the solution here is to not name
features under the GTAxx classification.

- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFHtbAdOjLpvpq7dMoRAhkNAJ9fldV/846OZLyIYem++WK/f0T30wCeMRMz
3nvN7onxvPmKsh2asK/5MpU=
=sDAS
-----END PGP SIGNATURE-----