linux-kernel - Re: musb as module broken in 2.6.38

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110316090327.GA2325@legolas.emea.dhcp.ti.com>
Date:	Wed, 16 Mar 2011 11:03:28 +0200
From:	Felipe Balbi <balbi@...com>
To:	Alexander Holler <holler@...oftware.de>
Cc:	balbi@...com, linux-kernel@...r.kernel.org,
	linux-usb@...r.kernel.org
Subject: Re: musb as module broken in 2.6.38

Hi,

On Wed, Mar 16, 2011 at 02:55:53AM +0100, Alexander Holler wrote:
> in commit dc09886bfa781e2b442301116c18199519e36f0f the name of the
> platform-driver was splitted and musb-omap2430 is used for several
> boards (arch/arm/mach-omap2/usb-musb.c).
> 
> But musb_hdrc still uses musb-hdrc as name when
> platform_driver_probe() is called. The result is that loading the
> driver (when build as a module) doesn't work anymore (it doesn't find
> the platform-device).
> 
> Do I miss something or was something forgotten when the glue-layers
> for musb got introduced?
> 
> (The driver still works when linked into the kernel, but is
> disfunctional when build as a module.)

Send me the output you get on console and a snippet of the .config with
the MUSB section.

-- 
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/