Re: [yocto] assuming someone will update kernel versions in kernel dev manual?
I scrubbed out the old examples and references. There were quite a few. You might want to take a look and be sure that everything is good. See http://www.yoctoproject.org/docs/1.8/kernel-dev/kernel-dev.html. Scott -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto- boun...@yoctoproject.org] On Behalf Of Robert P. J. Day Sent: Sunday, March 01, 2015 5:01 AM To: Yocto discussion list Subject: [yocto] assuming someone will update kernel versions in kernel dev manual? still perusing kernel dev manual and there are references to version 3.4, which doesn't even exist anymore as a recipe in OE. should i assume that someone will be doing a sweeping update of the KDM and bringing it up to, say, 3.19? rday -- === = Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday === = -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] Documentation: Add link for Yocto LTSI page to kernel manual.
Patch applied... thanks. -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto- boun...@yoctoproject.org] On Behalf Of Robert P. J. Day Sent: Sunday, March 01, 2015 4:19 AM To: Yocto discussion list Subject: [yocto] [PATCH] Documentation: Add link for Yocto LTSI page to kernel manual. Might as well point the reference to LTSI to the Yocto page for it. Signed-off-by: Robert P. J. Day rpj...@crashcourse.ca --- and throw in a hyphen while i'm there. diff --git a/documentation/kernel-dev/kernel-dev-intro.xml b/documentation/kernel-dev/kernel-dev-intro.xml index 1e5043c..a18e797 100644 --- a/documentation/kernel-dev/kernel-dev-intro.xml +++ b/documentation/kernel-dev/kernel-dev-intro.xml @@ -47,11 +47,13 @@ ulink url='YOCTO_GIT_URL;'Source Repositories/ulink under the Yocto Linux Kernel heading. New recipes for the release track the latest upstream developments -and introduce newly supported platforms. +and introduce newly-supported platforms. Previous recipes in the release are refreshed and supported for at least one additional release. As they align, these previous releases are updated to include the -latest from the Long Term Support Initiative (LTSI) project. +latest from the +ulink url='https://www.yoctoproject.org/organization/long-term- support-initiative-ltsi' +Long Term Support Initiative/ulink (LTSI) project. Also included is a linux-yocto development recipe (filenamelinux-yocto-dev.bb/filename) should you want to work with the very latest in upstream Linux kernel development and -- === = Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday === = -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Release Candidate Build for yocto-1.8_M3.rc2 now available.
-e A release candidate build for yocto-1.8_M3.rc2 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-1.8_M3.rc2 Please begin QA on this build as soon as possible. Build hash information: meta-intel : 367fd4758d23318b3adab8021d7bdc8b56e04917 meta-fsl-arm : c5dde2d3e1c89e11b9a4920ca328648664457b7c meta-minnow : 13a5f2ab84c7284647a3e067a33109c11dae0568 meta-qt3 : 3016129d90b7ac8517a5227d819f10ad417b5b45 meta-fsl-ppc : 5eeeb3ad74b72d904f805bc6e248e93e722b45c4 poky : 4a2632695eb10017abda3e7b3d904699e6db12b5 This is an automated message from The Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder Email: elizabeth.flana...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] Documentation: Ref Manual, fill out missing machines for MACHINE variable
Signed-off-by: Robert P. J. Day rpj...@crashcourse.ca
---
diff --git a/documentation/ref-manual/ref-variables.xml
b/documentation/ref-manual/ref-variables.xml
index 0346092..fc84605 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -6668,7 +6668,9 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR =
${INC_PR}.3
shipped include the following:
literallayout class='monospaced'
MACHINE ?= qemuarm
+ MACHINE ?= qemuarm64
MACHINE ?= qemumips
+ MACHINE ?= qemumips64
MACHINE ?= qemuppc
MACHINE ?= qemux86
MACHINE ?= qemux86-64
--
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] SDK generation issue
Hi Paul Eggleton, Thanks for your help in the solving the issue for adding the bsp to yocto. Now I am working on the yocto sdk generation. I am generated the yocto SDK using the yocto sdk script bitbake core-image-minimal -c populate_sdk command. With this command I am able to generte the installation script file and .manifest file. I run the installation script file. After running installation script file it propts that following message: Extracting SDK...done Setting it up...done SDK has been successfully set up and is ready to be used. After this i run the . /opt/poky/1.7/environment-setup-mips32rel-poky-linux and echo $PATH i got the correct path. After this i built wrote a small example and try to build with the sdk generated toolchain by running following command: mipsel-poky-linux-gcc test.c but i got the following errors: ** /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find crt1.o: No such file or directory /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find crti.o: No such file or directory /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find crtbegin.o: No such file or directory /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find -lgcc /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find -lgcc_s /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find -lc /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find -lgcc /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find -lgcc_s /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find crtend.o: No such file or directory /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find crtn.o: No such file or directory collect2: error: ld returned 1 exit status *** Please help me to resolving this issue. Thanks in advance. Cheers, Raghavendra Kakarla. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] dizzy 1.7 udev automount misbehaviour
Hello, Did you have a chance to understand the problem concerning the automount failure ? Best regards. Stéphane -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Fwd: dizzy 1.7 udev automount misbehaviour
-- Forwarded message -- From: Ayoub Zaki ayoub.z...@googlemail.com Date: 2015-03-02 10:24 GMT+01:00 Subject: Re: [yocto] dizzy 1.7 udev automount misbehaviour To: scerveau scerv...@gmail.com Hello Stephane, Yes please read this : http://www.volkerschatz.com/unix/advmount.html Regards 2015-03-02 9:56 GMT+01:00 scerveau scerv...@gmail.com: Hello, Did you have a chance to understand the problem concerning the automount failure ? Best regards. Stéphane -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Eclipse configuration : Battery Charger : Cross compilation on imx28evk
Hi,
First of all, thank you very much if you can take the time to read my email and
give me some answers to my questions.I'm sorry for this mail beeing quite long
but I'm trying to give you the necessary details so you would have more chances
to help me out ;)
I am pretty new to cross compilation methods and a big newbie in Linux
architecture, user's and kernel space.I'm working on an imx28evk board, linux
kernel 2.6.35 and to start with this board I'm trying to write a simple code
for Battery Monitoring.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - -
In this document (Using the PMU + Battery Charger) :
http://cache.freescale.com/files/32bit/doc/app_note/AN4199.pdfand making a ctlf
+f with keyword modif, shows that (Kernel side):
1/- in file /linux-2.6.35.3/arch/arm/mach-mx28/bus_freq.c : VDDIO can be
modified- in file /linux-2.6.35.3/arch/arm/mach-mx28/device.c : the values of
u16ChargingCurrent, u16ChargingThresholdCurrent can be modified.
2/In power_prep.c the brownout level can be modified according to the battery
reference voltage.
Correct me if I'm wrong but for me the changes made to the files described in
1/ and 2/ have to be done on the git downloaded archive and prior to bitbaking
an image. Then the image obtained contains the battery charger configured in
the way we specified it in those files.Is this correct ?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - -
But now what to do if I want to for example write a C code with Eclipse
configured using autotools to monitor the Battery Charger ?
To configure eclipse, I followed the steps in section 4.2.2 of :
http://www.yoctoproject.org/docs/1.7.1/dev-manual/dev-manual.html#modifying-temporary-source-code
As the image I bitbaked is a core-image-sato-sdk I have a rootfs directory
inside the core-image-sato-sdk directory and I don't know if this is the one to
use or to use the sysroot directory in /fsl-community/build/tmp/sysroots.
Toolchain root location: /home/pjo/fsl-community/buildSysroot Location :
/home/pjo/fsl-community/build/tmp/work/imx28evk-poky-linux-gnueabi/core-image-sato-sdk/1.0-ro/rootfsTarget
architecture : armv5te-poky-linux-gnueabi
The Hello World project is working well when exported on the target.
But now when I try to add to the Hello World project some headers like for
example : #includeddi_bc_hw.h or ddi_bc_internal.h, I created an
environment variable called INCLUDES =
-I/home/pjo/fsl-community-bsp/build/tmp/sysroots/imx28evk/usr/src/kernel/drivers/power/mxs
-I/home/pjo/fsl-community-bsp/build/tmp/sysroots/imx28evk/usr/src/kernel/arch/arm/plat-mxs/include/mach
The headers are now recognized. But when I try to access the function
ddi_bc_hwGetBatteryVoltage() :
voltage = ddi_bc_hwGetBatteryVoltage();printf(Voltage = %u \n, voltage);
There is an undefined reference to this function (defined in ddi_bc_hw.h)
In this document chapter 27 the functions for Battery Charger are described:
http://www.element14.com/community/servlet/JiveServlet/download/56891-1-44201/Freescale-i.MX28-MCIMX281AVM4B-Gallery%20MCU-Reference%20Manuals-Freescale.Reference_Maunal_1.pdf
So now my question is the following: Is it possible to use those headers when
programming ? or are they in kernel space and not accessible by the application
developper ? If not : Will the battery charger behaviour be the same all the
time after the image is copied on a SD card ?If yes : How to get rid of the
undefined reference ?
I tried to use readelf to find the libs that match the headers. But it was
unsuccessfull. So I added to several environment variables in Eclipse all the
folders named include so Eclipse ca n find the libs in the correct paths. I
tried to get some documentation on how to add packages to the build, or
modules. I've read some documentation on ioctl's but according to the reference
manual above ioctl's are only for frame buffer driver, pixel pipeline etc ...
(but not battery charger ?)
All I found is a file :
/home/pjo/fsl-community-bsp/build/tmp/work/imx28evk-poky-linux-gnueabi/core-image-sato-sdk/1.0-r0/rootfs/usr/lib/matchbox-panel/libbattery.so
But it seems like this is not the correct lib to add and it gererates many
errors during build : all of this type :
/home/pjo/fsl-community-bsp/build/tmp/sysroots/imx28evk/usr/include/gtk/gtk.h:32:21:
fatal error: gdk/gdk.h: No such file or directorySo i create the symbolic
links so the files are found but I don't think it's the correct way.
All I can do right now is a program like this : (which is capable of
retrieving the voltage in user space)
int main(void) {puts(Hello World);char voltage_from_file[12]
= ;FILE* fd = NULL;fd =
fopen(/sys/class/power_supply/battery/voltage_now, r);
[yocto] [PATCH] Documentation: Clarify a couple minor things in kernel manual, ch 2.
Replace files with ${PN} and reword discussion of defconfig file.
Signed-off-by: Robert P. J. Day rpj...@crashcourse.ca
---
diff --git a/documentation/kernel-dev/kernel-dev-common.xml
b/documentation/kernel-dev/kernel-dev-common.xml
index 56fa17d..7840c0e 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -156,23 +156,25 @@
titleChanging the Configuration/title
para
-You can make wholesale or incremental changes to the Linux
-kernel filename.config/filename file by including a
-filenamedefconfig/filename and by specifying
+You can make wholesale or incremental changes to the final
+filename.config/filename file used for the eventual
+Linux kernel configuration by including a
+filenamedefconfig/filename file and by specifying
configuration fragments in the
-ulink
url='YOCTO_DOCS_REF_URL;#var-SRC_URI'filenameSRC_URI/filename/ulink.
+ulink
url='YOCTO_DOCS_REF_URL;#var-SRC_URI'filenameSRC_URI/filename/ulink
+to be applied to that file.
/para
para
-If you have a final Linux kernel filename.config/filename
-file you want to use, copy it to a directory named
-filenamefiles/filename, which must be in
-your layer's filenamerecipes-kernel/linux/filename
-directory, and name the file defconfig.
-Then, add the following lines to your linux-yocto
+If you have a complete, working Linux kernel
filename.config/filename
+file you want to use for the configuration, as before, copy
that file
+to the appropriate filename${PN}/filename directory in your
+layer's filenamerecipes-kernel/linux/filename directory,
+and rename the copied file to defconfig.
+Then, add the following lines to the linux-yocto
filename.bbappend/filename file in your layer:
literallayout class='monospaced'
- FILESEXTRAPATHS_prepend := ${THISDIR}/files:
+ FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}:
SRC_URI += file://defconfig
/literallayout
The filenameSRC_URI/filename tells the build system how to
@@ -181,7 +183,7 @@
extends the
ulink
url='YOCTO_DOCS_REF_URL;#var-FILESPATH'filenameFILESPATH/filename/ulink
variable (search directories) to include the
-filenamefiles/filename directory you created for the
+filename${PN}/filename directory you created to hold the
configuration changes.
/para
--
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] (no subject)
Hi Yocto Team, Now I am working on the yocto sdk generation. I am generated the yocto SDK using the yocto sdk script bitbake core-image-minimal -c populate_sdk command. With this command I am able to generte the installation script file and .manifest file. I run the installation script file. After running installation script file it propts that following message: Extracting SDK...done Setting it up...done SDK has been successfully set up and is ready to be used. After this i run the . /opt/poky/1.7/environment-setup-mips32rel-poky-linux and echo $PATH i got the correct path. After this i built wrote a small example and try to build with the sdk generated toolchain by running following command: mipsel-poky-linux-gcc test.c but i got the following errors: ** /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find crt1.o: No such file or directory /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find crti.o: No such file or directory /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find crtbegin.o: No such file or directory /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find -lgcc /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find -lgcc_s /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find -lc /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find -lgcc /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find -lgcc_s /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find crtend.o: No such file or directory /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find crtn.o: No such file or directory collect2: error: ld returned 1 exit status *** Please help me to resolving this issue. Thanks in advance. Cheers, Raghavendra Kakarla. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Recipe reporting system] Upgradable recipe name list
This mail was sent out by Recipe reporting system. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade this time, they can fill in RECIPE_NO_UPDATE_REASON_pn-xxx in upstream_tracking files to ignore this recipe remainder until newer upstream version was detected. Example: RECIPE_NO_UPDATE_REASON_pn-xxx = Not upgrade to 2.0 is unstable You can check the detail information at: http://packages.yoctoproject.org/ Package Version Upstream version Maintainer NoUpgradeReason --- --- -- nfs-utils 1.3.11.3.2 Alejandro Hernandez midori0.5.80.5.9 Alejandro Hernandez python-smmap 0.8.20.9.0 Alejandro Hernandez gnome-icon-theme 2.31.0 3.12.0Alejandro Hernandez waiting for the sato gtk3 port jpeg 8d 9aAníbal Limón webkit-gtk 1.8.3 doesn't wo... apt 0.9.9.4 1.0.9.7 Aníbal Limón dpkg 1.17.21 1.17.24 Aníbal Limón sqlite3 3.8.7.4 3.8.8.3. Aníbal Limón screen4.0.34.2.1 Aníbal Limón nettle2.7.13.0 Armin Kuster 3.0.0 breaks gnutls, api ch... resolvconf1.76 1.76.1Chen Qi console-tools 0.3.21999.03.02Chen Qi util-linux2.25.2 2.26 Chen Qi kmod 19+gitX 20+gitAUTOINC+d9c... Chen Qi curl 7.40.0 7.41.0Chen Qi sudo 1.8.11p2 1.8.12Chen Qi sysstat 11.0.2 11.1.3Chen Qi xz5.2.05.2.1 Chen Qi dbus-glib 0.1020.104 Chong Lu dbus-test 1.8.10 1.9.12Chong Lu dbus 1.8.10 1.9.12Chong Lu D-BUS 1.9.x is the developm... bison 2.7.13.0.4 Chong Lu bluez44.1015.28 Cristian Iorga BlueZ 5.x is not backward-c... gst-plugin-bluetooth 4.1015.28 Cristian Iorga iproute2 3.17.0 3.19.0Cristian Iorga alsa-lib 1.0.28 1.0.29Cristian Iorga alsa-utils-alsaconf 1.0.28 1.0.29Cristian Iorga alsa-utils1.0.28 1.0.29Cristian Iorga gst-ffmpeg0.10.13 0.11.2Cristian Iorga gst-fluendo-mp3 0.10.31 0.10.32 Cristian Iorga gst-plugins-bad 0.10.23 1.4.5 Cristian Iorga not compatible with gst-flu... gst-plugins-base 0.10.36 1.4.5 Cristian Iorga not compatible with gst-flu... gst-plugins-good 0.10.31 1.4.5 Cristian Iorga not compatible with gst-flu... gst-plugins-ugly 0.10.19 1.4.5 Cristian Iorga gstreamer 0.10.36 1.4.5 Cristian Iorga not compatible with gst-fl... libatomics-ops7.2 7.4.0 Cristian Iorga speex 1.2rc1 1.2rc2Cristian Iorga db6.0.30 6.1.23.NC Cristian Iorga API compatibility issue libical 1.0.01.0.1 Cristian Iorga quota 4.01 4.02 Cristian Iorga hwlatdetect 0.89 0.91 Darren Hart rt-tests 0.89 0.91 Darren Hart dhcp 4.3.14.3.2 Hongxu Jia socat 1.7.2.4 1.7.3.0 Hongxu Jia distcc3.1 3.2rc1Hongxu Jia qmmp 0.7.70.8.3 Hongxu Jia patch 2.7.12.7.4 Hongxu Jia perl 5.20.0 5.21.9Hongxu Jia createrepo0.4.11 0.10.3Hongxu Jia Versions after 0.9.* use YU... bash 4.3 4.3.30Hongxu Jia The latest version in yocto... libgcrypt 1.6.21.6.3 Hongxu Jia groff 1.22.2 1.22.3Hongxu Jia 1.18.1.4 is latest GPLv2 Ve... gnupg 2.1.12.1.2 Hongxu Jia man-pages 3.76 3.80 Hongxu Jia directfb 1.7.61.7.7
Re: [yocto] [PATCH] Documentation: Clarify a couple minor things in kernel manual, ch 2.
Applied... thanks Robert.
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Robert P. J. Day
Sent: Monday, March 02, 2015 3:13 AM
To: Yocto discussion list
Subject: [yocto] [PATCH] Documentation: Clarify a couple minor things in
kernel manual, ch 2.
Replace files with ${PN} and reword discussion of defconfig file.
Signed-off-by: Robert P. J. Day rpj...@crashcourse.ca
---
diff --git a/documentation/kernel-dev/kernel-dev-common.xml
b/documentation/kernel-dev/kernel-dev-common.xml
index 56fa17d..7840c0e 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -156,23 +156,25 @@
titleChanging the Configuration/title
para
-You can make wholesale or incremental changes to the Linux
-kernel filename.config/filename file by including a
-filenamedefconfig/filename and by specifying
+You can make wholesale or incremental changes to the final
+filename.config/filename file used for the eventual
+Linux kernel configuration by including a
+filenamedefconfig/filename file and by specifying
configuration fragments in the
-ulink url='YOCTO_DOCS_REF_URL;#var-
SRC_URI'filenameSRC_URI/filename/ulink.
+ulink url='YOCTO_DOCS_REF_URL;#var-
SRC_URI'filenameSRC_URI/filename/ulink
+to be applied to that file.
/para
para
-If you have a final Linux kernel filename.config/filename
-file you want to use, copy it to a directory named
-filenamefiles/filename, which must be in
-your layer's filenamerecipes-kernel/linux/filename
-directory, and name the file defconfig.
-Then, add the following lines to your linux-yocto
+If you have a complete, working Linux kernel
filename.config/filename
+file you want to use for the configuration, as before, copy
that file
+to the appropriate filename${PN}/filename directory in
your
+layer's filenamerecipes-kernel/linux/filename directory,
+and rename the copied file to defconfig.
+Then, add the following lines to the linux-yocto
filename.bbappend/filename file in your layer:
literallayout class='monospaced'
- FILESEXTRAPATHS_prepend := ${THISDIR}/files:
+ FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}:
SRC_URI += file://defconfig
/literallayout
The filenameSRC_URI/filename tells the build system how to
@@ -181,7 +183,7 @@
extends the
ulink url='YOCTO_DOCS_REF_URL;#var-
FILESPATH'filenameFILESPATH/filename/ulink
variable (search directories) to include the
-filenamefiles/filename directory you created for the
+filename${PN}/filename directory you created to
+ hold the
configuration changes.
/para
--
===
=
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
===
=
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] difference in explanation of kernel build directory
while kernel dev manual claims that:
... the Build Directory:
${WORKDIR}/linux-${MACHINE}-${KTYPE}-build
the include file linux-yocto.inc actually contains the line:
B = ${WORKDIR}/linux-${PACKAGE_ARCH}-${LINUX_KERNEL_TYPE}-build
someone else can decide if this difference should be resolved.
rday
--
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] kernel dev manual: KBRANCH_DEFAULT is dead, jim.
On Mon, 2 Mar 2015, Rifenbark, Scott M wrote: Robert, I have updated the docs to take care of this issue. KBRANCH_DEFAULT is gone from the variable glossary, KBRANCH has been updated as well as the section in the kernel-dev manual that mentions its use. cool ... stay tuned for my next session of annoying, pedantic whining. :-) rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] merging eclipse-poky-juno eclipse-poky-kepler
Todor and Beth, I updated the section in the dev-manual that provides the steps for installing the plug-in from the latest source code. I need verification if this section is technically correct now. See http://www.yoctoproject.org/docs/1.8/dev-manual/dev-manual.html#zip-file-method. Thanks, Scott -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto- boun...@yoctoproject.org] On Behalf Of Minchev, Todor Sent: Tuesday, February 24, 2015 4:37 AM To: yocto@yoctoproject.org Subject: [yocto] merging eclipse-poky-juno eclipse-poky-kepler I just wanted to check if anyone is using the Yocto ADT Eclipse plug-in from the eclipse-poky repo here: http://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky/ This repo hasn't been maintained for a couple of years. The most up-to-date code for the ADT plug-in for Eclipse Juno Kepler can be found in these two repos. http://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky-juno/ http://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky-kepler/ We have decided to merge the two repos above and maintain the plug-in under the original eclipse-poky repo for all versions of Eclipse. In other words, we are planning to overwrite eclipse-poky with the merge result from eclipse-poky-juno and eclipse-poky-kepler. I am planning to do this on Friday, 27 Feb 2015. If anyone has any objections please let me know before then. Thanks, Todor -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] kernel dev manual: KBRANCH_DEFAULT is dead, jim.
Robert, I have updated the docs to take care of this issue. KBRANCH_DEFAULT is gone from the variable glossary, KBRANCH has been updated as well as the section in the kernel-dev manual that mentions its use. Thanks, Scott -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto- boun...@yoctoproject.org] On Behalf Of Robert P. J. Day Sent: Wednesday, February 25, 2015 3:20 AM To: Yocto discussion list Subject: [yocto] kernel dev manual: KBRANCH_DEFAULT is dead, jim. ch 3 still refers to the variable KBRANCH_DEFAULT even though that variable was tossed back in march of 2014: commit e631fc989b08873f559c5927117301294f04298c Author: Bruce Ashfield bruce.ashfi...@windriver.com Date: Tue Mar 18 23:01:19 2014 -0400 kernel-yocto: remove KBRANCH_DEFAULT KBRANCH_DEFAULT is no longer used, so we can remove it from all recipes (and it won't be missed). rday -- === = Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday === = -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] kernel dev manual ... KMACHINE/fri2 content seems out of date
again, kernel dev manual, section 3.2: Multiple BSPs can reuse the same KMACHINE name if they are built using the same BSP description. The fri2 and fri2-noemgd BSP combination in the meta-intel layer is a good example of two BSPs using the same KMACHINE value (i.e. fri2). i don't think that's accurate anymore ... i don't see KMACHINE being used relative to fri2 stuff. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
