From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Gamari Subject: Re: Unbuildable kernel with musb Date: Mon, 28 Mar 2011 10:40:38 -0400 Message-ID: <8739m7tijd.fsf@gmail.com> References: <87vcz5sd2x.fsf@gmail.com> <20110328083450.GD2251@legolas.emea.dhcp.ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: <20110328083450.GD2251-UiBtZHVXSwEVvW8u9ZQWYwjfymiNCTlR@public.gmane.org> Sender: linux-usb-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: balbi-l0cyMroinI0@public.gmane.org Cc: linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-omap List-Id: linux-omap@vger.kernel.org On Mon, 28 Mar 2011 11:34:51 +0300, Felipe Balbi wrote: > Hi, > > On Sat, Mar 26, 2011 at 06:59:18PM -0400, Ben Gamari wrote: > > Today I've been trying to work through the mess that is musb bring-up on > > recent kernels (v2.6.38). While I still haven't succeeded in getting a > > patches are welcome. > I'm working on it. Hopefully none will be necessary as this is all the fault of incorrect configuration. > > working gadget stack (modprobe g_ether fails with ENODEV), I've come > > across configuration where musb causes a link failure in 2.6.38 if built > > as a module: > > > > MODPOST 249 modules > > ERROR: "musb_read_fifo" [drivers/usb/musb/musb_hdrc.ko] undefined! > > > > Configuration attached. > > musb can't be built as module, I sent a patch making it bool recently > until we re-work those parts of the code. > Ahh good, thanks for that change! This should eliminate at least one nasty failure mode. - Ben -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html