[U-Boot] MinnowBoard Max uboot

[Simon Glass]

Hi,

On 19 June 2015 at 09:21, Simon Glass <sjg at chromium.org> wrote:
> Hi Thomas,
>
> On 19 June 2015 at 09:17, Beaman, Thomas <Thomas.Beaman at xerox.com> wrote:
>> Hi Bin,
>>
>> I have tried both suggestions and the kernel boot still hangs in the same place. I have enclosed a snipit from boot that shows the command line.
>>
>> Thanks,
>> Tom
>>
>> -----Original Message-----
>> From: Bin Meng [mailto:bmeng.cn at gmail.com]
>> Sent: Thursday, June 18, 2015 9:16 PM
>> To: Beaman, Thomas
>> Cc: Simon Glass; u-boot at lists.denx.de
>> Subject: Re: [U-Boot] MinnowBoard Max uboot
>>
>>> Can you try typing 'run ramboot' on the U-Boot shell to load linux kernel? Or below ...
>>
>>> Or append acpi=off to the kernel command line manually, to see how it goes.
>>
>>
>> => run ramboot
>> Using RTL8169#0 device
>> TFTP from server 10.40.101.102; our IP address is 10.40.101.244
>> Filename 'atom_64/kernel'.
>> Load address: 0x10000000
>> Loading: ##################################################  5.6 MiB
>>          3.6 MiB/s
>> done
>> Bytes transferred = 5861312 (596fc0 hex)
>> Using RTL8169#0 device
>> TFTP from server 10.40.101.102; our IP address is 10.40.101.244
>> Filename 'atom_64/ramdisk'.
>> Load address: 0x20000000
>> Loading: ##################################################  29.1 MiB
>>          3.5 MiB/s
>> done
>> Bytes transferred = 30497951 (1d15c9f hex)
>> Valid Boot Flag
>> Setup Size = 0x00003e00
>> Magic signature found
>> Using boot protocol version 2.0c
>> Linux kernel version 3.10.62-ltsi-WR6.0.0.20_standard (tbeaman at wocket) #1 SMP PREEMPT Wed Jun 17 15:19:47 EDT 2015
>> Building boot_params at 0x00090000
>> Loading bzImage at address 100000 (5845440 bytes)
>> Magic signature found
>> Initial RAM disk at linear address 0x20000000, size 30497951 bytes
>> Kernel command line: "root=/dev/ram rw ip=10.40.101.244:10.40.101.102::255.255.255.0:x86:eth0:off console=ttyS0,115200 acpi=off ramdisk_size=300000"
>>
>> Starting kernel ...
>>
>
> I'll see if I can repeat this.  I recall that last time I tested it it
> appeared to hang, but in fact the machine was running (just without a
> Linux console).
>
> Regards,
> Simon

Just to follow up, my guess is that this is caused by interrupts not
being set up correctly.

I sent some patches to tidy this up along with an RFC for the
interrupts part itself. Since then Bin has sent a better patch. So I
am going to try this again and I suspect this will be resolved in
u-boot-x86 within two weeks.

Regards,
Simon