Hi, On Wed, Oct 19, 2011 at 06:08:45PM +0530, Gupta, Ajay Kumar wrote: > > > You point holds good for a multiconfig compile and if people are OK > > > with this then no issue. > > > > why wouldn't they be ok ? It's not like there will be a gigantic amount > > of extra code in the kernel. You also have to remember that building > > always DRD support, allows for hacks like the Android Accessory > > Framework even on an uncertified OTG device. > > Things are fine from driver wise but the concern in the way mecuconfig > Would comeup in a single board config for boards with a host only > musb port. at the end of the day, we are targetting generic ARM kernels. So, in a few release cycles, we will, hopefully, be able to use make ARCH=arm allmodconfig, then have a very small kernel, with initramfs and a bunch of modules. In the long run, we will not have board-files in kernel even, so will you know if a particular board is host- or device-only ? See, what you're asking for, can't be done now and will just cause more problems in the long run. -- balbi
Attachment:
signature.asc
Description: Digital signature
