platform_build/target/board/generic
Doug Zongker e01100c7ac generalize the definition of a "radio image"
Non-HTC devices may have multiple files constituting their "radio
image".  Generalize the INSTALLED_RADIOIMAGE_TARGET variable a bit:
initially define it as empty, then let AndroidBoard.mk files add to
it.  Provide a convenience function add-radio-image for them to call
to add files.  Put all those files into the target_files zip for use
in OTA and fastboot package construction.

Note that for HTC devices, this changes the name of the radio image in
the target_files zip:  instead of "RADIO/image" it will be
"RADIO/radio.img".  Tools that use the target_files zip will need to
be changed.
2009-06-22 17:46:19 -07:00
..
AndroidBoard.mk auto import from //depot/cupcake/@135843 2009-03-03 19:28:42 -08:00
BoardConfig.mk generalize the definition of a "radio image" 2009-06-22 17:46:19 -07:00
README.txt auto import from //depot/cupcake/@135843 2009-03-03 19:28:42 -08:00
system.prop auto import from //depot/cupcake/@135843 2009-03-03 19:28:42 -08:00
tuttle2.kcm auto import from //depot/cupcake/@135843 2009-03-03 19:28:42 -08:00
tuttle2.kl auto import from //depot/cupcake/@135843 2009-03-03 19:28:42 -08:00

The "generic" product defines a non-hardware-specific target
without a kernel or bootloader.

It can be used to build the entire user-level system, and
will work with the emulator, though sound will not work
(see the "emulator" product for that).

It is not a product "base class"; no other products inherit
from it or use it in any way.