On Tue, 14 Jun 2011, Felipe Balbi wrote: > > --- a/drivers/usb/gadget/Makefile > > +++ b/drivers/usb/gadget/Makefile > > @@ -34,6 +34,12 @@ obj-$(CONFIG_USB_FUSB300) += fusb300_udc.o > > # USB gadget drivers > > # > > g_zero-y := zero.o > > +g_zero-y += composite.o > > +g_zero-y += usbstring.o > > +g_zero-y += config.o > > +g_zero-y += epautoconf.o > > +g_zero-y += f_sourcesink.o > > +g_zero-y += f_loopback.o > > yes, you can do that. But the problem is the runtime memory footprint > that we will have with that. At least that was the reason why Greg had > asked Dave to change it to how it is done now. What exactly is the runtime memory footprint problem? I thought the whole reason for #include'ing .c files was that back then, the kbuild system wasn't able to do this. > Do we support gcc --combine already ? As far as I know, the only advantage of gcc -combine is that it allows the optimizer to work on more than one file at a time. Would that really make any significant difference for these particular source files? Alan Stern -- 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
