All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Liming Wang <liming.wang@windriver.com>
Cc: yocto@yoctoproject.org, dvhart@linux.intel.com,
	Saul Wold <saul.wold@intel.com>
Subject: Re: [PATCH 0/1] script/runqemu: change boot command line for qemuppc
Date: Wed, 24 Aug 2011 14:33:00 -0400	[thread overview]
Message-ID: <4E5543DC.8090501@windriver.com> (raw)
In-Reply-To: <1314175707-9214-1-git-send-email-liming.wang@windriver.com>

On 11-08-24 04:48 AM, Liming Wang wrote:
> This patch is just a workaround to speed up boot time of qemuppc, because
> qemuppc has no framebuffer support, no need to start X server for qemuppc.
>
> Richard suggested to fix the X scripts so that if an fbdev X server is in use and
> the framebuffer device node does not exist, it just exits cleanly with a
> suitable message and doesn't timeout on boot.
>
> But I think it needs more time to implement and test.
>> X scripts serve for all the boards. And we also can't assume all the
>> boards use the same
>> framebuffer device. So how to detect whether the framebuffer device
>> exists is board dependent.
>> Maybe we can see whether the device /dev/fb0 exists(it could be created
>> manually, so we should try to open it to verify)
>> or the file /proc/fb exists to confirm the framebuffer device. Anyway,
>> any modification should be
>> tested on all boards to see whether it works. I prefer to mark it as
>> todo task in 1.1

We need to cc Richard/Saul on this, so they can re-consider
and merge this as appropriate. But for me, I'm acking this
change.

Bruce

>
> Bruce also suggests:
>> I know I'm ok with this strategy, since time is short in the
>> 1.1 cycle. We can always open a bugzilla item to track this,
>> just to be sure it isn't forgotten. Preferably we'll get a
>> qemuppc with a framebuffer in 1.x timeframe and we won't need
>> this at all. Coming up with something generic and the amount
>> of testing required doesn't fit the timeframe that we currently
>> have for 1.1.
>
>
> Liming Wang (1):
>        script/runqemu: change boot command line for qemuppc
>
>   scripts/runqemu-internal |    4 ++--
>   1 files changed, 2 insertions(+), 2 deletions(-)
>



  parent reply	other threads:[~2011-08-24 18:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24  8:48 [PATCH 0/1] script/runqemu: change boot command line for qemuppc Liming Wang
2011-08-24  8:48 ` [PATCH 1/1] " Liming Wang
2011-08-24 18:33 ` Bruce Ashfield [this message]
2011-08-30 21:26   ` [PATCH 0/1] " Richard Purdie

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=4E5543DC.8090501@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=dvhart@linux.intel.com \
    --cc=liming.wang@windriver.com \
    --cc=saul.wold@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.