From: "Pali Rohár" <pali.rohar@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/8] omap-common: Common boot code OMAP3 support and cleanup
Date: Tue, 9 Jun 2015 16:48:36 +0200 [thread overview]
Message-ID: <20150609144836.GI31071@pali> (raw)
In-Reply-To: <1433798667-9171-2-git-send-email-contact@paulk.fr>
On Monday 08 June 2015 23:24:19 Paul Kocialkowski wrote:
> diff --git a/board/nokia/rx51/lowlevel_init.S b/board/nokia/rx51/lowlevel_init.S
> index 9d4ea1b..9048f31 100644
> --- a/board/nokia/rx51/lowlevel_init.S
> +++ b/board/nokia/rx51/lowlevel_init.S
> @@ -28,18 +28,6 @@ imagesize: /* maximal size of image */
> ih_magic: /* IH_MAGIC in big endian from include/image.h */
> .word 0x56190527
>
> -/*
> - * Routine: save_boot_params (called after reset from start.S)
> - * Description: Copy attached kernel to address KERNEL_ADDRESS
> - * Copy u-boot to address CONFIG_SYS_TEXT_BASE
> - * Return to copied u-boot address
> - */
> -
> -.global save_boot_params
> -save_boot_params:
> - /* Get return address */
> - ldr lr, =save_boot_params_ret
> -
> /* Copy valid attached kernel to address KERNEL_ADDRESS */
>
> copy_kernel_start:
Hi, I did not tested this code yet, but quick look at it I think
effectively means to totally break support for Nokia N900 (RX-51).
Routine save_boot_params() was called directly from start.S before
U-Boot did any HW setup and configuration. It stored needed data to make
U-Boot working and more important it calculated and stored linux kernel
image to safe place in RAM (which U-Boot do not touch) to make it able
to boot.
Nokia N900 setup is special. Nokia internal bootloader (which was not
possible to replace) boot arm image stored in MTD nand.
That arm image is compiled U-Boot binary with Linux kernel and Nokia
bootloader load this image to random address into RAM. To make sure that
U-Boot will be able to boot that kernel image we need to do some magic
before U-Boot relocates itself.
In next weekend (or later) I will try to find some time to test patches
on real N900 device. But I think with your changes it will not work...
--
Pali Roh?r
pali.rohar at gmail.com
next prev parent reply other threads:[~2015-06-09 14:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 17:03 [U-Boot] [RFC] [PATCH] omap-common: Common boot code OMAP3 support and cleanup Paul Kocialkowski
2015-06-03 17:03 ` [U-Boot] " Paul Kocialkowski
2015-06-08 21:24 ` [U-Boot] [PATCH v2 0/8] omap-common: Common boot code OMAP3 support and SYS_BOOT-based fallback boot device Paul Kocialkowski
2015-06-08 21:24 ` [U-Boot] [PATCH v2 1/8] omap-common: Common boot code OMAP3 support and cleanup Paul Kocialkowski
2015-06-09 14:48 ` Pali Rohár [this message]
2015-06-08 21:24 ` [U-Boot] [PATCH v2 2/8] omap: SPL boot devices cleanup and completion Paul Kocialkowski
2015-06-08 21:24 ` [U-Boot] [PATCH v2 3/8] omap-common: Boot device define instead of hardcoded value Paul Kocialkowski
2015-06-08 21:24 ` [U-Boot] [PATCH v2 4/8] siemens-am33x-common: Hardcoded value instead of non-included define Paul Kocialkowski
2015-06-08 21:24 ` [U-Boot] [PATCH v2 5/8] omap-common: SYS_BOOT-based fallback boot device selection for peripheral boot Paul Kocialkowski
2015-06-08 21:24 ` [U-Boot] [PATCH v2 6/8] omap3: Definitions for SYS_BOOT-based fallback boot device selection Paul Kocialkowski
2015-06-08 21:24 ` [U-Boot] [PATCH v2 7/8] omap4: " Paul Kocialkowski
2015-06-08 21:24 ` [U-Boot] [PATCH v2 8/8] omap5: " Paul Kocialkowski
2015-06-09 16:28 ` [U-Boot] [PATCH v2 0/8] omap-common: Common boot code OMAP3 support and SYS_BOOT-based fallback boot device Pali Rohár
2015-06-09 18:34 ` Pali Rohár
2015-06-10 9:54 ` Paul Kocialkowski
2015-06-10 10:34 ` Pali Rohár
2015-06-10 10:42 ` Pali Rohár
2015-06-10 10:58 ` Paul Kocialkowski
2015-06-10 11:35 ` Pali Rohár
2015-06-12 11:32 ` Paul Kocialkowski
2015-06-12 11:56 ` Pali Rohár
2015-06-12 13:01 ` Paul Kocialkowski
2015-06-12 13:10 ` Pali Rohár
2015-06-12 13:54 ` Paul Kocialkowski
2015-06-10 4:27 ` Marek Vasut
2015-06-10 6:08 ` Pali Rohár
2015-06-10 6:48 ` Pavel Machek
2015-06-10 7:47 ` Pali Rohár
2015-06-10 7:45 ` Pali Rohár
2015-06-10 8:47 ` Marek Vasut
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=20150609144836.GI31071@pali \
--to=pali.rohar@gmail.com \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox