All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Stoicescu, CorneliuX" <corneliux.stoicescu@intel.com>,
	yocto <yocto@yoctoproject.org>
Cc: jan alexandru vaduva <vaduva.jan.alexandru@gmail.com>
Subject: Re: Creating a custom mips64 layer using yocto-bsp
Date: Fri, 4 Oct 2013 08:58:45 -0400	[thread overview]
Message-ID: <524EBB85.7050600@windriver.com> (raw)
In-Reply-To: <33115ABC4887814E8A92A08FBC93416B0A196300@IRSMSX103.ger.corp.intel.com>

On 13-10-04 04:15 AM, Stoicescu, CorneliuX wrote:
> Hello,
>
> I am trying to create a custom mips64 layer for a project. I am using
> the “yocto-bsp” command to make the magic happen. Unfortunately, the
> tool only supports creating layers for mips (32 bit) architecture. So I
> tried a little magic of my own and I changed a line in
> meta-my_layer/conf/machine/my_layer.conf from:
>
> /require conf/machine/include/tune-mips.inc/
>
> //
>
> /to/
>
> //
>
> /require conf/machine/include/tune-mips64.inc/
>
> When building, it fails at linux-yocto task do_package with a lot of
> errors like:
>
> ERROR: QA Issue: Bit size did not match (64 to 32) linux-yocto on
> /work/mipstest-poky-linux/linux-yocto/3.10.11+gitAUTOINC+dad2b7e1ce_e1aa804148-r0.1/packages-split/kernel-module-sch-codel/lib/modules/3.10.11-yocto-standard/kernel/net/sched/sch_codel.ko
>
> I believe that means the modules still think they should be 32 bit but
> are not. Can anyone help me with my issue?

Did you check the kernel configuration ? Since the BSP tool didn't allow
you to use the 64 bit qemumips base, you got the 32 bit BSP. So it will
definitely build 32 bit modules, which gets you your warning.

Check the generated machine files, search for qemumips32 and mti-malta32
and switch them to the 64 bit variants.

Bruce

>
> PS: I looked through the Yocto mega-manual and I added the following
> line to my_layer.conf file without any luck:
>
> /TARGET_ARCH = "mips64"/
>
> Thank you!
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



      reply	other threads:[~2013-10-04 12:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-04  8:15 Creating a custom mips64 layer using yocto-bsp Stoicescu, CorneliuX
2013-10-04 12:58 ` 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=524EBB85.7050600@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=corneliux.stoicescu@intel.com \
    --cc=vaduva.jan.alexandru@gmail.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.