All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Alrae <leon.alrae@imgtec.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Liviu Ionescu <ilg@livius.net>,
	Christopher Covington <christopher.covington@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Matthew Fortune <matthew.fortune@imgtec.com>
Subject: Re: [Qemu-devel] [PATCH v3 2/2] semihosting: add --semihosting-config arg sub-argument
Date: Thu, 21 May 2015 14:57:47 +0100	[thread overview]
Message-ID: <555DE45B.4030101@imgtec.com> (raw)
In-Reply-To: <CAFEAcA_890C6hCn+PVC7cC62S4HR3BpNSgcmGROoEQC6Rd1bwg@mail.gmail.com>

On 20/05/2015 09:54, Peter Maydell wrote:
> On 20 May 2015 at 09:11, Leon Alrae <leon.alrae@imgtec.com> wrote:
>> Agreed. We could initialize semihosting.argv[0] with -kernel and argv[1]
>> with -append string if in semihosting mode and no semihosting args have
>> been specified. I'll update it in v4.
> 
> I'm tempted to suggest splitting -append on whitespace to initialize
> argv[1..n]. ARM will just re-concatenate it, but it seems more
> useful for the non-ARM cases.

I've been considering that, and I think we are better off without
splitting -append in semihosting mode because this is at least
consistent with MIPS machines in QEMU (in non-semihosting mode) --
pseudo-bootloaders in MALTA and Fulong2e have hardcoded argc to 2
(-kernel and -append). Therefore I would leave it as it is unless we
really need to change it.

Leon

  parent reply	other threads:[~2015-05-21 13:58 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 11:41 [Qemu-devel] [PATCH v3 0/2] semihosting: clean up and add --semihosting-config arg Leon Alrae
2015-05-08 11:41 ` [Qemu-devel] [PATCH v3 1/2] semihosting: create SemihostingConfig structure and semihost.h Leon Alrae
2015-05-08 11:41 ` [Qemu-devel] [PATCH v3 2/2] semihosting: add --semihosting-config arg sub-argument Leon Alrae
2015-05-18 16:18   ` Peter Maydell
2015-05-20  8:11     ` Leon Alrae
2015-05-20  8:30       ` Liviu Ionescu
2015-05-20  8:51         ` Leon Alrae
2015-05-20 11:12           ` Liviu Ionescu
2015-05-20 13:10             ` Leon Alrae
2015-05-20  8:54       ` Peter Maydell
2015-05-20  9:31         ` Leon Alrae
2015-05-20 13:49           ` Liviu Ionescu
2015-05-20 14:18             ` Peter Maydell
2015-05-20 14:31               ` Liviu Ionescu
2015-05-20 14:40                 ` Peter Maydell
2015-05-20 14:59                   ` Liviu Ionescu
2015-05-20 15:11                     ` Peter Maydell
2015-05-20 15:47                       ` Liviu Ionescu
2015-05-21 13:57         ` Leon Alrae [this message]
2015-05-21 14:01           ` Peter Maydell
2015-05-21 14:26             ` Leon Alrae
2015-05-21 14:28           ` Liviu Ionescu
2015-05-21 14:33             ` Peter Maydell
2015-05-21 14:57               ` Liviu Ionescu
2015-05-21 15:06                 ` Peter Maydell
2015-05-21 15:24                   ` Liviu Ionescu
2015-05-21 15:29                     ` Peter Maydell
2015-05-21 15:47                       ` Liviu Ionescu
2015-05-21 15:54                         ` Peter Maydell
2015-05-21 16:36                           ` Liviu Ionescu
2015-05-21 16:56                             ` Peter Maydell
2015-05-21 17:11                               ` Liviu Ionescu
2015-05-21 18:35             ` Maciej W. Rozycki
2015-05-21 18:58               ` Liviu Ionescu

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=555DE45B.4030101@imgtec.com \
    --to=leon.alrae@imgtec.com \
    --cc=christopher.covington@linaro.org \
    --cc=ilg@livius.net \
    --cc=matthew.fortune@imgtec.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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.