true, android site gives steps to create boardconfig.mk for new product http://source.android.com/porting/build_new_device.html
this is good start and mandatory step for a product., but, as project evolve, to add product specific features, we keep updating these platform specific changes to BoardConfig.mk for eg, u can refer how our BoardConfig.mk evolved over period http://git.omapzoom.org/?p=device/ti/blaze.git;a=history;f=BoardConfig.mk;hb=froyo http://git.omapzoom.org/?p=device/ti/blaze.git;a=history;f=BoardConfig.mk;hb=gingerbread On Mon, Jan 24, 2011 at 10:57 AM, A Curtis <[email protected]> wrote: > Hello, > > Is there any documentation for BoardConfig.mk? > > I am porting Gingerbread to a new hardware platform. The porting > section of source.android.com has documentation on creating a new > hardware platform. However if you look at any of the sample devices > like htc/passion, it looks like there is a whole lot more to it... > > BTW: Why are the samples under devices but you create new platforms > under vendor? That took a while to figure out they were the same too. > > TIA > > -- > unsubscribe: [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
