From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Best practice for loading platform modules
Date: Wed, 29 Apr 2009 19:25:31 +0000 [thread overview]
Message-ID: <20090429192531.GA15604@kroah.com> (raw)
In-Reply-To: <c4aed99f0904291105u1d4c0081qe91969a3ada64c96@mail.gmail.com>
On Wed, Apr 29, 2009 at 03:15:13PM -0400, Chris Hallinan wrote:
> On Wed, Apr 29, 2009 at 2:44 PM, Greg KH <greg@kroah.com> wrote:
> > On Wed, Apr 29, 2009 at 02:31:49PM -0400, Chris Hallinan wrote:
> >> On Wed, Apr 29, 2009 at 2:12 PM, Greg KH <greg@kroah.com> wrote:
> >> > On Wed, Apr 29, 2009 at 11:11:35AM -0700, Greg KH wrote:
> >> >> On Wed, Apr 29, 2009 at 02:05:37PM -0400, Chris Hallinan wrote:
> >> >> > I have an OMAP3 board, and want usb (host mode) configured as a
> >> >> > loadable module. Using a generic rule such as this:
> >> >> > RUN+="/sbin/modprobe -b $env{MODALIAS}"
> >> >> >
> >> >> > ends up passing "platform:musb_hdrc" to modprobe, which obviously
> >> >> > fails.
> >> >>
> >> >> Why would that fail? Do you have the proper modalias in the kernel
> >> >> module to handle this? If not, can you add it?
> >> >
> >> > I see:
> >> > MODULE_ALIAS("platform:" MUSB_DRIVER_NAME);
> >> > in the musb code, perhaps MUSB_DRIVER_NAME is not set correctly to be
> >> > "musb_hdrc" somehow?
> >>
> >> >From musb_core.c:
> >>
> >> #define MUSB_DRIVER_NAME "musb_hdrc"
> >> const char musb_driver_name[] = MUSB_DRIVER_NAME;
> >
> > Good, so you should be fine.
> >
> > Can you run:
> > modprobe -n -v platform:musb_hdrc
> > on your system?
> >
>
> # modprobe -n -v platform:musb_hdrc
> FATAL: Module platform:musb_hdrc not found.
> # modprobe --version
> module-init-tools version 3.7
>
> But...
>
> # modprobe -n -v musb_hdrc
> insmod /lib/modules/2.6.24_mvl5024/kernel/drivers/usb/core/usbcore.ko
> insmod /lib/modules/2.6.24_mvl5024/kernel/drivers/usb/musb/musb_hdrc.ko
>
> Seems to be complaining about the "platform:" prefix, I think. This
> is the very latest version of module-init-tools from git tree a couple
> days ago.
But your kernel is over a year old, not much we can do about that :)
I suggest poking your distro, it seems they need to provide a fix
for your kernel, nothing we can do here, everything works just fine with
the latest kernel releases from what I can tell.
good luck,
greg k-h
next prev parent reply other threads:[~2009-04-29 19:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 18:05 Best practice for loading platform modules Chris Hallinan
2009-04-29 18:11 ` Greg KH
2009-04-29 18:12 ` Greg KH
2009-04-29 18:31 ` Chris Hallinan
2009-04-29 18:44 ` Greg KH
2009-04-29 19:15 ` Chris Hallinan
2009-04-29 19:25 ` Greg KH [this message]
2009-04-29 19:33 ` Kay Sievers
2009-04-29 19:35 ` Chris Hallinan
2009-04-29 19:46 ` Kay Sievers
2009-04-29 19:53 ` Chris Hallinan
2009-04-29 20:18 ` Greg KH
2009-04-30 0:48 ` Chris Hallinan
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=20090429192531.GA15604@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.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).