Bug 5314 - add mips64 support to the 'yocto-bsp' script/command
Summary: add mips64 support to the 'yocto-bsp' script/command
Status: VERIFIED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: 1.6
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 1.8 M1
Assignee: Tom Zanussi
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-10-04 08:30 UTC by Stoicescu Cornel
Modified: 2014-12-15 09:01 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stoicescu Cornel 2013-10-04 08:30:03 UTC
The user should be able to create mips64 layers using the 'yocto-bsp' command. Currently it is not possible:

cornel@NODE1:~/SSD/poky/build$ yocto-bsp list karch
Architectures available:
    i386
    mips
    powerpc
    x86_64
    arm
    qemu

Please note that "mips" refers to 32 bit.

Also, to make architecture of a layer more clear, please make the "yocto-bsp list karch" command output similar to:

cornel@NODE1:~/SSD/poky/build$ yocto-bsp create layer_name qemu
Checking basic git connectivity...
Done.

Which qemu architecture would you like to use? [default: i386]
        1) i386    (32-bit)
        2) x86_64  (64-bit)
        3) ARM     (32-bit)
        4) PowerPC (32-bit)
        5) MIPS    (32-bit)
Comment 2 Yi Zhao 2014-12-15 09:01:00 UTC
Verified with 1.8 M1 (git rev: master/b813bdebb36501500e86fea5f7e15b4b15ea0902)

The qemumips64 can build without problems. But I found the runqemu can not launch the image directly: 

$ runqemu qemumips64 ~/vmlinux-myqemumips64.bin ~/core-image-sato-myqemumips64-20141210092048.rootfs.ext3 

Continuing with the following parameters:
KERNEL: [/home/build/vmlinux-myqemumips64.bin]
ROOTFS: [/home/build/core-image-sato-myqemumips64-20141210092048.rootfs.ext3]
FSTYPE: [ext3]
Acquiring lockfile for tap1...
Setting up tap interface under sudo
Acquiring lockfile for tap0...
Error: No QEMU binary 'qemu-system-mips64' could be found.
Set 'tap0' nonpersistent
Releasing lockfile of preconfigured tap device 'tap0'

I need to install qemu-system package in order to get command qemu-system-mips64 in Ubuntu host. I will file a new bug to report it.