Re: [U-Boot] MinnowBoard Max uboot

2015-08-03 Thread Simon Glass
Hi,

On 19 June 2015 at 09:21, Simon Glass s...@chromium.org wrote:
 Hi Thomas,

 On 19 June 2015 at 09:17, Beaman, Thomas thomas.bea...@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...@gmail.com]
 Sent: Thursday, June 18, 2015 9:16 PM
 To: Beaman, Thomas
 Cc: Simon Glass; u-boot@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: 0x1000
 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: 0x2000
 Loading: ##  29.1 MiB
  3.5 MiB/s
 done
 Bytes transferred = 30497951 (1d15c9f hex)
 Valid Boot Flag
 Setup Size = 0x3e00
 Magic signature found
 Using boot protocol version 2.0c
 Linux kernel version 3.10.62-ltsi-WR6.0.0.20_standard (tbeaman@wocket) #1 
 SMP PREEMPT Wed Jun 17 15:19:47 EDT 2015
 Building boot_params at 0x0009
 Loading bzImage at address 10 (5845440 bytes)
 Magic signature found
 Initial RAM disk at linear address 0x2000, 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=30

 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
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] MinnowBoard Max uboot

2015-08-03 Thread Beaman, Thomas

-Original Message-
From: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
Sent: Monday, August 03, 2015 2:52 PM
To: Beaman, Thomas
Cc: Bin Meng; u-boot@lists.denx.de
Subject: Re: [U-Boot] MinnowBoard Max uboot

Hi,

On 19 June 2015 at 09:21, Simon Glass s...@chromium.org wrote:
 Hi Thomas,

 On 19 June 2015 at 09:17, Beaman, Thomas thomas.bea...@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...@gmail.com]
 Sent: Thursday, June 18, 2015 9:16 PM
 To: Beaman, Thomas
 Cc: Simon Glass; u-boot@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: 0x1000
 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: 0x2000
 Loading: ##  29.1 MiB
  3.5 MiB/s
 done
 Bytes transferred = 30497951 (1d15c9f hex) Valid Boot Flag Setup Size 
 = 0x3e00 Magic signature found Using boot protocol version 2.0c 
 Linux kernel version 3.10.62-ltsi-WR6.0.0.20_standard 
 (tbeaman@wocket) #1 SMP PREEMPT Wed Jun 17 15:19:47 EDT 2015 Building 
 boot_params at 0x0009 Loading bzImage at address 10 (5845440 
 bytes) Magic signature found Initial RAM disk at linear address 
 0x2000, 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=30

 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


Thank you for the status update. If you let me know when this is updated,  I 
will do some additional testing.

Regards,
Tom


___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] MinnowBoard Max uboot

2015-06-19 Thread Simon Glass
Hi Thomas,

On 19 June 2015 at 09:17, Beaman, Thomas thomas.bea...@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...@gmail.com]
 Sent: Thursday, June 18, 2015 9:16 PM
 To: Beaman, Thomas
 Cc: Simon Glass; u-boot@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: 0x1000
 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: 0x2000
 Loading: ##  29.1 MiB
  3.5 MiB/s
 done
 Bytes transferred = 30497951 (1d15c9f hex)
 Valid Boot Flag
 Setup Size = 0x3e00
 Magic signature found
 Using boot protocol version 2.0c
 Linux kernel version 3.10.62-ltsi-WR6.0.0.20_standard (tbeaman@wocket) #1 SMP 
 PREEMPT Wed Jun 17 15:19:47 EDT 2015
 Building boot_params at 0x0009
 Loading bzImage at address 10 (5845440 bytes)
 Magic signature found
 Initial RAM disk at linear address 0x2000, 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=30

 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
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] MinnowBoard Max uboot

2015-06-19 Thread Beaman, Thomas
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...@gmail.com] 
Sent: Thursday, June 18, 2015 9:16 PM
To: Beaman, Thomas
Cc: Simon Glass; u-boot@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: 0x1000
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: 0x2000
Loading: ##  29.1 MiB
 3.5 MiB/s
