socfpga mmc (was Re: [GIT PULL] SOCFPGA DTS updates for 3.17)

[dinh.linux@gmail.com (Dinh Nguyen)]

On 8/14/14, 4:02 PM, Pavel Machek wrote:
> On Thu 2014-08-14 15:56:02, Dinh Nguyen wrote:
>>
>>
>> On 8/14/14, 1:47 PM, Pavel Machek wrote:
>>> Hi!
>>>
>>> I tried booting kernel based on ba36899, and got:
>>>
>>> mmc0: new SDHC card at address b368                                             
>>> mmcblk0: mmc0:b368 USD   7.45 GiB                                               
>>>  mmcblk0: p1 p2 p3 p4                                                           
>>> VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0): error
>>> -6        
>>> Please append a correct "root=" boot option; here are the available
>>> partitions: 
>>> b300         7822336 mmcblk0  driver: mmcblk                                    
>>>   b301          102400 mmcblk0p1 00082434-01                                    
>>>   b302         1048576 mmcblk0p2 00082434-02                                    
>>>   b303            1024 mmcblk0p3 00082434-03                                    
>>>   b304         6086656 mmcblk0p4 00082434-04                                    
>>> Kernel panic - not syncing: VFS: Unable to mount root fs on
>>> unknown-block(0,0)  
>>> CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.16.0-11208-gef74117-dirty
>>> #2        
>>
>> Hmm...today's tip-top(899552d6) and ba36899 booted just fine for me. I
>> noticed something, you must have commits on top of your ba36899? Mine
>> shows 3.16.0-11149-gba36899.
> 
> Ok, thanks for info. I went back to 3.16, and it worked in same
> config, and went to 3.17, and it broke.
> 
>> But just a thought, should one really be developing and debugging with
>> commits in a merge window?
> 
> Well, some people test -next :-). I must admit it was initially a
> mistake, but it is usually good to catch bugs ASAP.
> 

I see. Just booted linux-next and it booted fine and was able to mount
/dev/mmcblk0p2 as the RFS.

Dinh