[U-Boot] MinnowBoard Max uboot

[Beaman, Thomas]

Hi Simon,

I have enclosed both kernel boot files

Thanks,
Tom

-----Original Message-----
From: sjg at google.com [mailto:sjg at google.com] On Behalf Of Simon Glass
Sent: Wednesday, June 10, 2015 9:15 PM
To: Beaman, Thomas
Cc: u-boot at lists.denx.de
Subject: Re: MinnowBoard Max uboot

Hi Thomas,

On 10 June 2015 at 12:38, Beaman, Thomas <Thomas.Beaman at xerox.com> wrote:
> Hi Simon,
>
> I have just picked up u-boot-2015.07-rc2 with your support for multiple CPUs on the minnowboard max. I can see using the uboot cpu list command that both CPUs now show up.  But the kernel does not see 2 CPUs in /proc/cpuinfo. If I boot the same kernel using an EFI BIOS I do see 2 CPUs in /proc/cpuinfo. Is there some uboot to kernel hand off I do not have configured properly ? I am not sure how the number of CPUs gets transferred from the boot to the kernel.
>
> Thanks for any input you may have.
> Tom
>
> => cpu list
>   0: cpu at 0              Intel(R) Atom(TM) CPU  E3825  @ 1.33GHz
>   1: cpu at 1              Intel(R) Atom(TM) CPU  E3825  @ 1.33GHz
>
> ## minnow max when booted from uboot 2015-07.rc2 root at atom_230:~# cat 
> /proc/cpuinfo | grep processor
> processor       : 0
>
> ## minnow max when booted from BIOS
> root at atom_230:~# cat /proc/cpuinfo | grep processor
> processor       : 0
> processor       : 1

Do you have the output from the kernel boot please?

Regards,
Simon

>
>
>
> -----Original Message-----
> From: sjg at google.com [mailto:sjg at google.com] On Behalf Of Simon Glass
> Sent: Tuesday, March 10, 2015 1:21 PM
> To: Beaman, Thomas
> Cc: u-boot at lists.denx.de; Bin Meng; gabriel huau
> Subject: Re: MinnowBoard Max uboot
>
> Hi Tom,
>
> On 10 March 2015 at 05:24, Beaman, Thomas <Thomas.Beaman at xerox.com> wrote:
>> Hi Simon,
>>
>> Do you know what will be the timeframe of when someone may be able to 
>> look at this in more detail. I will be able to help test any updates 
>> if needed
>>
>
> I will take a look once I have things lined up for the next release, likely mid April.
>
> Regards,
> Simon
>
>> Thanks,
>> Tom
>>
>> -----Original Message-----
>> From: sjg at google.com [mailto:sjg at google.com] On Behalf Of Simon Glass
>> Sent: Monday, March 09, 2015 11:49 AM
>> To: Beaman, Thomas
>> Cc: u-boot at lists.denx.de; Bin Meng; gabriel huau
>> Subject: Re: MinnowBoard Max uboot
>>
>> +Bin and Gabriel
>>
>> Hi Tom,
>>
>> On 9 March 2015 at 08:08, Beaman, Thomas <Thomas.Beaman at xerox.com> wrote:
>>>
>>>
>>> Hi Simon,
>>>
>>>
>>>
>>> I see you have put support for the MinnowBoard Max in the u-boot mainline.
>>> Thanks this is a very useful addition.  I have been able to follow 
>>> your readme and build a working bare metal uboot. Using the built 
>>> uboot I can load and bring up a Linux Kernel.
>>>
>>>
>>>
>>> What I noticed from the running kernel is that only one of the two 
>>> cores on the E3825 is running. In the power PC uboots I usually see 
>>> a section for the multiple cores in the .dts file. My questions is 
>>> how do I get both CPUs running on this board. Is it a uboot .dts 
>>> file setup that will enable this, or is something in the kernel start up that does this.
>>>
>>>
>>>
>>> As a test I boot the same kernel using the EFI BIOS on the minnow 
>>> board and both CPUs are running.
>>>
>>>
>>>
>>> Any suggestions or comments you have would be welcomed.
>>>
>>>
>>
>> My guess is that the LAPIC CPU start-up is missing. It isn't 100% clear what the FSP does and does not do, but perhaps it does not do that.
>>
>> I did make something of a start on this with ivybridge but it isn't complete, and it seems to be needed here.
>>
>> Regards,
>> Simon
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: minnowmaxBootEFI.txt
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150611/b4d8cc47/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: minnowmaxBootUboot.txt
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150611/b4d8cc47/attachment-0001.txt>