done
Bytes transferred = 30497951 (1d15c9f hex)
Valid Boot Flag
Setup Size = 0x3e00
Magic signature found
Using boot protocol version 2.0c
Linux kernel version 3.10.62-ltsi-WR6.0.0.20_standard (tbeaman@wocket) #1 SMP 
PREEMPT Wed Jun 17 15:19:47 EDT 2015
Building boot_params at 0x0009
Loading bzImage at address 10 (5845440 bytes)
Magic signature found
Initial RAM disk at linear address 0x2000, 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=30

Starting kernel ...

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] MinnowBoard Max uboot

2015-06-18 Thread Beaman, Thomas
Hi Bin,

After adding CONFIG_SFI=y to the kernel config, I was able to see both CPUs in 
the kernel boot, but now the kernel hangs at boot time. It did not hang when 
CONFIG_SFI was not set.  and if I boot the CONFIG_SFI=y kernel using EFI BIOS 
it does not hang either.  I have repeated the test a few times with the same 
results each time. I have enclosed the kernel boot log if you can see anything, 
or have any more suggestions.

Thanks,
Tom

*** kernel bootlog  *

U-Boot 2015.07-rc2 (Jun 10 2015 - 09:48:35 -0400)
gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-9)
GNU ld version 2.23.52.0.1-16.el7 20130226

bootargs= root=/dev/ram rw ramdisk_size=30  console=ttyS0,115200
Using RTL8169#0 device
TFTP from server 10.40.101.102; our IP address is 10.40.101.212
Filename 'atom_64/kernel'.
Load address: 0x1000
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.212
Filename 'atom_64/ramdisk'.
Load address: 0x2000
Loading: ##  29.1 MiB
 3.6 MiB/s
done
Bytes transferred = 30497951 (1d15c9f hex)
Valid Boot Flag
Setup Size = 0x3e00
Magic signature found
Using boot protocol version 2.0c
Linux kernel version 3.10.62-ltsi-WR6.0.0.20_standard (tbeaman@wocket) #1 SMP 
PREEMPT Wed Jun 17 15:19:47 EDT 2015
Building boot_params at 0x0009
Loading bzImage at address 10 (5845440 bytes)
Magic signature found
Initial RAM disk at linear address 0x2000, size 67108864 bytes
Kernel command line:  root=/dev/ram rw ramdisk_size=30  
console=ttyS0,115200

Starting kernel ...

Timer summary in microseconds:
   MarkElapsed  Stage
  0  0  reset
107,427107,427  board_init_r
  1,946,048  1,838,621  id=64
  1,948,082  2,034  id=65
  1,954,410  6,328  main_loop
  7,960,693  6,006,283  id=80
  7,960,695  2  eth_start
  7,960,825130  bootp_start
  8,947,233986,408  bootp_stop
  8,947,240  7  id=81
  8,947,376136  id=82
  8,967,941 20,565  tftp_start
 10,541,240  1,573,299  id=84
 10,541,242  2  tftp_done
 18,606,478  8,065,236  start_kernel

Accumulated time:
   330,199  ahci
 1,388,929  vesa display
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Initializing cgroup subsys cpuacct
Linux version 3.10.62-ltsi-WR6.0.0.20_standard (tbeaman@wocket) (gcc version 
4.8.1 (Wind River Linux Sourcery CodeBench 4.8-44) ) #1 SMP PREEMPT Wed Jun 17 
15:19:47 EDT 2015
Command line:  root=/dev/ram rw ramdisk_size=30  console=ttyS0,115200
KERNEL supported cpus:
  Intel GenuineIntel
  AMD AuthenticAMD
  Centaur CentaurHauls
