you can hack generic.mk to have a working build, or if you need to
maintain you better create "device/<vendor-name>/<platform>" directory
to keep platform/board configuration files.

samples
http://git.omapzoom.org/?p=device/ti/blaze.git;a=tree;h=refs/heads/froyo;hb=froyo
http://git.omapzoom.org/?p=device/ti/zoom2.git;a=tree;h=refs/heads/froyo;hb=froyo

detailed steps for new platform -
http://source.android.com/porting/build_new_device.html

regarding ambiguity of device or vendor folder -> you can use either
as of ur choice,
as per ./build/core/config.mk

# Boards may be defined under $(SRC_TARGET_DIR)/board/$(TARGET_DEVICE)
# or under vendor/*/$(TARGET_DEVICE).  Search in both places, but
# make sure only one exists.
# Real boards should always be associated with an OEM vendor.
board_config_mk := \
        $(strip $(wildcard \
                $(SRC_TARGET_DIR)/board/$(TARGET_DEVICE)/BoardConfig.mk \
                device/*/$(TARGET_DEVICE)/BoardConfig.mk \
                vendor/*/$(TARGET_DEVICE)/BoardConfig.mk \
        ))



On Mon, Jan 17, 2011 at 8:52 AM,  <lakshman.b...@gmail.com> wrote:
> Thank you very much. It helped. I need to bring it up but in any case I have
> the build at least.
> lb
>
> On Jan 16, 2011 1:41pm, Subramani Venkatesh <subbu31m...@gmail.com> wrote:
>> You can use  Omapzoom, rowboat or tegra development trees as reference,
>>
>>
>> In particular give importance to device and vendor directory, you will
>>
>>
>> get most of  information to port to new hardware.
>>
>>
>>
>>
>>
>> here are the links
>>
>>
>>
>>
>>
>> www.omapzoom.org
>>
>>
>> http://code.google.com/p/rowboat/wiki/Source?tm=4
>>
>>
>> http://android.git.kernel.org/?p=kernel/tegra.git;a=summary
>>
>>
>>
>>
>>
>> -Subbu
>>
>>
>> On Sun, Jan 16, 2011 at 12:03 PM, lb lakshman.b...@gmail.com> wrote:
>>
>>
>> > Hi All,
>>
>>
>> > After long struggle I was able to compile kernel and generic android
>>
>>
>> > for my new hardware independently.
>>
>>
>> > I took a peek at the generic.mk and I realized I need a different kind
>>
>>
>> > of configuration to use the kernel that I compiled. By searching in
>>
>>
>> > google I found that one is telling create a partner directory and
>>
>>
>> > other is telling vendor directory.
>>
>>
>> > Is there a sample configuration that I can use as a baseline?
>>
>>
>> > Thanks a lot for all your helps.
>>
>>
>> > -lb
>>
>>
>> >
>>
>>
>> > --
>>
>>
>> > unsubscribe: android-porting+unsubscr...@googlegroups.com
>>
>>
>> > website: http://groups.google.com/group/android-porting
>>
>>
>> >
>>
>>
>>
>
> --
> unsubscribe: android-porting+unsubscr...@googlegroups.com
> website: http://groups.google.com/group/android-porting
>



-- 
Regards,
Deva
www.bittoggler.com

-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

Reply via email to