2010/12/13 Felipe Balbi <balbi@xxxxxx>: > On Mon, Dec 13, 2010 at 08:31:28PM +0800, Ming Lei wrote: >> >> 2010/12/13 Felipe Balbi <balbi@xxxxxx>: >>> >>> Hi, >>> >>> On Mon, Dec 13, 2010 at 07:46:20PM +0800, Ming Lei wrote: >>>> >>>> No, only modprobe musb-omap2430 is enough, which has been OK now in >>>> my beagle with this patch set. >>>> >>>> If we want to run one single binary to support multiple machines and >>>> if glue driver can't be built as module, we have to load all glue driver >>>> into >>>> ram, which is sure very ugly. >>> >>> glue layer's probe() won't be called as musb-XXXX won't be available. So >>> no resources will be used, right ? >> >> It is right, but the glue code without device may consume some memory and >> does nothing since it have to be loaded always. >> >> If we can build glue layer driver as module, it will be loaded until there >> has >> the musb-XXXX device. So I think we should support to build glue driver >> as module to reduce memory footprint. >> >> see size of glue modules built with this patch set in my beagle-xm: >> >> -rw-rw-r-- 1 500 500 132068 Dec 13 2010 am35x.ko >> -rw-rw-r-- 1 500 500 135279 Dec 13 2010 omap2430.ko >> -rw-rw-r-- 1 500 500 152696 Dec 13 2010 tusb6010.ko > > that's all on .init.text section, no ?!? then it'll be freed after we're > out of initcalls. No, only very few function/variables of glue driver is declared as __init, and is in .init section. Others will still stay in ram for ever. -- Lei Ming -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