e820: BIOS-provided physical RAM map:
BIOS-e820: [mem 0x-0x0009] usable
BIOS-e820: [mem 0x000a-0x000f] reserved
BIOS-e820: [mem 0x0010-0x7adf] usable
BIOS-e820: [mem 0x7ae0-0x7fff] reserved
NX (Execute Disable) protection: active
DMI not present or invalid.
No AGP bridge found
e820: last_pfn = 0x7ae00 max_arch_pfn = 0x4
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
__next_free_mem_range: Usage of MAX_NUMNODES is depricated. Use NUMA_NO_NODE 
instead
Scanning 1 areas for low memory corruption
init_memory_mapping: [mem 0x-0x000f]
init_memory_mapping: [mem 0x7ac0-0x7adf]
init_memory_mapping: [mem 0x7800-0x7abf]
init_memory_mapping: [mem 0x0010-0x77ff]
RAMDISK: [mem 0x2000-0x23ff]
ACPI BIOS Bug: Error: A valid RSDP was not found (20130328/tbxfroot-218)
No NUMA configuration found
Faking a node at [mem 0x-0x7adf]
Initmem setup node 0 [mem 0x-0x7adf]
  NODE_DATA [mem 0x7adfe000-0x7adf]
Zone ranges:
  DMA  [mem 0x1000-0x00ff]
  DMA32[mem 0x0100-0x]
  Normal   empty
Movable zone start for each node
Early memory node ranges
  node   0: [mem 0x1000-0x0009]
  node   0: [mem 0x0010-0x7adf]
x86/hpet: Will disable the HPET for this platform because it's not reliable
SFI: Simple Firmware Interface v0.81 http://simplefirmware.org
SFI: SYST F0070, 0030 (v1 U-Boot Table v1)
SFI: CPUS F, 0020 (v1 U-Boot Table v1)
SFI: APIC F0020, 0020 (v1 U-Boot Table v1)
SFI: XSDT F0040, 0024 (v1 U-Boot Table v1)
SFI: registering lapic[0]
SFI: registering lapic[4]
IOAPIC[0]: apic_id 0, version 32, address 0xfec0, GSI 0-86
smpboot: Allowing 2 CPUs, 0 hotplug CPUs
PM: Registered nosave memory: 000a - 0010
e820: [mem 0x8000-0x] available for PCI devices
setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:2 nr_node_ids:1
PERCPU: Embedded 26 pages/cpu @88007aa0 s76352 r8192 d21952 u1048576
Built 1 zonelists in Node order, mobility grouping on.  Total pages: 495313
Policy zone: DMA32

Re: [U-Boot] MinnowBoard Max uboot

2015-06-18 Thread Bin Meng
Hi Tom,

On Thu, Jun 18, 2015 at 9:07 PM, Beaman, Thomas thomas.bea...@xerox.com wrote:
 Hi Bin,

 After adding CONFIG_SFI=y to the kernel config, I was able to see both CPUs 
 in the kernel boot, but now the kernel hangs at boot time. It did not hang 
 when CONFIG_SFI was not set.  and if I boot the CONFIG_SFI=y kernel using EFI 
 BIOS it does not hang either.  I have repeated the test a few times with the 
 same results each time. I have enclosed the kernel boot log if you can see 
 anything, or have any more suggestions.

 Thanks,
 Tom

 *** kernel bootlog  *

 U-Boot 2015.07-rc2 (Jun 10 2015 - 09:48:35 -0400)
 gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-9)
 GNU ld version 2.23.52.0.1-16.el7 20130226

 bootargs= root=/dev/ram rw ramdisk_size=30  console=ttyS0,115200

Can you try typing 'run ramboot' on the U-Boot shell to load linux
kernel? Or below ...

 Using RTL8169#0 device
 TFTP from server 10.40.101.102; our IP address is 10.40.101.212
 Filename 'atom_64/kernel'.
 Load address: 0x1000
 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.212
 Filename 'atom_64/ramdisk'.
 Load address: 0x2000
 Loading: ##  29.1 MiB
  3.6 MiB/s
 done
 Bytes transferred = 30497951 (1d15c9f hex)
 Valid Boot Flag
 Setup Size = 0x3e00
 Magic signature found
 Using boot protocol version 2.0c
 Linux kernel version 3.10.62-ltsi-WR6.0.0.20_standard (tbeaman@wocket) #1 SMP 
 PREEMPT Wed Jun 17 15:19:47 EDT 2015
 Building boot_params at 0x0009
 Loading bzImage at address 10 (5845440 bytes)
 Magic signature found
 Initial RAM disk at linear address 0x2000, size 67108864 bytes
 Kernel command line:  root=/dev/ram rw ramdisk_size=30  
 console=ttyS0,115200

