[yocto] [PATCH 0/1] script/runqemu: change boot command line for qemuppc

Bruce Ashfield bruce.ashfield at windriver.com
Wed Aug 24 11:33:00 PDT 2011


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(-)
>




More information about the yocto mailing list