From: Vagrant Cascadian <vagrant@debian.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Set ramdisk_addr_r to a higher address location on meson-gxbb.
Date: Wed, 12 Apr 2017 16:59:51 -0700 [thread overview]
Message-ID: <87a87lmb2g.fsf@aikidev.net> (raw)
In-Reply-To: <31b2db97-0262-8f6e-562f-1b4ae55e96d3@suse.de>
On 2017-04-12, Andreas Färber wrote:
> Am 12.04.2017 um 23:28 schrieb Vagrant Cascadian:
>> Set ramdisk_addr_r to 0x20000000, otherwise it may conflict with
>> kernel_addr_r location (0x01080000) with a moderately large kernel.
...
>> diff --git a/include/configs/meson-gxbb-common.h b/include/configs/meson-gxbb-common.h
>> index cc2b5b61d4..32602cb7c2 100644
>> --- a/include/configs/meson-gxbb-common.h
>> +++ b/include/configs/meson-gxbb-common.h
>> @@ -48,7 +48,7 @@
>> "scriptaddr=0x1f000000\0" \
>> "kernel_addr_r=0x01080000\0" \
>> "pxefile_addr_r=0x01080000\0" \
>> - "ramdisk_addr_r=0x10000000\0" \
>> + "ramdisk_addr_r=0x20000000\0" \
>
> So that's at 512 MiB. Have you checked for any S905 devices (e.g., TV
> boxes) with little RAM?
I didn't. I just picked a value out of the air and tried it. :)
I just now tested with 0x12000000 and it worked, where 0x10000000
consistantly failed.
Debian ships a largely modular multiplatform kernel, so should be on the
small side, and the current value (0x10000000) conflicted.
Not sure how much of a buffer 0x12000000 gives for the kernel to grow,
but that's considerably less than 0x20000000 (at 512MiB), and still
works for me so far...
live well,
vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170412/76f1ed9a/attachment.sig>
next prev parent reply other threads:[~2017-04-12 23:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 21:28 [U-Boot] [PATCH] Set ramdisk_addr_r to a higher address location on meson-gxbb Vagrant Cascadian
2017-04-12 21:35 ` Tom Rini
2017-04-14 20:49 ` Vagrant Cascadian
2017-04-12 21:35 ` Andreas Färber
2017-04-12 23:59 ` Vagrant Cascadian [this message]
2017-04-16 21:27 ` Vagrant Cascadian
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=87a87lmb2g.fsf@aikidev.net \
--to=vagrant@debian.org \
--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