All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: Mainline kernel on snowball
Date: Thu, 25 Jul 2013 05:40:36 +0000	[thread overview]
Message-ID: <20130725054036.GD31954@1wt.eu> (raw)
In-Reply-To: <20130725052317.GA25854@verge.net.au>

Hi Simon,

On Thu, Jul 25, 2013 at 02:23:17PM +0900, Simon Horman wrote:
> Hi,
> 
> I apologise for the naïve nature of this question,
> but I do not seem to be able to make any progress of my own accord.
> 
> I would like to boot the mainline kernel - ideally v3.10 and v3.11-rcX -
> on snowball. The reason being to verify CPU hotplug which
> seems to be broken on shmobile, though that is tangential to this post.
> 
> My procedure, which does not work, is as follows.
> I have tried a number of different versions all with roughly
> the same result.
> 
> 1. Build kernel
> # git checkout v3.10.2 # I have tried several over versions too.
> # make u8500_defconfig
> Edit .config to enable CONFIG_ARM_APPENDED_DTB
> # LOADADDR=0x100000 make uImage dtbs
> 
> 2. Append dtb to zImage and recreate uImage
> mv arch/arm/boot/zImage arch/arm/boot/zImage.tmp
> cat arch/arm/boot/zImage.tmp arch/arm/boot/dts/snowball.dtb
> /bin/sh scripts/mkuboot.sh \
> 	-A arm -O linux -C none  -T kernel \
> 	-a 0x100000 -e 0x100000 -n 'Linux-3.10.2' \
> 	-d arch/arm/boot/zImage arch/arm/boot/uImage
> 
> 3. Boot uImage from u-boot
> Snowball $ setenv ethaddr 3e:c4:73:05:d1:a1
> Snowball $ bootp;bootm
> smc911x: detected LAN9221 controller
> smc911x: phy initialized
> smc911x: MAC 3e:c4:73:05:d1:a1
> BOOTP broadcast 1
> *** Unhandled DHCP Option in OFFER/ACK: 28
> *** Unhandled DHCP Option in OFFER/ACK: 44
> *** Unhandled DHCP Option in OFFER/ACK: 28
> *** Unhandled DHCP Option in OFFER/ACK: 44
> DHCP client bound to address 10.3.3.146
> Using smc911x-0 device
> TFTP from server 10.3.3.135; our IP address is 10.3.3.146
> Filename 'snowball/uImage'.
> Load address: 0x100000
> Loading: #################################################################
>          #################################################################
>          #################################################################
>          #################################################################
>          ##########################################################
> done
> Bytes transferred = 2540191 (26c29f hex)
> ## Booting kernel from Legacy Image at 00100000 ...
>    Image Name:   'Linux-3.10.2'
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    2540127 Bytes =  2.4 MB
>    Load Address: 00100000
>    Entry Point:  00100000
>    XIP Kernel Image ... OK
> OK
> 
> Starting kernel ...
> 
> 
> This is as far as it gets.

Are you sure you have the correct bootargs by default ? It was a
pain for me to figure the correct ones, and I finally found them
in the boot scripts. Mine is booted with this :

# cat /proc/cmdline 
console=tty0 console=ttyAMA2,115200n8  root=UUID\x018e1580-e7e9-460b-95c5-236f6b87b13d rootwait ro fixrtc nocompcache vmalloc00M mem\x128M@0 mali.mali_memdM@128M hwmem\x168M@192M mem"M@360M mem_issw=1M@383M memd0M@384M

# uname -a
Linux snowball 3.10.0-rc5-snowball #2 SMP Fri Jun 14 09:19:28 CEST 2013 armv7l GNU/Linux

I don't have the CONFIG_ARM_APPENDED_DTB set, instead I have copied
the dtb on the flash since u-boot supports it (I find this boot
procedure quite annoying btw).

Hoping this helps,
Willy


WARNING: multiple messages have this Message-ID (diff)
From: w@1wt.eu (Willy Tarreau)
To: linux-arm-kernel@lists.infradead.org
Subject: Mainline kernel on snowball
Date: Thu, 25 Jul 2013 07:40:36 +0200	[thread overview]
Message-ID: <20130725054036.GD31954@1wt.eu> (raw)
In-Reply-To: <20130725052317.GA25854@verge.net.au>

Hi Simon,