Or append acpi=off to the kernel command line manually, to see how it goes.

[snip]

Regards,
Bin
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] MinnowBoard Max uboot

2015-06-12 Thread Bin Meng
Hi Tom,

On Thu, Jun 11, 2015 at 11:02 PM, Beaman, Thomas
thomas.bea...@xerox.com wrote:
 Hi Simon,

 I have enclosed both kernel boot files

 Thanks,
 Tom


Please stop top-posting.

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

 Hi Thomas,

 On 10 June 2015 at 12:38, Beaman, Thomas thomas.bea...@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@0  Intel(R) Atom(TM) CPU  E3825  @ 1.33GHz
   1: cpu@1  Intel(R) Atom(TM) CPU  E3825  @ 1.33GHz

 ## minnow max when booted from uboot 2015-07.rc2 root@atom_230:~# cat
 /proc/cpuinfo | grep processor
 processor   : 0

 ## minnow max when booted from BIOS
 root@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: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
 Sent: Tuesday, March 10, 2015 1:21 PM
 To: Beaman, Thomas
 Cc: u-boot@lists.denx.de; Bin Meng; gabriel huau
 Subject: Re: MinnowBoard Max uboot

 Hi Tom,

 On 10 March 2015 at 05:24, Beaman, Thomas thomas.bea...@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: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
 Sent: Monday, March 09, 2015 11:49 AM
 To: Beaman, Thomas
 Cc: u-boot@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.bea...@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


I've checked your kernel log, and it turns out that you did not turn
on CONFIG_SFI in your kernel build. Please make sure CONFIG_SFI=y to
build the kernel and have a try.

Regards,
Bin
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] MinnowBoard Max uboot

2015-06-11 Thread Beaman, Thomas
Hi Simon,

I have enclosed both kernel boot files

Thanks,
Tom

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

Hi Thomas,

