From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Liming Wang <liming.wang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1] V2 qemuppc/kernel: replace emulation of qemuppc
Date: Mon, 23 Jan 2012 12:57:57 -0500 [thread overview]
Message-ID: <4F1D9FA5.4050202@windriver.com> (raw)
In-Reply-To: <4F0FC6A6.70502@windriver.com>
On 12-01-13 12:52 AM, Liming Wang wrote:
> On 2012-1-12 21:45, Bruce Ashfield wrote:
>> On 12-01-12 03:42 AM, Liming Wang wrote:
>>> v2 change log:
>>> - disable CONFIG_DEVTMPFS option to avoid /dev/console
>>> pointing to serial. Otherwise, keyboard doesn't work well
>>> on X-windows.
>>
>> This looks fine to me, but can you resend it as an incremental on top
>> of:
>>
>> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/commit/?h=meta&id=73dafd44ea875df654129b32b2877f342d5573e4
>>
>>
>> Since I pushed the core support yesterday (you won't see it in
>> your local build unless you use AUTOREV or pull in my series
>> from yesterday).
>>
>> Making it incremental will show the tweak more clearly, and I can
>> merge it directly.
>
> Is pull request is enough? BTW: I used linux-yocto-dev git tree in
> previous pull request.
While fixing another problem, I tried just taking this change
and I still had no keyboard. So I went with the console=tty option
that we discussed another time.
That at least gets keyboard working for me in the tree, and we can
revisit it at a later date.
Cheers,
Bruce
>
> The following changes since commit
> 73dafd44ea875df654129b32b2877f342d5573e4:
>
> meta/qemuppc: replace kernel config file of qemu-ppc32 with mac99
> (2012-01-06 15:09:36 -0500)
>
> are available in the git repository at:
> git://128.224.163.150/linux-yocto-3.0.git meta-qemuppc
>
> Liming Wang (1):
> meta/qemuppc: disable CONFIG_DEVTMPFS option
>
> .../cfg/kernel-cache/bsp/qemu-ppc32/qemu-ppc32.cfg | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
>
> Liming Wang
>
>>
>> Cheers,
>>
>> Bruce
>>
>>>
>>> The following changes since commit
>>> a8ebc77767e034c589e8041406f4282136a2219b:
>>>
>>> meta/qemu-ppc32: remove references to non-existent patches
>>> (2012-01-05 10:42:40 -0500)
>>>
>>> are available in the git repository at:
>>> git://128.224.163.150/linux-yocto-dev.git meta-qemuppc
>>>
>>> Liming Wang (1):
>>> meta/qemuppc: replace kernel config file of qemu-ppc32 with mac99
>>>
>>> .../kernel-cache/bsp/qemu-ppc32/qemu-ppc32-gfx.cfg | 11 +++++
>>> .../cfg/kernel-cache/bsp/qemu-ppc32/qemu-ppc32.cfg | 44
>>> +++++++++++++++----
>>> .../cfg/kernel-cache/bsp/qemu-ppc32/qemu-ppc32.scc | 1 +
>>> 3 files changed, 46 insertions(+), 10 deletions(-)
>>> create mode 100644
>>> meta/cfg/kernel-cache/bsp/qemu-ppc32/qemu-ppc32-gfx.cfg
>>>
>>
>>
>
prev parent reply other threads:[~2012-01-23 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 8:42 [PATCH 0/1] V2 qemuppc/kernel: replace emulation of qemuppc Liming Wang
2012-01-12 8:42 ` [PATCH 1/1] V2 meta/qemuppc: replace kernel config file of qemu-ppc32 with mac99 Liming Wang
2012-01-12 13:45 ` [PATCH 0/1] V2 qemuppc/kernel: replace emulation of qemuppc Bruce Ashfield
2012-01-13 5:52 ` Liming Wang
2012-01-13 14:45 ` Bruce Ashfield
2012-01-23 17:57 ` Bruce Ashfield [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=4F1D9FA5.4050202@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=liming.wang@windriver.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