On Thu, Jul 25, 2013 at 02:23:17PM +0900, Simon Horman wrote:
> Hi,
> 
> I apologise for the na?ve nature of this question,
> but I do not seem to be able to make any progress of my own accord.
> 
> I would like to boot the mainline kernel - ideally v3.10 and v3.11-rcX -
> on snowball. The reason being to verify CPU hotplug which
> seems to be broken on shmobile, though that is tangential to this post.
> 
> My procedure, which does not work, is as follows.
> I have tried a number of different versions all with roughly
> the same result.
> 
> 1. Build kernel
> # git checkout v3.10.2 # I have tried several over versions too.
> # make u8500_defconfig
> Edit .config to enable CONFIG_ARM_APPENDED_DTB
> # LOADADDR=0x100000 make uImage dtbs
> 
> 2. Append dtb to zImage and recreate uImage
> mv arch/arm/boot/zImage arch/arm/boot/zImage.tmp
> cat arch/arm/boot/zImage.tmp arch/arm/boot/dts/snowball.dtb
> /bin/sh scripts/mkuboot.sh \
> 	-A arm -O linux -C none  -T kernel \
> 	-a 0x100000 -e 0x100000 -n 'Linux-3.10.2' \
> 	-d arch/arm/boot/zImage arch/arm/boot/uImage
> 
> 3. Boot uImage from u-boot
> Snowball $ setenv ethaddr 3e:c4:73:05:d1:a1
> Snowball $ bootp;bootm
> smc911x: detected LAN9221 controller
> smc911x: phy initialized
> smc911x: MAC 3e:c4:73:05:d1:a1
> BOOTP broadcast 1
> *** Unhandled DHCP Option in OFFER/ACK: 28
> *** Unhandled DHCP Option in OFFER/ACK: 44
> *** Unhandled DHCP Option in OFFER/ACK: 28
> *** Unhandled DHCP Option in OFFER/ACK: 44
> DHCP client bound to address 10.3.3.146
> Using smc911x-0 device
> TFTP from server 10.3.3.135; our IP address is 10.3.3.146
> Filename 'snowball/uImage'.
> Load address: 0x100000
> Loading: #################################################################
>          #################################################################
>          #################################################################
>          #################################################################
>          ##########################################################
> done
> Bytes transferred = 2540191 (26c29f hex)
> ## Booting kernel from Legacy Image at 00100000 ...
>    Image Name:   'Linux-3.10.2'
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    2540127 Bytes =  2.4 MB
>    Load Address: 00100000
>    Entry Point:  00100000
>    XIP Kernel Image ... OK
> OK
> 
> Starting kernel ...
> 
> 
> This is as far as it gets.

Are you sure you have the correct bootargs by default ? It was a
pain for me to figure the correct ones, and I finally found them
in the boot scripts. Mine is booted with this :

# cat /proc/cmdline 
console=tty0 console=ttyAMA2,115200n8  root=UUID=018e1580-e7e9-460b-95c5-236f6b87b13d rootwait ro fixrtc nocompcache vmalloc=300M mem=128M at 0 mali.mali_mem=64M at 128M hwmem=168M at 192M mem=22M at 360M mem_issw=1M at 383M mem=640M at 384M

# uname -a
Linux snowball 3.10.0-rc5-snowball #2 SMP Fri Jun 14 09:19:28 CEST 2013 armv7l GNU/Linux

I don't have the CONFIG_ARM_APPENDED_DTB set, instead I have copied
the dtb on the flash since u-boot supports it (I find this boot
procedure quite annoying btw).

Hoping this helps,
Willy

  reply	other threads:[~2013-07-25  5:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25  5:23 Mainline kernel on snowball Simon Horman
2013-07-25  5:23 ` Simon Horman
2013-07-25  5:40 ` Willy Tarreau [this message]
2013-07-25  5:40   ` Willy Tarreau
2013-07-25  7:25   ` Simon Horman
2013-07-25  7:25     ` Simon Horman
2013-07-25  7:52     ` Willy Tarreau
2013-07-25  7:52       ` Willy Tarreau
2013-07-25  8:26       ` Simon Horman
2013-07-25  8:26         ` Simon Horman
2013-07-25  8:36         ` Willy Tarreau
2013-07-25  8:36           ` Willy Tarreau
2013-07-25  6:41 ` Uwe Kleine-König
2013-07-25  6:41   ` Uwe Kleine-König
2013-07-25  7:22   ` Simon Horman
2013-07-25  7:22     ` Simon Horman
2013-07-25  9:27 ` Linus Walleij
2013-07-25  9:27   ` Linus Walleij

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130725054036.GD31954@1wt.eu \
    --to=w@1wt.eu \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.