On Fri, 2014-03-21 at 08:53 -0500, Robert Nelson wrote:
On Fri, Mar 21, 2014 at 8:33 AM, Peter Robinson
<pbrobinson(a)gmail.com> wrote:
>>> I admit I gave up too easily yesterday, built a Robert Nelson 3.12.13
>>> and got my F20 image going with that. After I got running, I did update
>>> the Fedora kernel to current 3.13.6 and tried to boot that. Same
>>> problem, mmc driver not loading. I'll try to get to the bottom of this
>>> afternoon. I'll diff the fedora/RN kernel config and see if anything
>>> jumps out. If not, I'll start looking at am3* dts/dtsi files....
>>>
>>> Robert, if you're reading this, don't suppose you can point me in
the
>>> direction of where to start looking? ;)
>>
>> v3.13.x pretty much works out of the box, so no dts/dtsi changes are
necessary..
>>
>> I'd first start looking at make sure the mmc driver is setup:
>>
>> CONFIG_TI_EDMA=y
>> CONFIG_DMA_ENGINE=y
>
> We've always had that, the BBBlack wouldn't work without it either and
> the BBBlack works fine. It's like it needs a different regulator or
> something.
Okay, that's weirder then. They both share the same tps65217
regulator. The black has one regulator (ldo3_reg) that's different,
but it should be taken care of in the dts.
Thanks, Robert.
tps65217 was the clue I needed. Fedora config has it building as a
module. But the module is not included in the initramfs, so not
available at boot time.
Solution: Either rebuild the Fedora kernel with
"CONFIG_REGULATOR_TPS65217=y" or edit /etc/dracut.conf, 'add_drivers
+="tps65217-regulator"' and rebuild initramfs/uinitrd, gets the Fedora
kernel booting.
Now need to figure out where the power management has gone. I suspect
your kernels have it built-in and Fedora has "CONFIG_XXX=m", so more
module nonsense.
Regards
Clive
--
Clive Messer <clive.m.messer(a)gmail.com>