[OE-core] [PATCH 0/4] Add qemumips64 machine support

[Trevor Woerner]

On Tue, May 14, 2013 at 4:28 AM, Robert P. J. Day <rpjday at crashcourse.ca> wrote:
> On Mon, 13 May 2013, Khem Raj wrote:
>> can you try this
>>
>> add
>>
>> SRCREV_machine_qemumips64 = "bbefde394205a1b317eae31942bfc13afce0b0ac"
>>
>> to linux-yocto_3.8.bb
>>
>> and rebuild the kernel and see if that boots
>
>   ok, that gives me a successful boot (tried it twice, success both
> times) but i'm now at a boot prompt:
>
>   qemumips64 login:
>
> that's not accepting any keyboard input.  tried a couple more times,
> same result -- boot to login prompt, but no keyboard input. thoughts?

Me too. If I use the "serial" option on the "runqemu" cmdline I can
log in via the serial console. There was a time when I would get an
unresponsive qemumips console (via SDL) but could log in on console...
3? or 4? That isn't the case with qemumips64.

By the way, my build is still wanting to use linux-yocto_3.4.43.

What's interesting is: without the change described by Khem above if I put:

    PREFERRED_VERSION_linux-yocto := "3.8%"

in my local.conf I would get 3.8.11. When I add the change as
described above, this line in local.conf gives me linux-yocto_3.8.4!


With Khem's suggestion above:
- linux-yocto_3.8.4 boots but the SDL console doesn't accept input
- linux-yocto_3.4.43 doesn't fully boot (as before)


> p.s.  i can ping the VM (192.168.7.2) but can't ssh into it, FWIW.

I don't have any issue ssh'ing into the VM (with the 3.8.4 kernel)
when I add "ssh-server-openssh" to "EXTRA_IMAGE_FEATURES".