-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 14 Jul 2012 09:32:17 +0100
Peter Robinson <pbrobinson(a)gmail.com> wrote:
On Sat, Jul 14, 2012 at 7:53 AM, Jon Masters
<jonathan(a)jonmasters.org> wrote:
> Folks,
>
> The latest F18 kernel is configured with CONFIG_MMC_OMAP_HS=m
> (which was previously configured as a builtin driver, as it
> probably should be). While in theory this would be working, it
> doesn't actually seem to result in dracut picking up the module as
> a necessary platform device. It is best fixed by building in the
> module again, which isn't happening because some other config
> option is forcing this to be modular too. I haven't tracked down
> what the other option was yet, feel free to help.
Interesting because the config bits don't appear to have changed:
CONFIG_MMC_OMAP=m
CONFIG_MMC_OMAP_HS=y
These two bits are the same on both kernels, maybe some more generic
config that's been moved around that's causing the regression.
> In the interim, the following dracut config fileis a workaround:
>
> # /etc/dracut.conf.d/omap_hsmmc.conf
> # Dracut is not picking up the platform device driver for the HSMMC
> # interface
>
> add_drivers+="omap_hsmmc"
So surely that's a bug in dracut that needs to detect that the module
is needed for booting.
Peter
Right this neeeds fixed in dracut. ill get patches sent in, and applied
to fedora in the mean time
Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
iEYEARECAAYFAlABca0ACgkQkSxm47BaWfdASQCgllRhk+M4MTYMC1E3kTP994HQ
afkAmgKpuDIKPwojTxXbGrE3DcX+9sHf
=X0ip
-----END PGP SIGNATURE-----