From: Scott Garman <scott.a.garman@intel.com>
To: yocto@yoctoproject.org
Subject: Re: oddities in "runqemu" script
Date: Thu, 14 Jun 2012 12:58:40 -0700 [thread overview]
Message-ID: <4FDA4270.80507@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1206141434210.11150@oneiric>
On 06/14/2012 11:39 AM, Robert P. J. Day wrote:
>
> just a few observations:
>
> 1) usage suggests this possible option:
>
> MACHINE=xyz
>
> not sure what that's supposed to accomplish, that will be rejected
> by the arg parsing loop, will it not? or how is one supposed to
> interpret that?
This is a bug in the usage() documentation, thanks for reporting it.
> 2) the process_filename() function appears to accept a filesystem type
> of "ext4", but the arg parsing loop immediately after that doesn't
> recognize that as valid, only ext[23].
Our QEMU machines only generate .ext3 images, so that would explain why
this never got tested. It's still not good that it's inconsistent, so
I've filed a bug to fix that and the above issue:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=2611
> 3) the arg parsing script clearly recognizes the option "audio", but
> that's not mentioned in the usage() function.
That's because we're not yet ready to advertise that the audio option is
fully supported, see this bug:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=1018
which isn't even slated for work in 1.3, but rather 1.4.
Thanks for these inquiries!
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
prev parent reply other threads:[~2012-06-14 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 18:39 oddities in "runqemu" script Robert P. J. Day
2012-06-14 19:58 ` Scott Garman [this message]
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=4FDA4270.80507@intel.com \
--to=scott.a.garman@intel.com \
--cc=yocto@yoctoproject.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.