We add few product files in .mk files like below

See
http://git.omapzoom.org/?p=device/ti/blaze.git;a=blob;f=blaze.mk;hb=refs/heads/froyo#l44<http://git.omapzoom.org/?p=device/ti/blaze.git;a=blob;f=blaze.mk;h=c7cc734f87d00e34e8c0d819ae711cfeec7501e1;hb=refs/heads/froyo#l44>

44<http://git.omapzoom.org/?p=device/ti/blaze.git;a=blob;f=blaze.mk;h=c7cc734f87d00e34e8c0d819ae711cfeec7501e1;hb=refs/heads/froyo#l44>PRODUCT_COPY_FILES
+= device/ti/blaze/apns.xml:system/etc/apns-conf.xml \
45<http://git.omapzoom.org/?p=device/ti/blaze.git;a=blob;f=blaze.mk;h=c7cc734f87d00e34e8c0d819ae711cfeec7501e1;hb=refs/heads/froyo#l45>
       
frameworks/base/data/etc/android.hardware.camera.flash-autofocus.xml:system/etc/permissions/android.hardware.camera.flash-autofocus.xml
\
46<http://git.omapzoom.org/?p=device/ti/blaze.git;a=blob;f=blaze.mk;h=c7cc734f87d00e34e8c0d819ae711cfeec7501e1;hb=refs/heads/froyo#l46>
       
packages/wallpapers/LivePicker/android.software.live_wallpaper.xml:/system/etc/permissions/android.software.live_wallpaper.xml
\
47<http://git.omapzoom.org/?p=device/ti/blaze.git;a=blob;f=blaze.mk;h=c7cc734f87d00e34e8c0d819ae711cfeec7501e1;hb=refs/heads/froyo#l47>
       
frameworks/base/data/etc/android.hardware.wifi.xml:system/etc/permissions/android.hardware.wifi.xml
\
48<http://git.omapzoom.org/?p=device/ti/blaze.git;a=blob;f=blaze.mk;h=c7cc734f87d00e34e8c0d819ae711cfeec7501e1;hb=refs/heads/froyo#l48>
       
frameworks/base/data/etc/android.hardware.touchscreen.multitouch.distinct.xml:system/etc/permissions/android.hardware.touchscreen.multitouch.distinct.xml


or like in opencore, you can do simple copy with some add call routine
(havent tried, but u can explore)
see
http://git.omapzoom.org/?p=platform/external/opencore.git;a=blob;f=Android.mk;hb=refs/heads/p-froyo#l9

9<http://git.omapzoom.org/?p=platform/external/opencore.git;a=blob;f=Android.mk;hb=refs/heads/p-froyo#l9>$(call
add-prebuilt-files, ETC, pvplayer.cfg)

On Tue, Dec 7, 2010 at 4:22 PM, hamleter <[email protected]> wrote:

> Hi all,
>
> I try to build divers which under \kernel\drivers into loadable
> modules (*.ko), how do I put these generated *.ko files into
> system.img?
> Currently, I push these files in ADB manually.
>
> Thanks.
>
> --
> unsubscribe: 
> [email protected]<android-porting%[email protected]>
> website: http://groups.google.com/group/android-porting
>



-- 
Regards,
Deva
www.bittoggler.com

-- 
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting

Reply via email to