On 10 June 2015 at 12:38, Beaman, Thomas thomas.bea...@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@0  Intel(R) Atom(TM) CPU  E3825  @ 1.33GHz
   1: cpu@1  Intel(R) Atom(TM) CPU  E3825  @ 1.33GHz

 ## minnow max when booted from uboot 2015-07.rc2 root@atom_230:~# cat 
 /proc/cpuinfo | grep processor
 processor   : 0

 ## minnow max when booted from BIOS
 root@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: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
 Sent: Tuesday, March 10, 2015 1:21 PM
 To: Beaman, Thomas
 Cc: u-boot@lists.denx.de; Bin Meng; gabriel huau
 Subject: Re: MinnowBoard Max uboot

 Hi Tom,

 On 10 March 2015 at 05:24, Beaman, Thomas thomas.bea...@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: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
 Sent: Monday, March 09, 2015 11:49 AM
 To: Beaman, Thomas
 Cc: u-boot@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.bea...@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




  Booting `minnow max'

error: no suitable video mode found.
Booting in blind mode
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Initializing cgroup subsys cpuacct
Linux version 3.10.55-ltsi-WR6.0.0.16_standard (tbeaman@varelse) (gcc version 
4.8.1 (Wind River Linux Sourcery CodeBench 4.8-40) ) #1 SMP PREEMPT Thu Feb 19 
15:50:54 EST 2015
Command line: BOOT_IMAGE=(memdisk)/boot/grub/netboot.bzImage 
console=ttyS0,115200n8 ramdisk_size=30
KERNEL supported cpus:
  Intel GenuineIntel
  AMD AuthenticAMD
  Centaur CentaurHauls
e820: BIOS-provided physical RAM map:
BIOS-e820: [mem 0x-0x0008efff] usable
BIOS-e820: [mem 0x0008f000-0x0008] ACPI NVS
BIOS-e820: [mem 0x0009-0x0009dfff] usable
BIOS-e820: [mem 0x0009e000-0x0009] reserved
BIOS-e820: [mem 0x0010-0x1fff] usable
BIOS-e820: [mem 0x2000-0x200f] reserved
BIOS-e820: [mem 0x2010-0x79c64fff] usable
BIOS-e820: [mem 0x79c65000-0x7a490fff] reserved
BIOS-e820: [mem 0x7a491000-0x7a590fff] ACPI NVS
BIOS-e820: [mem 0x7a591000-0x7a5d0fff] ACPI data
BIOS-e820: [mem 0x7a5d1000-0x7aff] usable
BIOS-e820: [mem 0xe00f8000-0xe00f8fff] reserved
BIOS-e820: [mem 0xfed01000-0xfed01fff] reserved
NX (Execute Disable) protection: active
efi: EFI v2.40 by EDK II
efi:  ACPI=0x7a5d  ACPI 2.0=0x7a5d0014  SMBIOS=0x79c8c000
efi: mem00: type=7, 

Re: [U-Boot] MinnowBoard Max uboot

2015-06-10 Thread Beaman, Thomas
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@0  Intel(R) Atom(TM) CPU  E3825  @ 1.33GHz
  1: cpu@1  Intel(R) Atom(TM) CPU  E3825  @ 1.33GHz
 
## minnow max when booted from uboot 2015-07.rc2
root@atom_230:~# cat /proc/cpuinfo | grep processor
processor   : 0

## minnow max when booted from BIOS
root@atom_230:~# cat /proc/cpuinfo | grep processor
processor   : 0
processor   : 1



-Original Message-
From: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
Sent: Tuesday, March 10, 2015 1:21 PM
To: Beaman, Thomas
Cc: u-boot@lists.denx.de; Bin Meng; gabriel huau
Subject: Re: MinnowBoard Max uboot

Hi Tom,

On 10 March 2015 at 05:24, Beaman, Thomas thomas.bea...@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: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
 Sent: Monday, March 09, 2015 11:49 AM
 To: Beaman, Thomas
 Cc: u-boot@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.bea...@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
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] MinnowBoard Max uboot

2015-06-10 Thread Simon Glass
Hi Thomas,

On 10 June 2015 at 12:38, Beaman, Thomas thomas.bea...@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@0  Intel(R) Atom(TM) CPU  E3825  @ 1.33GHz
   1: cpu@1  Intel(R) Atom(TM) CPU  E3825  @ 1.33GHz

 ## minnow max when booted from uboot 2015-07.rc2
 root@atom_230:~# cat /proc/cpuinfo | grep processor
 processor   : 0

 ## minnow max when booted from BIOS
 root@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: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
 Sent: Tuesday, March 10, 2015 1:21 PM
 To: Beaman, Thomas
 Cc: u-boot@lists.denx.de; Bin Meng; gabriel huau
 Subject: Re: MinnowBoard Max uboot

 Hi Tom,

 On 10 March 2015 at 05:24, Beaman, Thomas thomas.bea...@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: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
 Sent: Monday, March 09, 2015 11:49 AM
 To: Beaman, Thomas
 Cc: u-boot@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.bea...@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
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] MinnowBoard Max uboot

2015-04-27 Thread Beaman, Thomas
Hi Simon,

Thanks for the update and I will be glad to help with testing if needed.

Tom 

-Original Message-
From: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
Sent: Sunday, April 26, 2015 8:36 PM
To: Beaman, Thomas
Cc: u-boot@lists.denx.de; Bin Meng; gabriel huau
Subject: Re: MinnowBoard Max uboot

Hi Thomas,

On 12 March 2015 at 16:20, Simon Glass s...@chromium.org wrote:
 Hi Thomas,

 On 11 March 2015 at 05:06, Beaman, Thomas thomas.bea...@xerox.com wrote:
 Thank you, can you keep me updated if possible.

 OK I'll see if I can copy you on the patches.

I got back into this last week and hope to have something to send to this in 
the next week or so.

Regards,
Simon


 Tom

 -Original Message-
 From: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
 Sent: Tuesday, March 10, 2015 1:21 PM
 To: Beaman, Thomas
 Cc: u-boot@lists.denx.de; Bin Meng; gabriel huau
 Subject: Re: MinnowBoard Max uboot

 Hi Tom,

 On 10 March 2015 at 05:24, Beaman, Thomas thomas.bea...@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: s...@google.com [mailto:s...@google.com] On Behalf Of Simon 
 Glass
 Sent: Monday, March 09, 2015 11:49 AM
 To: Beaman, Thomas
 Cc: u-boot@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.bea...@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
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] MinnowBoard Max uboot

2015-04-26 Thread Simon Glass
Hi Thomas,

On 12 March 2015 at 16:20, Simon Glass s...@chromium.org wrote:
 Hi Thomas,

 On 11 March 2015 at 05:06, Beaman, Thomas thomas.bea...@xerox.com wrote:
 Thank you, can you keep me updated if possible.

 OK I'll see if I can copy you on the patches.

I got back into this last week and hope to have something to send to
this in the next week or so.

Regards,
Simon


 Tom

 -Original Message-
 From: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
 Sent: Tuesday, March 10, 2015 1:21 PM
 To: Beaman, Thomas
 Cc: u-boot@lists.denx.de; Bin Meng; gabriel huau
 Subject: Re: MinnowBoard Max uboot

 Hi Tom,

 On 10 March 2015 at 05:24, Beaman, Thomas thomas.bea...@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: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
 Sent: Monday, March 09, 2015 11:49 AM
 To: Beaman, Thomas
 Cc: u-boot@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.bea...@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
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] MinnowBoard Max uboot

2015-03-12 Thread Simon Glass
Hi Tom,

On 10 March 2015 at 05:24, Beaman, Thomas thomas.bea...@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: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
 Sent: Monday, March 09, 2015 11:49 AM
 To: Beaman, Thomas
 Cc: u-boot@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.bea...@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
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] MinnowBoard Max uboot

2015-03-12 Thread Simon Glass
Hi Thomas,

On 11 March 2015 at 05:06, Beaman, Thomas thomas.bea...@xerox.com wrote:
 Thank you, can you keep me updated if possible.

OK I'll see if I can copy you on the patches.

Regards,
Simon


 Tom

 -Original Message-
 From: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
 Sent: Tuesday, March 10, 2015 1:21 PM
 To: Beaman, Thomas
 Cc: u-boot@lists.denx.de; Bin Meng; gabriel huau
 Subject: Re: MinnowBoard Max uboot

 Hi Tom,

 On 10 March 2015 at 05:24, Beaman, Thomas thomas.bea...@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: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
 Sent: Monday, March 09, 2015 11:49 AM
 To: Beaman, Thomas
 Cc: u-boot@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.bea...@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
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] MinnowBoard Max uboot

2015-03-11 Thread Beaman, Thomas
Thank you, can you keep me updated if possible.

Tom

-Original Message-
From: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
Sent: Tuesday, March 10, 2015 1:21 PM
To: Beaman, Thomas
Cc: u-boot@lists.denx.de; Bin Meng; gabriel huau
Subject: Re: MinnowBoard Max uboot

Hi Tom,

On 10 March 2015 at 05:24, Beaman, Thomas thomas.bea...@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: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
 Sent: Monday, March 09, 2015 11:49 AM
 To: Beaman, Thomas
 Cc: u-boot@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.bea...@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
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] MinnowBoard Max uboot

2015-03-10 Thread Beaman, Thomas
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

Thanks,
Tom

-Original Message-
From: s...@google.com [mailto:s...@google.com] On Behalf Of Simon Glass
Sent: Monday, March 09, 2015 11:49 AM
To: Beaman, Thomas
Cc: u-boot@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.bea...@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
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] MinnowBoard Max uboot

2015-03-09 Thread Simon Glass
+Bin and Gabriel

Hi Tom,

On 9 March 2015 at 08:08, Beaman, Thomas thomas.bea...@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
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


[U-Boot] MinnowBoard Max uboot

2015-03-09 Thread Beaman, Thomas

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.

Thanks,
Tom Beaman

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot