From: Richard A Griffiths <richard.a.griffiths@linux.intel.com>
To: Scott Rifenbark <srifenbark@gmail.com>,
Don Osmond <dosmond@comporium.net>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: Yocto Porject
Date: Mon, 28 Jan 2019 14:07:00 -0800 [thread overview]
Message-ID: <1548713220.31553.31.camel@linux.intel.com> (raw)
In-Reply-To: <CAFNP8Os5TsSy27zXXtN+MZHpJN+=O5XDgY3pw2yH-0EnknoM+g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4085 bytes --]
On Mon, 2019-01-28 at 10:33 -0800, Scott Rifenbark wrote:
> Hi Don,
>
> I can't really advise you on this as I am not a Yocto developer.
> However, I can forward this question to the yocto@yoctoproject.org
> mail group and, in particular, to a resource that is looking closely
> at kernel stuff to help improve that manual and get it more up-to-
> date. That guy is named Richard Griffiths of Intel. You should be
> able to get some help with this. Sorry... I wish I was a crack YP
> developer :)
>
> Thanks,
> Scott
>
> On Sun, Jan 27, 2019 at 11:50 AM Don Osmond <dosmond@comporium.net>
> wrote:
> > Scott
> > I have been reading your https://www.yoctoproject.org/docs/2.4/kern
> > el-dev/kernel-dev.html and it has been very helpful. I have a
> > project where I am needing to get the ability to use iptables NAT
> > which does not come in the core image from Digi which also uses
> > Yocto. In my Ubuntu 16.04 LTS development VM, I am able to build
> > the base image (bitbake dey-image-qt), menuconfig the kernel config
> > (bitbake -c devshell virtual/kernel), compile the kernel (bitbake
> > -C compile virtual/kernel). The results are in the
> > /workspace/ccimx6ulsbc/tmp/deploy/images/ccimx6ulsbc as see in list
> > below:
> >
> > dosmond@ubuntu:/workspace/ccimx6ulsbc/tmp/deploy/images/ccimx6ulsbc
> > $ ls
> > boot.scr
> > dey-image-qt-x11-ccimx6ulsbc-20190127164412.boot.ubifs
> > dey-image-qt-x11-ccimx6ulsbc-20190127164412.recovery.ubifs
> > dey-image-qt-x11-ccimx6ulsbc-20190127164412.rootfs.manifest
> > dey-image-qt-x11-ccimx6ulsbc-20190127164412.rootfs.tar.bz2
> > dey-image-qt-x11-ccimx6ulsbc-20190127164412.rootfs.ubifs
> > dey-image-qt-x11-ccimx6ulsbc-20190127164412.testdata.json
> > dey-image-qt-x11-ccimx6ulsbc.boot.ubifs
> > dey-image-qt-x11-ccimx6ulsbc.manifest
> > dey-image-qt-x11-ccimx6ulsbc.recovery.ubifs
> > dey-image-qt-x11-ccimx6ulsbc.tar.bz2
> > dey-image-qt-x11-ccimx6ulsbc.testdata.json
> > dey-image-qt-x11-ccimx6ulsbc.ubifs
> > dey-image-recovery-initramfs-ccimx6ulsbc-
> > 20190127161551.rootfs.cpio.gz.u-boot.tf
> > dey-image-recovery-initramfs-ccimx6ulsbc-
> > 20190127161551.rootfs.manifest
> > dey-image-recovery-initramfs-ccimx6ulsbc-
> > 20190127161551.testdata.json
> > dey-image-recovery-initramfs-ccimx6ulsbc.cpio.gz.u-boot.tf
> > dey-image-recovery-initramfs-ccimx6ulsbc.manifest
> > dey-image-recovery-initramfs-ccimx6ulsbc.testdata.json
> > imx6ul-ccimx6ulsbc.dtb
> > imx6ul-ccimx6ulsbc-id135.dtb
> > imx6ul-ccimx6ulsbc-id136.dtb
> > imx6ul-ccimx6ulsbc-wb.dtb
> > install_linux_fw_sd.scr
> > modules--4.9-r0.5-ccimx6ulsbc-20190127182701.tgz
> > modules-ccimx6ulsbc.tgz
> > u-boot-ccimx6ulsbc1GB-2017.03-r0.imx
> > u-boot-ccimx6ulsbc1GB.imx
> > u-boot-ccimx6ulsbc-2017.03-r0.imx
> > u-boot-ccimx6ulsbc.imx
> > u-boot-ccimx6ulsbc.imx-ccimx6ulsbc
> > u-boot-ccimx6ulsbc.imx-ccimx6ulsbc1GB
> > u-boot.imx
> > zImage
> > zImage--4.9-r0.5-ccimx6ulsbc-20190127182701.bin
> > zImage--4.9-r0.5-imx6ul-ccimx6ulsbc-20190127182701.dtb
> > zImage--4.9-r0.5-imx6ul-ccimx6ulsbc-id135-20190127182701.dtb
> > zImage--4.9-r0.5-imx6ul-ccimx6ulsbc-id136-20190127182701.dtb
> > zImage--4.9-r0.5-imx6ul-ccimx6ulsbc-wb-20190127182701.dtb
> > zImage-ccimx6ulsbc.bin
> > zImage-imx6ul-ccimx6ulsbc.dtb
> > zImage-imx6ul-ccimx6ulsbc-id135.dtb
> > zImage-imx6ul-ccimx6ulsbc-id136.dtb
> > zImage-imx6ul-ccimx6ulsbc-wb.dtb
> >
> > So, what I am having an issue with are the steps to get the latest
> > kernel changes a part of the image? I thought if I ran “bitbake
> > dey-image-qt” again that it would. I think I am missing
> > something. Anything you can share would be greatly appreciated.
> > Thanks
> > Don
> >
Hi Don,
Are you asking how do you save changes to your kernel configuration so
they become part of the kernel recipe? If so, the
2.2.3 Changing The Configuration section of the Kernel Dev manual gives
an example.
If that is not what you're asking, please clarify and I will do my best
to help.
Regards,
Richard
[-- Attachment #2: Type: text/html, Size: 6742 bytes --]
prev parent reply other threads:[~2019-01-28 22:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000901d4b679$962481e0$c26d85a0$@comporium.net>
2019-01-28 18:33 ` Yocto Porject Scott Rifenbark
2019-01-28 22:07 ` Richard A Griffiths [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=1548713220.31553.31.camel@linux.intel.com \
--to=richard.a.griffiths@linux.intel.com \
--cc=dosmond@comporium.net \
--cc=srifenbark@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.