All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Prince <vincent.prince.fr@gmail.com>
To: Teemu K <maillinglists18@gmail.com>
Cc: meta-freescale <meta-freescale@yoctoproject.org>
Subject: Re: Status of i.MX8 support
Date: Wed, 9 Jan 2019 10:44:31 +0100	[thread overview]
Message-ID: <CAB2nKc-Ak+rTvL=uRCkfOV1r8VwnaBRnjP7V5ATnV+5K9SNbsQ@mail.gmail.com> (raw)
In-Reply-To: <CAAmVmrrDKht70ZJUn27GyD6eLEx7HDknADJmtqks0daJr-9mzQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2967 bytes --]

Hi,

Did you try to compile with rpm support instead?
Also, it seems that default kernel for imx8 is linux-fslc-imx and not
linux-imx:

IMX_DEFAULT_KERNEL_mx8 = "linux-fslc-imx"

Regards,
Vincent

Le mer. 9 janv. 2019 à 09:30, Teemu K <maillinglists18@gmail.com> a écrit :

> On Tue, Jan 8, 2019 at 9:04 AM Teemu K <maillinglists18@gmail.com> wrote:
> >
> > Hi,
> >
> > What is the state of the meta-freescale i.MX8 support? I'm trying to
> > compile image for NXP i.MX8 development board (MCIMX8QXP - CPU).
> >
> > I'm using thud - branch of everything, but while compiling and using
> > kernel linux-imx_4.9.123 (that's the only one with i.MX8 support as
> > far as I can tell based on recipes) the kernel fails to build
> > properly. I think it's more of the kernel modules that create some
> > bitbake related errors.
> >
> > --
> > ERROR: linux-imx-4.9.123-r0 do_package_write_deb: Fatal errors
> > occurred in subprocesses:
> >  dpkg-deb -b
> /home/teemu/proj/imx8dev/src/platform/hv/build/tmp/work/imx8qxpmek-poky-linux/linux-imx/4.9.123-r0/packages-split/kernel-module-snd-usb-audio-4.9.123-imx_4.9.123_imx8mm_ga+g6a71cbc
> >
> /home/teemu/proj/imx8dev/src/platform/hv/build/tmp/work/imx8qxpmek-poky-linux/linux-imx/4.9.123-r0/deploy-debs/imx8qxpmek'
> > returned non-zero exit status 2: Traceback (most recent call last):
> >   File
> "/home/teemu/proj/imx8dev/src/platform/common/../../poky/../poky/meta/lib/oe/utils.py",
> > line 272, in run
> >     ret = self._target(*self._args, **self._kwargs)
> >   File
> "/home/teemu/proj/imx8dev/src/platform/common/../../poky/../poky/meta/classes/package_deb.bbclass",
> > line 274, in deb_write_pkg
> >     shell=True)
> >   File "/usr/lib/python3.5/subprocess.py", line 626, in check_output
> >     **kwargs).stdout
> >   File "/usr/lib/python3.5/subprocess.py", line 708, in run
> >     output=stdout, stderr=stderr)
> > --
> >
> > I cut that some and there are more of similar errors coming. If I
> > remove those modules from kernel I'll get error on some other module.
> >
> > Just wondering if that should work? I know it's quite new and may have
> > some problems so if it's known not to work then I guess I'll do
> > something else.
> >
> > -TeemuK
>
> I did some digging and it seems that the dpkg-deb - command, fails to
> this error when run manually:
>
> dpkg-deb: error: failed to open package info file
>
> '/home/teemu/proj/imx8dev/src/platform/hv/build/tmp/work/imx8qxpmek-poky-linux/linux-imx/4.9.123-r0/packages-split/kernel-module-snd-hwdep-4.9.123-imx_4.9.123_imx8mm_ga+g6a71cbc/DEBIAN/control'
> for reading: No such file or directory
>
> How has anyone else managed to build Yocto image for i.MX8? Or has
> anyone done that?
>
> -Teemu
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>

[-- Attachment #2: Type: text/html, Size: 3907 bytes --]

  reply	other threads:[~2019-01-09  9:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08  7:04 Status of i.MX8 support Teemu K
2019-01-09  8:29 ` Teemu K
2019-01-09  9:44   ` Vincent Prince [this message]
2019-01-09 15:17     ` Max Krummenacher
2019-01-10  4:25     ` Teemu K
2019-01-11  8:12       ` Teemu K
2019-01-11 12:26         ` Daiane Angolini
2019-01-14  4:55           ` Teemu K

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='CAB2nKc-Ak+rTvL=uRCkfOV1r8VwnaBRnjP7V5ATnV+5K9SNbsQ@mail.gmail.com' \
    --to=vincent.prince.fr@gmail.com \
    --cc=maillinglists18@gmail.com \
    --cc=meta-freescale@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.