Re: [yocto] Build appliance

[Ilya Dmitrichenko]

I have made some progress, and found out that it's `
*virtual/fakeroot-native*` that had to be in `*ASSUME_PROVIDED`.* But now I
find there are quite a few more assumptions of the path to native tools.
I'll see what I can patch locally and send out an update if get something
working.
On Sat Jan 24 2015 at 11:00:47 PM Ilya Dmitrichenko <
errordevelo...@gmail.com> wrote:

> Adding Robert to CC list...
>
> On Sat Jan 24 2015 at 9:53:32 PM Ilya Dmitrichenko <
> errordevelo...@gmail.com> wrote:
>
>> Hi List,
>>
>> I have attempted to define a custom build appliance image, with some
>> degree of success. The only problem is that I have noticed is there is
>> still a whole lot of `*-native` packages being pulled in when trying to
>> build something. So I have attempted adding all of those to my image and
>> set `ASSUME_PROVIDED` accordingly, it was still trying to build
>> pseudo-native and sqlite3-native for some reason... Ideally, I'd like to
>> have all of the `*-native` deps pre-installed on my build appliance's base
>> filesystem, I believe this should work and I shouldn't have to bootstrap
>> `tmp/work/sysroots/` and use the sysroot in `/usr` instead.
>>
>> More specifically, I am trying to build a container image that would
>> cover the purpose of the build appliance and SDKs/ADTs, I think container
>> could simplify a lot for Yocto... I haven't fully figured it out yet, still
>> exploring the options, so hope the idea makes sense overall.
>>
>> Cheers,
>> Ilya
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] dansguardian

[Paul Eggleton]

Hi Mahdi,

On Saturday 24 January 2015 11:05:45 Mahdi Saadat wrote:
> Does anyone knows about how put dansguardian on core-image-minimal?
> I Did some steps on creating the recipe but had some errors on config stage.

You'll need to be a bit more specific about the errors you received before 
anyone will be able to help.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] One recipe, two gits with destsuffix, how to patch?

[Paul Eggleton]

Hi Kalle,

On Saturday 24 January 2015 08:34:56 Kalle Komierowski wrote:
> I'm working with the ti-compat-wireless recipe.
> It contains two gits like this:
> 
> SRC_URI =
> "git://git.ti.com/wilink8-wlan/wl18xx.git;branch=${BRANCH_wl18xx};destsuffi
> x=wl18xx;name=wl18xx \
> git://git.ti.com/wilink8-wlan/backports.git;branch=${BRANCH_backports};dest
> suffix=backports;name=backports \ file://wl18xx.patch \
> 
> Now I want to add the wl18xx.patch file, and this file ends up in the S and
> applying it fails since the git it should be applied to is under
> S/backports due to the destsuffix.
> 
> I tried to use the quilt and create new patches from the S but they fail to.
> 
> What would be the correct way of adding a patch so it applies to backports?

You may find the patchdir option for the patch SRC_URI entry to be useful. I 
should imagine you'll want something like:
...
  file://wl18xx.patch;patchdir=../backports
...

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] One recipe, two gits with destsuffix, how to patch?

[Kalle Komierowski]

Thanks Paul!

I was hoping it was as simple as that but I couldn't find info about it. Maybe 
if it was just called destsuffix like when it's used for gits.

BR
-Kalle Komierowski



On January 26, 2015, Paul Eggleton  wrote:
> Hi Kalle,
> 
> On Saturday 24 January 2015 08:34:56 Kalle Komierowski wrote:
> > I'm working with the ti-compat-wireless recipe.
> > It contains two gits like this:
> > 
> > SRC_URI =
> > "git://git.ti.com/wilink8-wlan/wl18xx.git;branch=${BRANCH_wl18xx};destsuffi
> > x=wl18xx;name=wl18xx \
> > git://git.ti.com/wilink8-wlan/backports.git;branch=${BRANCH_backports};dest
> > suffix=backports;name=backports \ file://wl18xx.patch \
> > 
> > Now I want to add the wl18xx.patch file, and this file ends up in the S and
> > applying it fails since the git it should be applied to is under
> > S/backports due to the destsuffix.
> > 
> > I tried to use the quilt and create new patches from the S but they fail to.
> > 
> > What would be the correct way of adding a patch so it applies to backports?
> > 
> You may find the patchdir option for the patch SRC_URI entry to be useful. I
> should imagine you'll want something like:
> ...
> file://wl18xx.patch;patchdir=../backports
> ...
> 
> Cheers,
> Paul
> 
> -- 
> 
> Paul Eggleton
> Intel Open Source Technology Centre
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] One recipe, two gits with destsuffix, how to patch?

[Paul Eggleton]

On Monday 26 January 2015 11:24:50 Kalle Komierowski wrote:
> On January 26, 2015, Paul Eggleton  wrote:
> > Hi Kalle,
> > 
> > On Saturday 24 January 2015 08:34:56 Kalle Komierowski wrote:
> > > I'm working with the ti-compat-wireless recipe.
> > > It contains two gits like this:
> > > 
> > > SRC_URI =
> > > "git://git.ti.com/wilink8-wlan/wl18xx.git;branch=${BRANCH_wl18xx};destsu
> > > ffi
> > > x=wl18xx;name=wl18xx \
> > > git://git.ti.com/wilink8-wlan/backports.git;branch=${BRANCH_backports};d
> > > est
> > > suffix=backports;name=backports \ file://wl18xx.patch \
> > > 
> > > Now I want to add the wl18xx.patch file, and this file ends up in the S
> > > and
> > > applying it fails since the git it should be applied to is under
> > > S/backports due to the destsuffix.
> > > 
> > > I tried to use the quilt and create new patches from the S but they fail
> > > to.
> > > 
> > > What would be the correct way of adding a patch so it applies to
> > > backports?
> > 
> > You may find the patchdir option for the patch SRC_URI entry to be useful.
> > I should imagine you'll want something like:
> > ...
> > file://wl18xx.patch;patchdir=../backports
> > ...
> > 
>
> Thanks Paul!
> 
> I was hoping it was as simple as that but I couldn't find info about it.
> Maybe if it was just called destsuffix like when it's used for gits.

destsuffix and patchdir aren't quite the same though - destsuffix controls 
where 
the git repository is unpacked, whereas patchdir is the directory that the 
patch is applied in rather than where the patch file itself is written to.

(Oddly, as it happens, patchdir is in the documentation and destsuffix isn't - 
Scott, we'll have to take care of that.)

Cheers,
Paul 

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Installing a Yocto image on BeagleBone Black MMC

[Christian Schultz]

I looked at the doc, and it gives the instructions to write the image to
othe SD Card and run from the card. I didn't find yet instructions about
how to write the images to the MMC. For example, I made an image with
Yocto, and from the system, I should create the partitions (for boot and
rootfs), format them, and copy the contents, but my image lacks the
mkfs.vfat and mkfs.ext3, so I didn't figure how to setup the MMC memory to
receive the files.

Can somebody please help me with those steps?

Best regards
Christian

On Fri, Jan 23, 2015 at 12:00 AM, Kevin Hao  wrote:

> On Thu, Jan 22, 2015 at 09:41:51AM -0200, Christian Schultz wrote:
> > Hello
> >
> > I'm new to Yocto, I baked a core-image-minimal and booted it via SD Card
> on my
> > BeagleBone Black. I erased the contents on the MMC in order to boot from
> SD
> > Card.
> > I'm searching for instructions on how do I install or flash the MMC with
> the
> > Yocto image I created, in order to boot the image without the SD Card,
> but I
> > can't find how to do it, anyone knows where I can find such instructions?
>
> Have you looked at the README.hardware in yocto? There are steps about how
> to
> flash the SD card in a host environment. You can copy the built images to
> the
> SD card and then use the same steps to flash the eMMC on the target. Please
> remember to change the block device to mmcblk1 when you are executing these
> commands on target.
>
> Thanks,
> Kevin
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-cgl][PATCH] meta-fsl-ppc: layer.conf: Rename BBFILE_COLLECTIONS

[Alexey Firago]

BBFILE_COLLECTIONS is currently set to "cgl" which is also used
by meta-cgl-common. Some tools/scripts use this field for
automatic layers detection, so rename it to "fsl-ppc-cgl".

Signed-off-by: Alexey Firago 
---
 meta-fsl-ppc/conf/layer.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-fsl-ppc/conf/layer.conf b/meta-fsl-ppc/conf/layer.conf
index 6818475..be345ff 100644
--- a/meta-fsl-ppc/conf/layer.conf
+++ b/meta-fsl-ppc/conf/layer.conf
@@ -5,6 +5,6 @@ BBPATH .= ":${LAYERDIR}"
 BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/recipes-*/*/*.bbappend"
 
-BBFILE_COLLECTIONS += "cgl"
+BBFILE_COLLECTIONS += "fsl-ppc-cgl"
 BBFILE_PATTERN_cgl = "^${LAYERDIR}/"
 BBFILE_PRIORITY_cgl = "7"
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] adding all the pieces of WiFi to core-image-minimal

[James Abernathy]

> On Jan 23, 2015, at 12:37 PM, Gary Thomas  wrote:
> 
> On 2015-01-23 10:24, Jim Abernathy wrote:
>> I'm starting a project mostly for self-education.  I have already done the 
>> project using Ubuntu Server 14.04 using a Intel NUC and a Pandaboard as 
>> targets.  Now I want to see how
>> easy it is to move it to Yocto.
>> 
>> Starting with the NUC, I can boot Dizzy 1.7.1 core-image-minimal and 
>> core-image-sato, both built with bitbake and not the prebuilt images. 
>> However, core-image-minimal doesn't have
>> WiFi and core-image-sato does, but I don't need all the GUI stuff.  It's a 
>> headless application.
>> 
>> So what is recommended; eliminating the GUI from sato or adding wifi and 
>> wpa-supplicant, etc to minimal??  Also any pointers to how to do the 
>> adding/subtracting would be most helpful.
>> 
>> Once this is working all I have to do is put apache-tomcat, and 
>> openjdk-7-jre, then my application.
> 
> We use just iw & wpa-supplicant and set up the configuration
> files manually (e.g. the wpa-supplicant configurations).

Could you help with a little more details.  What I envision is adding an append 
statement of some kind to local.conf to load in the wireless related files to 
core-image-minimal, same with openjdk-7-jre and tomcat7, but my first efforts 
have generated some unintelligible error for me.  So that’s why I’m looking for 
direction on where to start with this.

Jim A

> 
> -- 
> 
> Gary Thomas |  Consulting for the
> MLB Associates  |Embedded world
> 
> -- 
> ___
> 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] [meta-cgl][PATCH] meta-fsl-ppc: layer.conf: Rename BBFILE_COLLECTIONS

[Gary Thomas]

On 2015-01-23 02:47, Alexey Firago wrote:

BBFILE_COLLECTIONS is currently set to "cgl" which is also used
by meta-cgl-common. Some tools/scripts use this field for
automatic layers detection, so rename it to "fsl-ppc-cgl".

Signed-off-by: Alexey Firago 
---
  meta-fsl-ppc/conf/layer.conf | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-fsl-ppc/conf/layer.conf b/meta-fsl-ppc/conf/layer.conf
index 6818475..be345ff 100644
--- a/meta-fsl-ppc/conf/layer.conf
+++ b/meta-fsl-ppc/conf/layer.conf
@@ -5,6 +5,6 @@ BBPATH .= ":${LAYERDIR}"
  BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/recipes-*/*/*.bbappend"

-BBFILE_COLLECTIONS += "cgl"
+BBFILE_COLLECTIONS += "fsl-ppc-cgl"
  BBFILE_PATTERN_cgl = "^${LAYERDIR}/"
  BBFILE_PRIORITY_cgl = "7"


Shouldn't these last two also be changed, e.g.
  BBFILE_PATTERN_fsl-ppc-cgl

Also, why is it called 'cgl' in the first place?  The logic
of that name eludes me...

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] adding all the pieces of WiFi to core-image-minimal

[Gary Thomas]

On 2015-01-26 06:29, James Abernathy wrote:



On Jan 23, 2015, at 12:37 PM, Gary Thomas  wrote:

On 2015-01-23 10:24, Jim Abernathy wrote:

I'm starting a project mostly for self-education.  I have already done the 
project using Ubuntu Server 14.04 using a Intel NUC and a Pandaboard as 
targets.  Now I want to see how
easy it is to move it to Yocto.

Starting with the NUC, I can boot Dizzy 1.7.1 core-image-minimal and 
core-image-sato, both built with bitbake and not the prebuilt images. However, 
core-image-minimal doesn't have
WiFi and core-image-sato does, but I don't need all the GUI stuff.  It's a 
headless application.

So what is recommended; eliminating the GUI from sato or adding wifi and 
wpa-supplicant, etc to minimal??  Also any pointers to how to do the 
adding/subtracting would be most helpful.

Once this is working all I have to do is put apache-tomcat, and openjdk-7-jre, 
then my application.


We use just iw & wpa-supplicant and set up the configuration
files manually (e.g. the wpa-supplicant configurations).


Could you help with a little more details.  What I envision is adding an append 
statement of some kind to local.conf to load in the wireless related files to 
core-image-minimal, same with openjdk-7-jre and tomcat7, but my first efforts 
have generated some unintelligible error for me.  So that’s why I’m looking for 
direction on where to start with this.


What was the error you got?  I'll bet it was for 'iw' which
is a package from meta-oe, so you'll need to add that layer

Once you've added the meta-oe layer, you should be able to
put this line in your local.conf:
  CORE_IMAGE_EXTRA_INSTALL += " iw wpa-supplicant"

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] meta-qt5 problem in yocto 1.7

[peterengcomau001]

I have just downloaded yocto poky 1.7 and try to build an image. I get
teh follwing problems with fetching qt5 source:
Summary: 5 tasks failed:
  /home/lachlan/poky-1.7/meta-qt5/recipes-qt/qt5/qt3d_git.bb,
do_fetch
 
/home/lachlan/poky-1.7/meta-qt5/recipes-qt/qt5/qtmultimedia_5.3.2.bb,
do_fetch
  /home/lachlan/poky-1.7/meta-qt5/recipes-qt/qt5/qtwebkit_5.3.2.bb,
do_fetch
 
/home/lachlan/poky-1.7/meta-atmel/recipes-multimedia/gstreamer1.0-plugins/gstreamer1.0-plugins-hantro_1.0.bb,
do_configure
 
/home/lachlan/poky-1.7/meta-atmel/recipes-utils/obp-utils/obp-utils_git.bb,
do_install

I presume the last two problems(do_configure & do_install)  result
from dependencies on the previous three failed fetches.

The more complete error code for teh first three errors is:
WARNING: Failed to fetch URL
git://qt.gitorious.org/qt/qt3d.git;branch=master, attempting MIRRORS
if available
ERROR: Fetcher failure: Unable to find revision
8a9723d7420829a2ba0141a9f7d8dc8cd11d8331 in branch master even from
upstream
ERROR: Function failed: Fetcher failure for URL:
'git://qt.gitorious.org/qt/qt3d.git;branch=master'. Unable to fetch
URL from any source.
ERROR: Logfile of failure stored in:
/home/lachlan/poky-1.7/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/qt3d/5.3.99+5.4.0-beta1+gitAUTOINC+8a9723d742-r0/temp/log.do_fetch.29304
ERROR: Task 1993
(/home/lachlan/poky-1.7/meta-qt5/recipes-qt/qt5/qt3d_git.bb,
do_fetch) failed with exit code '1'
WARNING: Failed to fetch URL
http://download.qt-project.org/official_releases/qt/5.3/5.3.2/submodules/qtmultimedia-opensource-src-5.3.2.tar.xz,
attempting MIRRORS if available
ERROR: Fetcher failure: Fetch command failed with exit code 4, no
output
ERROR: Function failed: Fetcher failure for URL:
'http://download.qt-project.org/official_releases/qt/5.3/5.3.2/submodules/qtmultimedia-opensource-src-5.3.2.tar.xz'.
Unable to fetch URL from any source.
ERROR: Logfile of failure stored in:
/home/lachlan/poky-1.7/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/qtmultimedia/5.3.2-r0/temp/log.do_fetch.7762
ERROR: Task 535
(/home/lachlan/poky-1.7/meta-qt5/recipes-qt/qt5/qtmultimedia_5.3.2.bb,
do_fetch) failed with exit code '1'
WARNING: Failed to fetch URL
http://www.apache.org/dist/subversion/subversion-1.8.9.tar.bz2,
attempting MIRRORS if available
WARNING: Failed to fetch URL
http://download.qt-project.org/official_releases/qt/5.3/5.3.2/submodules/qtwebkit-opensource-src-5.3.2.tar.xz,
attempting MIRRORS if available
ERROR: Fetcher failure: Fetch command failed with exit code 4, no
output
ERROR: Function failed: Fetcher failure for URL:
'http://download.qt-project.org/official_releases/qt/5.3/5.3.2/submodules/qtwebkit-opensource-src-5.3.2.tar.xz'.
Unable to fetch URL from any source.
ERROR: Logfile of failure stored in:
/home/lachlan/poky-1.7/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/qtwebkit/5.3.2-r0/temp/log.do_fetch.19587
ERROR: Task 675
(/home/lachlan/poky-1.7/meta-qt5/recipes-qt/qt5/qtwebkit_5.3.2.bb,
do_fetch) failed with exit code '1'
NOTE: validating kernel config, see log.do_kernel_configcheck for
details

If I manually download the one of the files, e.g.  :
'http://download.qt-project.org/official_releases/qt/5.3/5.3.2/submodules/qtwebkit-opensource-src-5.3.2.tar.xz
This works fine.

Can anyone suggest what I can look fro to determine the problem. I
have tried this a number of time over 24 hours and get the exact same
failures.

Thank you for any suggestions moving forward.

Regards
Lachlan

 Message sent via Adam Internet WebMail - http://www.adam.com.au/
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] adding all the pieces of WiFi to core-image-minimal

[James Abernathy]

> On Jan 26, 2015, at 8:49 AM, Gary Thomas  wrote:
> 
> On 2015-01-26 06:29, James Abernathy wrote:
>> 
>>> On Jan 23, 2015, at 12:37 PM, Gary Thomas  wrote:
>>> 
>>> On 2015-01-23 10:24, Jim Abernathy wrote:
 I'm starting a project mostly for self-education.  I have already done the 
 project using Ubuntu Server 14.04 using a Intel NUC and a Pandaboard as 
 targets.  Now I want to see how
 easy it is to move it to Yocto.
 
 Starting with the NUC, I can boot Dizzy 1.7.1 core-image-minimal and 
 core-image-sato, both built with bitbake and not the prebuilt images. 
 However, core-image-minimal doesn't have
 WiFi and core-image-sato does, but I don't need all the GUI stuff.  It's a 
 headless application.
 
 So what is recommended; eliminating the GUI from sato or adding wifi and 
 wpa-supplicant, etc to minimal??  Also any pointers to how to do the 
 adding/subtracting would be most helpful.
 
 Once this is working all I have to do is put apache-tomcat, and 
 openjdk-7-jre, then my application.
>>> 
>>> We use just iw & wpa-supplicant and set up the configuration
>>> files manually (e.g. the wpa-supplicant configurations).
>> 
>> Could you help with a little more details.  What I envision is adding an 
>> append statement of some kind to local.conf to load in the wireless related 
>> files to core-image-minimal, same with openjdk-7-jre and tomcat7, but my 
>> first efforts have generated some unintelligible error for me.  So that’s 
>> why I’m looking for direction on where to start with this.
> 
> What was the error you got?  I'll bet it was for 'iw' which
> is a package from meta-oe, so you'll need to add that layer
> 
> Once you've added the meta-oe layer, you should be able to
> put this line in your local.conf:
>  CORE_IMAGE_EXTRA_INSTALL += " iw wpa-supplicant”
> 
Okay, what I don’t get is the fact that without any additional layers, bitbake 
core-image-sato builds all the WiFi features I need.  bitbake 
core-image-minimal does not.  So I’m thinking that there is some 
CORE_IMAGE_EXTRA_INSTALL statement that can just add what is needed without 
extra layers.  

I guess it just doesn’t make sense to me right now.

Jim A


> -- 
> 
> Gary Thomas |  Consulting for the
> MLB Associates  |Embedded world
> 
> -- 
> ___
> 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] [meta-yocto] [PATCH 0/1] tiny-init: set proper S value

[Burton, Ross]

On 24 January 2015 at 09:22, Petter Mabäcker  wrote:

> Since bug [5627] has reached poky repo, can you please consider propose
> merging of below change to meta-yocto, to avoid the warning about 'S' not
> set to a proper value?
>

Whoops, I missed that when merging the other pieces, thanks for pinging.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] adding all the pieces of WiFi to core-image-minimal

[Gary Thomas]

On 2015-01-26 08:26, James Abernathy wrote:



On Jan 26, 2015, at 8:49 AM, Gary Thomas mailto:g...@mlbassoc.com>> wrote:

On 2015-01-26 06:29, James Abernathy wrote:



On Jan 23, 2015, at 12:37 PM, Gary Thomas mailto:g...@mlbassoc.com>> wrote:

On 2015-01-23 10:24, Jim Abernathy wrote:

I'm starting a project mostly for self-education.  I have already done the 
project using Ubuntu Server 14.04 using a Intel NUC and a Pandaboard as 
targets.  Now I want to see how
easy it is to move it to Yocto.

Starting with the NUC, I can boot Dizzy 1.7.1 core-image-minimal and 
core-image-sato, both built with bitbake and not the prebuilt images. However, 
core-image-minimal doesn't have
WiFi and core-image-sato does, but I don't need all the GUI stuff.  It's a 
headless application.

So what is recommended; eliminating the GUI from sato or adding wifi and 
wpa-supplicant, etc to minimal??  Also any pointers to how to do the 
adding/subtracting would be most
helpful.

Once this is working all I have to do is put apache-tomcat, and openjdk-7-jre, 
then my application.


We use just iw & wpa-supplicant and set up the configuration
files manually (e.g. the wpa-supplicant configurations).


Could you help with a little more details.  What I envision is adding an append 
statement of some kind to local.conf to load in the wireless related files to 
core-image-minimal,
same with openjdk-7-jre and tomcat7, but my first efforts have generated some 
unintelligible error for me.  So that’s why I’m looking for direction on where 
to start with this.


What was the error you got?  I'll bet it was for 'iw' which
is a package from meta-oe, so you'll need to add that layer

Once you've added the meta-oe layer, you should be able to
put this line in your local.conf:
 CORE_IMAGE_EXTRA_INSTALL += " iw wpa-supplicant”


Okay, what I don’t get is the fact that without any additional layers, bitbake 
core-image-sato builds all the WiFi features I need.  bitbake 
core-image-minimal does not.  So I’m
thinking that there is some CORE_IMAGE_EXTRA_INSTALL statement that can just 
add what is needed without extra layers.

I guess it just doesn’t make sense to me right now.


Try using
  CORE_IMAGE_EXTRA_INSTALL += " packagegroup-base-wifi"
which will bring in 'wireless-tools' and 'wpa-supplicant'.

I prefer 'iw' to 'wireless-tools' as it is newer and [IMO]
simpler to use.

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [Recipe reporting system] Upgradable recipe name list

[anibal . limon]

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/upgradepkgname

Package   VersionUpstream version  Maintainer   
NoUpgradeReason
  -    ---  
--
gnome-icon-theme  2.31.0 3.7.4 Alejandro Hernandez  
waiting for the sato gtk3 port
midori0.5.8  0.5.9 Alejandro Hernandez
dpkg  1.17.211.17.23   Aníbal Limón
screen4.0.3  4.2.1 Aníbal Limón
apt   0.9.9.41.0.9.6   Aníbal Limón
jpeg  8d 9 Aníbal Limón 
webkit-gtk 1.8.3 doesn't wo...
nettle2.7.1  3.0   Armin Kuster 
3.0.0 breaks gnutls, api ch...
linux-libc-headers3.17.7 3.18.3Bruce Ashfield
sysstat   11.0.2 11.1.2Chen Qi
busybox   1.22.1 1.23.0Chen Qi
systemd   216+gitX   218+gitAUTOINC+cc...  Chen Qi
console-tools 0.3.2  1999.03.02Chen Qi
bison 2.7.1  3.0.4 Chong Lu
dbus  1.8.10 1.9.6 Chong Lu 
D-BUS 1.9.x is the developm...
quota 4.01   4.02  Cristian Iorga
libical   1.0.0  1.0.1 Cristian Iorga
pulseaudio5.05.99.3Cristian Iorga
libatomics-ops7.27.4.0 Cristian Iorga
neon  0.30.0 0.30.1Cristian Iorga
speex 1.2rc1 1.2rc2Cristian Iorga
gst-fluendo-mpegd...  0.10.720.10.85   Cristian Iorga
gst-fluendo-mp3   0.10.310.10.32   Cristian Iorga
db6.0.30 6.1.19Cristian Iorga   
API compatibility issue
flac  1.3.0  1.3.1 Cristian Iorga
connman   1.26   1.27  Cristian Iorga
gst-plugin-bluetooth  4.101  5.27  Cristian Iorga
bluez44.101  5.27  Cristian Iorga   
BlueZ 5.x is not backward-c...
iproute2  3.17.0 3.18.0Cristian Iorga
ofono 1.15   1.16  Cristian Iorga
neard 0.14   0.15  Cristian Iorga
harfbuzz  0.9.37 0.9.38Cristian Iorga
linux-yocto   3.14.24+gitX   3.14.26+gitAUTOIN...  Darren Hart
kernelshark   1.2+gitX   2.5.1+gitAUTOINC+...  Darren Hart  
0.2 is the latest version.
trace-cmd 2.3.2+gitX 2.5.1+gitAUTOINC+...  Darren Hart
pigz  2.3.1  2.3.3 Hongxu Jia
qmmp  0.7.7  0.8.3 Hongxu Jia
man   1.6g   2.5a6 Hongxu Jia
perl  5.20.0 5.21.8Hongxu Jia
libxml-parser-perl2.41   2.44  Hongxu Jia
groff 1.22.2 1.22.3Hongxu Jia   
1.18.1.4 is latest GPLv2 Ve...
bash  4.34.3.30Hongxu Jia
patch 2.7.1  2.7.3 Hongxu Jia
createrepo0.4.11 0.10.3Hongxu Jia   
Versions after 0.9.* use YU...
socat 1.7.2.41.7.3.0   Hongxu Jia
man-pages 3.76   3.78  Hongxu Jia
adt-installer 0.2.0  1.1   Jessica Zhang
bind  9.9.5  11Kai Kang
libsdl1.2.15 1.2.15-1  Kai Kang
python-numpy  1.7.0  1.9.1 Khem Raj
rpm   5.4.14 5.4.15-0.20140824 Mark Hatle
libinput  0.7.0  0.8.0 No Maintainer
libgfortran   4.9.1  4.9.2 No Maintainer
gcc-source4.9.1  4.9.2 No Maintainer
u-bootv2014.07+gitX  v2015.01+gitAUTOI...  No Maintainer
linux-yocto-dev   3.17++gitX 3.17.6++5ff54d8fb...  No Mainta

Re: [yocto] adding all the pieces of WiFi to core-image-minimal

[James Abernathy]

> On Jan 26, 2015, at 10:52 AM, Gary Thomas  wrote:
> 
> On 2015-01-26 08:26, James Abernathy wrote:
>> 
>>> On Jan 26, 2015, at 8:49 AM, Gary Thomas >> > wrote:
>>> 
>>> On 2015-01-26 06:29, James Abernathy wrote:
 
> On Jan 23, 2015, at 12:37 PM, Gary Thomas  > wrote:
> 
> On 2015-01-23 10:24, Jim Abernathy wrote:
>> I'm starting a project mostly for self-education.  I have already done 
>> the project using Ubuntu Server 14.04 using a Intel NUC and a Pandaboard 
>> as targets.  Now I want to see how
>> easy it is to move it to Yocto.
>> 
>> Starting with the NUC, I can boot Dizzy 1.7.1 core-image-minimal and 
>> core-image-sato, both built with bitbake and not the prebuilt images. 
>> However, core-image-minimal doesn't have
>> WiFi and core-image-sato does, but I don't need all the GUI stuff.  It's 
>> a headless application.
>> 
>> So what is recommended; eliminating the GUI from sato or adding wifi and 
>> wpa-supplicant, etc to minimal??  Also any pointers to how to do the 
>> adding/subtracting would be most
>> helpful.
>> 
>> Once this is working all I have to do is put apache-tomcat, and 
>> openjdk-7-jre, then my application.
> 
> We use just iw & wpa-supplicant and set up the configuration
> files manually (e.g. the wpa-supplicant configurations).
 
 Could you help with a little more details.  What I envision is adding an 
 append statement of some kind to local.conf to load in the wireless 
 related files to core-image-minimal,
 same with openjdk-7-jre and tomcat7, but my first efforts have generated 
 some unintelligible error for me.  So that’s why I’m looking for direction 
 on where to start with this.
>>> 
>>> What was the error you got?  I'll bet it was for 'iw' which
>>> is a package from meta-oe, so you'll need to add that layer
>>> 
>>> Once you've added the meta-oe layer, you should be able to
>>> put this line in your local.conf:
>>> CORE_IMAGE_EXTRA_INSTALL += " iw wpa-supplicant”
>>> 
>> Okay, what I don’t get is the fact that without any additional layers, 
>> bitbake core-image-sato builds all the WiFi features I need.  bitbake 
>> core-image-minimal does not.  So I’m
>> thinking that there is some CORE_IMAGE_EXTRA_INSTALL statement that can just 
>> add what is needed without extra layers.
>> 
>> I guess it just doesn’t make sense to me right now.
> 
> Try using
>  CORE_IMAGE_EXTRA_INSTALL += " packagegroup-base-wifi"
> which will bring in 'wireless-tools' and 'wpa-supplicant'.
> 
> I prefer 'iw' to 'wireless-tools' as it is newer and [IMO]
> simpler to use.
> 
Thanks, I found that I can clean build with just the wpa-supplicant added and 
I’m hoping that will bring in the wifi drivers.  If it does, all I want to do 
is edit the /etc/interfaces file with the Static IP of the wlan0, the static IP 
of the eth0 and the wpa-xxx for the WKPA2_PSK information.  

Do I really need the tools?  I don’t need CLI commands to change any network 
parameters later.

Jim A

> -- 
> 
> Gary Thomas |  Consulting for the
> MLB Associates  |Embedded world
> 
> -- 
> ___
> 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] Difference between target, cross, native and nativesdk.

[Dominic Sacré]

On 2015-01-23 13:54, Otavio Salvador wrote:
> On Thu, Jan 22, 2015 at 8:31 PM, Dominic Sacré  wrote:
>> When I build the recipe I get what appear to be the correct binaries for
>> the host architecture, located in the target-specific work directory
>> (e.g. tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-fw-utils-cross).
>> However, these binaries don't get installed anywhere other recipes (like
>> my sdcard image) would be able to find them.
> 
> I sent a patch and seems to do the right thing. Can you test it?

I tried your patch, but it doesn't seem to solve the issue I described
above.
The recipe builds ok (in master it didn't before), but I still don't see
the binaries installed in a sysroot or any other directory in $PATH.

Which directory should these binaries be installed in anyway?


Dominic
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [Recipe reporting system] Upgradable recipe name list

[anibal . limon]

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/upgradepkgname

Package   VersionUpstream version  Maintainer   
NoUpgradeReason
  -    ---  
--
gnome-icon-theme  2.31.0 3.7.4 Alejandro Hernandez  
waiting for the sato gtk3 port
midori0.5.8  0.5.9 Alejandro Hernandez
dpkg  1.17.211.17.23   Aníbal Limón
screen4.0.3  4.2.1 Aníbal Limón
apt   0.9.9.41.0.9.6   Aníbal Limón
jpeg  8d 9 Aníbal Limón 
webkit-gtk 1.8.3 doesn't wo...
nettle2.7.1  3.0   Armin Kuster 
3.0.0 breaks gnutls, api ch...
linux-libc-headers3.17.7 3.18.3Bruce Ashfield
sysstat   11.0.2 11.1.2Chen Qi
busybox   1.22.1 1.23.0Chen Qi
systemd   216+gitX   218+gitAUTOINC+cc...  Chen Qi
console-tools 0.3.2  1999.03.02Chen Qi
bison 2.7.1  3.0.4 Chong Lu
dbus-test 1.8.10 1.9.6 Chong Lu
dbus  1.8.10 1.9.6 Chong Lu 
D-BUS 1.9.x is the developm...
quota 4.01   4.02  Cristian Iorga
libical   1.0.0  1.0.1 Cristian Iorga
pulseaudio5.05.99.3Cristian Iorga
libatomics-ops7.27.4.0 Cristian Iorga
neon  0.30.0 0.30.1Cristian Iorga
speex 1.2rc1 1.2rc2Cristian Iorga
gst-fluendo-mpegd...  0.10.720.10.85   Cristian Iorga
gst-fluendo-mp3   0.10.310.10.32   Cristian Iorga
db6.0.30 6.1.19Cristian Iorga   
API compatibility issue
flac  1.3.0  1.3.1 Cristian Iorga
connman   1.26   1.27  Cristian Iorga
gst-plugin-bluetooth  4.101  5.27  Cristian Iorga
bluez44.101  5.27  Cristian Iorga   
BlueZ 5.x is not backward-c...
iproute2  3.17.0 3.18.0Cristian Iorga
ofono 1.15   1.16  Cristian Iorga
neard 0.14   0.15  Cristian Iorga
harfbuzz  0.9.37 0.9.38Cristian Iorga
linux-yocto-dev   3.17++gitX 3.17.6++5ff54d8fb...  Darren Hart
linux-yocto-tiny  3.17.6+gitX2012+gitAUTOINC+5...  Darren Hart
linux-yocto   3.14.24+gitX   3.14.26+gitAUTOIN...  Darren Hart
kernelshark   1.2+gitX   2.5.1+gitAUTOINC+...  Darren Hart  
0.2 is the latest version.
trace-cmd 2.3.2+gitX 2.5.1+gitAUTOINC+...  Darren Hart
u-bootv2014.07+gitX  v2015.01+gitAUTOI...  Denys Dmytriyenko
u-boot-mkimagev2014.07+gitX  v2015.01+gitAUTOI...  Denys Dmytriyenko
u-boot-fw-utils   v2014.07+gitX  v2015.01+gitAUTOI...  Denys Dmytriyenko
pigz  2.3.1  2.3.3 Hongxu Jia
qmmp  0.7.7  0.8.3 Hongxu Jia
man   1.6g   2.5a6 Hongxu Jia
perl  5.20.0 5.21.8Hongxu Jia
libxml-parser-perl2.41   2.44  Hongxu Jia
groff 1.22.2 1.22.3Hongxu Jia   
1.18.1.4 is latest GPLv2 Ve...
bash  4.34.3.30Hongxu Jia   
The latest version in yocto...
patch 2.7.1  2.7.3 Hongxu Jia
createrepo0.4.11 0.10.3Hongxu Jia   
Versions after 0.9.* use YU...
socat 1.7.2.41.7.3.0   Hongxu Jia
man-pages 3.76   3.78  Hongxu Jia
adt-installer 0.2.0  1.1   Jessica Zhang
bind  9.9.5  11Kai Kang
libsdl1.2.15 1.2.15-1  Kai Kang
python-numpy   

Re: [yocto] Difference between target, cross, native and nativesdk.

[Denys Dmytriyenko]

On Fri, Jan 23, 2015 at 10:54:39AM -0200, Otavio Salvador wrote:
> On Thu, Jan 22, 2015 at 8:31 PM, Dominic Sacré  wrote:
> > On 2015-01-21 14:37, Otavio Salvador wrote:
> >> The fw tools inside of U-Boot qualifies for both target and cross use
> >> cases. When used in cross or crosssdk, it can be used to change things
> >> in the generated image (sdcard for example) while in the target case
> >> it can be used in the runtime system.
> >
> > I've been wondering about the "u-boot-fw-utils-cross" recipe myself.
> > When I build the recipe I get what appear to be the correct binaries for
> > the host architecture, located in the target-specific work directory
> > (e.g. tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-fw-utils-cross).
> > However, these binaries don't get installed anywhere other recipes (like
> > my sdcard image) would be able to find them.
> >
> > My workaround so far has been to build a native package instead (by
> > simply adding BBCLASSEXTEND = "native" to the regular "u-boot-fw-utils"
> > recipe).
> > This way the binaries get installed to the host's sysroot and are found
> > just fine, but I feel like I'm missing something about how the cross
> > recipe should be used properly for this purpose.
> >
> > Can anyone shed some light on this?
> 
> I sent a patch and seems to do the right thing. Can you test it?

Well, again, you didn't really answer the question...

The question wasn't about the breakage, but rather about the process. How do 
you mean to use the u-boot-fw-utils-cross "package"?

In other words, SYSROOT_PREPROCESS_FUNCS doesn't seem to work, as no binaries 
are being deployed or staged in sysroots. Moreover, if you use rm_work class, 
the only binary in the tmp/work directory gets deleted right away and you 
can't use the output of this recipe in any way.

-- 
Denys
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] adding all the pieces of WiFi to core-image-minimal

[James Abernathy]

I get a clean build when I add: CORE_IMAGE_EXTRA_INSTALL += " 
packagegroup-base-wifi”

However, I have no wireless drivers.  I must have to add something to add the 
drivers and firmware to the kernel.  Not sure what though.

Jim A

> On Jan 26, 2015, at 11:09 AM, James Abernathy  wrote:
> 
>> 
>> On Jan 26, 2015, at 10:52 AM, Gary Thomas  wrote:
>> 
>> On 2015-01-26 08:26, James Abernathy wrote:
>>> 
 On Jan 26, 2015, at 8:49 AM, Gary Thomas >>> > wrote:
 
 On 2015-01-26 06:29, James Abernathy wrote:
> 
>> On Jan 23, 2015, at 12:37 PM, Gary Thomas > > wrote:
>> 
>> On 2015-01-23 10:24, Jim Abernathy wrote:
>>> I'm starting a project mostly for self-education.  I have already done 
>>> the project using Ubuntu Server 14.04 using a Intel NUC and a 
>>> Pandaboard as targets.  Now I want to see how
>>> easy it is to move it to Yocto.
>>> 
>>> Starting with the NUC, I can boot Dizzy 1.7.1 core-image-minimal and 
>>> core-image-sato, both built with bitbake and not the prebuilt images. 
>>> However, core-image-minimal doesn't have
>>> WiFi and core-image-sato does, but I don't need all the GUI stuff.  
>>> It's a headless application.
>>> 
>>> So what is recommended; eliminating the GUI from sato or adding wifi 
>>> and wpa-supplicant, etc to minimal??  Also any pointers to how to do 
>>> the adding/subtracting would be most
>>> helpful.
>>> 
>>> Once this is working all I have to do is put apache-tomcat, and 
>>> openjdk-7-jre, then my application.
>> 
>> We use just iw & wpa-supplicant and set up the configuration
>> files manually (e.g. the wpa-supplicant configurations).
> 
> Could you help with a little more details.  What I envision is adding an 
> append statement of some kind to local.conf to load in the wireless 
> related files to core-image-minimal,
> same with openjdk-7-jre and tomcat7, but my first efforts have generated 
> some unintelligible error for me.  So that’s why I’m looking for 
> direction on where to start with this.
 
 What was the error you got?  I'll bet it was for 'iw' which
 is a package from meta-oe, so you'll need to add that layer
 
 Once you've added the meta-oe layer, you should be able to
 put this line in your local.conf:
 CORE_IMAGE_EXTRA_INSTALL += " iw wpa-supplicant”
 
>>> Okay, what I don’t get is the fact that without any additional layers, 
>>> bitbake core-image-sato builds all the WiFi features I need.  bitbake 
>>> core-image-minimal does not.  So I’m
>>> thinking that there is some CORE_IMAGE_EXTRA_INSTALL statement that can 
>>> just add what is needed without extra layers.
>>> 
>>> I guess it just doesn’t make sense to me right now.
>> 
>> Try using
>> CORE_IMAGE_EXTRA_INSTALL += " packagegroup-base-wifi"
>> which will bring in 'wireless-tools' and 'wpa-supplicant'.
>> 
>> I prefer 'iw' to 'wireless-tools' as it is newer and [IMO]
>> simpler to use.
>> 
> Thanks, I found that I can clean build with just the wpa-supplicant added and 
> I’m hoping that will bring in the wifi drivers.  If it does, all I want to do 
> is edit the /etc/interfaces file with the Static IP of the wlan0, the static 
> IP of the eth0 and the wpa-xxx for the WKPA2_PSK information.  
> 
> Do I really need the tools?  I don’t need CLI commands to change any network 
> parameters later.
> 
> Jim A
> 
>> -- 
>> 
>> Gary Thomas |  Consulting for the
>> MLB Associates  |Embedded world
>> 
>> -- 
>> ___
>> 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 mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] adding all the pieces of WiFi to core-image-minimal

[Chris Tapp]

On 26 Jan 2015, at 19:31, James Abernathy  wrote:

> I get a clean build when I add: CORE_IMAGE_EXTRA_INSTALL += " 
> packagegroup-base-wifi”
> 
> However, I have no wireless drivers.  I must have to add something to add the 
> drivers and firmware to the kernel.  Not sure what though.

I'm not an expert here, but I think that adding kernel-modules and 
linux-firmware to your extra_install should give you what you need.

> 
> Jim A
> 
>> On Jan 26, 2015, at 11:09 AM, James Abernathy  
>> wrote:
>> 
>>> 
>>> On Jan 26, 2015, at 10:52 AM, Gary Thomas  wrote:
>>> 
>>> On 2015-01-26 08:26, James Abernathy wrote:
 
> On Jan 26, 2015, at 8:49 AM, Gary Thomas  > wrote:
> 
> On 2015-01-26 06:29, James Abernathy wrote:
>> 
>>> On Jan 23, 2015, at 12:37 PM, Gary Thomas >> > wrote:
>>> 
>>> On 2015-01-23 10:24, Jim Abernathy wrote:
 I'm starting a project mostly for self-education.  I have already done 
 the project using Ubuntu Server 14.04 using a Intel NUC and a 
 Pandaboard as targets.  Now I want to see how
 easy it is to move it to Yocto.
 
 Starting with the NUC, I can boot Dizzy 1.7.1 core-image-minimal and 
 core-image-sato, both built with bitbake and not the prebuilt images. 
 However, core-image-minimal doesn't have
 WiFi and core-image-sato does, but I don't need all the GUI stuff.  
 It's a headless application.
 
 So what is recommended; eliminating the GUI from sato or adding wifi 
 and wpa-supplicant, etc to minimal??  Also any pointers to how to do 
 the adding/subtracting would be most
 helpful.
 
 Once this is working all I have to do is put apache-tomcat, and 
 openjdk-7-jre, then my application.
>>> 
>>> We use just iw & wpa-supplicant and set up the configuration
>>> files manually (e.g. the wpa-supplicant configurations).
>> 
>> Could you help with a little more details.  What I envision is adding an 
>> append statement of some kind to local.conf to load in the wireless 
>> related files to core-image-minimal,
>> same with openjdk-7-jre and tomcat7, but my first efforts have generated 
>> some unintelligible error for me.  So that’s why I’m looking for 
>> direction on where to start with this.
> 
> What was the error you got?  I'll bet it was for 'iw' which
> is a package from meta-oe, so you'll need to add that layer
> 
> Once you've added the meta-oe layer, you should be able to
> put this line in your local.conf:
> CORE_IMAGE_EXTRA_INSTALL += " iw wpa-supplicant”
> 
 Okay, what I don’t get is the fact that without any additional layers, 
 bitbake core-image-sato builds all the WiFi features I need.  bitbake 
 core-image-minimal does not.  So I’m
 thinking that there is some CORE_IMAGE_EXTRA_INSTALL statement that can 
 just add what is needed without extra layers.
 
 I guess it just doesn’t make sense to me right now.
>>> 
>>> Try using
>>> CORE_IMAGE_EXTRA_INSTALL += " packagegroup-base-wifi"
>>> which will bring in 'wireless-tools' and 'wpa-supplicant'.
>>> 
>>> I prefer 'iw' to 'wireless-tools' as it is newer and [IMO]
>>> simpler to use.
>>> 
>> Thanks, I found that I can clean build with just the wpa-supplicant added 
>> and I’m hoping that will bring in the wifi drivers.  If it does, all I want 
>> to do is edit the /etc/interfaces file with the Static IP of the wlan0, the 
>> static IP of the eth0 and the wpa-xxx for the WKPA2_PSK information.  
>> 
>> Do I really need the tools?  I don’t need CLI commands to change any network 
>> parameters later.
>> 
>> Jim A
>> 
>>> -- 
>>> 
>>> Gary Thomas |  Consulting for the
>>> MLB Associates  |Embedded world
>>> 
>>> -- 
>>> ___
>>> 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 mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

--

Chris Tapp
opensou...@keylevel.com
www.keylevel.com


You can tell you're getting older when your car insurance gets real cheap!

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] adding all the pieces of WiFi to core-image-minimal

[Moore, Thomas (FtWorth)]

Try building core-image-base or adding packagegroup-base-extended to your 
IMAGE_INSTALL. This should add the modules and firmware.

core-image-minimal is just that and only includes just enough to boot the 
system.

P.S. if you add "wifi" to your DISTRO_FEATURES, then packagegroup-base-wifi 
should automatically get added to the image. Checkout 
meta/recipes-core/packagegroups/packagegroup-base.bb to see how that works.

Thomas

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Chris Tapp
Sent: Monday, January 26, 2015 2:28 PM
To: James Abernathy
Cc: yocto@yoctoproject.org; Gary Thomas
Subject: Re: [yocto] adding all the pieces of WiFi to core-image-minimal


On 26 Jan 2015, at 19:31, James Abernathy  wrote:


I get a clean build when I add: CORE_IMAGE_EXTRA_INSTALL += " 
packagegroup-base-wifi"

However, I have no wireless drivers.  I must have to add something to add the 
drivers and firmware to the kernel.  Not sure what though.

I'm not an expert here, but I think that adding kernel-modules and 
linux-firmware to your extra_install should give you what you need.


Jim A

On Jan 26, 2015, at 11:09 AM, James Abernathy  wrote:


On Jan 26, 2015, at 10:52 AM, Gary Thomas  wrote:

On 2015-01-26 08:26, James Abernathy wrote:



On Jan 26, 2015, at 8:49 AM, Gary Thomas mailto:g...@mlbassoc.com>> wrote:

On 2015-01-26 06:29, James Abernathy wrote:



On Jan 23, 2015, at 12:37 PM, Gary Thomas mailto:g...@mlbassoc.com>> wrote:

On 2015-01-23 10:24, Jim Abernathy wrote:

I'm starting a project mostly for self-education.  I have already done the 
project using Ubuntu Server 14.04 using a Intel NUC and a Pandaboard as 
targets.  Now I want to see how
easy it is to move it to Yocto.

Starting with the NUC, I can boot Dizzy 1.7.1 core-image-minimal and 
core-image-sato, both built with bitbake and not the prebuilt images. However, 
core-image-minimal doesn't have
WiFi and core-image-sato does, but I don't need all the GUI stuff.  It's a 
headless application.

So what is recommended; eliminating the GUI from sato or adding wifi and 
wpa-supplicant, etc to minimal??  Also any pointers to how to do the 
adding/subtracting would be most
helpful.

Once this is working all I have to do is put apache-tomcat, and openjdk-7-jre, 
then my application.

We use just iw & wpa-supplicant and set up the configuration
files manually (e.g. the wpa-supplicant configurations).

Could you help with a little more details.  What I envision is adding an append 
statement of some kind to local.conf to load in the wireless related files to 
core-image-minimal,
same with openjdk-7-jre and tomcat7, but my first efforts have generated some 
unintelligible error for me.  So that's why I'm looking for direction on where 
to start with this.

What was the error you got?  I'll bet it was for 'iw' which
is a package from meta-oe, so you'll need to add that layer

Once you've added the meta-oe layer, you should be able to
put this line in your local.conf:
CORE_IMAGE_EXTRA_INSTALL += " iw wpa-supplicant"
Okay, what I don't get is the fact that without any additional layers, bitbake 
core-image-sato builds all the WiFi features I need.  bitbake 
core-image-minimal does not.  So I'm
thinking that there is some CORE_IMAGE_EXTRA_INSTALL statement that can just 
add what is needed without extra layers.

I guess it just doesn't make sense to me right now.

Try using
CORE_IMAGE_EXTRA_INSTALL += " packagegroup-base-wifi"
which will bring in 'wireless-tools' and 'wpa-supplicant'.

I prefer 'iw' to 'wireless-tools' as it is newer and [IMO]
simpler to use.
Thanks, I found that I can clean build with just the wpa-supplicant added and 
I'm hoping that will bring in the wifi drivers.  If it does, all I want to do 
is edit the /etc/interfaces file with the Static IP of the wlan0, the static IP 
of the eth0 and the wpa-xxx for the WKPA2_PSK information.  

Do I really need the tools?  I don't need CLI commands to change any network 
parameters later.

Jim A


-- 

Gary Thomas |  Consulting for the
MLB Associates  |    Embedded world

-- 
___
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 mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

--

Chris Tapp
opensou...@keylevel.com
www.keylevel.com


You can tell you're getting older when your car insurance gets real cheap!

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] adding all the pieces of WiFi to core-image-minimal

[James Abernathy]

> On Jan 26, 2015, at 3:36 PM, Moore, Thomas (FtWorth)  
> wrote:
> 
> Try building core-image-base or adding packagegroup-base-extended to your 
> IMAGE_INSTALL. This should add the modules and firmware.
> 
> core-image-minimal is just that and only includes just enough to boot the 
> system.
> 
> P.S. if you add "wifi" to your DISTRO_FEATURES, then packagegroup-base-wifi 
> should automatically get added to the image. Checkout 
> meta/recipes-core/packagegroups/packagegroup-base.bb to see how that works.
> 
> Thomas
> 

Interesting!  are we talking about doing this in the local.conf? or are we 
talking about modifying existing recipes?  I’d like to do this cleanly and not 
mess up what’s in the default files.  Maybe create my own layer??

Jim A

> From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] 
> On Behalf Of Chris Tapp
> Sent: Monday, January 26, 2015 2:28 PM
> To: James Abernathy
> Cc: yocto@yoctoproject.org; Gary Thomas
> Subject: Re: [yocto] adding all the pieces of WiFi to core-image-minimal
> 
> 
> On 26 Jan 2015, at 19:31, James Abernathy  wrote:
> 
> 
> I get a clean build when I add: CORE_IMAGE_EXTRA_INSTALL += " 
> packagegroup-base-wifi"
> 
> However, I have no wireless drivers.  I must have to add something to add the 
> drivers and firmware to the kernel.  Not sure what though.
> 
> I'm not an expert here, but I think that adding kernel-modules and 
> linux-firmware to your extra_install should give you what you need.
> 
> 
> Jim A
> 
> On Jan 26, 2015, at 11:09 AM, James Abernathy  wrote:
> 
> 
> On Jan 26, 2015, at 10:52 AM, Gary Thomas  wrote:
> 
> On 2015-01-26 08:26, James Abernathy wrote:
> 
> 
> 
> On Jan 26, 2015, at 8:49 AM, Gary Thomas  > wrote:
> 
> On 2015-01-26 06:29, James Abernathy wrote:
> 
> 
> 
> On Jan 23, 2015, at 12:37 PM, Gary Thomas  > wrote:
> 
> On 2015-01-23 10:24, Jim Abernathy wrote:
> 
> I'm starting a project mostly for self-education.  I have already done the 
> project using Ubuntu Server 14.04 using a Intel NUC and a Pandaboard as 
> targets.  Now I want to see how
> easy it is to move it to Yocto.
> 
> Starting with the NUC, I can boot Dizzy 1.7.1 core-image-minimal and 
> core-image-sato, both built with bitbake and not the prebuilt images. 
> However, core-image-minimal doesn't have
> WiFi and core-image-sato does, but I don't need all the GUI stuff.  It's a 
> headless application.
> 
> So what is recommended; eliminating the GUI from sato or adding wifi and 
> wpa-supplicant, etc to minimal??  Also any pointers to how to do the 
> adding/subtracting would be most
> helpful.
> 
> Once this is working all I have to do is put apache-tomcat, and 
> openjdk-7-jre, then my application.
> 
> We use just iw & wpa-supplicant and set up the configuration
> files manually (e.g. the wpa-supplicant configurations).
> 
> Could you help with a little more details.  What I envision is adding an 
> append statement of some kind to local.conf to load in the wireless related 
> files to core-image-minimal,
> same with openjdk-7-jre and tomcat7, but my first efforts have generated some 
> unintelligible error for me.  So that's why I'm looking for direction on 
> where to start with this.
> 
> What was the error you got?  I'll bet it was for 'iw' which
> is a package from meta-oe, so you'll need to add that layer
> 
> Once you've added the meta-oe layer, you should be able to
> put this line in your local.conf:
> CORE_IMAGE_EXTRA_INSTALL += " iw wpa-supplicant"
> Okay, what I don't get is the fact that without any additional layers, 
> bitbake core-image-sato builds all the WiFi features I need.  bitbake 
> core-image-minimal does not.  So I'm
> thinking that there is some CORE_IMAGE_EXTRA_INSTALL statement that can just 
> add what is needed without extra layers.
> 
> I guess it just doesn't make sense to me right now.
> 
> Try using
> CORE_IMAGE_EXTRA_INSTALL += " packagegroup-base-wifi"
> which will bring in 'wireless-tools' and 'wpa-supplicant'.
> 
> I prefer 'iw' to 'wireless-tools' as it is newer and [IMO]
> simpler to use.
> Thanks, I found that I can clean build with just the wpa-supplicant added and 
> I'm hoping that will bring in the wifi drivers.  If it does, all I want to do 
> is edit the /etc/interfaces file with the Static IP of the wlan0, the static 
> IP of the eth0 and the wpa-xxx for the WKPA2_PSK information.  
> 
> Do I really need the tools?  I don't need CLI commands to change any network 
> parameters later.
> 
> Jim A
> 
> 
> -- 
> 
> Gary Thomas |  Consulting for the
> MLB Associates  |Embedded world
> 
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
> 
> -- 
> ___
> yocto 

Re: [yocto] adding all the pieces of WiFi to core-image-minimal

[James Abernathy]

> On Jan 26, 2015, at 3:28 PM, Chris Tapp  wrote:
> 
> 
> On 26 Jan 2015, at 19:31, James Abernathy  > wrote:
> 
>> I get a clean build when I add: CORE_IMAGE_EXTRA_INSTALL += " 
>> packagegroup-base-wifi”
>> 
>> However, I have no wireless drivers.  I must have to add something to add 
>> the drivers and firmware to the kernel.  Not sure what though.
> 
> I'm not an expert here, but I think that adding kernel-modules and 
> linux-firmware to your extra_install should give you what you need.
> 

Well you are right!  All I added was:
CORE_IMAGE_EXTRA_INSTALL += “ packagegroup-base-wifi kernel-modules 
linux-firmware”

After booting this image via USB on a NUC, I had all the drivers for LAN and 
WiFi devices and the 80211 firmware so I should be able to make it work now.  

Thanks all,

Jim A

>> 
>> Jim A
>> 
>>> On Jan 26, 2015, at 11:09 AM, James Abernathy >> > wrote:
>>> 
 
 On Jan 26, 2015, at 10:52 AM, Gary Thomas >>> > wrote:
 
 On 2015-01-26 08:26, James Abernathy wrote:
> 
>> On Jan 26, 2015, at 8:49 AM, Gary Thomas >  > >> wrote:
>> 
>> On 2015-01-26 06:29, James Abernathy wrote:
>>> 
 On Jan 23, 2015, at 12:37 PM, Gary Thomas >>>  >> wrote:
 
 On 2015-01-23 10:24, Jim Abernathy wrote:
> I'm starting a project mostly for self-education.  I have already 
> done the project using Ubuntu Server 14.04 using a Intel NUC and a 
> Pandaboard as targets.  Now I want to see how
> easy it is to move it to Yocto.
> 
> Starting with the NUC, I can boot Dizzy 1.7.1 core-image-minimal and 
> core-image-sato, both built with bitbake and not the prebuilt images. 
> However, core-image-minimal doesn't have
> WiFi and core-image-sato does, but I don't need all the GUI stuff.  
> It's a headless application.
> 
> So what is recommended; eliminating the GUI from sato or adding wifi 
> and wpa-supplicant, etc to minimal??  Also any pointers to how to do 
> the adding/subtracting would be most
> helpful.
> 
> Once this is working all I have to do is put apache-tomcat, and 
> openjdk-7-jre, then my application.
 
 We use just iw & wpa-supplicant and set up the configuration
 files manually (e.g. the wpa-supplicant configurations).
>>> 
>>> Could you help with a little more details.  What I envision is adding 
>>> an append statement of some kind to local.conf to load in the wireless 
>>> related files to core-image-minimal,
>>> same with openjdk-7-jre and tomcat7, but my first efforts have 
>>> generated some unintelligible error for me.  So that’s why I’m looking 
>>> for direction on where to start with this.
>> 
>> What was the error you got?  I'll bet it was for 'iw' which
>> is a package from meta-oe, so you'll need to add that layer
>> 
>> Once you've added the meta-oe layer, you should be able to
>> put this line in your local.conf:
>> CORE_IMAGE_EXTRA_INSTALL += " iw wpa-supplicant”
>> 
> Okay, what I don’t get is the fact that without any additional layers, 
> bitbake core-image-sato builds all the WiFi features I need.  bitbake 
> core-image-minimal does not.  So I’m
> thinking that there is some CORE_IMAGE_EXTRA_INSTALL statement that can 
> just add what is needed without extra layers.
> 
> I guess it just doesn’t make sense to me right now.
 
 Try using
 CORE_IMAGE_EXTRA_INSTALL += " packagegroup-base-wifi"
 which will bring in 'wireless-tools' and 'wpa-supplicant'.
 
 I prefer 'iw' to 'wireless-tools' as it is newer and [IMO]
 simpler to use.
 
>>> Thanks, I found that I can clean build with just the wpa-supplicant added 
>>> and I’m hoping that will bring in the wifi drivers.  If it does, all I want 
>>> to do is edit the /etc/interfaces file with the Static IP of the wlan0, the 
>>> static IP of the eth0 and the wpa-xxx for the WKPA2_PSK information.  
>>> 
>>> Do I really need the tools?  I don’t need CLI commands to change any 
>>> network parameters later.
>>> 
>>> Jim A
>>> 
 -- 
 
 Gary Thomas |  Consulting for the
 MLB Associates  |Embedded world
 
 -- 
 ___
 yocto mailing list
 yocto@yoctoproject.org 
 https://lists.yoctoproject.org/listinfo/yocto 
 
>>> 
>>> -- 
>>> 

Re: [yocto] adding all the pieces of WiFi to core-image-minimal

[Moore, Thomas (FtWorth)]

For now, I'd just get everything working with the local.conf:

DISTRO_FEATURES += "wifi"

bitbake core-image-base

Ultimately, you may want to make a custom machine and distro config and 
incorporate all of the things you've specified in local.conf in those configs. 
For example, I have a system that's an intel-based single-board computer with 
several expansion cards. I've created a machine configuration to define the 
basic hardware components (features, drivers, etc). I've also created a custom 
distro because we prefer system over systemv and to include some other 
non-machine specific packages. Finally, I've created a custom image that 
includes some other extras.

The power of local.conf is nice, but it's a little tricky transitioning from 
that to more of a BSP approach like I described above because most people just 
say to add it to your local.conf, but that's not really how it should be done 
at the end. Think global variables vs classes.

P.S. Never edit anything in the poky folder. If you want to modify an existing 
recipe, create a new layer with a bbappend and modify away.

Thomas


-Original Message-
From: James Abernathy [mailto:jfaberna...@outlook.com] 
Sent: Monday, January 26, 2015 2:53 PM
To: Moore, Thomas (FtWorth)
Cc: Chris Tapp; yocto@yoctoproject.org; Gary Thomas
Subject: Re: [yocto] adding all the pieces of WiFi to core-image-minimal


> On Jan 26, 2015, at 3:36 PM, Moore, Thomas (FtWorth)  
> wrote:
> 
> Try building core-image-base or adding packagegroup-base-extended to your 
> IMAGE_INSTALL. This should add the modules and firmware.
> 
> core-image-minimal is just that and only includes just enough to boot the 
> system.
> 
> P.S. if you add "wifi" to your DISTRO_FEATURES, then packagegroup-base-wifi 
> should automatically get added to the image. Checkout 
> meta/recipes-core/packagegroups/packagegroup-base.bb to see how that works.
> 
> Thomas
> 

Interesting!  are we talking about doing this in the local.conf? or are we 
talking about modifying existing recipes?  I'd like to do this cleanly and not 
mess up what's in the default files.  Maybe create my own layer??

Jim A

> From: yocto-boun...@yoctoproject.org 
> [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Chris Tapp
> Sent: Monday, January 26, 2015 2:28 PM
> To: James Abernathy
> Cc: yocto@yoctoproject.org; Gary Thomas
> Subject: Re: [yocto] adding all the pieces of WiFi to 
> core-image-minimal
> 
> 
> On 26 Jan 2015, at 19:31, James Abernathy  wrote:
> 
> 
> I get a clean build when I add: CORE_IMAGE_EXTRA_INSTALL += " 
> packagegroup-base-wifi"
> 
> However, I have no wireless drivers.  I must have to add something to add the 
> drivers and firmware to the kernel.  Not sure what though.
> 
> I'm not an expert here, but I think that adding kernel-modules and 
> linux-firmware to your extra_install should give you what you need.
> 
> 
> Jim A
> 
> On Jan 26, 2015, at 11:09 AM, James Abernathy  wrote:
> 
> 
> On Jan 26, 2015, at 10:52 AM, Gary Thomas  wrote:
> 
> On 2015-01-26 08:26, James Abernathy wrote:
> 
> 
> 
> On Jan 26, 2015, at 8:49 AM, Gary Thomas  > wrote:
> 
> On 2015-01-26 06:29, James Abernathy wrote:
> 
> 
> 
> On Jan 23, 2015, at 12:37 PM, Gary Thomas  > wrote:
> 
> On 2015-01-23 10:24, Jim Abernathy wrote:
> 
> I'm starting a project mostly for self-education.  I have already done 
> the project using Ubuntu Server 14.04 using a Intel NUC and a Pandaboard as 
> targets.  Now I want to see how easy it is to move it to Yocto.
> 
> Starting with the NUC, I can boot Dizzy 1.7.1 core-image-minimal and 
> core-image-sato, both built with bitbake and not the prebuilt images. 
> However, core-image-minimal doesn't have WiFi and core-image-sato does, but I 
> don't need all the GUI stuff.  It's a headless application.
> 
> So what is recommended; eliminating the GUI from sato or adding wifi 
> and wpa-supplicant, etc to minimal??  Also any pointers to how to do the 
> adding/subtracting would be most helpful.
> 
> Once this is working all I have to do is put apache-tomcat, and 
> openjdk-7-jre, then my application.
> 
> We use just iw & wpa-supplicant and set up the configuration files 
> manually (e.g. the wpa-supplicant configurations).
> 
> Could you help with a little more details.  What I envision is adding 
> an append statement of some kind to local.conf to load in the wireless 
> related files to core-image-minimal, same with openjdk-7-jre and tomcat7, but 
> my first efforts have generated some unintelligible error for me.  So that's 
> why I'm looking for direction on where to start with this.
> 
> What was the error you got?  I'll bet it was for 'iw' which is a 
> package from meta-oe, so you'll need to add that layer
> 
> Once you've added the meta-oe layer, you should be able to put this 
> line in your local.conf:
> CORE_IMAGE_EXTRA_INSTALL += " iw wpa-supplicant"
> Okay, what I don't get is the fact that without any additional layers

Re: [yocto] adding all the pieces of WiFi to core-image-minimal

[Jim Abernathy]

> From: thomas.moo...@atk.com
> To: jfaberna...@outlook.com
> CC: opensou...@keylevel.com; yocto@yoctoproject.org; g...@mlbassoc.com
> Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal
> Date: Mon, 26 Jan 2015 21:04:54 +
> 
> For now, I'd just get everything working with the local.conf:
> 
> DISTRO_FEATURES += "wifi"
> 
> bitbake core-image-base
> 
> Ultimately, you may want to make a custom machine and distro config and 
> incorporate all of the things you've specified in local.conf in those 
> configs. For example, I have a system that's an intel-based single-board 
> computer with several expansion cards. I've created a machine configuration 
> to define the basic hardware components (features, drivers, etc). I've also 
> created a custom distro because we prefer system over systemv and to include 
> some other non-machine specific packages. Finally, I've created a custom 
> image that includes some other extras.
> 
> The power of local.conf is nice, but it's a little tricky transitioning from 
> that to more of a BSP approach like I described above because most people 
> just say to add it to your local.conf, but that's not really how it should be 
> done at the end. Think global variables vs classes.
> 
> P.S. Never edit anything in the poky folder. If you want to modify an 
> existing recipe, create a new layer with a bbappend and modify away.
> 
> Thomas
> 
> 
I tried just adding DISTRO_FEATURES += "wifi" to the local.conf and bitbaking 
core-image-base, but I got a lot of errors:

NOTE: Resolving any missing task queue dependencies
ERROR: Nothing PROVIDES 'glibc'
ERROR: glibc was skipped: missing required distro feature 'ipv4' (not in 
DISTRO_FEATURES)
ERROR: Required build target 'core-image-base' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-base', 'glibc']

So I got it working with core-image-minimal as I mentioned earlier just before 
your reply.

> -Original Message-
> From: James Abernathy [mailto:jfaberna...@outlook.com] 
> Sent: Monday, January 26, 2015 2:53 PM
> To: Moore, Thomas (FtWorth)
> Cc: Chris Tapp; yocto@yoctoproject.org; Gary Thomas
> Subject: Re: [yocto] adding all the pieces of WiFi to core-image-minimal
> 
> 
> > On Jan 26, 2015, at 3:36 PM, Moore, Thomas (FtWorth) 
> >  wrote:
> > 
> > Try building core-image-base or adding packagegroup-base-extended to your 
> > IMAGE_INSTALL. This should add the modules and firmware.
> > 
> > core-image-minimal is just that and only includes just enough to boot the 
> > system.
> > 
> > P.S. if you add "wifi" to your DISTRO_FEATURES, then packagegroup-base-wifi 
> > should automatically get added to the image. Checkout 
> > meta/recipes-core/packagegroups/packagegroup-base.bb to see how that works.
> > 
> > Thomas
> > 
> 
> Interesting!  are we talking about doing this in the local.conf? or are we 
> talking about modifying existing recipes?  I'd like to do this cleanly and 
> not mess up what's in the default files.  Maybe create my own layer??
> 
> Jim A
> 
> > From: yocto-boun...@yoctoproject.org 
> > [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Chris Tapp
> > Sent: Monday, January 26, 2015 2:28 PM
> > To: James Abernathy
> > Cc: yocto@yoctoproject.org; Gary Thomas
> > Subject: Re: [yocto] adding all the pieces of WiFi to 
> > core-image-minimal
> > 
> > 
> > On 26 Jan 2015, at 19:31, James Abernathy  wrote:
> > 
> > 
> > I get a clean build when I add: CORE_IMAGE_EXTRA_INSTALL += " 
> > packagegroup-base-wifi"
> > 
> > However, I have no wireless drivers.  I must have to add something to add 
> > the drivers and firmware to the kernel.  Not sure what though.
> > 
> > I'm not an expert here, but I think that adding kernel-modules and 
> > linux-firmware to your extra_install should give you what you need.
> > 
> > 
> > Jim A
> > 
> > On Jan 26, 2015, at 11:09 AM, James Abernathy  
> > wrote:
> > 
> > 
> > On Jan 26, 2015, at 10:52 AM, Gary Thomas  wrote:
> > 
> > On 2015-01-26 08:26, James Abernathy wrote:
> > 
> > 
> > 
> > On Jan 26, 2015, at 8:49 AM, Gary Thomas  > > wrote:
> > 
> > On 2015-01-26 06:29, James Abernathy wrote:
> > 
> > 
> > 
> > On Jan 23, 2015, at 12:37 PM, Gary Thomas  > > wrote:
> > 
> > On 2015-01-23 10:24, Jim Abernathy wrote:
> > 
> > I'm starting a project mostly for self-education.  I have already done 
> > the project using Ubuntu Server 14.04 using a Intel NUC and a Pandaboard as 
> > targets.  Now I want to see how easy it is to move it to Yocto.
> > 
> > Starting with the NUC, I can boot Dizzy 1.7.1 core-image-minimal and 
> > core-image-sato, both built with bitbake and not the prebuilt images. 
> > However, core-image-minimal doesn't have WiFi and core-image-sato does, but 
> > I don't need all the GUI stuff.  It's a headless application.
> > 
> > So what is recommended; eliminating the GUI from sato or adding wifi 
> > and wpa-supplicant, etc to minimal??  Also any poin

Re: [yocto] adding all the pieces of WiFi to core-image-minimal

[Moore, Thomas (FtWorth)]

Looks like you also need to add ipv4 to the DISTRO_FEATURES:

DISTRO_FEATURES += "ipv4 wifi"

Might be worth trying.

Thomas

From: Jim Abernathy [mailto:jfaberna...@outlook.com]
Sent: Monday, January 26, 2015 3:38 PM
To: Moore, Thomas (FtWorth)
Cc: Chris Tapp; yocto@yoctoproject.org; Gary Thomas
Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal


> From: thomas.moo...@atk.com
> To: jfaberna...@outlook.com
> CC: opensou...@keylevel.com; yocto@yoctoproject.org; g...@mlbassoc.com
> Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal
> Date: Mon, 26 Jan 2015 21:04:54 +
>
> For now, I'd just get everything working with the local.conf:
>
> DISTRO_FEATURES += "wifi"
>
> bitbake core-image-base
>
> Ultimately, you may want to make a custom machine and distro config and 
> incorporate all of the things you've specified in local.conf in those 
> configs. For example, I have a system that's an intel-based single-board 
> computer with several expansion cards. I've created a machine configuration 
> to define the basic hardware components (features, drivers, etc). I've also 
> created a custom distro because we prefer system over systemv and to include 
> some other non-machine specific packages. Finally, I've created a custom 
> image that includes some other extras.
>
> The power of local.conf is nice, but it's a little tricky transitioning from 
> that to more of a BSP approach like I described above because most people 
> just say to add it to your local.conf, but that's not really how it should be 
> done at the end. Think global variables vs classes.
>
> P.S. Never edit anything in the poky folder. If you want to modify an 
> existing recipe, create a new layer with a bbappend and modify away.
>
> Thomas
>
>
I tried just adding DISTRO_FEATURES += "wifi" to the local.conf and bitbaking 
core-image-base, but I got a lot of errors:

NOTE: Resolving any missing task queue dependencies
ERROR: Nothing PROVIDES 'glibc'
ERROR: glibc was skipped: missing required distro feature 'ipv4' (not in 
DISTRO_FEATURES)
ERROR: Required build target 'core-image-base' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-base', 'glibc']

So I got it working with core-image-minimal as I mentioned earlier just before 
your reply.

> -Original Message-
> From: James Abernathy 
> [mailto:jfaberna...@outlook.com]
> Sent: Monday, January 26, 2015 2:53 PM
> To: Moore, Thomas (FtWorth)
> Cc: Chris Tapp; yocto@yoctoproject.org; Gary 
> Thomas
> Subject: Re: [yocto] adding all the pieces of WiFi to core-image-minimal
>
>
> > On Jan 26, 2015, at 3:36 PM, Moore, Thomas (FtWorth) 
> > mailto:thomas.moo...@atk.com>> wrote:
> >
> > Try building core-image-base or adding packagegroup-base-extended to your 
> > IMAGE_INSTALL. This should add the modules and firmware.
> >
> > core-image-minimal is just that and only includes just enough to boot the 
> > system.
> >
> > P.S. if you add "wifi" to your DISTRO_FEATURES, then packagegroup-base-wifi 
> > should automatically get added to the image. Checkout 
> > meta/recipes-core/packagegroups/packagegroup-base.bb to see how that works.
> >
> > Thomas
> >
>
> Interesting! are we talking about doing this in the local.conf? or are we 
> talking about modifying existing recipes? I'd like to do this cleanly and not 
> mess up what's in the default files. Maybe create my own layer??
>
> Jim A
>
> > From: yocto-boun...@yoctoproject.org
> > [mailto:yocto-boun...@yoctoproject.org]
> >  On Behalf Of Chris Tapp
> > Sent: Monday, January 26, 2015 2:28 PM
> > To: James Abernathy
> > Cc: yocto@yoctoproject.org; Gary Thomas
> > Subject: Re: [yocto] adding all the pieces of WiFi to
> > core-image-minimal
> >
> >
> > On 26 Jan 2015, at 19:31, James Abernathy 
> > mailto:jfaberna...@outlook.com>> wrote:
> >
> >
> > I get a clean build when I add: CORE_IMAGE_EXTRA_INSTALL += " 
> > packagegroup-base-wifi"
> >
> > However, I have no wireless drivers. I must have to add something to add 
> > the drivers and firmware to the kernel. Not sure what though.
> >
> > I'm not an expert here, but I think that adding kernel-modules and 
> > linux-firmware to your extra_install should give you what you need.
> >
> >
> > Jim A
> >
> > On Jan 26, 2015, at 11:09 AM, James Abernathy 
> > mailto:jfaberna...@outlook.com>> wrote:
> >
> >
> > On Jan 26, 2015, at 10:52 AM, Gary Thomas 
> > mailto:g...@mlbassoc.com>> wrote:
> >
> > On 2015-01-26 08:26, James Abernathy wrote:
> >
> >
> >
> > On Jan 26, 2015, at 8:49 AM, Gary Thomas  > >>
> >  wrote:
> >
> > On 2015-01-26 06:29, James Abernathy wrote:
> >
> >
> >
> > On Jan 23, 2015, at 12:37 PM, Gary Thomas  > 

Re: [yocto] adding all the pieces of WiFi to core-image-minimal

[Jim Abernathy]

From: thomas.moo...@atk.com
To: jfaberna...@outlook.com
CC: opensou...@keylevel.com; yocto@yoctoproject.org; g...@mlbassoc.com
Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal
Date: Mon, 26 Jan 2015 21:51:47 +









Looks like you also need to add ipv4 to the DISTRO_FEATURES:
 
DISTRO_FEATURES += "ipv4 wifi"
 
Might be worth trying.
 

Thomas

 I'll test with it, but why core-image-base vs. core-image-minimal?
Jim A




From: Jim Abernathy [mailto:jfaberna...@outlook.com]


Sent: Monday, January 26, 2015 3:38 PM

To: Moore, Thomas (FtWorth)

Cc: Chris Tapp; yocto@yoctoproject.org; Gary Thomas

Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal


 

 

> From: thomas.moo...@atk.com

> To: jfaberna...@outlook.com

> CC: opensou...@keylevel.com; yocto@yoctoproject.org; g...@mlbassoc.com

> Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal

> Date: Mon, 26 Jan 2015 21:04:54 +

> 

> For now, I'd just get everything working with the local.conf:

> 

> DISTRO_FEATURES += "wifi"

> 

> bitbake core-image-base

> 

> Ultimately, you may want to make a custom machine and distro config and 
> incorporate all of the things you've specified in local.conf in those 
> configs. For example, I have a system that's an intel-based single-board 
> computer with several expansion cards. I've
 created a machine configuration to define the basic hardware components 
(features, drivers, etc). I've also created a custom distro because we prefer 
system over systemv and to include some other non-machine specific packages. 
Finally, I've created a custom
 image that includes some other extras.

> 

> The power of local.conf is nice, but it's a little tricky transitioning from 
> that to more of a BSP approach like I described above because most people 
> just say to add it to your local.conf, but that's not really how it should be 
> done at the end. Think global
 variables vs classes.

> 

> P.S. Never edit anything in the poky folder. If you want to modify an 
> existing recipe, create a new layer with a bbappend and modify away.

> 

> Thomas

> 

> 

I tried just adding DISTRO_FEATURES += "wifi" to the local.conf and bitbaking 
core-image-base, but I got a lot of errors:



NOTE: Resolving any missing task queue dependencies

ERROR: Nothing PROVIDES 'glibc'

ERROR: glibc was skipped: missing required distro feature 'ipv4' (not in 
DISTRO_FEATURES)

ERROR: Required build target 'core-image-base' has no buildable providers.

Missing or unbuildable dependency chain was: ['core-image-base', 'glibc']



So I got it working with core-image-minimal as I mentioned earlier just before 
your reply.



> -Original Message-

> From: James Abernathy [mailto:jfaberna...@outlook.com]


> Sent: Monday, January 26, 2015 2:53 PM

> To: Moore, Thomas (FtWorth)

> Cc: Chris Tapp; yocto@yoctoproject.org; Gary Thomas

> Subject: Re: [yocto] adding all the pieces of WiFi to core-image-minimal

> 

> 

> > On Jan 26, 2015, at 3:36 PM, Moore, Thomas (FtWorth) 
> >  wrote:

> > 

> > Try building core-image-base or adding packagegroup-base-extended to your 
> > IMAGE_INSTALL. This should add the modules and firmware.

> > 

> > core-image-minimal is just that and only includes just enough to boot the 
> > system.

> > 

> > P.S. if you add "wifi" to your DISTRO_FEATURES, then packagegroup-base-wifi 
> > should automatically get added to the image. Checkout 
> > meta/recipes-core/packagegroups/packagegroup-base.bb to see how that works.

> > 

> > Thomas

> > 

> 

> Interesting! are we talking about doing this in the local.conf? or are we 
> talking about modifying existing recipes? I'd like to do this cleanly and not 
> mess up what's in the default files. Maybe create my own layer??

> 

> Jim A

> 

> > From: yocto-boun...@yoctoproject.org


> > [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Chris Tapp

> > Sent: Monday, January 26, 2015 2:28 PM

> > To: James Abernathy

> > Cc: yocto@yoctoproject.org; Gary Thomas

> > Subject: Re: [yocto] adding all the pieces of WiFi to 

> > core-image-minimal

> > 

> > 

> > On 26 Jan 2015, at 19:31, James Abernathy  wrote:

> > 

> > 

> > I get a clean build when I add: CORE_IMAGE_EXTRA_INSTALL += " 
> > packagegroup-base-wifi"

> > 

> > However, I have no wireless drivers. I must have to add something to add 
> > the drivers and firmware to the kernel. Not sure what though.

> > 

> > I'm not an expert here, but I think that adding kernel-modules and 
> > linux-firmware to your extra_install should give you what you need.

> > 

> > 

> > Jim A

> > 

> > On Jan 26, 2015, at 11:09 AM, James Abernathy  
> > wrote:

> > 

> > 

> > On Jan 26, 2015, at 10:52 AM, Gary Thomas  wrote:

> > 

> > On 2015-01-26 08:26, James Abernathy wrote:

> > 

> > 

> > 

> > On Jan 26, 2015, at 8:49 AM, Gary Thomas  > > wrote:

> > 

> > On 2015-01-26 06:29, James Abernathy wrote:

> > 

> > 

> > 

> > On J

Re: [yocto] adding all the pieces of WiFi to core-image-minimal

[Gary Thomas]

On 2015-01-26 12:31, James Abernathy wrote:

I get a clean build when I add: CORE_IMAGE_EXTRA_INSTALL += " 
packagegroup-base-wifi”

However, I have no wireless drivers.  I must have to add something to add the 
drivers and firmware to the kernel.  Not sure what though.


That's a whole separate issue.  To get the drivers you typically need
to add kernel-modules and linux-firmware (as others have stated).  However,
if you want a truly minimal system, those are poor choices as they bring
in TONS of packages.  You probably want to just include the kernel-module-XXX
and linux-firmware-XXX that are actually needed by your hardware.


On Jan 26, 2015, at 11:09 AM, James Abernathy mailto:jfaberna...@outlook.com>> wrote:



On Jan 26, 2015, at 10:52 AM, Gary Thomas mailto:g...@mlbassoc.com>> wrote:

On 2015-01-26 08:26, James Abernathy wrote:



On Jan 26, 2015, at 8:49 AM, Gary Thomas mailto:g...@mlbassoc.com> 
> wrote:

On 2015-01-26 06:29, James Abernathy wrote:



On Jan 23, 2015, at 12:37 PM, Gary Thomas mailto:g...@mlbassoc.com> 
> wrote:

On 2015-01-23 10:24, Jim Abernathy wrote:

I'm starting a project mostly for self-education.  I have already done the 
project using Ubuntu Server 14.04 using a Intel NUC and a Pandaboard as 
targets.  Now I want to
see how
easy it is to move it to Yocto.

Starting with the NUC, I can boot Dizzy 1.7.1 core-image-minimal and 
core-image-sato, both built with bitbake and not the prebuilt images. However, 
core-image-minimal
doesn't have
WiFi and core-image-sato does, but I don't need all the GUI stuff.  It's a 
headless application.

So what is recommended; eliminating the GUI from sato or adding wifi and 
wpa-supplicant, etc to minimal??  Also any pointers to how to do the 
adding/subtracting would be most
helpful.

Once this is working all I have to do is put apache-tomcat, and openjdk-7-jre, 
then my application.


We use just iw & wpa-supplicant and set up the configuration
files manually (e.g. the wpa-supplicant configurations).


Could you help with a little more details.  What I envision is adding an append 
statement of some kind to local.conf to load in the wireless related files to 
core-image-minimal,
same with openjdk-7-jre and tomcat7, but my first efforts have generated some 
unintelligible error for me.  So that’s why I’m looking for direction on where 
to start with this.


What was the error you got?  I'll bet it was for 'iw' which
is a package from meta-oe, so you'll need to add that layer

Once you've added the meta-oe layer, you should be able to
put this line in your local.conf:
CORE_IMAGE_EXTRA_INSTALL += " iw wpa-supplicant”


Okay, what I don’t get is the fact that without any additional layers, bitbake 
core-image-sato builds all the WiFi features I need.  bitbake 
core-image-minimal does not.  So I’m
thinking that there is some CORE_IMAGE_EXTRA_INSTALL statement that can just 
add what is needed without extra layers.

I guess it just doesn’t make sense to me right now.


Try using
CORE_IMAGE_EXTRA_INSTALL += " packagegroup-base-wifi"
which will bring in 'wireless-tools' and 'wpa-supplicant'.

I prefer 'iw' to 'wireless-tools' as it is newer and [IMO]
simpler to use.


Thanks, I found that I can clean build with just the wpa-supplicant added and 
I’m hoping that will bring in the wifi drivers.  If it does, all I want to do 
is edit the
/etc/interfaces file with the Static IP of the wlan0, the static IP of the eth0 
and the wpa-xxx for the WKPA2_PSK information.

Do I really need the tools?  I don’t need CLI commands to change any network 
parameters later.

Jim A


--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org 
https://lists.yoctoproject.org/listinfo/yocto


--
___
yocto mailing list
yocto@yoctoproject.org 
https://lists.yoctoproject.org/listinfo/yocto




--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] adding all the pieces of WiFi to core-image-minimal

[Moore, Thomas (FtWorth)]

core-image-base installs packagegroup-base-extended, whereas core-image-minimal 
doesn't. packagegroup-base-extended adds things like kernel modules and other 
package groups that you'll want for a more full-featured system.

Thomas

From: Jim Abernathy [mailto:jfaberna...@outlook.com]
Sent: Monday, January 26, 2015 3:54 PM
To: Moore, Thomas (FtWorth)
Cc: Chris Tapp; yocto@yoctoproject.org; Gary Thomas
Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal



From: thomas.moo...@atk.com
To: jfaberna...@outlook.com
CC: opensou...@keylevel.com; yocto@yoctoproject.org; g...@mlbassoc.com
Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal
Date: Mon, 26 Jan 2015 21:51:47 +
Looks like you also need to add ipv4 to the DISTRO_FEATURES:

DISTRO_FEATURES += "ipv4 wifi"

Might be worth trying.

Thomas

I'll test with it, but why core-image-base vs. core-image-minimal?

Jim A
From: Jim Abernathy [mailto:jfaberna...@outlook.com]
Sent: Monday, January 26, 2015 3:38 PM
To: Moore, Thomas (FtWorth)
Cc: Chris Tapp; yocto@yoctoproject.org; Gary Thomas
Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal


> From: thomas.moo...@atk.com
> To: jfaberna...@outlook.com
> CC: opensou...@keylevel.com; yocto@yoctoproject.org; g...@mlbassoc.com
> Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal
> Date: Mon, 26 Jan 2015 21:04:54 +
>
> For now, I'd just get everything working with the local.conf:
>
> DISTRO_FEATURES += "wifi"
>
> bitbake core-image-base
>
> Ultimately, you may want to make a custom machine and distro config and 
> incorporate all of the things you've specified in local.conf in those 
> configs. For example, I have a system that's an intel-based single-board 
> computer with several expansion cards. I've created a machine configuration 
> to define the basic hardware components (features, drivers, etc). I've also 
> created a custom distro because we prefer system over systemv and to include 
> some other non-machine specific packages. Finally, I've created a custom 
> image that includes some other extras.
>
> The power of local.conf is nice, but it's a little tricky transitioning from 
> that to more of a BSP approach like I described above because most people 
> just say to add it to your local.conf, but that's not really how it should be 
> done at the end. Think global variables vs classes.
>
> P.S. Never edit anything in the poky folder. If you want to modify an 
> existing recipe, create a new layer with a bbappend and modify away.
>
> Thomas
>
>
I tried just adding DISTRO_FEATURES += "wifi" to the local.conf and bitbaking 
core-image-base, but I got a lot of errors:

NOTE: Resolving any missing task queue dependencies
ERROR: Nothing PROVIDES 'glibc'
ERROR: glibc was skipped: missing required distro feature 'ipv4' (not in 
DISTRO_FEATURES)
ERROR: Required build target 'core-image-base' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-base', 'glibc']

So I got it working with core-image-minimal as I mentioned earlier just before 
your reply.

> -Original Message-
> From: James Abernathy 
> [mailto:jfaberna...@outlook.com]
> Sent: Monday, January 26, 2015 2:53 PM
> To: Moore, Thomas (FtWorth)
> Cc: Chris Tapp; yocto@yoctoproject.org; Gary 
> Thomas
> Subject: Re: [yocto] adding all the pieces of WiFi to core-image-minimal
>
>
> > On Jan 26, 2015, at 3:36 PM, Moore, Thomas (FtWorth) 
> > mailto:thomas.moo...@atk.com>> wrote:
> >
> > Try building core-image-base or adding packagegroup-base-extended to your 
> > IMAGE_INSTALL. This should add the modules and firmware.
> >
> > core-image-minimal is just that and only includes just enough to boot the 
> > system.
> >
> > P.S. if you add "wifi" to your DISTRO_FEATURES, then packagegroup-base-wifi 
> > should automatically get added to the image. Checkout 
> > meta/recipes-core/packagegroups/packagegroup-base.bb to see how that works.
> >
> > Thomas
> >
>
> Interesting! are we talking about doing this in the local.conf? or are we 
> talking about modifying existing recipes? I'd like to do this cleanly and not 
> mess up what's in the default files. Maybe create my own layer??
>
> Jim A
>
> > From: yocto-boun...@yoctoproject.org
> > [mailto:yocto-boun...@yoctoproject.org]
> >  On Behalf Of Chris Tapp
> > Sent: Monday, January 26, 2015 2:28 PM
> > To: James Abernathy
> > Cc: yocto@yoctoproject.org; Gary Thomas
> > Subject: Re: [yocto] adding all the pieces of WiFi to
> > core-image-minimal
> >
> >
> > On 26 Jan 2015, at 19:31, James Abernathy 
> > mailto:jfaberna...@outlook.com>> wrote:
> >
> >
> > I get a clean build when I add: CORE_IMAGE_EXTRA_INSTALL += " 
> > packagegroup-base-wifi"
> >
> > However, I have no wireless

Re: [yocto] adding all the pieces of WiFi to core-image-minimal

[Jim Abernathy]

I was just coming to the realization that core-image-minimal isn't what I
 wanted.  So I'll experiment with core-image-base and a minimal set of 
local.conf statements that give me what I need.  Thanks,

Jim A


From: thomas.moo...@atk.com
To: jfaberna...@outlook.com
CC: opensou...@keylevel.com; yocto@yoctoproject.org; g...@mlbassoc.com
Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal
Date: Mon, 26 Jan 2015 22:23:12 +









core-image-base installs packagegroup-base-extended, whereas core-image-minimal 
doesn’t. packagegroup-base-extended adds things like kernel modules and other
 package groups that you’ll want for a more full-featured system.
 

Thomas

 


From: Jim Abernathy [mailto:jfaberna...@outlook.com]


Sent: Monday, January 26, 2015 3:54 PM

To: Moore, Thomas (FtWorth)

Cc: Chris Tapp; yocto@yoctoproject.org; Gary Thomas

Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal


 

 




From: thomas.moo...@atk.com

To: jfaberna...@outlook.com

CC: opensou...@keylevel.com; yocto@yoctoproject.org; g...@mlbassoc.com

Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal

Date: Mon, 26 Jan 2015 21:51:47 +

Looks like you also need to add ipv4 to the DISTRO_FEATURES:
 
DISTRO_FEATURES += "ipv4 wifi"
 
Might be worth trying.
 

Thomas

 
I'll test with it, but why core-image-base vs. core-image-minimal?
 
Jim A


From: Jim Abernathy [mailto:jfaberna...@outlook.com]


Sent: Monday, January 26, 2015 3:38 PM

To: Moore, Thomas (FtWorth)

Cc: Chris Tapp; yocto@yoctoproject.org; Gary Thomas

Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal


 

 

> From: thomas.moo...@atk.com

> To: jfaberna...@outlook.com

> CC: opensou...@keylevel.com; yocto@yoctoproject.org; g...@mlbassoc.com

> Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal

> Date: Mon, 26 Jan 2015 21:04:54 +

> 

> For now, I'd just get everything working with the local.conf:

> 

> DISTRO_FEATURES += "wifi"

> 

> bitbake core-image-base

> 

> Ultimately, you may want to make a custom machine and distro config and 
> incorporate all of the things you've specified in local.conf in those 
> configs. For example, I have a system that's an intel-based single-board 
> computer with several expansion cards. I've
 created a machine configuration to define the basic hardware components 
(features, drivers, etc). I've also created a custom distro because we prefer 
system over systemv and to include some other non-machine specific packages. 
Finally, I've created a custom
 image that includes some other extras.

> 

> The power of local.conf is nice, but it's a little tricky transitioning from 
> that to more of a BSP approach like I described above because most people 
> just say to add it to your local.conf, but that's not really how it should be 
> done at the end. Think global
 variables vs classes.

> 

> P.S. Never edit anything in the poky folder. If you want to modify an 
> existing recipe, create a new layer with a bbappend and modify away.

> 

> Thomas

> 

> 

I tried just adding DISTRO_FEATURES += "wifi" to the local.conf and bitbaking 
core-image-base, but I got a lot of errors:



NOTE: Resolving any missing task queue dependencies

ERROR: Nothing PROVIDES 'glibc'

ERROR: glibc was skipped: missing required distro feature 'ipv4' (not in 
DISTRO_FEATURES)

ERROR: Required build target 'core-image-base' has no buildable providers.

Missing or unbuildable dependency chain was: ['core-image-base', 'glibc']



So I got it working with core-image-minimal as I mentioned earlier just before 
your reply.



> -Original Message-

> From: James Abernathy [mailto:jfaberna...@outlook.com]


> Sent: Monday, January 26, 2015 2:53 PM

> To: Moore, Thomas (FtWorth)

> Cc: Chris Tapp; yocto@yoctoproject.org; Gary Thomas

> Subject: Re: [yocto] adding all the pieces of WiFi to core-image-minimal

> 

> 

> > On Jan 26, 2015, at 3:36 PM, Moore, Thomas (FtWorth) 
> >  wrote:

> > 

> > Try building core-image-base or adding packagegroup-base-extended to your 
> > IMAGE_INSTALL. This should add the modules and firmware.

> > 

> > core-image-minimal is just that and only includes just enough to boot the 
> > system.

> > 

> > P.S. if you add "wifi" to your DISTRO_FEATURES, then packagegroup-base-wifi 
> > should automatically get added to the image. Checkout 
> > meta/recipes-core/packagegroups/packagegroup-base.bb to see how that works.

> > 

> > Thomas

> > 

> 

> Interesting! are we talking about doing this in the local.conf? or are we 
> talking about modifying existing recipes? I'd like to do this cleanly and not 
> mess up what's in the default files. Maybe create my own layer??

> 

> Jim A

> 

> > From: yocto-boun...@yoctoproject.org


> > [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Chris Tapp

> > Sent: Monday, January 26, 2015 2:28 PM

> > To: James Abernathy

> > Cc: yocto@yoctoproject.org; Gary Thomas

> > 

Re: [yocto] adding all the pieces of WiFi to core-image-minimal

[Paul Eggleton]

On Monday 26 January 2015 16:37:37 Jim Abernathy wrote:
> > From: thomas.moo...@atk.com
> > To: jfaberna...@outlook.com
> > CC: opensou...@keylevel.com; yocto@yoctoproject.org; g...@mlbassoc.com
> > Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal
> > Date: Mon, 26 Jan 2015 21:04:54 +
> > 
> > For now, I'd just get everything working with the local.conf:
> > 
> > DISTRO_FEATURES += "wifi"
> > 
> > bitbake core-image-base
> > 
> > Ultimately, you may want to make a custom machine and distro config and
> > incorporate all of the things you've specified in local.conf in those
> > configs. For example, I have a system that's an intel-based single-board
> > computer with several expansion cards. I've created a machine
> > configuration to define the basic hardware components (features, drivers,
> > etc). I've also created a custom distro because we prefer system over
> > systemv and to include some other non-machine specific packages. Finally,
> > I've created a custom image that includes some other extras.
> > 
> > The power of local.conf is nice, but it's a little tricky transitioning
> > from that to more of a BSP approach like I described above because most
> > people just say to add it to your local.conf, but that's not really how
> > it should be done at the end. Think global variables vs classes.
> > 
> > P.S. Never edit anything in the poky folder. If you want to modify an
> > existing recipe, create a new layer with a bbappend and modify away.
> > 
> > Thomas
> 
> I tried just adding DISTRO_FEATURES += "wifi" to the local.conf and
> bitbaking core-image-base, but I got a lot of errors:
> 
> NOTE: Resolving any missing task queue dependencies
> ERROR: Nothing PROVIDES 'glibc'
> ERROR: glibc was skipped: missing required distro feature 'ipv4' (not in
> DISTRO_FEATURES) ERROR: Required build target 'core-image-base' has no
> buildable providers. Missing or unbuildable dependency chain was:

You're getting this error because you're actually replacing the value with 
"wifi" not adding it, because the default value is actually set *after* 
local.conf is parsed using ?=, so having set a value in local.conf, it's 
already set and thus ?= has no effect. Then we get to parsing the glibc recipe 
and that immediately fails because it states that all features in 
DISTRO_FEATURES_LIBC are required, and you've removed those. (As a side note I 
really dislike how this latter bit has been implemented, but at least it 
breaks early rather than what used to happen where it would get up to 
compiling glibc and then fail). The correct way to add to DISTRO_FEATURES in 
local.conf would be to use DISTRO_FEATURES_append = " ..." (and don't forget 
the leading space in the value).

However, that said, I'd guess that if your configuration is the default poky or 
reasonably close to it, DISTRO_FEATURES already contains "wifi", so there 
shouldn't even be a need to add it; particularly as you've already suggested 
wifi was working with core-image-sato.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] When I build kernel with toolchain comes from yocto, I met an issue

[Lei, Maohui]

ping


> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
> On Behalf Of Lei, Maohui
> Sent: Friday, January 23, 2015 10:37 AM
> To: yocto@yoctoproject.org
> Subject: [yocto] When I build kernel with toolchain comes from yocto, I met
> an issue
> 
> Hi all,
> 
> I compiled my kernel by toolchain that supported by yocto 1.7.
> The following is my steps:
> 1. Run the following command to install the toolchain.
># ./poky-lsb-glibc-x86_64-meta-toolchain-ppce500v2-toolchain-1.7.sh
> 
> 2. Set up the cross-development environment:
># . /opt/poky-lsb/1.7/environment-setup-ppce500v2-poky-linux-gnuspe
> 
> And then, I compiled the kernel source. But an error occurred:
> --
> --
> powerpc-poky-linux-gnuspe-ld: unrecognized option '-Wl,-O1'
> powerpc-poky-linux-gnuspe-ld: use the --help option for usage information
> make[1]: *** [init/mounts.o] Error 1
> make: *** [init] Error 2
> --
> --
> 
> I have to unset "LDFLAGS" to continue the build.
> 
> Is there some wrong with my step? Is there some good method to build a kernel
> source by the toolchain?
> 
> Cheers
> 
> Lei Maohui
> --
> ___
> 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] Agenda: Yocto Project Technical Team Meeting - Tuesday, Jan. 27, 2015 8:00 AM US Pacific Time

[Jolley, Stephen K]

Tuesday, January 27, 2015 8:00 AM US Pacific Time



Agenda:



* Opens collection - 5 min (Stephen)

* Yocto Project status - 5 min (Stephen/team)

https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.8_Status

https://wiki.yoctoproject.org/wiki/Yocto_1.8_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_1.8_Features

* SWAT team rotation: Saul -> Ross

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

* Opens - 10 min

* Team Sharing - 10 min





We encourage people attending the meeting to logon the Yocto Project IRC 
chancel during the meeting (optional):



Yocto IRC: http://webchat.freenode.net/?channels=#yocto

IRC Tutorial: http://www.irchelp.org/irchelp/irctutorial.html



Conference Details:

Company:   WIND RIVER SYS

Ready-Access Number: 8007302996/9139049836

Access Code: 2705751


For International numbers see: 
https://www.yoctoproject.org/tools-resources/community/weekly-technical-call


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*   Work Telephone:  (503) 712-0534
*Cell:(208) 244-4460
* Email: stephen.k.jol...@intel.com

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] adding all the pieces of WiFi to core-image-minimal

[James Abernathy]

Okay,  here’s the answer for me.  It should never have been core-image-minimal. 
 I just view that as not core-image-sato, meaning no gui.

If you take standard dizzy and change machine to nuc, then bitbake 
core-image-base, you get all the wifi, wpa-supplicant that you need.

So the trivial answer was that core-image-base is the console, CLI version I 
needed to start with all along.

Thanks for all the help.

Jim A

> On Jan 26, 2015, at 6:22 PM, Paul Eggleton  
> wrote:
> 
> On Monday 26 January 2015 16:37:37 Jim Abernathy wrote:
>>> From: thomas.moo...@atk.com
>>> To: jfaberna...@outlook.com
>>> CC: opensou...@keylevel.com; yocto@yoctoproject.org; g...@mlbassoc.com
>>> Subject: RE: [yocto] adding all the pieces of WiFi to core-image-minimal
>>> Date: Mon, 26 Jan 2015 21:04:54 +
>>> 
>>> For now, I'd just get everything working with the local.conf:
>>> 
>>> DISTRO_FEATURES += "wifi"
>>> 
>>> bitbake core-image-base
>>> 
>>> Ultimately, you may want to make a custom machine and distro config and
>>> incorporate all of the things you've specified in local.conf in those
>>> configs. For example, I have a system that's an intel-based single-board
>>> computer with several expansion cards. I've created a machine
>>> configuration to define the basic hardware components (features, drivers,
>>> etc). I've also created a custom distro because we prefer system over
>>> systemv and to include some other non-machine specific packages. Finally,
>>> I've created a custom image that includes some other extras.
>>> 
>>> The power of local.conf is nice, but it's a little tricky transitioning
>>> from that to more of a BSP approach like I described above because most
>>> people just say to add it to your local.conf, but that's not really how
>>> it should be done at the end. Think global variables vs classes.
>>> 
>>> P.S. Never edit anything in the poky folder. If you want to modify an
>>> existing recipe, create a new layer with a bbappend and modify away.
>>> 
>>> Thomas
>> 
>> I tried just adding DISTRO_FEATURES += "wifi" to the local.conf and
>> bitbaking core-image-base, but I got a lot of errors:
>> 
>> NOTE: Resolving any missing task queue dependencies
>> ERROR: Nothing PROVIDES 'glibc'
>> ERROR: glibc was skipped: missing required distro feature 'ipv4' (not in
>> DISTRO_FEATURES) ERROR: Required build target 'core-image-base' has no
>> buildable providers. Missing or unbuildable dependency chain was:
> 
> You're getting this error because you're actually replacing the value with 
> "wifi" not adding it, because the default value is actually set *after* 
> local.conf is parsed using ?=, so having set a value in local.conf, it's 
> already set and thus ?= has no effect. Then we get to parsing the glibc 
> recipe 
> and that immediately fails because it states that all features in 
> DISTRO_FEATURES_LIBC are required, and you've removed those. (As a side note 
> I 
> really dislike how this latter bit has been implemented, but at least it 
> breaks early rather than what used to happen where it would get up to 
> compiling glibc and then fail). The correct way to add to DISTRO_FEATURES in 
> local.conf would be to use DISTRO_FEATURES_append = " ..." (and don't forget 
> the leading space in the value).
> 
> However, that said, I'd guess that if your configuration is the default poky 
> or 
> reasonably close to it, DISTRO_FEATURES already contains "wifi", so there 
> shouldn't even be a need to add it; particularly as you've already suggested 
> wifi was working with core-image-sato.
> 
> Cheers,
> Paul
> 
> -- 
> 
> Paul Eggleton
> Intel Open Source Technology Centre

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] qtbase: Add basic Qt5 building support

[coldnew . tw]

Hi:

Sorry for the late reply :-S

I'll resend the patch to move it to qt5-layers just like
meta-fsl-arm does, just wait for a while :).

Andrei Gherzan writes:

> Hello,
>
> On Thu, Nov 20, 2014 at 1:58 PM, Andrei Gherzan  wrote:
>
>> Hello Yen,
>>
>> On Sat, Oct 25, 2014 at 10:21:47AM +0800, Yen-Chin Lee wrote:
>> > To build raspberrypi with Qt5, we need to add extra QT_CONFIG_FLAGS to
>> > indicate device config.
>> >
>> > Signed-off-by: Yen-Chin Lee 
>> > ---
>> >  recipes-qt/qt5/qtbase_%.bbappend | 7 +++
>> >  1 file changed, 7 insertions(+)
>> >  create mode 100644 recipes-qt/qt5/qtbase_%.bbappend
>> >
>> > diff --git a/recipes-qt/qt5/qtbase_%.bbappend
>> b/recipes-qt/qt5/qtbase_%.bbappend
>> > new file mode 100644
>> > index 000..c994cf5
>> > --- /dev/null
>> > +++ b/recipes-qt/qt5/qtbase_%.bbappend
>> > @@ -0,0 +1,7 @@
>> > +FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>> > +
>> > +QT_CONFIG_FLAGS += " \
>> > +-device linux-rasp-pi-g++ \
>> > +-device-option CROSS_COMPILE=${TARGET_PREFIX} \
>> > +-I${STAGING_DIR_TARGET}${includedir}/interface/vcos/pthreads \
>> > +"
>>
>> If we add this append we need to change the layer dependencies and
>> probably add
>> this package to the test image too. But maybe we can avoid this by using a
>> separate layer specific directory as meta-fsl-arm does with qt5-layer.
>>
>> Check https://github.com/Freescale/meta-fsl-arm and
>> https://github.com/Freescale/meta-fsl-arm/blob/master/conf/layer.conf
>>
>>
> Do you still work on this? I'm trying to catch up with old patches. Any
> updates on this one?

--
Sent from emacs with mu4e
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux][PATCH] audit-systemd: allow manual stop as sysvinit

[Joe MacDonald]

Merged, thanks, Jackie.

-J.

[[yocto] [meta-selinux][PATCH] audit-systemd: allow manual stop as sysvinit] On 
15.01.14 (Wed 13:30) jackie.hu...@windriver.com wrote:

> From: Jackie Huang 
> 
> The audit service should be manually stopped with systemd.
> 
> Signed-off-by: Jackie Huang 
> ---
>  recipes-security/audit/audit/auditd.service | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/recipes-security/audit/audit/auditd.service 
> b/recipes-security/audit/audit/auditd.service
> index adf4d3b..ebc0798 100644
> --- a/recipes-security/audit/audit/auditd.service
> +++ b/recipes-security/audit/audit/auditd.service
> @@ -5,7 +5,6 @@ After=local-fs.target
>  Conflicts=shutdown.target
>  Before=sysinit.target shutdown.target
>  After=systemd-tmpfiles-setup.service
> -RefuseManualStop=yes
>  
>  [Service]
>  ExecStart=/sbin/auditd -n
> -- 
> 1.9.1
> 
-- 
-Joe MacDonald.
:wq


signature.asc
Description: Digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH][meta-selinux] lxc: inherit enable-selinux

[Joe MacDonald]

[[yocto] [PATCH][meta-selinux] lxc: inherit enable-selinux] On 15.01.21 (Wed 
17:49) rongqing...@windriver.com wrote:

> From: Roy Li 
> 
> inherit enable-selinux to kill the warning that lxc rdepends on libselinux,
> but it isn't a build dependency
> 
> Signed-off-by: Roy Li 

Merged, thanks Roy.

-J.

> ---
>  recipes-containers/lxc/lxc_%.bbappend | 1 +
>  1 file changed, 1 insertion(+)
>  create mode 100644 recipes-containers/lxc/lxc_%.bbappend
> 
> diff --git a/recipes-containers/lxc/lxc_%.bbappend 
> b/recipes-containers/lxc/lxc_%.bbappend
> new file mode 100644
> index 000..8c11cac
> --- /dev/null
> +++ b/recipes-containers/lxc/lxc_%.bbappend
> @@ -0,0 +1 @@
> +inherit enable-selinux
> -- 
> 2.1.0
> 
-- 
-Joe MacDonald.
:wq


signature.asc
Description: Digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux][ 0/3] v2 More recipe updates.

[Joe MacDonald]

[[meta-selinux][ 0/3] v2 More recipe updates.] On 15.01.15 (Thu 02:59) Philip 
Tricca wrote:

> Greetings,
> 
> Three more recipe udpates to get meta-selinux building with oe-core master
> again. These are mostly mundane though the move from findutils from 4.4.x
> to 4.5.x removes the need for patches that have since gone upstream. This
> v2 patch set takes into account comments from Mark w/r to removing PRs due
> to the uprev.
> 
> Best,
> Philip

Thanks for these, Philip, I'd been starting to do the same work myself
but got distracted while auditing the findutils patches.  Merged.

-J.

> 
> Philip Tricca (3):
>   findutils: Upgrade recipe to 4.5 and use wildcard for pico version.
>   logrotate: Use wildcard for version number.
>   tar: Use wildcard for version number in bbappend.
> 
>  .../findutils-with-selinux-gnulib.patch|   55 --
>  .../findutils-4.4.2/findutils-with-selinux.patch   |  528 
> 
>  .../findutils/findutils_4.4.2.bbappend |   14 -
>  .../findutils/findutils_4.5.%.bbappend |2 +
>  recipes-extended/logrotate/logrotate_%.bbappend|5 +
>  .../logrotate/logrotate_3.8.7.bbappend |7 -
>  recipes-extended/tar/tar_%.bbappend|   11 +
>  recipes-extended/tar/tar_1.27.1.bbappend   |   13 -
>  8 files changed, 18 insertions(+), 617 deletions(-)
>  delete mode 100644 
> recipes-extended/findutils/findutils-4.4.2/findutils-with-selinux-gnulib.patch
>  delete mode 100644 
> recipes-extended/findutils/findutils-4.4.2/findutils-with-selinux.patch
>  delete mode 100644 recipes-extended/findutils/findutils_4.4.2.bbappend
>  create mode 100644 recipes-extended/findutils/findutils_4.5.%.bbappend
>  create mode 100644 recipes-extended/logrotate/logrotate_%.bbappend
>  delete mode 100644 recipes-extended/logrotate/logrotate_3.8.7.bbappend
>  create mode 100644 recipes-extended/tar/tar_%.bbappend
>  delete mode 100644 recipes-extended/tar/tar_1.27.1.bbappend
> 
-- 
-Joe MacDonald.
:wq


signature.asc
Description: Digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] (IIO) ADC freeze on am335x processor on 3.14.26ltsi kernel

[Yani Dubin]

Hi,

I have run up against a kernel bug on the dizzy branch where a read of an
ADC channel (IIO bus) on a Sitara (am335x) processor locks up the process
reading the /sys/bus/iio/devices/iio\:device0/in_voltage?_raw node. The
system remains stable, but the locked process does not respond to SIGKILL.
No kernel errors or debugging info in the logs - but I have taken no steps
to improve verbosity. fuser shows the files as being open by the crashed
process.

I did google the issue, but turned up nothing. This is very reproduceable,
and I have done my best to narrow it down on the dizzy timeline. In each
case I have used the same rootfs (built from dizzy tip), but just flashed a
different kernel.

The (yocto) changesets in question are:
36e42c0ddb7a40b3022e9b165560622479f1aa5c  - 3.14.26ltsi exhibits issue
446acfb5a474b23041b46c49732474f2d415160d   - 3.14.24 doesn't build
d7c61053da96d675c3912a45ee448c20ae91721b - 3.14.19 issue not present

The build error in question is "ERROR: Fetcher failure: Unable to find
revision fba2d0cdb745e0f807ce134fd9d1524b7bed9742 in branch meta even from
upstream".

These are 3 adjacent changesets on the dizzy branch - I gather that is as
much as I can narrow it down?

Should I be submitting this bug to yocto bugzilla (since it affects the
stable release, and I am using linux-yocto) or a linux kernel bug tracker /
mailing list? Or is there further information I should be getting (enabling
kernel debugging / increasing verbosity perhaps)? Should I do a build off
the unstable branch for comparison? (to see if this has a newer kernel,
with upstream fix which resolves the issue)

Meanwhile, I thought I would see if anyone else is experiencing this, or
has similar hardware and can see if they are also affected. This is a
custom board, but similar processor-wise to the Beaglebone Black.

Steps to reproduce:
cat /sys/bus/iio/devices/iio\:device0/in_voltage?_raw

The particular drivers in use are:
CONFIG_TI_AM335X_ADC=y
CONFIG_MFD_TI_AM335X_TSCADC=y

Regards,
Yani.

-- 

--
This email, including any attachments, is only for the intended recipient. 
It is subject to copyright, is confidential and may be the subject of legal 
or other privilege, none of which is waived or lost by reason of this 
transmission.
If you are not an intended recipient, you may not use, disseminate, 
distribute or reproduce such email, any attachments, or any part thereof. 
If you have received a message in error, please notify the sender 
immediately and erase all copies of the message and any attachments.
Unfortunately, we cannot warrant that the email has not been altered or 
corrupted during transmission nor can we guarantee that any email or any 
attachments are free from computer viruses or other conditions which may 
damage or interfere with recipient data, hardware or software. The 
recipient relies upon its own procedures and assumes all risk of use and of 
opening any attachments.
--
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi: Replace not working v3.16.1 by v3.16.5

[Petter Mabäcker]

Hi,

Actually this bump is already included in meta-raspberrypi:

efd760d linux-raspberrypi: faulty branch and srcrev for 3.16

BR,
Petter

2015-01-26 00:03 skrev Andrei Gherzan:


Hi Theodor,

On Wed, Dec 3, 2014 at 1:03 PM, Jens Lucius 
wrote:


From: Jens Lucius 

The recipe for 3.16.1 is not working because of a typo in branch
and the revision not being available any more.

Update to latest (and last) 3.16.5.

No Update to a 3.17.x because these get rebased regularly.

Signed-off-by: Jens Lucius 


Could you give this patch a spin?
--

ANDREI GHERZAN

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Add a new recipe/meta layer to Yocto

[Fung, Joshua]

I am new to Yocto project.  I have been working on some SW components, and I'll 
like to know how can I upstream it to Yocto so that it may be reused by others.
I have searched the FAQ and find 
https://www.yoctoproject.org/blogs/dvhart/2011/extending-yocto-project-poky-meta-layers.
Yet I still have no clue what to do with the job.
Anyone care to shed some light ?

Best regards,
Joshua Fung

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] Image will halt soon after boot

[Andrei Gherzan]

Dizzy branch created. Enjoy!
On Jan 26, 2015 12:35 AM, "Andrei Gherzan"  wrote:

> Dizzy branch on its way. Maintainer received the ping.
>
> On Thu, Dec 18, 2014 at 5:45 PM, Maciej Borzecki <
> maciej.borze...@open-rnd.pl> wrote:
>
>> On 12/18 16:42, Petter Gustad wrote:
>> > From: Maciej Borzecki 
>> > Subject: Re: [yocto] [meta-raspberrypi] Image will halt soon after boot
>> > Date: Thu, 18 Dec 2014 10:12:28 +0100
>> >
>> > > Have you seen the same on 1.7 or current master? I'm using a number of
>> > > Yocto built images (sone on 1.7.x, other mostly follow poky +
>> > > meta-raspberrypi master branches) and things seem to work just fine.
>> >
>> > Thanks! I just tried the master branch as given below and it works
>> > fine. I will switch to a more recent release. However, I can't seem to
>> > find a dizzy branch in meta-raspberrypi?
>>
>> It seems that thee is no dizzy branch at all in meta-raspberrypi. You
>> might want to ping the layer's maintainers about that.
>>
>> --
>> Maciej Borzęcki
>> Senior Software Developer at Open-RnD Sp. z o.o., Poland
>> www.open-rnd.pl
>> mobile: +48 889 117 365, fax: +48 42 657 9079
>>
>>
>> Niniejsza wiadomość wraz z załącznikami może
>> zawierać chronione prawem lub poufne informacje i została
>> wysłana wyłącznie do wiadomości i użytku osób, do których
>> została zaadresowana. Jeśli wiadomość została otrzymana
>> przypadkowo zabrania się jej kopiowania lub rozsyłania do osób
>> trzecich. W takim przypadku uprasza się o natychmiastowe
>> zniszczenie wiadomości oraz poinformowanie nadawcy o
>> zaistniałej sytuacji za pomocą wiadomości zwrotnej.
>> Dziękujemy.
>>
>> This message, including any attachments hereto,
>> may contain privileged or confidential information and is sent
>> solely for the attention and use of the intended addressee(s).
>> If you are not an intended addressee, you may neither use this
>> message nor copy or deliver it to anyone. In such case, you
>> should immediately destroy this message and kindly notify the
>> sender by reply email. Thank you.
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
>
>
> --
> *Andrei Gherzan*
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] dansguardian

[Mahdi Saadat]

Hi Paul
Thanks for your response the log file is as below:
DEBUG: Executing python function rootfs_process_ignore
DEBUG: Python function rootfs_process_ignore finished
DEBUG: Executing python function rootfs_runtime_mapping
DEBUG: Python function rootfs_runtime_mapping finished
DEBUG: Executing python function do_rootfs
NOTE: configuring RPM platform settings
NOTE: configuring RPM system provides
NOTE: configuring RPM DB settings
NOTE: configuring Smart settings
NOTE: Note: adding Smart channel nimak (45)
NOTE: Note: adding Smart channel core2_32 (40)
NOTE: Note: adding Smart channel all (35)
NOTE: adding Smart RPM DB channel
NOTE: Note: configuring RPM cross-install scriptlet_wrapper
NOTE: ## Generate rootfs ###
NOTE: Executing
'/home/nimak/poky/build/tmp/sysroots/x86_64-linux/usr/bin/createrepo
--update -q /home/nimak/poky/build/tmp/deploy/rpm/all' ...
NOTE: Executing
'/home/nimak/poky/build/tmp/sysroots/x86_64-linux/usr/bin/createrepo
--update -q /home/nimak/poky/build/tmp/deploy/rpm/nimak' ...
NOTE: Executing
'/home/nimak/poky/build/tmp/sysroots/x86_64-linux/usr/bin/createrepo
--update -q /home/nimak/poky/build/tmp/deploy/rpm/core2_32' .$
NOTE: Installing the following packages: iptables run-postinsts dansguardian
squid clamav snort packagegroup-core-boot
ERROR: dansguardian not found in the base feeds (nimak core2-32-intel-common
core2-32 i586 x86 noarch any all).
acl-2.2.52-r0@core2_32 acl-dbg-2.2.52-r0@core2_32 acl-dev-2.2.52-r0@core2_32
acl-doc-2.2.52-r0@core2_32 acl-locale-de-2.2.52-r0@core2_32 acl-local$
DEBUG: Python function do_rootfs finished
ERROR: Function failed: do_rootfs

---
Regards
Mahdi 

-Original Message-
From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com] 
Sent: Monday, January 26, 2015 2:18 PM
To: Mahdi Saadat
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] dansguardian

Hi Mahdi,

On Saturday 24 January 2015 11:05:45 Mahdi Saadat wrote:
> Does anyone knows about how put dansguardian on core-image-minimal?
> I Did some steps on creating the recipe but had some errors on config
stage.

You'll need to be a bit more specific about the errors you received before
anyone will be able to help.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto