From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 13/14] runqemu-internal: qemuarm can handle 256M
Date: Fri, 03 Feb 2012 08:54:10 -0800 [thread overview]
Message-ID: <4F2C1132.8090406@intel.com> (raw)
In-Reply-To: <5407fb2fc93f7d28a0e5000834c7b3b548826392.1328257913.git.raj.khem@gmail.com>
On 02/03/2012 12:36 AM, Khem Raj wrote:
> Raise the check for max RAM supported for QEMU/arm
> its 256M since we patched it to be so in OE
>
> Signed-off-by: Khem Raj<raj.khem@gmail.com>
Thanks Khem.
Acked-by: Scott Garman <scott.a.garman@intel.com>
> ---
> scripts/runqemu-internal | 13 +++++++------
> 1 files changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/scripts/runqemu-internal b/scripts/runqemu-internal
> index 21fbce3..73b8b41 100755
> --- a/scripts/runqemu-internal
> +++ b/scripts/runqemu-internal
> @@ -67,13 +67,14 @@ fi
> # QEMU_MEMORY has 'M' appended to mem_size
> QEMU_MEMORY="$mem_size"M
>
> -# Bug 433: qemuarm cannot use> 128 MB RAM
> +# Bug 433: qemuarm cannot use> 256 MB RAM
> if [ "$MACHINE" = "qemuarm" ]; then
> - if [[ -z "$mem_size" || $mem_size -gt 128 ]]; then
> - echo "WARNING: qemuarm does not support> 128M of RAM."
> - echo "Changing QEMU_MEMORY to default of 128M."
> - QEMU_MEMORY="128M"
> - SCRIPT_QEMU_EXTRA_OPT=`echo $SCRIPT_QEMU_EXTRA_OPT | sed -e "s/$mem_set/-m 128/" `
> + if [[ -z "$mem_size" || $mem_size -gt 256 ]]; then
> + echo "WARNING: qemuarm does not support> 256M of RAM."
> + echo "Changing QEMU_MEMORY to default of 256M."
> + QEMU_MEMORY="256M"
> + mem_size="256"
> + SCRIPT_QEMU_EXTRA_OPT=`echo $SCRIPT_QEMU_EXTRA_OPT | sed -e "s/$mem_set/-m 256/" `
> fi
> fi
>
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2012-02-03 17:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 8:36 [PATCH 00/14] uclibc upgrade, initial kmod and thumb tune Khem Raj
2012-02-03 8:36 ` [PATCH 01/14] task-core-tools: Divide it into 3 recipes Khem Raj
2012-02-03 8:36 ` [PATCH 02/14] Enable options needed for ltp to compile Khem Raj
2012-02-03 8:36 ` [PATCH 03/14] arm/tune: Correct the logic which added thumb-interwork to OVERRIDES Khem Raj
2012-02-03 8:36 ` [PATCH 04/14] tunearch/arm: Differentiate between thumb code generation and thumb capability Khem Raj
2012-02-03 8:36 ` [PATCH 05/14] tune-thumb.inc: Delete Khem Raj
2012-02-03 8:36 ` [PATCH 06/14] uclibc: Get the thumb features from tune flags Khem Raj
2012-02-03 8:36 ` [PATCH 07/14] kmod: Add recipes Khem Raj
2012-02-03 8:36 ` [PATCH 08/14] module-init-tools: Delete Khem Raj
2012-02-03 8:36 ` [PATCH 09/14] image.bbclass, kernel.bbclass: Use kmod-native instead of module-init-tools-cross Khem Raj
2012-02-03 8:36 ` [PATCH 10/14] pseudo: Wrap renameat and opendir Khem Raj
2012-02-03 8:36 ` [PATCH 11/14] uclibc: Upgrade recipes from 0.9.32 -> 0.9.33 Khem Raj
2012-02-03 8:36 ` [PATCH 12/14] zlib: Upgrade 1.2.5 -> 1.2.6 Khem Raj
2012-02-03 8:36 ` [PATCH 13/14] runqemu-internal: qemuarm can handle 256M Khem Raj
2012-02-03 16:54 ` Scott Garman [this message]
2012-02-03 8:36 ` [PATCH 14/14] gconf, consolekit: Avoid polkit when compiling with uclibc Khem Raj
2012-02-03 19:04 ` [PATCH 00/14] uclibc upgrade, initial kmod and thumb tune Khem Raj
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=4F2C1132.8090406@intel.com \
--to=scott.a.garman@intel.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox