linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi-l0cyMroinI0@public.gmane.org>
To: Ben Gamari <bgamari-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-omap <linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Unbuildable kernel with musb
Date: Mon, 28 Mar 2011 11:34:51 +0300	[thread overview]
Message-ID: <20110328083450.GD2251@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <87vcz5sd2x.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

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.

> 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.

-- 
balbi
--
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

  parent reply	other threads:[~2011-03-28  8:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-26 22:59 Unbuildable kernel with musb Ben Gamari
     [not found] ` <87vcz5sd2x.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-03-28  8:34   ` Felipe Balbi [this message]
     [not found]     ` <20110328083450.GD2251-UiBtZHVXSwEVvW8u9ZQWYwjfymiNCTlR@public.gmane.org>
2011-03-28 14:40       ` Ben Gamari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110328083450.GD2251@legolas.emea.dhcp.ti.com \
    --to=balbi-l0cymroini0@public.gmane.org \
    --cc=bgamari-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).