All of lore.kernel.org
 help / color / mirror / Atom feed
From: prakash m <prakash56755@gmail.com>
To: "Wiholm, Willie ActeSE" <Willie.wiholm@acte.se>
Cc: meta-freescale@yoctoproject.org
Subject: Re: Adding custom machine / dts files
Date: Mon, 14 Jan 2019 19:06:30 +0530	[thread overview]
Message-ID: <CAMdLBf-KxPf4RdhUmTWfhBqv=viX6TLmHEEv8kHDH70PxhiH0g@mail.gmail.com> (raw)
In-Reply-To: <VI1PR0801MB17606BCD4A7BE90547E037F2F5800@VI1PR0801MB1760.eurprd08.prod.outlook.com>

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

Hi,

Have you tried adding your custom patch file into the own created .bbapped
for kernel recipes.

SRC_URI_append = " file://0001-linux-driver-fix.patch"

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}

In SRC_URI_append add your custom patch names.

Or you could try by creating own git branch for your custom kernel.

1) Download the imx kernel which you need and patch your custom dts and
kernel configurations.

2) push this kernel into the git server.

3) create your own .bb file in freescale third party meta layer.

For your reference refer the below link

https://github.com/Freescale/meta-freescale-3rdparty/tree/master/recipes-kernel/linux


Thanks

Pitchaiah M



On Mon, 14 Jan, 2019, 18:28 Wiholm, Willie ActeSE <Willie.wiholm@acte.se
wrote:

> Hello Daiane,
>
> Thank you for pointing out that difference, I will be sure to talk to our
> supplier about using newer releases.
>
> But I believe the only reason this does not work is my lack of knowledge
> in Yocto.
>
> I realized that my previous error is because the patch is not applied
> correctly, by looking in /tmp/work/linux-im/4.1.15-r0/git/arch/arm/boot/dts
>
> In my custom-layer, I added the dts files in a subfolder under
> recipes-kernel, but when I look in meta-fsl-arm/recipes-kernel they have
> not supplied any dts files there, or anywhere else, they are only created
> when built.
>
> I tried to follow this guide : https://community.nxp.com/docs/DOC-95252
>
> But my dts files are never included when I'm building.
>
> Best regards,
> Willie
>
> -----Ursprungligt meddelande-----
> Från: angolini@gmail.com <angolini@gmail.com> För Daiane Angolini
> Skickat: den 14 januari 2019 13:00
> Till: Wiholm, Willie ActeSE <Willie.wiholm@acte.se>
> Kopia: prakash m <prakash56755@gmail.com>; meta-freescale@yoctoproject.org
> Ämne: Re: [meta-freescale] Adding custom machine / dts files
>
> On Mon, Jan 14, 2019 at 9:08 AM Wiholm, Willie ActeSE <
> Willie.wiholm@acte.se> wrote:
> >
> > Hello Prakash,
> >
> >
> >
> > The label in meta-fsl-arm is linux-imx-4.1.15
> >
> > Cloned from :
> >
> > repo init -u git://git.freescale.com/imx/fsl-arm-yocto-bsp.git -b
> > imx-4.1-krogoth -m imx-4.1.15-2.0.0.xml
> >
> > repo sync
> >
> > $pwd
> >
> > /linux/build/yocto/avalue_imx-4.1-krogoth/sources/meta-fsl-arm/recipes
> > -kernel/linux/linux-imx-4.1.15
> >
>
> Maybe this link can help somehow:
>
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ffreescale.github.io%2Fdoc%2Frelease-notes%2Fcurrent%2Findex.html%23the-differences-between-project-name-and-freescale-release-name&amp;data=02%7C01%7CWillie.wiholm%40acte.se%7Ccaafe5fcde184a265fad08d67a17ccab%7C309e17c286e24bd1ac236459b0d1065a%7C1%7C1%7C636830639977922129&amp;sdata=0ASHk%2F%2FWkNruJCKC%2FdVuMzk8StglS5fJ%2FvLdtKOiYo0%3D&amp;reserved=0
>
> And, if it's possible, it would be better to use some newer release/branch.
>
> Daiane
>
> >
> >
> > I realized that the problem was that there was another folder called
> “imx” which I did not have in my custom-layer. Now I’m facing another
> problem when compiling:
> >
> > | make[2]: *** No rule to make target 'e9697rsc6e5r.dts'.  Stop.
> > | Makefile:146: recipe for target 'sub-make' failed
> > | make[1]: *** [sub-make] Error 2
> > | Makefile:24: recipe for target '__sub-make' failed
> > | make: *** [__sub-make] Error 2
> > | ERROR: oe_runmake failed
> > | ERROR: Function failed: do_compile (log file is located at
> > | /build/yocto/tmp_rsc61/work/rsc61-poky-linux-gnueabi/linux-fslc-imx/
> > | 4.1-1.0.x+gitAUTOINC+59b38c323b-r0/temp/log.do_compile.11321)
> > ERROR: Task 57
> (/linux/build/yocto/avalue_imx-4.1-krogoth/sources/meta-fsl-arm/recipes-kernel/linux/
> linux-fslc-imx_4.1-1.0.x.bb, do_compile) failed with exit code '1'
> > NOTE: Tasks Summary: Attempted 1505 tasks of which 96 didn't need to be
> rerun and 1 failed.
> > Waiting for 0 running tasks to finish:
> >
> > Summary: 1 task failed:
> >
> > /linux/build/yocto/avalue_imx-4.1-krogoth/sources/meta-fsl-arm/recipes
> > -kernel/linux/linux-fslc-imx_4.1-1.0.x.bb, do_compile
> > Summary: There were 2 WARNING messages shown.
> > Summary: There were 2 ERROR messages shown, returning a non-zero exit
> code.
> >
> >
> >
> > Should Yocto not compile the dts files into dtb itself? Do I need to
> find an external program to first make them into dtb files before adding
> them into the recipe-kernel?
> >
> >
> >
> > I also tried to add the patch with dts and dtsi directly in the
> > meta-fsl-arm/recipes-kernel/linux/linux-imx-4.1.15/imx/
> >
> > But it was not added in the build, is there anything additional i need
> to do in order to apply my custom patches to the build?
> >
> > (I realize this is a bad habbit but I just want to verify that they
> work).
> >
> >
> >
> > Best Regards,
> >
> > Willie
> >
> > ________________________________
> >
> > Från: prakash m <prakash56755@gmail.com>
> > Skickat: den 13 januari 2019 17:24:44
> > Till: Wiholm, Willie ActeSE
> > Kopia: meta-freescale@yoctoproject.org
> > Ämne: Re: [meta-freescale] Adding custom machine / dts files
> >
> >
> >
> > Hi,
> >
> >
> >
> > I hope the naming convention is different from which you specified in
> your custom layer, so kindly check in meta-freescale/recipes-kernel/linux
> for the proper naming in freescale kernel recipes.
> >
> >
> >
> > I hope the proper naming would be linux-imx_4.1.15.bbappend.
> >
> >
> >
> >
> >
> > Thanks & Regards
> >
> > Pitchaiah M
> >
> >
> >
> >
> >
> > On Sun, 13 Jan, 2019, 13:59 Wiholm, Willie ActeSE <Willie.wiholm@acte.se
> wrote:
> >
> > Hello prakash,
> >
> > Yes the meta-local is added in bblayers.
> >
> > Best regards,
> >
> > Willie
> >
> > Från: prakash m
> >
> > Skickat: söndag 13 januari 03:55
> >
> > Ämne: Re: [meta-freescale] Adding custom machine / dts files
> >
> > Till: Wiholm, Willie ActeSE
> >
> > Kopia: meta-freescale@yoctoproject.org
> >
> > Hi,
> >
> > Could you please check that your custom layer has been added to your
> bblayer.conf which is under your build directory.
> >
> > Thanks & Regards
> >
> > Pitchaiah M
> >
> > On Sun, 13 Jan, 2019, 07:22 Wiholm, Willie ActeSE <Willie.wiholm@acte.se
> wrote:
> >
> > Hello guys,
> >
> > (Sorry if i sent this in multiple lists)
> >
> > I'm trying to build an image for an custom board that is based in the
> imx6dlsabresd, but I'm not sure how to add the custom dts files properly.
> >
> > First i built the kernel and created a patch in arch/arm/boot/dts where
> i added my files.
> >
> > Then I created a meta-custom layer, in which i created :
> >
> > recipes-kernel/linux-imx-4.1.15/linux-imx-4.1.15.bbappend
> >
> > and the bbappend points to my patch.
> >
> > Then i created my own machine that is a copy of the imx6dlsabre in
> > conf/machine/custom.conf
> >
> > My question is, is this the right approach? The goal is to build full
> images like "fsl-image-qt5" but I'm facing errors with core-image-minimal :
> >
> > No recipes available for:
> >
> >
> > /linux/build/yocto/avalue_imx-4.1-krogoth/sources/meta-avalue/recipes-
> > kernel/linux-imx-4.1.15/linux-imx-4.1.15.bbappend
> >
> > So i believe I'm making some fundamental errors.
> >
> > Any tips appreciated!
> >
> > Best Regards,
> >
> > Willie
> >
> > --
> >
> > _______________________________________________
> >
> > meta-freescale mailing list
> >
> > meta-freescale@yoctoproject.org
> >
> > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flis
> > ts.yoctoproject.org%2Flistinfo%2Fmeta-freescale&amp;data=02%7C01%7CWil
> > lie.wiholm%40acte.se%7Ccaafe5fcde184a265fad08d67a17ccab%7C309e17c286e2
> > 4bd1ac236459b0d1065a%7C1%7C1%7C636830639977922129&amp;sdata=2JnvmD2Uoy
> > qUHf3wk%2BysdFd1%2B67nooxIifSH%2BXnYI2Q%3D&amp;reserved=0
> >
> >
> >
> > --
> > _______________________________________________
> > meta-freescale mailing list
> > meta-freescale@yoctoproject.org
> > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flis
> > ts.yoctoproject.org%2Flistinfo%2Fmeta-freescale&amp;data=02%7C01%7CWil
> > lie.wiholm%40acte.se%7Ccaafe5fcde184a265fad08d67a17ccab%7C309e17c286e2
> > 4bd1ac236459b0d1065a%7C1%7C1%7C636830639977922129&amp;sdata=2JnvmD2Uoy
> > qUHf3wk%2BysdFd1%2B67nooxIifSH%2BXnYI2Q%3D&amp;reserved=0
>

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

      reply	other threads:[~2019-01-14 13:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-12 14:34 Adding custom machine / dts files Wiholm, Willie ActeSE
2019-01-13  2:55 ` prakash m
2019-01-13  8:29   ` Wiholm, Willie ActeSE
2019-01-13 16:24     ` prakash m
2019-01-13 20:20       ` Wiholm, Willie ActeSE
2019-01-14  8:35       ` Wiholm, Willie ActeSE
2019-01-14 11:59         ` Daiane Angolini
2019-01-14 12:57           ` Wiholm, Willie ActeSE
2019-01-14 13:36             ` prakash m [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='CAMdLBf-KxPf4RdhUmTWfhBqv=viX6TLmHEEv8kHDH70PxhiH0g@mail.gmail.com' \
    --to=prakash56755@gmail.com \
    --cc=Willie.wiholm@acte.se \
    --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.