[yocto] Installing linux image with two separate flash partitions

[A]

I'm currently using petalinux to build a image.ub that works fine for me so
far (petalinux hides many things from me, but is bitbake under the hood).

However, this image will get stored into a flash device which I intend to
configure with three partitions
1) uboot
2) linux
3) an extra jffs2 with data and executables from my linux recipes

I currently build this third partition manually with mkfs.jffs2, after my
bitbake recipe has completed.
However, since the openembedded framework is pretty nifty and extensible,
I'd like to be able to have this in a recipe.

So far, I've thought to store the things for partition #3 in a STAGING_*
area, and create a new recipe that will DEPEND on those other recipes.  The
new recipe will do a mkfs.jffs2 command in its do_compile().  Then I would
find that jffs file in the build subdirectories somewhere, and assemble it
into the larger image for insertion into the flash device.

However, a) I'm not sure if this is the best way do do this, and b) I have
a "DEPEND" statement, but the "do_stage()" function of the dependency still
doesn't appear to have been invoked.

All advice welcome.

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

[yocto] Question about temporary directories

[A]

I'd like multiple "helper" recipes to contribute files to a temporary
directory on my build host, and then a final recipe to combine them into a
compressed file.

But I DON'T want the helper recipe's files to get installed on the target
system.  My goal is to have them put into a jffs2 image, which will
eventually get flashed onto a target partition using JTAG.

So, I suspect I would have to fly under the radar in yocto, having the
helper recipes install something into the host filesystem, then have the
final recipe know about that location.

Any advice how I can do this as "properly" as possible in yocto?

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

Re: [yocto] Question about temporary directories

[A]

In the absence of any wise counsel, I am currently having all of my recipes
install into a temporary directory I created on the build host's
filesystem.  Then, I have one of my recipes create the filesystem image
with the contents of that location.

I'm not sure how portable this is going to be.  It would be less annoying
if I knew of a predefined variable I could use in the recipe (so I don't
have to go outside the workspace), but they all seem to be recipe-specific
or target-specific.



On Tue, Dec 18, 2018 at 1:27 PM A  wrote:

> I'd like multiple "helper" recipes to contribute files to a temporary
> directory on my build host, and then a final recipe to combine them into a
> compressed file.
>
> But I DON'T want the helper recipe's files to get installed on the target
> system.  My goal is to have them put into a jffs2 image, which will
> eventually get flashed onto a target partition using JTAG.
>
> So, I suspect I would have to fly under the radar in yocto, having the
> helper recipes install something into the host filesystem, then have the
> final recipe know about that location.
>
> Any advice how I can do this as "properly" as possible in yocto?
>
> Aaron
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Basic Yocto+CMake Usage question

[A]

I'm having issues with a yocto build that is combining recipes that should
depend on each other, and I need a sanity check.  Is this an ok forum for
stupid user questions?

The main idea is to have one recipe install some prebuilt libraries, and
have another cmake-based recipe use those libraries.

As a caveat, this is a native version of the build that I seem to be having
trouble with, but I assume that is mostly irrelevant:

In ProjectA, the meat of the matter is a do_install that copies
ProjectA*.so into STAGING_LIBDIR.  I don't recall why I chose that instead
of ${D}${libdir}... is it ok this way?
In ProjectB, I'd like CMake's find_library() to find Project A's libraries,
and I seem to be having trouble.

How would you approach this?  The recipe for Project B contains "inherit
cmake" and some variables I pass in with an EXTRA_OECMAKE and an
EXTRA_OECMAKE-native.

I also have there:
DEPENDS += "ProjectA"
DEPENDS_class-native = "ProjectA-native"

However,in ProjectB's find_library() call, I am uncertain how to direct it
to find those libraries - what PATHS or HINTS or whatever?

Any help is gladly appreciated.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Basic Yocto+CMake Usage question

[A]

Thank you for the quick suggestion.

Unfortunately, I tried setting OECMAKE_FIND_ROOT_PATH_MODE_LIBRARY to
"ONLY", "NEVER", and "BOTH" separately, and none of the above worked.  I
must be doing something fundamentally wrong.

Any other suggestions?


On Thu, Mar 28, 2019 at 12:30 PM Patrick Boettcher <
patrick.boettc...@posteo.de> wrote:

> Hi
>
> On Thu, 28 Mar 2019 12:20:43 -0400
> A  wrote:
>
> > I'm having issues with a yocto build that is combining recipes that
> > should depend on each other, and I need a sanity check.  Is this an
> > ok forum for stupid user questions?
> >
> > The main idea is to have one recipe install some prebuilt libraries,
> > and have another cmake-based recipe use those libraries.
> >
> > As a caveat, this is a native version of the build that I seem to be
> > having trouble with, but I assume that is mostly irrelevant:
> >
> > In ProjectA, the meat of the matter is a do_install that copies
> > ProjectA*.so into STAGING_LIBDIR.  I don't recall why I chose that
> > instead of ${D}${libdir}... is it ok this way?
> > In ProjectB, I'd like CMake's find_library() to find Project A's
> > libraries, and I seem to be having trouble.
> >
> > How would you approach this?  The recipe for Project B contains
> > "inherit cmake" and some variables I pass in with an EXTRA_OECMAKE
> > and an EXTRA_OECMAKE-native.
> >
> > I also have there:
> > DEPENDS += "ProjectA"
> > DEPENDS_class-native = "ProjectA-native"
> >
> > However,in ProjectB's find_library() call, I am uncertain how to
> > direct it to find those libraries - what PATHS or HINTS or whatever?
>
> I was having similar problems with this (a dependency for zeromq in my
> case).
>
>   DEPENDS = "zeromq" # build dependency
>
> I had to add the following variable to my recipes:
>
>   OECMAKE_FIND_ROOT_PATH_MODE_PROGRAM = "BOTH"
>
> this, iiuc, tells cmake that in case of cross-compiling (via a
> toolchain-file) that it shall also look in the sysroot for header
> and library-files when doing find_library(). Not sure if it will work
> with all find_package()-modules.
>
> It worked, I haven't investigated further why, but I should have.
>
> HTH.
> --
> Patrick.
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Creating a special file as a dependency., .. how do I cause a recipe to execute

[A]

I would like to create a directory structure under TMPDIR as part of the
installation of my bitbake environment... I later create a jffs2 image from
${TMPDIR}/myapptmp/*.

(If it matters, I'm doing this because I want all my proprietary software
installed in a separate partition in the QSPI that gets mounted to a
separate /app directory) on boot.

So, I have my do_install function do things like this:
MY_STAGING_DIR=${TMPDIR}/mytmp
install -d ${MY_STAGING_DIR}
install -d ${MY_STAGING_DIR}/bin
install -d ${MY_STAGING_DIR}/script
...

And my recipe also states things like this:
FILES_${PN} = " \
${TMPDIR}/mytmp  \
${TMPDIR}/mytmp  /bin \
${TMPDIR}/mytmp  /script \
...

However, when I delete this directory and run my recipe's do_install
function, I don't see the temporary directory getting created.
On the other hand, if I edit my recipe (say, to insert debugging to figure
out what is going on) and run it again, I see the temporary directory is
created..

I suppose I could delete the temp directory every time I change code,... if
I remember every time, this would be great.  On the other hand, how can I
make the recipe run the do_install when the output object (temp directory)
is not there?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Qemu Launch Issue:

[sadu A]

Hi Team,

I'm new to yocto environment, I need clarification on this:

Launching Qemu default and launching by using "-nographic" option makes any
difference.

Please clarify this.


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

[yocto] Doubt regarding python-elementtree rpm

[Varun A]

Hi

Had a doubt. While building python3 rpms using python 3.4.3 bit bake file, I am 
noticing that python-elementtree rpm is missing. It used to be available in 
package feeds in python 2.7 case. Has it been merged with another RPM? If so 
which one.

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

Re: [yocto] [PATCH 0/4] misc fixes for 1.3 meta-intel release

[Kamble, Nitin A]

> -Original Message-
> From: Zanussi, Tom
> Sent: Wednesday, October 31, 2012 1:58 PM
> To: Burton, Ross
> Cc: Kamble, Nitin A; Hart, Darren; yocto@yoctoproject.org
> Subject: Re: [PATCH 0/4] misc fixes for 1.3 meta-intel release
> 
> On Wed, 2012-10-31 at 20:53 +, Burton, Ross wrote:
> > On 31 October 2012 15:21, Burton, Ross  wrote:
> > > On 31 October 2012 15:17, Tom Zanussi  wrote:
> > >> That just leaves cedartrail before we can pull this in.
> > >
> > > That's odd, I was just about to write a mail.  My current images are
> > > broken as they are based on master which has a duff udev.  I'll do a
> > > rebuild against danny but that might not happen promptly.
> >
> > Just tested on Cedar Trail, good old Sintel plays fine at 4% CPU.
> >
> 
> OK, sounds like it works everywhere, so can be pulled in, but...
> 
> Nitin, did you need to refresh this patchset to .18 or should I pull this in 
> and
> pull in a .18 update later?
> 

Tom,
The patch set is not at the latest versions of libva components.
Nitin


> Tom
> 
> 
> > Ross
> 

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

Re: [yocto] [Patch v2 0/4] Misc Fixes for meta-intel 1.3 release

[Kamble, Nitin A]

> -Original Message-
> From: Zanussi, Tom
> Sent: Thursday, November 01, 2012 6:33 AM
> To: Hart, Darren
> Cc: Kamble, Nitin A; yocto@yoctoproject.org; Burton, Ross
> Subject: Re: [Patch v2 0/4] Misc Fixes for meta-intel 1.3 release
> 
> On Wed, 2012-10-31 at 22:26 -0700, Darren Hart wrote:
> > On 10/31/2012 10:14 PM, nitin.a.kam...@intel.com wrote:
> > > From: Nitin A Kamble 
> > >
> > > This v2 pull request is with newer version of libva-intel-driver.
> > > These commits tested on All the BSPs I am maintaining with expected
> results.
> > >
> >
> > Nitin, do these patches fix any specific bug? Such as 3348? You
> > mention a couple, but not clearly that these patches fix them. If so,
> > please
> > include:
> >
> > Fixes [YOCTO #]
> >
> > in the commit log for the associated patch(es).
> >
> 
> To save time, I'll go ahead and add that to those 2 patches when I pull it 
> in...
Thanks Tom,
Nitin
> 
> Tom
> 
> > Otherwise this looks to be what we have discussed.
> >
> > Thanks,
> >
> > Darren
> >
> > > Thanks,
> > > Nitin
> > >
> > > The following changes since commit
> 43b2e9c34363ade4241a60f699b47179929c6fb6:
> > >
> > >   n450: Add WEBTITLE and boilerplate README (2012-10-31 08:40:15
> > > -0700)
> > >
> > > are available in the git repository at:
> > >   git://git.yoctoproject.org/meta-intel-contrib nitin/misc
> > >
> > > http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=nitin
> > > /misc
> > >
> > > Nitin A Kamble (3):
> > >   libva: update to the latest version
> > >   libva-intel-driver: update to the latest version
> > >   mesa-dri.bbappend: avoid conflict with emgd-driver-bin
> > >
> > > Ross Burton (1):
> > >   libva: remove redundant libva 1.0.12
> > >
> > >  .../recipes-graphics/mesa/mesa-dri_8.0.4.bbappend  |   27
> +---
> > >  .../libva/libva-intel-driver.inc   |2 +-
> > >  .../libva/libva-intel-driver_1.0.15.bb |8 --
> > >  .../libva/libva-intel-driver_1.0.18.bb |8 ++
> > >  common/recipes-multimedia/libva/libva_1.0.12.bb|8 --
> > >  common/recipes-multimedia/libva/libva_1.0.15.bb|8 --
> > >  common/recipes-multimedia/libva/libva_1.0.16.bb|8 ++
> > >  7 files changed, 40 insertions(+), 29 deletions(-)  delete mode
> > > 100644 common/recipes-multimedia/libva/libva-intel-driver_1.0.15.bb
> > >  create mode 100644
> > > common/recipes-multimedia/libva/libva-intel-driver_1.0.18.bb
> > >  delete mode 100644 common/recipes-multimedia/libva/libva_1.0.12.bb
> > >  delete mode 100644 common/recipes-multimedia/libva/libva_1.0.15.bb
> > >  create mode 100644 common/recipes-multimedia/libva/libva_1.0.16.bb
> > >
> >
> 

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

Re: [yocto] [PATCH 4/4] mesa-dri.bbappend: avoid conflict with emgd-driver-bin

[Kamble, Nitin A]

> -Original Message-
> From: Burton, Ross [mailto:ross.bur...@intel.com]
> Sent: Wednesday, October 31, 2012 10:14 AM
> To: Kamble, Nitin A
> Cc: Zanussi, Tom; Hart, Darren; yocto@yoctoproject.org
> Subject: Re: [yocto] [PATCH 4/4] mesa-dri.bbappend: avoid conflict with
> emgd-driver-bin
> 
> Hi,
> 
> On 31 October 2012 02:23,   wrote:
> > Extend the mesa-dri recipe from oecore to avoid conflict with files
> > generated by emgd-driver-bin recipe.
> 
> The same problem happens with cdv-pvr-driver, right?
Yes, I have heard about the issue from Rahul.

> 
> It turns out that the binary DRI drivers these closed driver packages install 
> are
> very dependent on the Mesa - so it's likely that they just don't work with our
> Mesa 8.0.4.
> 
> cdv-pvr-driver needs Mesa 7.11.  I can't see anything in the documentation
> about what version of Mesa EMGD expects.

EMGD tarball release notes do mention Mesa version dependencies. We have not 
seen issues with the newer version of mesa, so went ahead with the newer 
versions of Mesa, while pinning the Mesa version in the machine.conf.


> 
> I think we've two options: either don't ship libGL in our BSP packages, or 
> ship
> a version that should actually work.  This means shipping a mesa recipe in
> meta-intel so that it's under meta-intel's control, with the useful side 
> effect
> that we can make it just build libGL and nothing else.

These are the right options IMO. We can also get complete mesa recipe in 
meta-intel, which will override the one from oecore layer completely. Then we 
have full control of mesa from meta-intel layers. Currently extending the 
oecore mesa recipe from meta-intel is not very elegant, but at least it is 
working as we want. Also making few changes to the oecore mesa recipe will make 
it easier to extend it from other layers. 

Nitin


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

[yocto] Ada layer for Yocto

[Luke A. Guest]

Hi,

I managed to get my Ada layer going for the official gumstix repo. I had
the code in the wrong bbappend file, should be the gcc-cross, not the
gcc one.

The repo is here: https://github.com/Lucretia/meta-ada

This is currently very basic support and I will be adding more. Please
see the README for problems. Please test and help me refine it.

Luke.


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

[yocto] [PATCH 0/1] Misc: detect trailing space in the patches

[nitin . a . kamble]

From: Nitin A Kamble 

This commit is for detecting trailing white space in the create-pull-request 
script.

Thanks,
Nitin

The following changes since commit 381c4b69c7e8b452f4d3de2f8214e6e5f6a9abe7:

  sstate.bbclass: fix detection of owners matching sstate files (2012-12-05 
15:34:07 +)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib nitin/misc
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/misc

Nitin A Kamble (1):
  create-pull-request: detect trailing white space

 scripts/create-pull-request |   13 -
 1 files changed, 12 insertions(+), 1 deletions(-)

-- 
1.7.3.4

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

[yocto] [PATCH 1/1] create-pull-request: detect trailing white space

[nitin . a . kamble]

From: Nitin A Kamble 

Add logic in the create-pull-request to detect the trailing white space
inserted by patches.

Signed-off-by: Nitin A Kamble 
---
 scripts/create-pull-request |   13 -
 1 files changed, 12 insertions(+), 1 deletions(-)

diff --git a/scripts/create-pull-request b/scripts/create-pull-request
index 9a8913d..c35c427 100755
--- a/scripts/create-pull-request
+++ b/scripts/create-pull-request
@@ -173,7 +173,6 @@ mkdir $ODIR
 # Generate the patches and cover letter
 git format-patch -M40 --subject-prefix="$PREFIX" -n -o $ODIR --thread=shallow 
--cover-letter $RELATIVE_TO..$COMMIT_ID > /dev/null
 
-
 # Customize the cover letter
 CL="$ODIR/-cover-letter.patch"
 PM="$ODIR/pull-msg"
@@ -229,3 +228,15 @@ Review their content, especially the summary mail:
 When you are satisfied, you can send them with:
 send-pull-request -a -p $ODIR
 EOM
+
+# Check the patches for trailing white space
+echo 
+egrep -nH -e "^\+\s+$" $ODIR/* > /dev/null
+if [ $? -ne 1 ]; then
+   echo "WARNING: Trailing white space detected at these locations"
+   egrep -nH -e "^\+\s+$" $ODIR/* 
+else
+   echo "Note: No trailing white space is detected in these patches :)"
+fi
+
+
-- 
1.7.3.4

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

[yocto] [Patch v2 0/1] Misc: check trailing white space in the patches

[nitin . a . kamble]

From: Nitin A Kamble 

The earlier (v1) patch was checking trailing white space only for added empty 
lines.
This v2 patch checks for all the lines added by patches.

Thanks,
Nitin

The following changes since commit 381c4b69c7e8b452f4d3de2f8214e6e5f6a9abe7:

  sstate.bbclass: fix detection of owners matching sstate files (2012-12-05 
15:34:07 +)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib nitin/misc
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/misc

Nitin A Kamble (1):
  create-pull-request: detect trailing white space

 scripts/create-pull-request |   13 -
 1 files changed, 12 insertions(+), 1 deletions(-)

-- 
1.7.3.4

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

[yocto] [Patch v2 1/1] create-pull-request: detect trailing white space

[nitin . a . kamble]

From: Nitin A Kamble 

Add logic in the create-pull-request to detect the trailing white space
inserted by patches.

Signed-off-by: Nitin A Kamble 
---
 scripts/create-pull-request |   13 -
 1 files changed, 12 insertions(+), 1 deletions(-)

diff --git a/scripts/create-pull-request b/scripts/create-pull-request
index 9a8913d..58e7df1 100755
--- a/scripts/create-pull-request
+++ b/scripts/create-pull-request
@@ -173,7 +173,6 @@ mkdir $ODIR
 # Generate the patches and cover letter
 git format-patch -M40 --subject-prefix="$PREFIX" -n -o $ODIR --thread=shallow 
--cover-letter $RELATIVE_TO..$COMMIT_ID > /dev/null
 
-
 # Customize the cover letter
 CL="$ODIR/-cover-letter.patch"
 PM="$ODIR/pull-msg"
@@ -229,3 +228,15 @@ Review their content, especially the summary mail:
 When you are satisfied, you can send them with:
 send-pull-request -a -p $ODIR
 EOM
+
+# Check the patches for trailing white space
+echo
+egrep -nH -e "^\+.*\s+$" $ODIR/* > /dev/null
+if [ $? -ne 1 ]; then
+   echo "WARNING: Trailing white space detected at these locations"
+   egrep -nH -e "^\+.*\s+$" $ODIR/*
+else
+   echo "Note: No trailing white space is detected in these patches :)"
+fi
+
+
-- 
1.7.3.4

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

Re: [yocto] [PATCH 0/1] Misc: detect trailing space in the patches

[Kamble, Nitin A]

From: Daniel Stone [mailto:dan...@fooishbar.org]
Sent: Wednesday, December 05, 2012 9:48 PM
To: Martin Jansa
Cc: Kamble, Nitin A; yocto@yoctoproject.org
Subject: Re: [yocto] [PATCH 0/1] Misc: detect trailing space in the patches

Hi,

On 6 December 2012 15:23, Martin Jansa 
mailto:martin.ja...@gmail.com>> wrote:

Can you add also detection of mixed whitespace? E.g. tab followed by space in 
multilinear indentation? Only as warning. Thanks

These checks can generate infuriating false positives when your patch modifies 
upstream code which has trailing or mixed whitespace in either context or 
removal lines; in this case, removing a line with trailing whitespace and 
replacing it with one which doesn't would generate a warning.  Mixed whitespace 
is also part of some coding styles, notably the kernel's.

Cheers,
Daniel

This code checks for the trialing whitespace only in the lines added by the 
patches. The context lines or removed lines are not checked. It is easy to 
check for mixed whitespace also, but before doing that I would like to know the 
final decision about it, as I see some objection to it too.

Thanks,
Nitin


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

[yocto] Host authenticity failures

[Thornburg, Christopher A]

I've started getting the following error from bitbake when it's trying to 
access my git server:

The authenticity of host '[]:([]:)' can't be 
established.
DSA key fingerprint is 

I understand this error means that the server's key has probably changed, and I 
understand in general how to deal with this via SSH config. When I manually 
ssh'd to the server the first time after receiving the error, I got the same 
message, as expected. I entered "yes" and tried again to verify that the error 
went away. It did. I then ran bitbake again and got the same error. I changed 
my ~/.ssh/ssh_config file to disable StrictHostKeyChecking and still get the 
error.

Is bitbake somehow using different known_hosts and ssh_config files from the 
ones I use for interactive logins? Other ideas on how to resolve this?


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

[yocto] Host authenticity failures

[Thornburg, Christopher A]

I've started getting the following error from bitbake when it's trying to 
access my git server:

The authenticity of host '[]:([]:)' can't be 
established.
DSA key fingerprint is 

I understand this error means that the server's key has probably changed, and I 
understand in general how to deal with this via SSH config. When I manually 
ssh'd to the server the first time after receiving the error, I got the same 
message, as expected. I entered "yes" and tried again to verify that the error 
went away. It did. I think ran bitbake again and got the same error. I changed 
my ~/.ssh/ssh_config file to disable StrictHostKeyChecking and still get the 
error.

Is bitbake somehow using different known_hosts and ssh_config files from the 
ones I use for interactive logins? Other ideas on how to resolve this?

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

Re: [yocto] Host authenticity failures

[Thornburg, Christopher A]

Yes...this is still happening. :(

From: Stewart, David C
Sent: Friday, January 04, 2013 7:50 PM
To: Thornburg, Christopher A; yocto@yoctoproject.org
Subject: Re: [yocto] Host authenticity failures

Is this still a problem?

From: , Christopher A 
mailto:christopher.a.thornb...@intel.com>>
Date: Wednesday, January 2, 2013 2:48 PM
To: "yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>" 
mailto:yocto@yoctoproject.org>>
Subject: [yocto] Host authenticity failures

I've started getting the following error from bitbake when it's trying to 
access my git server:

The authenticity of host '[]:([]:)' can't be 
established.
DSA key fingerprint is 

I understand this error means that the server's key has probably changed, and I 
understand in general how to deal with this via SSH config. When I manually 
ssh'd to the server the first time after receiving the error, I got the same 
message, as expected. I entered "yes" and tried again to verify that the error 
went away. It did. I think ran bitbake again and got the same error. I changed 
my ~/.ssh/ssh_config file to disable StrictHostKeyChecking and still get the 
error.

Is bitbake somehow using different known_hosts and ssh_config files from the 
ones I use for interactive logins? Other ideas on how to resolve this?

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

[yocto] Enabling shared state mirrors

[Thornburg, Christopher A]

Struggling to get shared state mirrors to work. I can see files with the same 
file name (and therefore the same hash) in my mirror and, after a build, in my 
local sstate cache direcotry. Ala:
/storage/yocto-cache/sstate-toolchain/Ubuntu-10.04/95/sstate-bzip2-native-i686-linux-1.0.6-r5-i686-2-95b6058a3f3f35386c8593e8447c59da_populate-lic.tgz.siginfo
and
/sstate-cache/Ubuntu-10.04/95/sstate-bzip2-native-i686-linux-1.0.6-r5-i686-2-95b6058a3f3f35386c8593e8447c59da_populate-lic.tgz.siginfo

bitbake-diffsigs confirms that the signatures match. I have the following in my 
local.conf:
SSTATE_MIRRORS ?= "\
file://.* file:///storage/yocto-cache/sstate-toolchain/PATH \
file://.* 
file:///storage/yocto-cache/sstate-kernel/PATH"

...and yet bitbake insists on rebuilding everything every time. I had this 
working yesterday, and today it fails again.

Any suggestions?

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

[linux-yocto] a new kernel repo branch for emgd 1.16 driver

[Kamble, Nitin A]

Hi Bruce,
 I have created a branch for emgd-1.16 kernel driver for the v3.4 kernel repo 
over here.
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=nitin/emgd-1.16

It consists of mainly following 2 commits on top of the standard/base branch.

Can you pull this branch in the v3.4 YP kernel repository so that BSPs can 
start using
emgd 1.16 driver for graphics?

Thanks,
Nitin

commit 39fa5392e05b98a1bd107a5c77f06679adc917e6
Author: Nitin A Kamble 
Date:   Fri Jan 18 21:02:20 2013 -0800

emgd: enable building within the kernel sources

Modify the build mechanism so that emgd can be configured and built
as a feature of the kernel.

Signed-off-by: Nitin A Kamble 

commit 99ae3010eeb048bd6fd63b554e2e3c6fddd80afa
Author: Nitin A Kamble 
Date:   Fri Jan 18 19:51:03 2013 -0800

emgd: add emgd 1.16 driver sources

This is starting-point code that subsequent patches will modify.  This is
a virgin copy of the code from the emgd 1.16 driver.

This code is coming from
 IEMGD_HEAD_Linux/common/drm/emgd_drm.tgz
which is a piece from the 'Linux Tar Ball' release of EMGD 1.16 downloaded
from here:
 https://edc.intel.com/App_Shared/Downloads/LIN_IEMGD_1_16_GOLD_3228.tgz

Signed-off-by: Nitin A Kamble 
___
linux-yocto mailing list
linux-yo...@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

[linux-yocto] [PATCH 0/1] meta: add emgd-1.16 driver support

[nitin . a . kamble]

From: Nitin A Kamble 

Here is a commit which adds an scc file for emgd-1.16 feature. It
depends on the emgd-1.16 branch in the kernel repo, for which a pull
request is already sent. 

This commit keeps the emgd-1.14 driver support in the repo intact.

Thanks,
Nitin

The following changes since commit c0b3904d60830e24b3930b0fa606a48b2758d979:

  meta: add config fragment for gma600 graphics driver (2013-01-18 23:07:15 
-0500)

are available in the git repository at:
  git://git.yoctoproject.org/linux-yocto-2.6.37-contrib nitin/meta
  
http://git.yoctoproject.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=nitin/meta

Nitin A Kamble (1):
  meta: add a kernel feature for drm-emgd-1.16 driver

 .../features/drm-emgd/drm-emgd-1.16.scc|2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)
 create mode 100644 meta/cfg/kernel-cache/features/drm-emgd/drm-emgd-1.16.scc

-- 
1.7.3.4

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

[linux-yocto] [PATCH 1/1] meta: add a kernel feature for drm-emgd-1.16 driver

[nitin . a . kamble]

From: Nitin A Kamble 

Use the newly created emgd-1.16 branch to get the emgd-1.16
kernel driver sources.

Signed-off-by: Nitin A Kamble 
---
 .../features/drm-emgd/drm-emgd-1.16.scc|2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)
 create mode 100644 meta/cfg/kernel-cache/features/drm-emgd/drm-emgd-1.16.scc

diff --git a/meta/cfg/kernel-cache/features/drm-emgd/drm-emgd-1.16.scc 
b/meta/cfg/kernel-cache/features/drm-emgd/drm-emgd-1.16.scc
new file mode 100644
index 000..8f2a167
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/drm-emgd/drm-emgd-1.16.scc
@@ -0,0 +1,2 @@
+kconf hardware drm-emgd.cfg
+git merge emgd-1.16
-- 
1.7.3.4

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

Re: [linux-yocto] [PATCH 0/1] meta: add emgd-1.16 driver support

[Kamble, Nitin A]

> -Original Message-
> From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
> Sent: Tuesday, January 22, 2013 1:04 PM
> To: Kamble, Nitin A
> Cc: linux-yo...@yoctoproject.org
> Subject: Re: [PATCH 0/1] meta: add emgd-1.16 driver support
> 
> On 13-01-22 03:38 PM, nitin.a.kam...@intel.com wrote:
> > From: Nitin A Kamble 
> >
> > Here is a commit which adds an scc file for emgd-1.16 feature. It
> > depends on the emgd-1.16 branch in the kernel repo, for which a pull
> > request is already sent.
> >
> > This commit keeps the emgd-1.14 driver support in the repo intact.
> >
> 
> merged. and pushed. SRCREV updates to follow, but you can test it locally
> before I do the updates.
> 
> Bruce


With current autorev it's ok. I am checking it here locally.
Thanks for pushing,
Nitin

> 
> > Thanks,
> > Nitin
> >
> > The following changes since commit
> c0b3904d60830e24b3930b0fa606a48b2758d979:
> >
> >meta: add config fragment for gma600 graphics driver (2013-01-18
> > 23:07:15 -0500)
> >
> > are available in the git repository at:
> >git://git.yoctoproject.org/linux-yocto-2.6.37-contrib nitin/meta
> >
> > http://git.yoctoproject.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h
> > =nitin/meta
> >
> > Nitin A Kamble (1):
> >meta: add a kernel feature for drm-emgd-1.16 driver
> >
> >   .../features/drm-emgd/drm-emgd-1.16.scc|2 ++
> >   1 files changed, 2 insertions(+), 0 deletions(-)
> >   create mode 100644
> > meta/cfg/kernel-cache/features/drm-emgd/drm-emgd-1.16.scc
> >

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

[linux-yocto] [PATCH 0/1] meta: add emgd-1.16 feature

[nitin . a . kamble]

From: Nitin A Kamble 

This is a commit picked from the v3.4 repo, to support the emgd-1.16
driver in the linux-yocto-dev repo.

Nitin

The following changes since commit 5ee0a634c97c44228c14177cb8c3088138e47f2f:

  meta: sync with yocto-3.4 config changes (2013-01-18 23:18:01 -0500)

are available in the git repository at:
  git://git.yoctoproject.org/linux-yocto-contrib nitin/meta
  http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=nitin/meta

Nitin A Kamble (1):
  meta: add a kernel feature for drm-emgd-1.16 driver

 .../features/drm-emgd/drm-emgd-1.16.scc|2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)
 create mode 100644 meta/cfg/kernel-cache/features/drm-emgd/drm-emgd-1.16.scc

-- 
1.7.3.4

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

[linux-yocto] [PATCH 1/1] meta: add a kernel feature for drm-emgd-1.16 driver

[nitin . a . kamble]

From: Nitin A Kamble 

Use the newly created emgd-1.16 branch to get the emgd-1.16
kernel driver sources.

Signed-off-by: Nitin A Kamble 
---
 .../features/drm-emgd/drm-emgd-1.16.scc|2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)
 create mode 100644 meta/cfg/kernel-cache/features/drm-emgd/drm-emgd-1.16.scc

diff --git a/meta/cfg/kernel-cache/features/drm-emgd/drm-emgd-1.16.scc 
b/meta/cfg/kernel-cache/features/drm-emgd/drm-emgd-1.16.scc
new file mode 100644
index 000..8f2a167
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/drm-emgd/drm-emgd-1.16.scc
@@ -0,0 +1,2 @@
+kconf hardware drm-emgd.cfg
+git merge emgd-1.16
-- 
1.7.3.4

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

Re: [linux-yocto] [PATCH 2/2] new feature for I/OAT DMA driver

[Kamble, Nitin A]

> -Original Message-
> From: linux-yocto-boun...@yoctoproject.org [mailto:linux-yocto-
> boun...@yoctoproject.org] On Behalf Of Tom Zanussi
> Sent: Friday, March 01, 2013 9:19 PM
> To: Development list for the linux-yocto*.git Linux kernel repositories
> Subject: Re: [linux-yocto] [PATCH 2/2] new feature for I/OAT DMA driver
> 
> On Fri, 2013-03-01 at 17:05 -0800, nitin.a.kam...@intel.com wrote:
> > From: Nitin A Kamble 
> >
> > This commit implements a new ioatdma feature by providing a config
> > fragment to enable Crystal Forest DMA/DCA (ioatdma) driver configuration
> for BSP kernels.
> >
> 
> I'm just wondering if there's any overlap or conflict with the existing dca
> feature - it seems that they at least have the CONFIG_INTEL_IOATDMA
> option in common, so wondering whether the existing dca feature could
> either use the ioatdma feature, or whether this new stuff could be using the
> dca feature instead.  I'm not too familiar with it, so can't say off the top 
> of my
> head, just pointing it out in case you missed it...
> 
> features/dca/dca.cfg:
> 
> CONFIG_INTEL_IOATDMA=m
> 
> and features/dca/dca.scc:
> 
> define KFEATURE_DESCRIPTION "Enable DCA for IOATDMA capable devices"
> define KFEATURE_COMPATIBILITY board
> 
> kconf hardware dca.cfg
> 
> include cfg/dmaengine.scc

Hi Tom,
 Good you found this overlap. This is the same feature with a different name. I 
will update my pull request
accordingly.

Nitin


> 
> 
> > Signed-off-by: Nitin A Kamble 
> > ---
> >  meta/cfg/kernel-cache/features/ioatdma/ioatdma.cfg |1 +
> >  meta/cfg/kernel-cache/features/ioatdma/ioatdma.scc |1 +
> >  2 files changed, 2 insertions(+), 0 deletions(-)  create mode 100644
> > meta/cfg/kernel-cache/features/ioatdma/ioatdma.cfg
> >  create mode 100644 meta/cfg/kernel-
> cache/features/ioatdma/ioatdma.scc
> >
> > diff --git a/meta/cfg/kernel-cache/features/ioatdma/ioatdma.cfg
> > b/meta/cfg/kernel-cache/features/ioatdma/ioatdma.cfg
> > new file mode 100644
> > index 000..b62aab2
> > --- /dev/null
> > +++ b/meta/cfg/kernel-cache/features/ioatdma/ioatdma.cfg
> > @@ -0,0 +1 @@
> > +CONFIG_INTEL_IOATDMA=y
> > diff --git a/meta/cfg/kernel-cache/features/ioatdma/ioatdma.scc
> > b/meta/cfg/kernel-cache/features/ioatdma/ioatdma.scc
> > new file mode 100644
> > index 000..f1951a6
> > --- /dev/null
> > +++ b/meta/cfg/kernel-cache/features/ioatdma/ioatdma.scc
> > @@ -0,0 +1 @@
> > +kconf hardware ioatdma.cfg
> 
> 
> ___
> linux-yocto mailing list
> linux-yo...@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/linux-yocto
___
linux-yocto mailing list
linux-yo...@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [PATCH 0/2] NTB & IOATDMA features for v3.8 kernel repo

[Kamble, Nitin A]

> -Original Message-
> From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
> Sent: Friday, March 01, 2013 9:07 PM
> To: Kamble, Nitin A
> Cc: linux-yo...@yoctoproject.org
> Subject: Re: [PATCH 0/2] NTB & IOATDMA features for v3.8 kernel repo
> 
> On 13-03-01 8:05 PM, nitin.a.kam...@intel.com wrote:
> > From: Nitin A Kamble
> >
> > Hi Bruce,
> > I have prepared commits for enabling non-transparent-bridge and
> > Crystal-Beach-DMA/DCA drivers in the kernel.
> >
> > This is needed to implement features in this bug:
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=2465
> >
> > I have created a new "ntb" git branch for the ntb feature. The branch is
> pushed here:
> >
> > http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-contrib/log/?h=n
> > itin/ntb
> >
> > As it is a new branch for kernel repo, I am not sending individual commits
> over ML.
> > You can directly fetch the ntb branch in the v3.8 repo.
> >
> > And new features for ioatdma (aka Crystal Beach DMA/DCA)&  ntb (non
> > transparent bridge) are created in the meta branch over here:
> >
> > http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-contrib/log/?h=n
> > itin/meta
> 
> Nitin,
> 
> In general this looks pretty good. I've been tracking NTB development for
> quite some time, so luckily I'm aware of the challenges working with the
> feature.
> 
> Just a few questions.
> 
> - I assume this has passed build tests ?
> 
> - Who's doing the NTB runtime testing ? I've seen this code in the past,
>   and while it builds relatively easily .. getting it tested is more
>   of a challenge.
> 
> And a request .. I realize that this wouldn't have been obvious when you
> were working on this, but that's what the mailing list review is for!
> 
> This feature in particular shouldn't be staged as a branch and merged, so just
> set it up as a .scc file (as you have it) without the patches. If you want the
> patches to be applied whenever ntb-common.scc is included, let me know
> and that's where I'll place them. I'll then merge these changes to the
> standard/base branch to make them available to all BSPs.
> 
> You are probably wondering why it shouldn't be a topic branch and merged.
> The reason comes down to the fact that it will conflict with both mainline
> development and BSP work. This is an active area of development (and
> hence bug fixing as well), so the chances of a topic branch conflicting and
> failing to merge are high. I'll need to resolve those conflicts in tree while
> stacking patches, I can't do that with a topic branch.
> 
> Features that usually get a topic branch are:
> 
>- features that are largely developed out of tree
>- features that are orthogonal to other code in the tree, and don't
>  touch many common files
>- features that may have active development, where we want to track
>  the history separately (versus patch based history) or we want to
>  track a significant amount of commits.
>- features that will update/upgrade and migrate over time.
>- "just because" :)
> 
> With that set of criteria, things like graphics drivers (emgd, or schedulers
> (EDF)) get topic branches. But other features like preempt-rt (it will always
> conflict) or lttng-1.x don't get topic branches. And that's why ntb really
> shouldn't have one either. IF we have to many topic branches, we'll end up
> with patch time merge failures of the topic branches .. which are difficult to
> resolve.
> 
> It should be a simple thing to re-order (since the content is all largely the
> same) .. and will take less time that I did typing all this up :)
> 
> Cheers,
> 
> Bruce

Hi Bruce,
   Thanks for explaining the process to me. I understand and agree with
 the reason of putting these bits in the base branch. This pull request from
me was  more of a RFC.
  I will do some more build testing with the new layout of commits. And send
 another pull for this.

Thanks,
Nitin


> 
> 
> >
> > Thanks,
> > Nitin
> >
> > The following changes since commit
> c2ed0f16fdec628242a682897d5d86df4547cf24:
> >
> >checkpoint dir: meta (2013-02-24 22:43:59 -0500)
> >
> > are available in the git repository at:
> >git://git.yoctoproject.org/linux-yocto-contrib nitin/meta
> >
> > http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=nitin/
> > meta
> >
> > Nitin A Kamble (2):
> >new feature for non-transparent-bridge driver
> >new feature for I/

Re: [linux-yocto] v3.8 kernel recipes in meta-intel

[Kamble, Nitin A]

> >
> > So the topic branch commit is present much deeper in the branch with
> different commit-id.
> > May be merging of the emgd branch resulted it. Is it issue with the
> > emgd branch rebased to an undesired point?
> 
> It shouldn't be. That commit shouldn't be present in the repository at all (it
> isn't in mine). The emgd branches are off master, same repo and can't bring
> in something like this.

Right. I think it got placed there after merge with the emgd branch done by the
kernel-tools.

> 
> So something is getting tied in a knot when the repository is fetched into the
> source dir.

I don't see any issue with the fetch. As noemgd BSPs are working as expected.

> 
> For your builds that work, do you have that commit present ?
> 

The emenlow-noemgd build sees the right HEAD commit. So the issue is definitely 
something to do
with the merge with the emgd branch.

Nitin


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

Re: [linux-yocto] v3.8 kernel recipes in meta-intel

[Kamble, Nitin A]

> -Original Message-
> From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
> Sent: Tuesday, March 05, 2013 9:50 AM
> To: Kamble, Nitin A
> Cc: linux-yo...@yoctoproject.org
> Subject: Re: v3.8 kernel recipes in meta-intel
> 
> On 13-03-05 12:35 PM, Kamble, Nitin A wrote:
> >>>
> >>> So the topic branch commit is present much deeper in the branch with
> >> different commit-id.
> >>> May be merging of the emgd branch resulted it. Is it issue with the
> >>> emgd branch rebased to an undesired point?
> >>
> >> It shouldn't be. That commit shouldn't be present in the repository
> >> at all (it isn't in mine). The emgd branches are off master, same
> >> repo and can't bring in something like this.
> >
> > Right. I think it got placed there after merge with the emgd branch
> > done by the kernel-tools.
> 
> That doesn't make sense either. The merge of the emgd branch is just the git
> merge of a locally staged branch in the linux-yocto repository.
> That commit you reference shouldn't be in the emgd branch, or any branch if
> a clean linux-yocto-3.8 tree is being used.

Right, so the kernl tools are producing unwanted state of the topic branch when
emgd branch is considered. And I guess you would know better why kernl tools 
are doing it.

Nitin


> 
> Cheers,
> 
> Bruce
> 
> >
> >>
> >> So something is getting tied in a knot when the repository is fetched
> >> into the source dir.
> >
> > I don't see any issue with the fetch. As noemgd BSPs are working as
> expected.
> >
> >>
> >> For your builds that work, do you have that commit present ?
> >>
> >
> > The emenlow-noemgd build sees the right HEAD commit. So the issue is
> > definitely something to do with the merge with the emgd branch.
> >
> > Nitin
> >
> >

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

Re: [linux-yocto] v3.8 kernel recipes in meta-intel

[Kamble, Nitin A]

> Not exactly, I must not be understanding what you are describing.
> There's no way for the kern-tools to create a commit ID. They can only work
> with what's present in the tree.
> 
> If you see the SRCREV to "foo", and validate_branches is telling you that
> "foo" isn't present in the tree at all, that's not related to the kern tools 
> at all.
> It's related to the repository that is cloned into the WORKDIR for building.
> 
> If you can make your recipes and updates public, I can try and do a build
> here.
> 

Bruce,
   I think I found the issue. The problem is the SRC_URI in the .bbappend is 
pointing to the linux-yocto-dev repo.
I guess that explains all the behavior. Thanks for looking into this. Now it 
does not look like kern tools issue.

Nitin


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

[yocto] dpatch files in Yocto tree

[Kamble, Nitin A]

I find following dpatch files in the Yocto tree. Dpatch files have a small 
shell script at the beginning of the patch.

Out of all these, all gcc patches are for all gcc-4.3.3 only, which is kind of 
outdated stuff now. And will be going out of the tree soon.

Binutils & tslib patches are in current use. Adding metadata vars likes 
upstream_status may break the dpatch format/script.

Do we care for the shell script inside the dpatch file? Is it ok to break it 
inside Yocto tree?



meta/recipes-devtools/binutils/binutils-2.21/binutils-uclibc-300-012_check_ldrunpath_length.patch
meta/recipes-devtools/binutils/binutils-2.21/binutils-uclibc-300-001_ld_makefile_patch.patch
meta/recipes-devtools/binutils/binutils-2.21/binutils-x86_64_i386_biarch.patch
meta/recipes-devtools/binutils/binutils-2.21/binutils-uclibc-300-006_better_file_error.patch
meta/recipes-devtools/gcc/gcc-4.5.1/libstdc++-pic.dpatch
meta/recipes-devtools/gcc/gcc-4.5.1/arm-unbreak-eabi-armv4t.dpatch
meta/recipes-devtools/gcc/gcc-4.5.1/gcc-ice-hack.dpatch
meta/recipes-devtools/gcc/gcc-4.5.1/pr30961.dpatch
meta/recipes-devtools/gcc/gcc-4.6.0/libstdc++-pic.dpatch
meta/recipes-devtools/gcc/gcc-4.6.0/arm-unbreak-eabi-armv4t.dpatch
meta/recipes-devtools/gcc/gcc-4.6.0/gcc-ice-hack.dpatch
meta/recipes-devtools/gcc/gcc-4.6.0/pr30961.dpatch
meta/recipes-devtools/gcc/gcc-4.3.3/300-libstdc++-pic.patch
meta/recipes-devtools/gcc/gcc-4.3.3/debian/libstdc++-pic.dpatch
meta/recipes-devtools/gcc/gcc-4.3.3/debian/arm-unbreak-eabi-armv4t.dpatch
meta/recipes-devtools/gcc/gcc-4.3.3/debian/gcc-ice-hack.dpatch
meta/recipes-devtools/gcc/gcc-4.3.3/debian/pr30961.dpatch
meta/recipes-graphics/tslib/tslib/32bitBE-support.patch

Thanks,
Nitin

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

[yocto] [PATCH 0/1] add a btrfs feature in linux-yocto-3.0

[nitin . a . kamble]

From: Nitin A Kamble 

The following changes since commit 3c9ebeed2598b74798a0c9247ef7c385e0cd96a7:

  meta: re-enable utrace feature for linux-yocto (2011-09-05 15:40:08 -0400)

are available in the git repository at:
  git://git.yoctoproject.org/linux-yocto-2.6.37-contrib 
nitin/linux-yocto-3.0/meta
  
http://git.yoctoproject.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=nitin/linux-yocto-3.0/meta

Nitin A Kamble (1):
  btrfs: Add a new kernel feature to enable the btrfs support

 meta/cfg/kernel-cache/features/btrfs/btrfs.cfg |1 +
 meta/cfg/kernel-cache/features/btrfs/btrfs.scc |1 +
 2 files changed, 2 insertions(+), 0 deletions(-)
 create mode 100644 meta/cfg/kernel-cache/features/btrfs/btrfs.cfg
 create mode 100644 meta/cfg/kernel-cache/features/btrfs/btrfs.scc

-- 
1.7.4.4

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

[yocto] [PATCH 1/1] btrfs: Add a new kernel feature to enable the btrfs support

[nitin . a . kamble]

From: Nitin A Kamble 

Signed-off-by: Nitin A Kamble 
---
 meta/cfg/kernel-cache/features/btrfs/btrfs.cfg |1 +
 meta/cfg/kernel-cache/features/btrfs/btrfs.scc |1 +
 2 files changed, 2 insertions(+), 0 deletions(-)
 create mode 100644 meta/cfg/kernel-cache/features/btrfs/btrfs.cfg
 create mode 100644 meta/cfg/kernel-cache/features/btrfs/btrfs.scc

diff --git a/meta/cfg/kernel-cache/features/btrfs/btrfs.cfg 
b/meta/cfg/kernel-cache/features/btrfs/btrfs.cfg
new file mode 100644
index 000..605c183
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/btrfs/btrfs.cfg
@@ -0,0 +1 @@
+CONFIG_BTRFS_FS=y
diff --git a/meta/cfg/kernel-cache/features/btrfs/btrfs.scc 
b/meta/cfg/kernel-cache/features/btrfs/btrfs.scc
new file mode 100644
index 000..cf18a2e
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/btrfs/btrfs.scc
@@ -0,0 +1 @@
+kconf non-hardware btrfs.cfg
-- 
1.7.4.4

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

Re: [yocto] [PATCH 1/1] btrfs: Add a new kernel feature to enable the btrfs support

[Kamble, Nitin A]

Thanks Bruce,
  BTW we should enable this btrfs feature for linux-yocto-3 kernel. What is the 
right way to do it? Shall I send a patch for the Linux-yocot-3.0 recipe in the 
oe-core repository?

Thanks,
Nitin


> -Original Message-
> From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
> Sent: Tuesday, September 06, 2011 1:30 PM
> To: Kamble, Nitin A
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] [PATCH 1/1] btrfs: Add a new kernel feature to
> enable the btrfs support
> 
> On 11-09-06 03:56 PM, nitin.a.kam...@intel.com wrote:
> > From: Nitin A Kamble
> 
> Looks good. If we are merging this as config only, I've been
> putting them in meta/cfg/kernel-cache/cfg/
> 
> So I relocated this configuration to that directory. I'll have
> it pushed out in the next day or so (I'm getting on a plane
> shortly).
> 
> Bruce
> 
> >
> > Signed-off-by: Nitin A Kamble
> > ---
> >   meta/cfg/kernel-cache/features/btrfs/btrfs.cfg |1 +
> >   meta/cfg/kernel-cache/features/btrfs/btrfs.scc |1 +
> >   2 files changed, 2 insertions(+), 0 deletions(-)
> >   create mode 100644 meta/cfg/kernel-cache/features/btrfs/btrfs.cfg
> >   create mode 100644 meta/cfg/kernel-cache/features/btrfs/btrfs.scc
> >
> > diff --git a/meta/cfg/kernel-cache/features/btrfs/btrfs.cfg
> b/meta/cfg/kernel-cache/features/btrfs/btrfs.cfg
> > new file mode 100644
> > index 000..605c183
> > --- /dev/null
> > +++ b/meta/cfg/kernel-cache/features/btrfs/btrfs.cfg
> > @@ -0,0 +1 @@
> > +CONFIG_BTRFS_FS=y
> > diff --git a/meta/cfg/kernel-cache/features/btrfs/btrfs.scc
> b/meta/cfg/kernel-cache/features/btrfs/btrfs.scc
> > new file mode 100644
> > index 000..cf18a2e
> > --- /dev/null
> > +++ b/meta/cfg/kernel-cache/features/btrfs/btrfs.scc
> > @@ -0,0 +1 @@
> > +kconf non-hardware btrfs.cfg

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

Re: [yocto] [PATCH 1/1] btrfs: Add a new kernel feature to enable the btrfs support

[Kamble, Nitin A]

Hi Bruce, 
  I am seeing that the patch is still not part of the Linux-yocto-3.0 
repository. Is there any reason it is being hold?

Thanks,
Nitin


> -Original Message-
> From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
> Sent: Tuesday, September 06, 2011 1:30 PM
> To: Kamble, Nitin A
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] [PATCH 1/1] btrfs: Add a new kernel feature to
> enable the btrfs support
> 
> On 11-09-06 03:56 PM, nitin.a.kam...@intel.com wrote:
> > From: Nitin A Kamble
> 
> Looks good. If we are merging this as config only, I've been
> putting them in meta/cfg/kernel-cache/cfg/
> 
> So I relocated this configuration to that directory. I'll have
> it pushed out in the next day or so (I'm getting on a plane
> shortly).
> 
> Bruce
> 
> >
> > Signed-off-by: Nitin A Kamble
> > ---
> >   meta/cfg/kernel-cache/features/btrfs/btrfs.cfg |1 +
> >   meta/cfg/kernel-cache/features/btrfs/btrfs.scc |1 +
> >   2 files changed, 2 insertions(+), 0 deletions(-)
> >   create mode 100644 meta/cfg/kernel-cache/features/btrfs/btrfs.cfg
> >   create mode 100644 meta/cfg/kernel-cache/features/btrfs/btrfs.scc
> >
> > diff --git a/meta/cfg/kernel-cache/features/btrfs/btrfs.cfg
> b/meta/cfg/kernel-cache/features/btrfs/btrfs.cfg
> > new file mode 100644
> > index 000..605c183
> > --- /dev/null
> > +++ b/meta/cfg/kernel-cache/features/btrfs/btrfs.cfg
> > @@ -0,0 +1 @@
> > +CONFIG_BTRFS_FS=y
> > diff --git a/meta/cfg/kernel-cache/features/btrfs/btrfs.scc
> b/meta/cfg/kernel-cache/features/btrfs/btrfs.scc
> > new file mode 100644
> > index 000..cf18a2e
> > --- /dev/null
> > +++ b/meta/cfg/kernel-cache/features/btrfs/btrfs.scc
> > @@ -0,0 +1 @@
> > +kconf non-hardware btrfs.cfg

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

Re: [yocto] [PATCH 1/1] btrfs: Add a new kernel feature to enable the btrfs support

[Kamble, Nitin A]

Yes, I found it. Thank you !
Nitin


> -Original Message-
> From: Ashfield, Bruce [mailto:bruce.ashfi...@windriver.com]
> Sent: Tuesday, September 13, 2011 1:18 PM
> To: Kamble, Nitin A
> Cc: 'yocto@yoctoproject.org'
> Subject: Re: [yocto] [PATCH 1/1] btrfs: Add a new kernel feature to
> enable the btrfs support
> 
> It's there. Have a look in the cfg Sabourin
> 
> Bruce
> 
> - Original Message -
> From: Kamble, Nitin A [mailto:nitin.a.kam...@intel.com]
> Sent: Tuesday, September 13, 2011 01:16 PM
> To: Ashfield, Bruce
> Cc: yocto@yoctoproject.org 
> Subject: RE: [yocto] [PATCH 1/1] btrfs: Add a new kernel feature to
> enable thebtrfs support
> 
> Hi Bruce,
>   I am seeing that the patch is still not part of the Linux-yocto-3.0
> repository. Is there any reason it is being hold?
> 
> Thanks,
> Nitin
> 
> 
> > -Original Message-
> > From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
> > Sent: Tuesday, September 06, 2011 1:30 PM
> > To: Kamble, Nitin A
> > Cc: yocto@yoctoproject.org
> > Subject: Re: [yocto] [PATCH 1/1] btrfs: Add a new kernel feature to
> > enable the btrfs support
> >
> > On 11-09-06 03:56 PM, nitin.a.kam...@intel.com wrote:
> > > From: Nitin A Kamble
> >
> > Looks good. If we are merging this as config only, I've been
> > putting them in meta/cfg/kernel-cache/cfg/
> >
> > So I relocated this configuration to that directory. I'll have
> > it pushed out in the next day or so (I'm getting on a plane
> > shortly).
> >
> > Bruce
> >
> > >
> > > Signed-off-by: Nitin A Kamble
> > > ---
> > >   meta/cfg/kernel-cache/features/btrfs/btrfs.cfg |1 +
> > >   meta/cfg/kernel-cache/features/btrfs/btrfs.scc |1 +
> > >   2 files changed, 2 insertions(+), 0 deletions(-)
> > >   create mode 100644 meta/cfg/kernel-cache/features/btrfs/btrfs.cfg
> > >   create mode 100644 meta/cfg/kernel-cache/features/btrfs/btrfs.scc
> > >
> > > diff --git a/meta/cfg/kernel-cache/features/btrfs/btrfs.cfg
> > b/meta/cfg/kernel-cache/features/btrfs/btrfs.cfg
> > > new file mode 100644
> > > index 000..605c183
> > > --- /dev/null
> > > +++ b/meta/cfg/kernel-cache/features/btrfs/btrfs.cfg
> > > @@ -0,0 +1 @@
> > > +CONFIG_BTRFS_FS=y
> > > diff --git a/meta/cfg/kernel-cache/features/btrfs/btrfs.scc
> > b/meta/cfg/kernel-cache/features/btrfs/btrfs.scc
> > > new file mode 100644
> > > index 000..cf18a2e
> > > --- /dev/null
> > > +++ b/meta/cfg/kernel-cache/features/btrfs/btrfs.scc
> > > @@ -0,0 +1 @@
> > > +kconf non-hardware btrfs.cfg

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

[yocto] [bernard 0/1] fix for bernard

[nitin . a . kamble]

From: Nitin A Kamble 

This commit fixes the binutils build issue on a perticular suse host.

Thanks,
Nitin

The following changes since commit 4f5622fb01bef25b121f293533cbfdd0067329ae:

  poky.conf: DISTRO bump (2011-12-19 14:35:40 -0800)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib nitin/bugfix
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/bugfix

Nitin Kamble (1):
  binutils-2.21: fix building on suse 11.4

 .../binutils/binutils-cross-canadian_2.21.bb   |2 +-
 .../binutils/binutils-crosssdk_2.21.bb |2 +-
 meta/recipes-devtools/binutils/binutils.inc|2 +-
 meta/recipes-devtools/binutils/binutils_2.21.bb|2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

-- 
1.7.6.4

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

[yocto] [bernard 1/1] binutils-2.21: fix building on suse 11.4

[nitin . a . kamble]

From: Nitin Kamble 

x86_64 opensuse 11.4 has bintuils version 2.21, and when this
binutils_2.21 recipe is built for x86_64 target then, the invocation
of distro gcc fails with errors like this:

| /usr/lib64/gcc/x86_64-suse-linux/4.5/../../../../x86_64-suse-linux/bin/as: 
symbol lookup error: 
/usr/lib64/gcc/x86_64-suse-linux/4.5/../../../../x86_64-suse-linux/bin/as: 
undefined symbol: concat
| make[2]: *** [sysinfo.o] Error 1

The issue rootcaused as incompatible LD_LIBRARY_PATH while running the distro 
gcc.

This commit fixes the issue by clearing the LD_LIBRARY_PATH for distro gcc 
(CC_FOR_BUILD)

This Fixes bug: [YOCTO #1833]

Signed-off-by: Nitin A Kamble 
---
 .../binutils/binutils-cross-canadian_2.21.bb   |2 +-
 .../binutils/binutils-crosssdk_2.21.bb |2 +-
 meta/recipes-devtools/binutils/binutils.inc|2 +-
 meta/recipes-devtools/binutils/binutils_2.21.bb|2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/recipes-devtools/binutils/binutils-cross-canadian_2.21.bb 
b/meta/recipes-devtools/binutils/binutils-cross-canadian_2.21.bb
index 7dad2a6..e91e7dc 100644
--- a/meta/recipes-devtools/binutils/binutils-cross-canadian_2.21.bb
+++ b/meta/recipes-devtools/binutils/binutils-cross-canadian_2.21.bb
@@ -1,3 +1,3 @@
 require binutils_${PV}.bb
 require binutils-cross-canadian.inc
-PR = "r0"
+PR = "r1"
diff --git a/meta/recipes-devtools/binutils/binutils-crosssdk_2.21.bb 
b/meta/recipes-devtools/binutils/binutils-crosssdk_2.21.bb
index 0d6efff..21289cd 100644
--- a/meta/recipes-devtools/binutils/binutils-crosssdk_2.21.bb
+++ b/meta/recipes-devtools/binutils/binutils-crosssdk_2.21.bb
@@ -4,7 +4,7 @@ inherit crosssdk
 
 PROVIDES = "virtual/${TARGET_PREFIX}binutils-crosssdk"
 
-PR = "r0"
+PR = "r1"
 
 do_configure_prepend () {
sed -i 's#/usr/local/lib /lib /usr/lib#${SDKPATHNATIVE}/lib 
${SDKPATHNATIVE}/usr/lib /usr/local/lib /lib /usr/lib#' ${S}/ld/configure.tgt
diff --git a/meta/recipes-devtools/binutils/binutils.inc 
b/meta/recipes-devtools/binutils/binutils.inc
index d9e859e..1178e0c 100644
--- a/meta/recipes-devtools/binutils/binutils.inc
+++ b/meta/recipes-devtools/binutils/binutils.inc
@@ -71,7 +71,7 @@ export RANLIB_FOR_TARGET = "${TARGET_PREFIX}ranlib"
 export CC_FOR_HOST = "${CCACHE}${HOST_PREFIX}gcc ${HOST_CC_ARCH}"
 export CXX_FOR_HOST = "${CCACHE}${HOST_PREFIX}gcc ${HOST_CC_ARCH}"
 
-export CC_FOR_BUILD = "${BUILD_CC}"
+export CC_FOR_BUILD = "LD_LIBRARY_PATH= ${BUILD_CC}"
 export CPP_FOR_BUILD = "${BUILD_CPP}"
 export CFLAGS_FOR_BUILD = "${BUILD_CFLAGS}"
 
diff --git a/meta/recipes-devtools/binutils/binutils_2.21.bb 
b/meta/recipes-devtools/binutils/binutils_2.21.bb
index 270c720..f34b69d 100644
--- a/meta/recipes-devtools/binutils/binutils_2.21.bb
+++ b/meta/recipes-devtools/binutils/binutils_2.21.bb
@@ -1,6 +1,6 @@
 require binutils.inc
 
-PR = "r0"
+PR = "r1"
 
 LIC_FILES_CHKSUM="\
 file://src-release;endline=17;md5=4830a9ef968f3b18dd5e9f2c00db2d35\
-- 
1.7.6.4

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

Re: [yocto] [bernard 1/1] binutils-2.21: fix building on suse 11.4

[Kamble, Nitin A]

> -Original Message-
> From: Martin Jansa [mailto:martin.ja...@gmail.com]
> Sent: Tuesday, December 20, 2011 11:56 PM
> To: Kamble, Nitin A
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] [bernard 1/1] binutils-2.21: fix building on suse
> 11.4
> 
> On Tue, Dec 20, 2011 at 11:37:03PM -0800, nitin.a.kam...@intel.com
> wrote:
> > From: Nitin Kamble 
> >
> > x86_64 opensuse 11.4 has bintuils version 2.21, and when this
> > binutils_2.21 recipe is built for x86_64 target then, the invocation
> > of distro gcc fails with errors like this:
> >
> > | /usr/lib64/gcc/x86_64-suse-linux/4.5/../../../../x86_64-suse-
> linux/b
> > | in/as: symbol lookup error:
> > | /usr/lib64/gcc/x86_64-suse-linux/4.5/../../../../x86_64-suse-
> linux/b
> > | in/as: undefined symbol: concat
> > | make[2]: *** [sysinfo.o] Error 1
> >
> > The issue rootcaused as incompatible LD_LIBRARY_PATH while running
> the distro gcc.
> >
> > This commit fixes the issue by clearing the LD_LIBRARY_PATH for
> distro
> > gcc (CC_FOR_BUILD)
> >
> > This Fixes bug: [YOCTO #1833]
> 
> FWIW: I see the same issue with binutils-2.22 and oe-core master when
> building qemux86-64 on gentoo.
> 
Good to know, the same fix should fix the binutils-2.22 build on gentoo. Can 
you please test and report?

Thanks,
Nitin

> > Signed-off-by: Nitin A Kamble 
> > ---
> >  .../binutils/binutils-cross-canadian_2.21.bb   |2 +-
> >  .../binutils/binutils-crosssdk_2.21.bb |2 +-
> >  meta/recipes-devtools/binutils/binutils.inc|2 +-
> >  meta/recipes-devtools/binutils/binutils_2.21.bb|2 +-
> >  4 files changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git
> > a/meta/recipes-devtools/binutils/binutils-cross-canadian_2.21.bb
> > b/meta/recipes-devtools/binutils/binutils-cross-canadian_2.21.bb
> > index 7dad2a6..e91e7dc 100644
> > --- a/meta/recipes-devtools/binutils/binutils-cross-canadian_2.21.bb
> > +++ b/meta/recipes-devtools/binutils/binutils-cross-canadian_2.21.bb
> > @@ -1,3 +1,3 @@
> >  require binutils_${PV}.bb
> >  require binutils-cross-canadian.inc
> > -PR = "r0"
> > +PR = "r1"
> > diff --git a/meta/recipes-devtools/binutils/binutils-crosssdk_2.21.bb
> > b/meta/recipes-devtools/binutils/binutils-crosssdk_2.21.bb
> > index 0d6efff..21289cd 100644
> > --- a/meta/recipes-devtools/binutils/binutils-crosssdk_2.21.bb
> > +++ b/meta/recipes-devtools/binutils/binutils-crosssdk_2.21.bb
> > @@ -4,7 +4,7 @@ inherit crosssdk
> >
> >  PROVIDES = "virtual/${TARGET_PREFIX}binutils-crosssdk"
> >
> > -PR = "r0"
> > +PR = "r1"
> >
> >  do_configure_prepend () {
> > sed -i 's#/usr/local/lib /lib /usr/lib#${SDKPATHNATIVE}/lib
> > ${SDKPATHNATIVE}/usr/lib /usr/local/lib /lib /usr/lib#'
> > ${S}/ld/configure.tgt diff --git
> > a/meta/recipes-devtools/binutils/binutils.inc
> > b/meta/recipes-devtools/binutils/binutils.inc
> > index d9e859e..1178e0c 100644
> > --- a/meta/recipes-devtools/binutils/binutils.inc
> > +++ b/meta/recipes-devtools/binutils/binutils.inc
> > @@ -71,7 +71,7 @@ export RANLIB_FOR_TARGET = "${TARGET_PREFIX}ranlib"
> >  export CC_FOR_HOST = "${CCACHE}${HOST_PREFIX}gcc ${HOST_CC_ARCH}"
> >  export CXX_FOR_HOST = "${CCACHE}${HOST_PREFIX}gcc ${HOST_CC_ARCH}"
> >
> > -export CC_FOR_BUILD = "${BUILD_CC}"
> > +export CC_FOR_BUILD = "LD_LIBRARY_PATH= ${BUILD_CC}"
> >  export CPP_FOR_BUILD = "${BUILD_CPP}"
> >  export CFLAGS_FOR_BUILD = "${BUILD_CFLAGS}"
> >
> > diff --git a/meta/recipes-devtools/binutils/binutils_2.21.bb
> > b/meta/recipes-devtools/binutils/binutils_2.21.bb
> > index 270c720..f34b69d 100644
> > --- a/meta/recipes-devtools/binutils/binutils_2.21.bb
> > +++ b/meta/recipes-devtools/binutils/binutils_2.21.bb
> > @@ -1,6 +1,6 @@
> >  require binutils.inc
> >
> > -PR = "r0"
> > +PR = "r1"
> >
> >  LIC_FILES_CHKSUM="\
> >
> > file://src-release;endline=17;md5=4830a9ef968f3b18dd5e9f2c00db2d35\
> > --
> > 1.7.6.4
> >
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> 
> --
> Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] qemu EFI build failure

[Kamble, Nitin A]

I just sent a patch to oecore mailing list to fix the grub issue with automake 
1.11.2.

Thanks,
Nitin


> -Original Message-
> From: Hart, Darren
> Sent: Thursday, January 12, 2012 1:39 PM
> To: Bodke, Kishore K
> Cc: Ahmad, Josef; yocto@yoctoproject.org; Kamble, Nitin A
> Subject: Re: [yocto] qemu EFI build failure
> 
> On 01/12/2012 01:28 PM, Bodke, Kishore K wrote:
> > I have only
> > MACHINE_FEATURES += "efi"
> > KERNEL_FEATURES_append_cedartrail += "cfg/efi-ext.scc".
> >
> > I am not having IMAGE_FSTYPES += "live".
> 
> The "live" change is just to trigger the live image type which builds
> grub-efi-native for efi systems. qemux86 needs this added explicitly.
> 
> --
> Darren
> 
> >
> > Thanks
> > Kishore.
> > -Original Message-
> > From: Hart, Darren
> > Sent: Thursday, January 12, 2012 1:20 PM
> > To: Ahmad, Josef
> > Cc: yocto@yoctoproject.org; Bodke, Kishore K; Kamble, Nitin A
> > Subject: Re: [yocto] qemu EFI build failure
> >
> > On 01/12/2012 10:27 AM, Darren Hart wrote:
> >>
> >>
> >> On 01/12/2012 08:19 AM, Josef Ahmad wrote:
> >>> I tried to build a qemux86 EFI image, by setting:
> >>> - in my local.conf: IMAGE_FSTYPES += "live"
> >>> - in poly/meta/conf/machine/qemux86.conf: MACHINE_FEATURES += "efi"
> >>>
> >>
> >> I haven't tried live images with QEMU. For one thing, they aren't
> really
> >> necessary as you can specify all the boot parameters on the qemu
> command
> >> line. Is there are reason you want to use the live image
> specifically?
> >>
> >> Also, in order to properly test EFI in QEMU, you will need to use an
> EFI
> >> BIOS - I believe you're aware of this already - but this isn't
> currently
> >> supported by the runqemu scripts that ship with yocto.
> >>
> >>> The build gave me the following error:
> >>
> >>
> >> I'll do some test builds - it isn't clear to me what is going on
> here.
> >>
> >> 
> >>
> >>>
> >>>
> >>> Has anyone encountered the same error?  I'm not sure I set up the
> >>> correct configuration. Also, is there another way to append "efi"
> to
> >>> MACHINE_FEATURES rather than by modifying qemux86.conf?
> >>
> >> You should be able to do something like:
> >> MACHINE_FEATURES_append_qemux86 = "efi"
> >>
> >> Note that you will also need to enable the efi support in the
> kernel,
> >> which is done with the KERNEL_FEATURES variable, something like:
> >> KERNEL_FEATURES_append_qemux86 = "conf/efi-ext.scc"
> >>
> >> Either of these can be set in your local.conf.
> >>
> >
> > More accurately:
> >
> > MACHINE_FEATURES_append_qemux86=" efi pcbios"
> > KERNEL_FEATURES_append_qemux86=" cfg/efi-ext.scc"
> > IMAGE_FSTYPES += "live"
> >
> > With these added to local.conf and building for qemux86 I see the
> same
> > configure failures reported by Kishore and Josef:
> >
> > | ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded
> from...
> > | acinclude.m4:363: grub_CHECK_STACK_ARG_PROBE is expanded from...
> >
> > I've discussed in IRC with Nitin and he thinks this may be related to
> > the automake update and is looking into it.
> >
> 
> 
> --
> Darren Hart
> Intel Open Source Technology Center
> Yocto Project - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] qemu EFI build failure

[Kamble, Nitin A]

Here is the commit: 
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=nitin/misc

Nitin

> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Kamble, Nitin A
> Sent: Thursday, January 12, 2012 2:32 PM
> To: Hart, Darren; Bodke, Kishore K
> Cc: Ahmad, Josef; yocto@yoctoproject.org
> Subject: Re: [yocto] qemu EFI build failure
> 
> 
> I just sent a patch to oecore mailing list to fix the grub issue with
> automake 1.11.2.
> 
> Thanks,
> Nitin
> 
> 
> > -Original Message-
> > From: Hart, Darren
> > Sent: Thursday, January 12, 2012 1:39 PM
> > To: Bodke, Kishore K
> > Cc: Ahmad, Josef; yocto@yoctoproject.org; Kamble, Nitin A
> > Subject: Re: [yocto] qemu EFI build failure
> >
> > On 01/12/2012 01:28 PM, Bodke, Kishore K wrote:
> > > I have only
> > > MACHINE_FEATURES += "efi"
> > > KERNEL_FEATURES_append_cedartrail += "cfg/efi-ext.scc".
> > >
> > > I am not having IMAGE_FSTYPES += "live".
> >
> > The "live" change is just to trigger the live image type which builds
> > grub-efi-native for efi systems. qemux86 needs this added explicitly.
> >
> > --
> > Darren
> >
> > >
> > > Thanks
> > > Kishore.
> > > -Original Message-
> > > From: Hart, Darren
> > > Sent: Thursday, January 12, 2012 1:20 PM
> > > To: Ahmad, Josef
> > > Cc: yocto@yoctoproject.org; Bodke, Kishore K; Kamble, Nitin A
> > > Subject: Re: [yocto] qemu EFI build failure
> > >
> > > On 01/12/2012 10:27 AM, Darren Hart wrote:
> > >>
> > >>
> > >> On 01/12/2012 08:19 AM, Josef Ahmad wrote:
> > >>> I tried to build a qemux86 EFI image, by setting:
> > >>> - in my local.conf: IMAGE_FSTYPES += "live"
> > >>> - in poly/meta/conf/machine/qemux86.conf: MACHINE_FEATURES +=
> "efi"
> > >>>
> > >>
> > >> I haven't tried live images with QEMU. For one thing, they aren't
> > really
> > >> necessary as you can specify all the boot parameters on the qemu
> > command
> > >> line. Is there are reason you want to use the live image
> > specifically?
> > >>
> > >> Also, in order to properly test EFI in QEMU, you will need to use
> an
> > EFI
> > >> BIOS - I believe you're aware of this already - but this isn't
> > currently
> > >> supported by the runqemu scripts that ship with yocto.
> > >>
> > >>> The build gave me the following error:
> > >>
> > >>
> > >> I'll do some test builds - it isn't clear to me what is going on
> > here.
> > >>
> > >> 
> > >>
> > >>>
> > >>>
> > >>> Has anyone encountered the same error?  I'm not sure I set up the
> > >>> correct configuration. Also, is there another way to append "efi"
> > to
> > >>> MACHINE_FEATURES rather than by modifying qemux86.conf?
> > >>
> > >> You should be able to do something like:
> > >> MACHINE_FEATURES_append_qemux86 = "efi"
> > >>
> > >> Note that you will also need to enable the efi support in the
> > kernel,
> > >> which is done with the KERNEL_FEATURES variable, something like:
> > >> KERNEL_FEATURES_append_qemux86 = "conf/efi-ext.scc"
> > >>
> > >> Either of these can be set in your local.conf.
> > >>
> > >
> > > More accurately:
> > >
> > > MACHINE_FEATURES_append_qemux86=" efi pcbios"
> > > KERNEL_FEATURES_append_qemux86=" cfg/efi-ext.scc"
> > > IMAGE_FSTYPES += "live"
> > >
> > > With these added to local.conf and building for qemux86 I see the
> > same
> > > configure failures reported by Kishore and Josef:
> > >
> > > | ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded
> > from...
> > > | acinclude.m4:363: grub_CHECK_STACK_ARG_PROBE is expanded from...
> > >
> > > I've discussed in IRC with Nitin and he thinks this may be related
> to
> > > the automake update and is looking into it.
> > >
> >
> >
> > --
> > Darren Hart
> > Intel Open Source Technology Center
> > Yocto Project - Linux Kernel
> ___
> 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] qemu EFI build failure

[Kamble, Nitin A]

Darren,
  I have reworked the commits to fix issues while building on other distros.
Can you check this branch 
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=nitin/grub-efi
It is working for me on Fedora 14, for which the other grub-efi commit was 
failing for me.

Thanks,
Nitin


> -Original Message-
> From: Kamble, Nitin A
> Sent: Thursday, January 12, 2012 2:33 PM
> To: Kamble, Nitin A; Hart, Darren; Bodke, Kishore K
> Cc: Ahmad, Josef; yocto@yoctoproject.org
> Subject: RE: [yocto] qemu EFI build failure
> 
> Here is the commit: http://git.yoctoproject.org/cgit.cgi/poky-
> contrib/log/?h=nitin/misc
> 
> Nitin
> 
> > -Original Message-
> > From: yocto-boun...@yoctoproject.org [mailto:yocto-
> > boun...@yoctoproject.org] On Behalf Of Kamble, Nitin A
> > Sent: Thursday, January 12, 2012 2:32 PM
> > To: Hart, Darren; Bodke, Kishore K
> > Cc: Ahmad, Josef; yocto@yoctoproject.org
> > Subject: Re: [yocto] qemu EFI build failure
> >
> >
> > I just sent a patch to oecore mailing list to fix the grub issue with
> > automake 1.11.2.
> >
> > Thanks,
> > Nitin
> >
> >
> > > -Original Message-
> > > From: Hart, Darren
> > > Sent: Thursday, January 12, 2012 1:39 PM
> > > To: Bodke, Kishore K
> > > Cc: Ahmad, Josef; yocto@yoctoproject.org; Kamble, Nitin A
> > > Subject: Re: [yocto] qemu EFI build failure
> > >
> > > On 01/12/2012 01:28 PM, Bodke, Kishore K wrote:
> > > > I have only
> > > > MACHINE_FEATURES += "efi"
> > > > KERNEL_FEATURES_append_cedartrail += "cfg/efi-ext.scc".
> > > >
> > > > I am not having IMAGE_FSTYPES += "live".
> > >
> > > The "live" change is just to trigger the live image type which
> builds
> > > grub-efi-native for efi systems. qemux86 needs this added
> explicitly.
> > >
> > > --
> > > Darren
> > >
> > > >
> > > > Thanks
> > > > Kishore.
> > > > -Original Message-
> > > > From: Hart, Darren
> > > > Sent: Thursday, January 12, 2012 1:20 PM
> > > > To: Ahmad, Josef
> > > > Cc: yocto@yoctoproject.org; Bodke, Kishore K; Kamble, Nitin A
> > > > Subject: Re: [yocto] qemu EFI build failure
> > > >
> > > > On 01/12/2012 10:27 AM, Darren Hart wrote:
> > > >>
> > > >>
> > > >> On 01/12/2012 08:19 AM, Josef Ahmad wrote:
> > > >>> I tried to build a qemux86 EFI image, by setting:
> > > >>> - in my local.conf: IMAGE_FSTYPES += "live"
> > > >>> - in poly/meta/conf/machine/qemux86.conf: MACHINE_FEATURES +=
> > "efi"
> > > >>>
> > > >>
> > > >> I haven't tried live images with QEMU. For one thing, they
> aren't
> > > really
> > > >> necessary as you can specify all the boot parameters on the qemu
> > > command
> > > >> line. Is there are reason you want to use the live image
> > > specifically?
> > > >>
> > > >> Also, in order to properly test EFI in QEMU, you will need to
> use
> > an
> > > EFI
> > > >> BIOS - I believe you're aware of this already - but this isn't
> > > currently
> > > >> supported by the runqemu scripts that ship with yocto.
> > > >>
> > > >>> The build gave me the following error:
> > > >>
> > > >>
> > > >> I'll do some test builds - it isn't clear to me what is going on
> > > here.
> > > >>
> > > >> 
> > > >>
> > > >>>
> > > >>>
> > > >>> Has anyone encountered the same error?  I'm not sure I set up
> the
> > > >>> correct configuration. Also, is there another way to append
> "efi"
> > > to
> > > >>> MACHINE_FEATURES rather than by modifying qemux86.conf?
> > > >>
> > > >> You should be able to do something like:
> > > >> MACHINE_FEATURES_append_qemux86 = "efi"
> > > >>
> > > >> Note that you will also need to enable the efi support in the
> > > kernel,
> > > >> which is done with the KERNEL_FEATURES variable, something like:
> > > >> KERNEL_FEATURES_append_qemux86 = "conf/efi-ext.scc"
> > > >>
> > > >> Either of these can be set in your local.conf.
> > > >>
> > > >
> > > > More accurately:
> > > >
> > > > MACHINE_FEATURES_append_qemux86=" efi pcbios"
> > > > KERNEL_FEATURES_append_qemux86=" cfg/efi-ext.scc"
> > > > IMAGE_FSTYPES += "live"
> > > >
> > > > With these added to local.conf and building for qemux86 I see the
> > > same
> > > > configure failures reported by Kishore and Josef:
> > > >
> > > > | ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded
> > > from...
> > > > | acinclude.m4:363: grub_CHECK_STACK_ARG_PROBE is expanded
> from...
> > > >
> > > > I've discussed in IRC with Nitin and he thinks this may be
> related
> > to
> > > > the automake update and is looking into it.
> > > >
> > >
> > >
> > > --
> > > Darren Hart
> > > Intel Open Source Technology Center
> > > Yocto Project - Linux Kernel
> > ___
> > 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-x32: disagreement between ref manual and README.TXT

[Kamble, Nitin A]

> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Robert P. J. Day
> Sent: Sunday, March 25, 2012 9:17 AM
> To: Yocto discussion list
> Subject: [yocto] meta-x32: disagreement between ref manual and
> README.TXT
> 
> 
>   poky ref manual reads:
> 
> "As usual, use BitBake to build an image that supports the x32 psABI.
> Here is an example:
> 
>  $ bitake core-image-sato
> 
> As usual, run your image using QUEM [sic]:
> 
>  $ runqemu qemux86-64 core-image-sato"
> 
> while the README.TXT file that comes with the experimental/meta-x32
> layer reads:
> 
> "build
>   bitbake core-image-minimal-x32
> 
> 4. boot the image
>   runqemu qemux86-64 core-image-minimal-x32"
> 
>   thoughts?
> 
> rday

Hi Robert,
  It is not a significant difference. Images with -x32 in their names contain 
an additional utility named file. Which can let one check the file types of elf 
binaries. And the absence of this file utility does not affect functionality of 
x32 images.
Thanks,
Nitin

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

[yocto] yassl recipe in the yocto project

[Kamble, Nitin A]

Hi Chris,
  Here is the recipe we have in yocto-project for openssl projects to be 
incorporated into embedded Linux distributions.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-connectivity/openssl
Please visit www.yoctoproject.org for more 
information on the Yocto Project.

It would be nice to get yassl recipe also in there as an alternative to openssl.

Context for others: I came across Chris at ESC, He works for yassl .com which 
provides GPLv2  ssl solution like openssl which is smaller compared to openssl 
and targeted for embedded solutions.

Thanks,
Nitin

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

[yocto] [PATCH 0/3] Misc Fixes

[nitin . a . kamble]

From: Nitin A Kamble 

The following changes since commit 06fc2d2ec8e72f063f2c67601b2f027f76971e05:

  documentation/dev-manual/dev-manual-common-tasks.xml: Title change 
(2012-03-30 17:20:51 +0100)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib nitin/misc
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/misc

Nitin A Kamble (3):
  nasm: fix issue with repeat configure
  cross-canadian.bbclass: fix rpath for sdk executables
  poky-tiny: avoid eglibc locale packaging

 meta-yocto/conf/distro/poky-tiny.conf   |3 +++
 meta/classes/cross-canadian.bbclass |4 +++-
 meta/recipes-devtools/nasm/nasm_2.07.bb |8 
 3 files changed, 10 insertions(+), 5 deletions(-)

-- 
1.7.6.4

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

[yocto] [PATCH 1/3] nasm: fix issue with repeat configure

[nitin . a . kamble]

From: Nitin A Kamble 

This Fixes bug: [YOCTO #2176]

This fixes the following issue as mentioned in the bug:
If nasm-native has to be rebuilt (due to a signature change) it will fail:

| checking for a BSD-compatible install... /usr/bin/install -c
| /media/large/tmp/work/x86_64-linux/nasm-native-2.07-r1/nasm-2.07/configure:
line 4261: syntax error near unexpected token `-W'
| /media/large/tmp/work/x86_64-linux/nasm-native-2.07-r1/nasm-2.07/configure:
line 4261: `PA_ADD_CFLAGS(-W)'
| ERROR: oe_runconf failed
NOTE: package nasm-native-2.07-r1: task do_configure: Failed

The failure appears to be caused by do_patch_fixaclocal being run a second time

Signed-off-by: Nitin A Kamble 
---
 meta/recipes-devtools/nasm/nasm_2.07.bb |8 
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/recipes-devtools/nasm/nasm_2.07.bb 
b/meta/recipes-devtools/nasm/nasm_2.07.bb
index 9b75496..fc2d531 100644
--- a/meta/recipes-devtools/nasm/nasm_2.07.bb
+++ b/meta/recipes-devtools/nasm/nasm_2.07.bb
@@ -13,12 +13,12 @@ SRC_URI[sha256sum] = 
"ac70ee451c73d742c9ff830502e5f8b1f648b2abffa8fd00944243283b
 
 inherit autotools
 
-do_patch_fixaclocal () {
-   mv aclocal.m4 acinclude.m4
+do_configure_prepend () {
+   if [ -f aclocal.m4 ] && [ ! -f acinclude.m4 ]; then
+   mv aclocal.m4 acinclude.m4
+   fi
 }
 
-addtask do_patch_fixaclocal after do_patch before do_configure
-
 do_install() {
install -d ${D}${bindir}
install -d ${D}${mandir}/man1
-- 
1.7.6.4

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

[yocto] [PATCH 2/3] cross-canadian.bbclass: fix rpath for sdk executables

[nitin . a . kamble]

From: Nitin A Kamble 

This makes the libraries located in places like this findable:
/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/lib

Which avoids linking cross canadian sdk executables with host libraries like 
this:

$ ldd 
/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/bin/x86_64-oe-linux/x86_64-oe-linux-gdb
linux-vdso.so.1 =>  (0x7fffb7fff000)
libreadline.so.6 => 
/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/lib/x86_64-oe-linux/../libreadline.so.6
 (0x7fbfb5511000)
libdl.so.2 => 
/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/lib/libdl.so.2 
(0x7fbfb530c000)
libncurses.so.5 => 
/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/lib/libncurses.so.5 
(0x7fbfb50e9000)
libtinfo.so.5 => 
/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/lib/libtinfo.so.5 
(0x7fbfb4ec2000)
libz.so.1 => 
/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/lib/x86_64-oe-linux/../libz.so.1
 (0x7fbfb4cac000)
libm.so.6 => 
/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/lib/libm.so.6 
(0x7fbfb4a2a000)
libpthread.so.0 => 
/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/lib/libpthread.so.0 
(0x7fbfb480d000)
libutil.so.1 => 
/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/lib/libutil.so.1 
(0x7fbfb4609000)
libexpat.so.1 => 
/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/lib/x86_64-oe-linux/../libexpat.so.1
 (0x7fbfb43e)
libc.so.6 => 
/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/lib/libc.so.6 
(0x7fbfb4059000)

/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/lib/ld-linux-x86-64.so.2 
=> /lib64/ld-linux-x86-64.so.2 (0x003f0500)

Signed-off-by: Nitin A Kamble 
---
 meta/classes/cross-canadian.bbclass |4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/meta/classes/cross-canadian.bbclass 
b/meta/classes/cross-canadian.bbclass
index e187b88..4ff092c 100644
--- a/meta/classes/cross-canadian.bbclass
+++ b/meta/classes/cross-canadian.bbclass
@@ -48,7 +48,9 @@ DPKG_ARCH = "${SDK_ARCH}"
 CPPFLAGS = "${BUILDSDK_CPPFLAGS}"
 CFLAGS = "${BUILDSDK_CFLAGS}"
 CXXFLAGS = "${BUILDSDK_CFLAGS}"
-LDFLAGS = "${BUILDSDK_LDFLAGS}"
+LDFLAGS = "${BUILDSDK_LDFLAGS} \
+   -Wl,-rpath-link,${STAGING_LIBDIR}/.. \
+-Wl,-rpath,${libdir}/.. "
 
 DEPENDS_GETTEXT = "gettext-native gettext-nativesdk"
 
-- 
1.7.6.4

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

[yocto] [PATCH 3/3] poky-tiny: avoid eglibc locale packaging

[nitin . a . kamble]

From: Nitin A Kamble 

This fixes bug: [YOCTO #2089]

This avoids these errors
NOTE: package eglibc-locale-2.13-r19: task do_populate_sysroot: Started
ERROR: Error executing a python function in
/opt/poky.git/meta/recipes-core/eglibc/eglibc-locale_2.13.bb:
OSError: [Errno 2] No such file or directory:
'/home/rchatre/concordia/dev/ccd-distro-work/tmp/work/core2-poky-linux/eglibc-locale-2.13-r19/package/usr/lib/gconv'

ERROR: The stack trace of python calls that resulted in this exception/failure
was:
ERROR:   File "package_do_split_gconvs", line 264, in 
ERROR:·
ERROR:   File "package_do_split_gconvs", line 45, in package_do_split_gconvs
ERROR:·
ERROR:   File "package.bbclass", line 30, in do_split_packages
ERROR:·
ERROR: The code that was being executed was:
ERROR:  0260:»--»---bb.note("generation of binary locales disabled.
this may break i18n!")
ERROR:  0261:
ERROR:  0262:
ERROR:  0263:
ERROR:  *** 0264:package_do_split_gconvs(d)
ERROR:  0265:
ERROR: (file: 'package_do_split_gconvs', lineno: 264, function: )
ERROR:  0041:»--»---»---d.setVar('RPROVIDES_%s' % pkg,
pkg.replace(bpn, 'glibc'))
ERROR:  0042:
ERROR:  0043:»--do_split_packages(d, gconv_libdir,
file_regex='^(.*)\.so$', output_pattern=bpn+'-gconv-%s', \
ERROR:  0044:»--»---description='gconv module for character set
%s', hook=calc_gconv_deps, \
ERROR:  *** 0045:»--»---extra_depends=bpn+'-gconv')
ERROR:  0046:
ERROR:  0047:»--def calc_charmap_deps(fn, pkg, file_regex,
output_pattern, group):
ERROR:  0048:»--»---deps = []
ERROR:  0049:»--»---f = open(fn, "r")
ERROR: (file: 'package_do_split_gconvs', lineno: 45, function:
package_do_split_gconvs)
ERROR: Function failed: package_do_split_gconvs
ERROR: Logfile of failure stored in:
/home/rchatre/concordia/dev/ccd-distro-work/tmp/work/core2-poky-linux/eglibc-locale-2.13-r19/temp/log.do_package.31042
NOTE: package eglibc-locale-2.13-r19: task do_package: Failed
ERROR: Task 552 (/opt/poky.git/meta/recipes-core/eglibc/eglibc-locale_2.13.bb,
do_package) failed with exit code '1'

Signed-Off-By: Nitin A Kamble 
---
 meta-yocto/conf/distro/poky-tiny.conf |3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/meta-yocto/conf/distro/poky-tiny.conf 
b/meta-yocto/conf/distro/poky-tiny.conf
index 6fa4c90..a745338 100644
--- a/meta-yocto/conf/distro/poky-tiny.conf
+++ b/meta-yocto/conf/distro/poky-tiny.conf
@@ -74,6 +74,9 @@ DISTRO_FEATURES_LIBC = "${DISTRO_FEATURES_LIBC_TINY} \
 ${DISTRO_FEATURES_LIBC_NET} \
"
 
+# This tells libc packaging that no locales are to be packaged
+PACKAGE_NO_GCONV = "1"
+
 # Comment out any of the lines below to disable them in the build
 # DISTRO_FEATURES options:
 # alsa bluetooth ext2 irda pcmcia usbgadget usbhost wifi nfs zeroconf pci
-- 
1.7.6.4

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

Re: [yocto] [PATCH 3/3] poky-tiny: avoid eglibc locale packaging

[Kamble, Nitin A]

> -Original Message-
> From: Darren Hart [mailto:dvh...@linux.intel.com]
> 
> Thanks for looking into this Nitin! I'm fine with this fix if it gets
> things going. I wonder though, I presume omitting something from
> DISTRO_FEATURES_LIBC is what triggers this bug... could that same
> omission not be tested to avoid the failure? Seems strange to have to
> explicitly set PACKAGE_NO_GCONV.
> 
> Thoughts?

Makes sense, I will look into such solution.

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

[yocto] [PATCH 0/2] Misc bugfixes

[nitin . a . kamble]

From: Nitin A Kamble 

The following changes since commit 190f6d791d51aaa4cfb9f1cf932bc205ff674fb5:

  runqemu-internal: Add console=tty for qemuppc and NFS (2012-04-06 01:12:47 
+0100)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib nitin/bugfixes
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/bugfixes

Nitin A Kamble (2):
  tclibc-eglibc.inc: make locale packages dependency conditional
  poky-tiny.conf: adjust eglibc options for poky-tiny

 meta-yocto/conf/distro/poky-tiny.conf  |6 ++
 meta/conf/distro/include/tclibc-eglibc.inc |   23 ---
 2 files changed, 22 insertions(+), 7 deletions(-)

-- 
1.7.7

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

[yocto] [PATCH 1/2] tclibc-eglibc.inc: make locale packages dependency conditional

[nitin . a . kamble]

From: Nitin A Kamble 

Only add locale package dependencies if the eglibc is configured
with locale support.
  This avoids dependencies issues for distros such as poky-tiny

Signed-off-by: Nitin A Kamble 
---
 meta/conf/distro/include/tclibc-eglibc.inc |   23 ---
 1 files changed, 16 insertions(+), 7 deletions(-)

diff --git a/meta/conf/distro/include/tclibc-eglibc.inc 
b/meta/conf/distro/include/tclibc-eglibc.inc
index 8b8a214..aed82d1 100644
--- a/meta/conf/distro/include/tclibc-eglibc.inc
+++ b/meta/conf/distro/include/tclibc-eglibc.inc
@@ -23,10 +23,19 @@ LIBC_DEPENDENCIES = "libsegfault \
 eglibc-dev \
 eglibc-utils \
 eglibc-thread-db \
-eglibc-localedata-i18n \
-eglibc-gconv-ibm850 \
-eglibc-gconv-cp1252 \
-eglibc-gconv-iso8859-1 \
-eglibc-gconv-iso8859-15 \
-locale-base-en-us \
-locale-base-en-gb "
+${@get_libc_locales_dependencies(d)}"
+
+LIBC_LOCALE_DEPENDENCIES = "\
+   eglibc-localedata-i18n \
+   eglibc-gconv-ibm850 \
+   eglibc-gconv-cp1252 \
+   eglibc-gconv-iso8859-1 \
+   eglibc-gconv-iso8859-15 \
+   locale-base-en-us \
+   locale-base-en-gb"
+
+def get_libc_locales_dependencies(d):
+if 'libc-locales' in (d.getVar('DISTRO_FEATURES', True) or '').split() :
+return d.getVar('LIBC_LOCALE_DEPENDENCIES', True) or ''
+else:
+return ''
-- 
1.7.7

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

[yocto] [PATCH 2/2] poky-tiny.conf: adjust eglibc options for poky-tiny

[nitin . a . kamble]

From: Nitin A Kamble 

Avoid errors for building meta-toolchain for poky-tiny

This Fixes Bug: [YOCTO #2259]

Signed-off-by: Nitin A Kamble 
---
 meta-yocto/conf/distro/poky-tiny.conf |6 ++
 1 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/meta-yocto/conf/distro/poky-tiny.conf 
b/meta-yocto/conf/distro/poky-tiny.conf
index 395c6fb..58d64ec 100644
--- a/meta-yocto/conf/distro/poky-tiny.conf
+++ b/meta-yocto/conf/distro/poky-tiny.conf
@@ -63,6 +63,12 @@ ASSUME_PROVIDED += "pkgconfig$"
 # Reconfigure eglibc for a smaller installation
 # Comment out any of the lines below to disable them in the build
 DISTRO_FEATURES_LIBC_TINY = "libc-libm libc-crypt"
+# for gettext
+DISTRO_FEATURES_LIBC_TINY += "libc-posix-clang-wchar"
+# for m4
+DISTRO_FEATURES_LIBC_TINY += "libc-spawn libc-locale-code"
+# for elfutils
+DISTRO_FEATURES_LIBC_TINY += "libc-ftraverse"
 # Required for "who"
 DISTRO_FEATURES_LIBC_MINIMAL = "libc-utmp libc-getlogin"
 DISTRO_FEATURES_LIBC_REGEX = "libc-posix-regexp"
-- 
1.7.7

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

Re: [yocto] Is there a OE core based mgetty?

[Peter A. Bigot]

On 08/28/2013 03:19 PM, Brian Hutchinson wrote:
On Tue, Aug 27, 2013 at 6:56 PM, Brian Hutchinson 
mailto:b.hutch...@gmail.com>> wrote:


Hi,

I need mgetty and don't see it anywhere in any of the OE core
based layers.  Did something replace it?  I'm trying to migrate
some OE classic work to OE core based distros.

Regards,

Brian


Ping!  I'll take that as a "No" then.  :)

So  I'm working on adding this to OE Core based distros ... should 
it go in meta/recipes-connectivity? The ppp stuff is in 
meta/recipes-connectivity so I'm thinking that's where it belongs???


FWIW, linux-utils provides agetty; busybox also has a getty (was in 
tinylogin in earlier versions, but should be in busybox now).  Dunno if 
those would meet your needs.


Peter

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

[linux-yocto] [Patch v2 1/1] common-pc-wifi.cfg: add support for broadcom wifi drivers

[nitin . a . kamble]

From: Nitin A Kamble 

This enables broadcom wifi driver modules for the common-pc(-64)
machines.

Fixes Bug:
[YOCTO #5238]

Signed-off-by: Nitin A Kamble 
---
 meta/cfg/kernel-cache/bsp/common-pc/common-pc-wifi.cfg | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/meta/cfg/kernel-cache/bsp/common-pc/common-pc-wifi.cfg 
b/meta/cfg/kernel-cache/bsp/common-pc/common-pc-wifi.cfg
index 1769b15..a19e028 100644
--- a/meta/cfg/kernel-cache/bsp/common-pc/common-pc-wifi.cfg
+++ b/meta/cfg/kernel-cache/bsp/common-pc/common-pc-wifi.cfg
@@ -16,3 +16,9 @@ CONFIG_ATH9K=m
 
 CONFIG_RT2X00=m
 CONFIG_RT2800PCI=m
+
+CONFIG_BRCMUTIL=m
+CONFIG_BRCMSMAC=m
+CONFIG_BRCMFMAC=m
+CONFIG_BRCMFMAC_SDIO=y
+CONFIG_BRCMFMAC_USB=y
-- 
1.8.1.4

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

[linux-yocto] [Patch v2 0/1] update commit message for a commit

[nitin . a . kamble]

From: Nitin A Kamble 

Adding more information to the commit adding broadcom wifi drivers.

Thanks,
Nitin

The following changes since commit ba7add39d0c088bc5fc4acbbcdd9a3b4f79d1958:

  common-pc-64: add kernel CONFIG options for sugarbay platform (2013-09-24 
18:15:39 +)

are available in the git repository at:

  git://git.yoctoproject.org/linux-yocto-contrib nitin/3.10-meta
  
http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=nitin/3.10-meta

Nitin A Kamble (1):
  common-pc-wifi.cfg: add support for broadcom wifi drivers

 meta/cfg/kernel-cache/bsp/common-pc/common-pc-wifi.cfg | 6 ++
 1 file changed, 6 insertions(+)

-- 
1.8.1.4

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

[linux-yocto] [PATCH 08/16] media/pci-capture : A feature for PCI media capture devices

[nitin . a . kamble]

From: Nitin A Kamble 

This enables kernel configuration for bunch of PCI media capture
devices.

Signed-off-by: Nitin A Kamble 
---
 .../kernel-cache/features/media/pci-capture.cfg| 80 ++
 .../kernel-cache/features/media/pci-capture.scc|  8 +++
 2 files changed, 88 insertions(+)
 create mode 100644 meta/cfg/kernel-cache/features/media/pci-capture.cfg
 create mode 100644 meta/cfg/kernel-cache/features/media/pci-capture.scc

diff --git a/meta/cfg/kernel-cache/features/media/pci-capture.cfg 
b/meta/cfg/kernel-cache/features/media/pci-capture.cfg
new file mode 100644
index 000..232de32
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/pci-capture.cfg
@@ -0,0 +1,80 @@
+#
+# Media capture support for PCI devices
+#
+CONFIG_MEDIA_PCI_SUPPORT=y
+
+#
+# Media capture/analog TV support
+#
+CONFIG_VIDEO_IVTV=m
+CONFIG_VIDEO_IVTV_ALSA=m
+CONFIG_VIDEO_FB_IVTV=m
+
+CONFIG_VIDEO_ZORAN=m
+CONFIG_VIDEO_ZORAN_DC30=m
+CONFIG_VIDEO_ZORAN_ZR36060=m
+# CONFIG_VIDEO_ZORAN_BUZ is not set
+CONFIG_VIDEO_ZORAN_DC10=m
+CONFIG_VIDEO_ZORAN_LML33=m
+CONFIG_VIDEO_ZORAN_LML33R10=m
+CONFIG_VIDEO_ZORAN_AVS6EYES=m
+
+CONFIG_VIDEO_HEXIUM_GEMINI=m
+CONFIG_VIDEO_HEXIUM_ORION=m
+CONFIG_VIDEO_MXB=m
+
+#
+# Media capture/analog/hybrid TV support
+#
+CONFIG_VIDEO_CX18=m
+CONFIG_VIDEO_CX18_ALSA=m
+
+CONFIG_VIDEO_CX23885=m
+CONFIG_MEDIA_ALTERA_CI=m
+
+CONFIG_VIDEO_CX25821=m
+CONFIG_VIDEO_CX25821_ALSA=m
+
+CONFIG_VIDEO_CX88=m
+CONFIG_VIDEO_CX88_ALSA=m
+CONFIG_VIDEO_CX88_BLACKBIRD=m
+CONFIG_VIDEO_CX88_DVB=m
+CONFIG_VIDEO_CX88_VP3054=m
+CONFIG_VIDEO_CX88_MPEG=m
+
+CONFIG_VIDEO_BT848=m
+CONFIG_DVB_BT8XX=m
+
+CONFIG_VIDEO_SAA7134=m
+CONFIG_VIDEO_SAA7134_ALSA=m
+CONFIG_VIDEO_SAA7134_RC=y
+CONFIG_VIDEO_SAA7134_DVB=m
+CONFIG_VIDEO_SAA7164=m
+
+#
+# Media digital TV PCI Adapters
+#
+CONFIG_DVB_AV7110=m
+CONFIG_DVB_AV7110_OSD=y
+CONFIG_DVB_BUDGET_CORE=m
+CONFIG_DVB_BUDGET=m
+CONFIG_DVB_BUDGET_CI=m
+CONFIG_DVB_BUDGET_AV=m
+CONFIG_DVB_BUDGET_PATCH=m
+
+CONFIG_DVB_B2C2_FLEXCOP_PCI=m
+# CONFIG_DVB_B2C2_FLEXCOP_PCI_DEBUG is not set
+
+CONFIG_DVB_PLUTO2=m
+
+CONFIG_DVB_DM1105=m
+
+CONFIG_DVB_PT1=m
+
+CONFIG_MANTIS_CORE=m
+CONFIG_DVB_MANTIS=m
+CONFIG_DVB_HOPPER=m
+
+CONFIG_DVB_NGENE=m
+
+CONFIG_DVB_DDBRIDGE=m
diff --git a/meta/cfg/kernel-cache/features/media/pci-capture.scc 
b/meta/cfg/kernel-cache/features/media/pci-capture.scc
new file mode 100644
index 000..e24e6c8
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/pci-capture.scc
@@ -0,0 +1,8 @@
+define KFEATURE_DESCRIPTION "Enable Configuration For Media PCI Capture 
Devices"
+define KFEATURE_COMPATIBILITY all
+
+include media.scc
+include ../pci/pci.scc
+include common.scc
+
+kconf hardware pci-capture.cfg
-- 
1.8.1.4

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

[linux-yocto] [PATCH 14/16] media/dvb-frontends : A feature for Digital Video Broadcast Devices

[nitin . a . kamble]

From: Nitin A Kamble 

This enables configuration for bunch of Digital Video Broadcast devices.

Signed-off-by: Nitin A Kamble 
---
 .../kernel-cache/features/media/dvb_frontends.cfg  | 116 +
 .../kernel-cache/features/media/dvb_frontends.scc  |   6 ++
 2 files changed, 122 insertions(+)
 create mode 100644 meta/cfg/kernel-cache/features/media/dvb_frontends.cfg
 create mode 100644 meta/cfg/kernel-cache/features/media/dvb_frontends.scc

diff --git a/meta/cfg/kernel-cache/features/media/dvb_frontends.cfg 
b/meta/cfg/kernel-cache/features/media/dvb_frontends.cfg
new file mode 100644
index 000..08d94a1
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/dvb_frontends.cfg
@@ -0,0 +1,116 @@
+#
+# Multistandard (satellite) frontends
+#
+CONFIG_DVB_STB0899=m
+CONFIG_DVB_STB6100=m
+CONFIG_DVB_STV090x=m
+CONFIG_DVB_STV6110x=m
+
+#
+# Multistandard (cable + terrestrial) frontends
+#
+CONFIG_DVB_DRXK=m
+CONFIG_DVB_TDA18271C2DD=m
+
+#
+# DVB-S (satellite) frontends
+#
+CONFIG_DVB_CX24110=m
+CONFIG_DVB_CX24123=m
+CONFIG_DVB_MT312=m
+CONFIG_DVB_ZL10036=m
+CONFIG_DVB_ZL10039=m
+CONFIG_DVB_S5H1420=m
+CONFIG_DVB_STV0288=m
+CONFIG_DVB_STB6000=m
+CONFIG_DVB_STV0299=m
+CONFIG_DVB_STV6110=m
+CONFIG_DVB_STV0900=m
+CONFIG_DVB_TDA8083=m
+CONFIG_DVB_TDA10086=m
+CONFIG_DVB_TDA8261=m
+CONFIG_DVB_VES1X93=m
+CONFIG_DVB_TUNER_ITD1000=m
+CONFIG_DVB_TUNER_CX24113=m
+CONFIG_DVB_TDA826X=m
+CONFIG_DVB_TUA6100=m
+CONFIG_DVB_CX24116=m
+CONFIG_DVB_SI21XX=m
+CONFIG_DVB_DS3000=m
+CONFIG_DVB_MB86A16=m
+CONFIG_DVB_TDA10071=m
+
+#
+# DVB-T (terrestrial) frontends
+#
+CONFIG_DVB_SP8870=m
+CONFIG_DVB_SP887X=m
+CONFIG_DVB_CX22700=m
+CONFIG_DVB_CX22702=m
+CONFIG_DVB_DRXD=m
+CONFIG_DVB_L64781=m
+CONFIG_DVB_TDA1004X=m
+CONFIG_DVB_NXT6000=m
+CONFIG_DVB_MT352=m
+CONFIG_DVB_ZL10353=m
+CONFIG_DVB_DIB3000MB=m
+CONFIG_DVB_DIB3000MC=m
+CONFIG_DVB_DIB7000M=m
+CONFIG_DVB_DIB7000P=m
+CONFIG_DVB_TDA10048=m
+CONFIG_DVB_AF9013=m
+CONFIG_DVB_EC100=m
+CONFIG_DVB_STV0367=m
+CONFIG_DVB_CXD2820R=m
+CONFIG_DVB_RTL2830=m
+CONFIG_DVB_RTL2832=m
+
+#
+# DVB-C (cable) frontends
+#
+CONFIG_DVB_VES1820=m
+CONFIG_DVB_TDA10021=m
+CONFIG_DVB_TDA10023=m
+CONFIG_DVB_STV0297=m
+
+#
+# ATSC (North American/Korean Terrestrial/Cable DTV) frontends
+#
+CONFIG_DVB_NXT200X=m
+CONFIG_DVB_OR51211=m
+CONFIG_DVB_OR51132=m
+CONFIG_DVB_BCM3510=m
+CONFIG_DVB_LGDT330X=m
+CONFIG_DVB_LGDT3305=m
+CONFIG_DVB_LG2160=m
+CONFIG_DVB_S5H1409=m
+CONFIG_DVB_AU8522=m
+CONFIG_DVB_AU8522_DTV=m
+CONFIG_DVB_AU8522_V4L=m
+CONFIG_DVB_S5H1411=m
+
+# ISDB-T (terrestrial) frontends
+#
+CONFIG_DVB_S921=m
+CONFIG_DVB_DIB8000=m
+CONFIG_DVB_MB86A20S=m
+
+#
+# Digital terrestrial only tuners/PLL
+#
+CONFIG_DVB_PLL=m
+# SEC control devices for DVB-S
+#
+CONFIG_DVB_LNBP21=m
+CONFIG_DVB_LNBP22=m
+CONFIG_DVB_ISL6405=m
+CONFIG_DVB_ISL6421=m
+CONFIG_DVB_ISL6423=m
+CONFIG_DVB_A8293=m
+CONFIG_DVB_LGS8GXX=m
+CONFIG_DVB_ATBM8830=m
+CONFIG_DVB_TDA665x=m
+CONFIG_DVB_IX2505V=m
+CONFIG_DVB_IT913X_FE=m
+CONFIG_DVB_M88RS2000=m
+CONFIG_DVB_AF9033=m
diff --git a/meta/cfg/kernel-cache/features/media/dvb_frontends.scc 
b/meta/cfg/kernel-cache/features/media/dvb_frontends.scc
new file mode 100644
index 000..d3df591
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/dvb_frontends.scc
@@ -0,0 +1,6 @@
+define KFEATURE_DESCRIPTION "Enable Configuration For DVB (Digital Video 
Broadcast) Frontends"
+define KFEATURE_COMPATIBILITY all
+
+include media.scc
+
+kconf hardware dvb_frontends.cfg
-- 
1.8.1.4

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

[linux-yocto] [PATCH 15/16] minnow.scc: enable media & firmware features

[nitin . a . kamble]

From: Nitin A Kamble 

This takes out the need of the media.cfg from the kernel recipe.

Signed-off-by: Nitin A Kamble 
---
 meta/cfg/kernel-cache/bsp/minnow/minnow.scc | 9 +
 1 file changed, 9 insertions(+)

diff --git a/meta/cfg/kernel-cache/bsp/minnow/minnow.scc 
b/meta/cfg/kernel-cache/bsp/minnow/minnow.scc
index 089d913..14a0abd 100644
--- a/meta/cfg/kernel-cache/bsp/minnow/minnow.scc
+++ b/meta/cfg/kernel-cache/bsp/minnow/minnow.scc
@@ -11,6 +11,15 @@ include cfg/timer/rtc.scc
 include features/leds/leds.scc
 include features/spi/spidev.scc
 include features/i2c/i2cdev.scc
+include features/media/dvb_frontends.scc
+include features/media/i2c.scc
+include features/media/pci-capture.scc
+include features/media/platform.scc
+include features/media/radio.scc
+include features/media/rc.scc
+include features/media/tuners.scc
+include features/media/usb_tv.scc
+include features/firmware/firmware.scc
 
 # Earlyprintk and port debug requires 8250
 # This is a =y fragment
-- 
1.8.1.4

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

[linux-yocto] [PATCH 03/16] remove old MEDIA config fragments

[nitin . a . kamble]

From: Nitin A Kamble 

These are getting replaced with newer extensive MEDIA config fragments.

Signed-off-by: Nitin A Kamble 
---
 .../kernel-cache/features/media/media-camera.cfg|  4 
 .../kernel-cache/features/media/media-camera.scc|  4 
 meta/cfg/kernel-cache/features/media/v4l2.cfg   | 21 -
 meta/cfg/kernel-cache/features/media/v4l2.scc   |  6 --
 meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg |  3 ---
 meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc |  7 ---
 6 files changed, 45 deletions(-)
 delete mode 100644 meta/cfg/kernel-cache/features/media/media-camera.cfg
 delete mode 100644 meta/cfg/kernel-cache/features/media/media-camera.scc
 delete mode 100644 meta/cfg/kernel-cache/features/media/v4l2.cfg
 delete mode 100644 meta/cfg/kernel-cache/features/media/v4l2.scc
 delete mode 100644 meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg
 delete mode 100644 meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc

diff --git a/meta/cfg/kernel-cache/features/media/media-camera.cfg 
b/meta/cfg/kernel-cache/features/media/media-camera.cfg
deleted file mode 100644
index 6e173a9..000
--- a/meta/cfg/kernel-cache/features/media/media-camera.cfg
+++ /dev/null
@@ -1,4 +0,0 @@
-# Enable Multimedia and Camera Device support
-CONFIG_MEDIA_SUPPORT=m
-CONFIG_MEDIA_CAMERA_SUPPORT=y
-CONFIG_MEDIA_SUBDRV_AUTOSELECT=y
diff --git a/meta/cfg/kernel-cache/features/media/media-camera.scc 
b/meta/cfg/kernel-cache/features/media/media-camera.scc
deleted file mode 100644
index 15d04e4..000
--- a/meta/cfg/kernel-cache/features/media/media-camera.scc
+++ /dev/null
@@ -1,4 +0,0 @@
-define KFEATURE_DESCRIPTION "Enable camera media device as a module"
-define KFEATURE_COMPATIBILITY all
-
-kconf non-hardware media-camera.cfg
diff --git a/meta/cfg/kernel-cache/features/media/v4l2.cfg 
b/meta/cfg/kernel-cache/features/media/v4l2.cfg
deleted file mode 100644
index 614886c..000
--- a/meta/cfg/kernel-cache/features/media/v4l2.cfg
+++ /dev/null
@@ -1,21 +0,0 @@
-# Enable the V4L2 core and API
-CONFIG_VIDEO_DEV=m
-CONFIG_VIDEO_V4L2=m
-VIDEO_V4L2_SUBDEV_API=y
-
-# Used by drivers that need v4l2-mem2mem.ko
-V4L2_MEM2MEM_DEV=m
-
-# Used by drivers that need Videobuf modules
-VIDEOBUF_GEN=m
-VIDEOBUF_DMA_SG=m
-VIDEOBUF_VMALLOC=m
-VIDEOBUF_DMA_CONTIG=m
-VIDEOBUF_DVB=m
-
-# Used by drivers that need Videobuf2 modules
-CONFIG_VIDEOBUF2_CORE=m
-CONFIG_VIDEOBUF2_MEMOPS=m
-CONFIG_VIDEOBUF2_VMALLOC=m
-VIDEOBUF2_DMA_CONTIG=m
-VIDEOBUF2_DMA_SG=m
diff --git a/meta/cfg/kernel-cache/features/media/v4l2.scc 
b/meta/cfg/kernel-cache/features/media/v4l2.scc
deleted file mode 100644
index 09ab7d6..000
--- a/meta/cfg/kernel-cache/features/media/v4l2.scc
+++ /dev/null
@@ -1,6 +0,0 @@
-define KFEATURE_DESCRIPTION "Enable Video for Linux 2 as a module"
-define KFEATURE_COMPATIBILITY all
-
-include media-camera.scc
-
-kconf non-hardware v4l2.cfg
diff --git a/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg 
b/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg
deleted file mode 100644
index 366f08b..000
--- a/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg
+++ /dev/null
@@ -1,3 +0,0 @@
-# Enable USB Video Class camera support
-CONFIG_MEDIA_USB_SUPPORT=y
-CONFIG_USB_VIDEO_CLASS=m
diff --git a/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc 
b/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc
deleted file mode 100644
index a8cd0f1..000
--- a/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc
+++ /dev/null
@@ -1,7 +0,0 @@
-define KFEATURE_DESCRIPTION "Enable USB UVC Video Camera Module"
-define KFEATURE_COMPATIBILITY board
-
-include usb-base.scc
-include features/media/media-camera.scc
-
-kconf hardware usb-uvcvideo.cfg
-- 
1.8.1.4

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

[linux-yocto] [PATCH 07/16] media/i2c: A feature for i2c media devices

[nitin . a . kamble]

From: Nitin A Kamble 

This enables kernel configuration for bunch of i2c media devices.

Signed-off-by: Nitin A Kamble 
---
 meta/cfg/kernel-cache/features/media/i2c.cfg | 74 
 meta/cfg/kernel-cache/features/media/i2c.scc |  7 +++
 2 files changed, 81 insertions(+)
 create mode 100644 meta/cfg/kernel-cache/features/media/i2c.cfg
 create mode 100644 meta/cfg/kernel-cache/features/media/i2c.scc

diff --git a/meta/cfg/kernel-cache/features/media/i2c.cfg 
b/meta/cfg/kernel-cache/features/media/i2c.cfg
new file mode 100644
index 000..a59631f
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/i2c.cfg
@@ -0,0 +1,74 @@
+#
+# Media I2C Support
+#
+
+#
+# Encoders, Decoders, Sensors And Other Helper Chips
+#
+CONFIG_VIDEO_IR_I2C=y
+CONFIG_VIDEO_TVAUDIO=m
+CONFIG_VIDEO_TDA7432=m
+CONFIG_VIDEO_TDA9840=m
+CONFIG_VIDEO_TEA6415C=m
+CONFIG_VIDEO_TEA6420=m
+CONFIG_VIDEO_MSP3400=m
+CONFIG_VIDEO_CS5345=m
+CONFIG_VIDEO_CS53L32A=m
+CONFIG_VIDEO_WM8775=m
+CONFIG_VIDEO_WM8739=m
+CONFIG_VIDEO_VP27SMPX=m
+
+#
+# RDS decoders
+#
+CONFIG_VIDEO_SAA6588=m
+
+#
+# Video decoders
+#
+CONFIG_VIDEO_BT819=m
+CONFIG_VIDEO_BT856=m
+CONFIG_VIDEO_BT866=m
+CONFIG_VIDEO_KS0127=m
+CONFIG_VIDEO_SAA7110=m
+CONFIG_VIDEO_SAA711X=m
+CONFIG_VIDEO_TVP5150=m
+CONFIG_VIDEO_VPX3220=m
+
+#
+# Video and audio decoders
+#
+CONFIG_VIDEO_SAA717X=m
+CONFIG_VIDEO_CX25840=m
+
+#
+# MPEG video encoders
+#
+CONFIG_VIDEO_CX2341X=m
+
+#
+# Video encoders
+#
+CONFIG_VIDEO_SAA7127=m
+CONFIG_VIDEO_ADV7170=m
+CONFIG_VIDEO_ADV7175=m
+
+#
+# Camera sensor devices
+#
+CONFIG_VIDEO_MT9V011=m
+
+#
+# Flash devices
+#
+
+#
+# Video improvement chips
+#
+CONFIG_VIDEO_UPD64031A=m
+CONFIG_VIDEO_UPD64083=m
+
+#
+# Miscelaneous helper chips
+#
+CONFIG_VIDEO_M52790=m
diff --git a/meta/cfg/kernel-cache/features/media/i2c.scc 
b/meta/cfg/kernel-cache/features/media/i2c.scc
new file mode 100644
index 000..195266b
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/i2c.scc
@@ -0,0 +1,7 @@
+define KFEATURE_DESCRIPTION "Enable Configuration For I2C Media devices"
+define KFEATURE_COMPATIBILITY all
+
+include media.scc
+include ../i2c/i2c.scc
+
+kconf hardware i2c.cfg
-- 
1.8.1.4

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

[linux-yocto] [PATCH 05/16] media/common : A feature for common media support

[nitin . a . kamble]

From: Nitin A Kamble 

This enables the kernel configuration for media support common to
some PCI and USB media devices.

Signed-off-by: Nitin A Kamble 
---
 meta/cfg/kernel-cache/features/media/common.cfg | 15 +++
 meta/cfg/kernel-cache/features/media/common.scc |  6 ++
 2 files changed, 21 insertions(+)
 create mode 100644 meta/cfg/kernel-cache/features/media/common.cfg
 create mode 100644 meta/cfg/kernel-cache/features/media/common.scc

diff --git a/meta/cfg/kernel-cache/features/media/common.cfg 
b/meta/cfg/kernel-cache/features/media/common.cfg
new file mode 100644
index 000..bb5db0b
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/common.cfg
@@ -0,0 +1,15 @@
+#
+# Media Common Options
+#
+CONFIG_MEDIA_COMMON_OPTIONS=y
+
+CONFIG_DVB_B2C2_FLEXCOP=m
+
+CONFIG_VIDEO_SAA7146=m
+CONFIG_VIDEO_SAA7146_VV=m
+
+CONFIG_SMS_SIANO_MDTV=m
+CONFIG_SMS_SIANO_RC=y
+
+CONFIG_VIDEO_BTCX=m
+CONFIG_VIDEO_TVEEPROM=m
diff --git a/meta/cfg/kernel-cache/features/media/common.scc 
b/meta/cfg/kernel-cache/features/media/common.scc
new file mode 100644
index 000..e3df51d
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/common.scc
@@ -0,0 +1,6 @@
+define KFEATURE_DESCRIPTION "Enable Common Media Options"
+define KFEATURE_COMPATIBILITY all
+
+include media.scc
+
+kconf hardware common.cfg
-- 
1.8.1.4

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

[linux-yocto] [PATCH 06/16] media/usb: A feature for USB media devices.

[nitin . a . kamble]

From: Nitin A Kamble 

This enables various USB media devices. Many of the USB webcams
drivers are enabled here.

Signed-off-by: Nitin A Kamble 
---
 meta/cfg/kernel-cache/features/media/usb.cfg | 76 
 meta/cfg/kernel-cache/features/media/usb.scc |  7 +++
 2 files changed, 83 insertions(+)
 create mode 100644 meta/cfg/kernel-cache/features/media/usb.cfg
 create mode 100644 meta/cfg/kernel-cache/features/media/usb.scc

diff --git a/meta/cfg/kernel-cache/features/media/usb.cfg 
b/meta/cfg/kernel-cache/features/media/usb.cfg
new file mode 100644
index 000..12ac598
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/usb.cfg
@@ -0,0 +1,76 @@
+# Support For USB Media Adapters/devices
+CONFIG_MEDIA_USB_SUPPORT=y
+
+# USB Video Class Webcam Drivers
+CONFIG_USB_VIDEO_CLASS=m
+CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
+
+# USB GSPCA Webcam Drivers
+CONFIG_USB_GSPCA=m
+CONFIG_USB_M5602=m
+CONFIG_USB_STV06XX=m
+CONFIG_USB_GL860=m
+CONFIG_USB_GSPCA_BENQ=m
+CONFIG_USB_GSPCA_CONEX=m
+CONFIG_USB_GSPCA_CPIA1=m
+CONFIG_USB_GSPCA_ETOMS=m
+CONFIG_USB_GSPCA_FINEPIX=m
+CONFIG_USB_GSPCA_JEILINJ=m
+CONFIG_USB_GSPCA_JL2005BCD=m
+CONFIG_USB_GSPCA_KINECT=m
+CONFIG_USB_GSPCA_KONICA=m
+CONFIG_USB_GSPCA_MARS=m
+CONFIG_USB_GSPCA_MR97310A=m
+CONFIG_USB_GSPCA_NW80X=m
+CONFIG_USB_GSPCA_OV519=m
+CONFIG_USB_GSPCA_OV534=m
+CONFIG_USB_GSPCA_OV534_9=m
+CONFIG_USB_GSPCA_PAC207=m
+CONFIG_USB_GSPCA_PAC7302=m
+CONFIG_USB_GSPCA_PAC7311=m
+CONFIG_USB_GSPCA_SE401=m
+CONFIG_USB_GSPCA_SN9C2028=m
+CONFIG_USB_GSPCA_SN9C20X=m
+CONFIG_USB_GSPCA_SONIXB=m
+CONFIG_USB_GSPCA_SONIXJ=m
+CONFIG_USB_GSPCA_SPCA500=m
+CONFIG_USB_GSPCA_SPCA501=m
+CONFIG_USB_GSPCA_SPCA505=m
+CONFIG_USB_GSPCA_SPCA506=m
+CONFIG_USB_GSPCA_SPCA508=m
+CONFIG_USB_GSPCA_SPCA561=m
+CONFIG_USB_GSPCA_SPCA1528=m
+CONFIG_USB_GSPCA_SQ905=m
+CONFIG_USB_GSPCA_SQ905C=m
+CONFIG_USB_GSPCA_SQ930X=m
+CONFIG_USB_GSPCA_STK014=m
+CONFIG_USB_GSPCA_STV0680=m
+CONFIG_USB_GSPCA_SUNPLUS=m
+CONFIG_USB_GSPCA_T613=m
+CONFIG_USB_GSPCA_TOPRO=m
+CONFIG_USB_GSPCA_TV8532=m
+CONFIG_USB_GSPCA_VC032X=m
+CONFIG_USB_GSPCA_VICAM=m
+CONFIG_USB_GSPCA_XIRLINK_CIT=m
+CONFIG_USB_GSPCA_ZC3XX=m
+
+# USB Philips Camera Drivers
+CONFIG_USB_PWC=m
+# CONFIG_USB_PWC_DEBUG is not set
+CONFIG_USB_PWC_INPUT_EVDEV=y
+
+# Vision's CPiA2 (Colour Processor Interface ASIC) Camera Drivers
+CONFIG_VIDEO_CPIA2=m
+
+# CONFIG_USB_ZR364XX is not set
+
+# USB Syntek DC1125 Camera Support
+CONFIG_USB_STKWEBCAM=m
+
+# USB Sensoray 2255 video capture Device
+CONFIG_USB_S2255=m
+
+# USB SN9C1xx PC Camera Controller Support
+CONFIG_USB_SN9C102=m
+
+# CONFIG_USB_G_WEBCAM is not set
diff --git a/meta/cfg/kernel-cache/features/media/usb.scc 
b/meta/cfg/kernel-cache/features/media/usb.scc
new file mode 100644
index 000..5602311
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/usb.scc
@@ -0,0 +1,7 @@
+define KFEATURE_DESCRIPTION "Enable Configuration For USB Media Adapters"
+define KFEATURE_COMPATIBILITY all
+
+include media.scc
+include ../usb/usb-base.cfg
+
+kconf hardware usb.cfg
-- 
1.8.1.4

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

[linux-yocto] [PATCH 01/16] minnow.cfg: Enable TEA575X sound driver

[nitin . a . kamble]

From: Nitin A Kamble 

The TEA575X sound driver configuration is relocated from the kernel
recipe's media.cfg to here.

Signed-off-by: Nitin A Kamble 
---
 meta/cfg/kernel-cache/bsp/minnow/minnow.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg 
b/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg
index 2be4ea4..b08f411 100644
--- a/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg
+++ b/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg
@@ -8,6 +8,7 @@ CONFIG_MTRR=y
 # Basic hardware support for the box - network, USB, PCI, sound
 CONFIG_PCI=y
 CONFIG_PCIEPORTBUS=y
+CONFIG_SND_TEA575X=m
 
 # Ensure we can boot over MMC
 CONFIG_MMC=y
-- 
1.8.1.4

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

[linux-yocto] [PATCH 10/16] media/radio : A feature for AM/FM radio devices

[nitin . a . kamble]

From: Nitin A Kamble 

This enables kernel configuration for various AM/FM radio devices.

Signed-off-by: Nitin A Kamble 
---
 meta/cfg/kernel-cache/features/media/radio.cfg | 24 
 meta/cfg/kernel-cache/features/media/radio.scc |  6 ++
 2 files changed, 30 insertions(+)
 create mode 100644 meta/cfg/kernel-cache/features/media/radio.cfg
 create mode 100644 meta/cfg/kernel-cache/features/media/radio.scc

diff --git a/meta/cfg/kernel-cache/features/media/radio.cfg 
b/meta/cfg/kernel-cache/features/media/radio.cfg
new file mode 100644
index 000..2cbedf2
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/radio.cfg
@@ -0,0 +1,24 @@
+#
+# Media AM/FM Radio Adapters
+#
+CONFIG_RADIO_ADAPTERS=y
+CONFIG_RADIO_SI470X=y
+CONFIG_USB_SI470X=m
+CONFIG_I2C_SI470X=m
+CONFIG_USB_MR800=m
+CONFIG_USB_DSBR=m
+CONFIG_RADIO_MAXIRADIO=m
+CONFIG_RADIO_SHARK=m
+CONFIG_RADIO_SHARK2=m
+CONFIG_I2C_SI4713=m
+CONFIG_RADIO_SI4713=m
+CONFIG_USB_KEENE=m
+CONFIG_RADIO_TEA5764=m
+CONFIG_RADIO_SAA7706H=m
+CONFIG_RADIO_TEF6862=m
+CONFIG_RADIO_WL1273=m
+
+#
+# Multi Function Device Radio
+#
+CONFIG_MFD_WL1273_CORE=m
diff --git a/meta/cfg/kernel-cache/features/media/radio.scc 
b/meta/cfg/kernel-cache/features/media/radio.scc
new file mode 100644
index 000..4844a4c
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/radio.scc
@@ -0,0 +1,6 @@
+define KFEATURE_DESCRIPTION "Enable Configuration for Radio Adapters"
+define KFEATURE_COMPATIBILITY all
+
+include media.scc
+
+kconf hardware radio.cfg
-- 
1.8.1.4

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

[linux-yocto] [PATCH 04/16] media.scc : A feature for Media infrastructure

[nitin . a . kamble]

From: Nitin A Kamble 

This replaces the previous limited media config fragments.
Other hardware media features depends on this feature.

Signed-off-by: Nitin A Kamble 
---
 meta/cfg/kernel-cache/features/media/media.cfg | 54 ++
 meta/cfg/kernel-cache/features/media/media.scc |  4 ++
 2 files changed, 58 insertions(+)
 create mode 100644 meta/cfg/kernel-cache/features/media/media.cfg
 create mode 100644 meta/cfg/kernel-cache/features/media/media.scc

diff --git a/meta/cfg/kernel-cache/features/media/media.cfg 
b/meta/cfg/kernel-cache/features/media/media.cfg
new file mode 100644
index 000..b7b5f5e
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/media.cfg
@@ -0,0 +1,54 @@
+#
+# Enable support for multimedia devices such as webcams and Video grabber 
devices
+#
+CONFIG_MEDIA_SUPPORT=m
+CONFIG_MEDIA_CAMERA_SUPPORT=y
+CONFIG_MEDIA_ANALOG_TV_SUPPORT=y
+CONFIG_MEDIA_DIGITAL_TV_SUPPORT=y
+CONFIG_MEDIA_RADIO_SUPPORT=y
+CONFIG_MEDIA_CONTROLLER=y
+
+#
+# Enable the V4L2 core and API
+#
+CONFIG_VIDEO_DEV=m
+CONFIG_VIDEO_V4L2=m
+CONFIG_VIDEO_V4L2_SUBDEV_API=y
+
+#
+# Used by drivers that need v4l2-mem2mem.ko
+#
+CONFIG_V4L2_MEM2MEM_DEV=m
+
+#
+# Used by drivers that need Videobuf modules
+#
+CONFIG_VIDEOBUF_GEN=m
+CONFIG_VIDEOBUF_DMA_SG=m
+CONFIG_VIDEOBUF_DMA_CONTIG=m
+CONFIG_VIDEOBUF_VMALLOC=m
+CONFIG_VIDEOBUF_DVB=m
+
+#
+# Used by drivers that need Videobuf2 modules
+#
+CONFIG_VIDEOBUF2_CORE=m
+CONFIG_VIDEOBUF2_MEMOPS=m
+CONFIG_VIDEOBUF2_DMA_SG=m
+CONFIG_VIDEOBUF2_DMA_CONTIG=m
+CONFIG_VIDEOBUF2_VMALLOC=m
+
+#
+# Digital Video Broadcast support
+#
+CONFIG_DVB_CORE=y
+CONFIG_DVB_NET=y
+CONFIG_DVB_MAX_ADAPTERS=8
+CONFIG_DVB_DYNAMIC_MINORS=y
+
+#
+# Autoselect ancillary drivers (tuners, sensors, i2c, frontends)
+#
+CONFIG_MEDIA_SUBDRV_AUTOSELECT=y
+
+CONFIG_MEDIA_ATTACH=y
diff --git a/meta/cfg/kernel-cache/features/media/media.scc 
b/meta/cfg/kernel-cache/features/media/media.scc
new file mode 100644
index 000..838782d
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/media.scc
@@ -0,0 +1,4 @@
+define KFEATURE_DESCRIPTION "Enable support for multimedia devices such as 
webcams and Video grabber devices"
+define KFEATURE_COMPATIBILITY all
+
+kconf non-hardware media.cfg
-- 
1.8.1.4

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

[linux-yocto] [PATCH 11/16] media/rc : A feature for remote control media devices

[nitin . a . kamble]

From: Nitin A Kamble 

This enables kernel configuration for bunch of remote control media
devices.

Signed-off-by: Nitin A Kamble 
---
 meta/cfg/kernel-cache/features/media/rc.cfg | 18 ++
 meta/cfg/kernel-cache/features/media/rc.scc |  6 ++
 2 files changed, 24 insertions(+)
 create mode 100644 meta/cfg/kernel-cache/features/media/rc.cfg
 create mode 100644 meta/cfg/kernel-cache/features/media/rc.scc

diff --git a/meta/cfg/kernel-cache/features/media/rc.cfg 
b/meta/cfg/kernel-cache/features/media/rc.cfg
new file mode 100644
index 000..f8a345e
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/rc.cfg
@@ -0,0 +1,18 @@
+# support for remote control
+CONFIG_MEDIA_RC_SUPPORT=y
+CONFIG_RC_CORE=y
+CONFIG_RC_MAP=y
+CONFIG_RC_DECODERS=y
+
+# Support for Infra Red devices
+CONFIG_LIRC=m
+CONFIG_IR_LIRC_CODEC=m
+CONFIG_IR_NEC_DECODER=y
+CONFIG_IR_RC5_DECODER=y
+CONFIG_IR_RC6_DECODER=y
+CONFIG_IR_JVC_DECODER=y
+CONFIG_IR_SONY_DECODER=y
+CONFIG_IR_RC5_SZ_DECODER=y
+CONFIG_IR_SANYO_DECODER=y
+CONFIG_IR_MCE_KBD_DECODER=y
+
diff --git a/meta/cfg/kernel-cache/features/media/rc.scc 
b/meta/cfg/kernel-cache/features/media/rc.scc
new file mode 100644
index 000..7ee158f
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/rc.scc
@@ -0,0 +1,6 @@
+define KFEATURE_DESCRIPTION "Enable Configuration For Remote Control Media 
Devices"
+define KFEATURE_COMPATIBILITY all
+
+include media.scc
+
+kconf hardware rc.cfg
-- 
1.8.1.4

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

[linux-yocto] [PATCH 12/16] media/tuners: A feature for tuner media devices

[nitin . a . kamble]

From: Nitin A Kamble 

This enables kernel configuration for tuner media devices

Signed-off-by: Nitin A Kamble 
---
 meta/cfg/kernel-cache/features/media/tuners.cfg | 30 +
 meta/cfg/kernel-cache/features/media/tuners.scc |  7 ++
 2 files changed, 37 insertions(+)
 create mode 100644 meta/cfg/kernel-cache/features/media/tuners.cfg
 create mode 100644 meta/cfg/kernel-cache/features/media/tuners.scc

diff --git a/meta/cfg/kernel-cache/features/media/tuners.cfg 
b/meta/cfg/kernel-cache/features/media/tuners.cfg
new file mode 100644
index 000..90d8f47
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/tuners.cfg
@@ -0,0 +1,30 @@
+CONFIG_VIDEO_TUNER=m
+CONFIG_MEDIA_TUNER=y
+CONFIG_MEDIA_TUNER_SIMPLE=y
+CONFIG_MEDIA_TUNER_TDA8290=y
+CONFIG_MEDIA_TUNER_TDA827X=y
+CONFIG_MEDIA_TUNER_TDA18271=y
+CONFIG_MEDIA_TUNER_TDA9887=y
+CONFIG_MEDIA_TUNER_TEA5761=y
+CONFIG_MEDIA_TUNER_TEA5767=y
+CONFIG_MEDIA_TUNER_MT20XX=y
+CONFIG_MEDIA_TUNER_MT2060=m
+CONFIG_MEDIA_TUNER_MT2063=m
+CONFIG_MEDIA_TUNER_MT2266=m
+CONFIG_MEDIA_TUNER_MT2131=m
+CONFIG_MEDIA_TUNER_QT1010=m
+CONFIG_MEDIA_TUNER_XC2028=y
+CONFIG_MEDIA_TUNER_XC5000=y
+CONFIG_MEDIA_TUNER_XC4000=y
+CONFIG_MEDIA_TUNER_MXL5005S=m
+CONFIG_MEDIA_TUNER_MXL5007T=m
+CONFIG_MEDIA_TUNER_MC44S803=y
+CONFIG_MEDIA_TUNER_MAX2165=m
+CONFIG_MEDIA_TUNER_TDA18218=m
+CONFIG_MEDIA_TUNER_FC0011=m
+CONFIG_MEDIA_TUNER_FC0012=m
+CONFIG_MEDIA_TUNER_FC0013=m
+CONFIG_MEDIA_TUNER_TDA18212=m
+CONFIG_MEDIA_TUNER_E4000=m
+CONFIG_MEDIA_TUNER_FC2580=m
+CONFIG_MEDIA_TUNER_TUA9001=m
diff --git a/meta/cfg/kernel-cache/features/media/tuners.scc 
b/meta/cfg/kernel-cache/features/media/tuners.scc
new file mode 100644
index 000..d6965cb
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/tuners.scc
@@ -0,0 +1,7 @@
+define KFEATURE_DESCRIPTION "Enable Configuration For Tuner Media Devices"
+define KFEATURE_COMPATIBILITY all
+
+include media.scc
+include ../i2c/i2c.scc
+
+kconf hardware tuners.cfg
-- 
1.8.1.4

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

[linux-yocto] [PATCH 13/16] media/usb_tv: A feature for usb tv media adapters

[nitin . a . kamble]

From: Nitin A Kamble 

This enables kernel configuration fo bunch of USB TV adapters.

Signed-off-by: Nitin A Kamble 
---
 meta/cfg/kernel-cache/features/media/usb_tv.cfg | 82 +
 meta/cfg/kernel-cache/features/media/usb_tv.scc |  8 +++
 2 files changed, 90 insertions(+)
 create mode 100644 meta/cfg/kernel-cache/features/media/usb_tv.cfg
 create mode 100644 meta/cfg/kernel-cache/features/media/usb_tv.scc

diff --git a/meta/cfg/kernel-cache/features/media/usb_tv.cfg 
b/meta/cfg/kernel-cache/features/media/usb_tv.cfg
new file mode 100644
index 000..4641fa1
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/usb_tv.cfg
@@ -0,0 +1,82 @@
+#
+# Analog TV USB devices
+#
+CONFIG_VIDEO_AU0828=m
+CONFIG_VIDEO_PVRUSB2=m
+CONFIG_VIDEO_PVRUSB2_SYSFS=y
+CONFIG_VIDEO_PVRUSB2_DVB=y
+# CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set
+CONFIG_VIDEO_HDPVR=m
+CONFIG_VIDEO_TLG2300=m
+CONFIG_VIDEO_USBVISION=m
+CONFIG_VIDEO_STK1160=m
+# CONFIG_VIDEO_STK1160_AC97 is not set
+
+#
+# Analog/digital TV USB devices
+#
+CONFIG_VIDEO_CX231XX=m
+CONFIG_VIDEO_CX231XX_RC=y
+CONFIG_VIDEO_CX231XX_ALSA=m
+CONFIG_VIDEO_CX231XX_DVB=m
+CONFIG_VIDEO_TM6000=m
+CONFIG_VIDEO_TM6000_ALSA=m
+CONFIG_VIDEO_TM6000_DVB=m
+
+#
+# Digital TV USB devices
+#
+CONFIG_DVB_USB=m
+# CONFIG_DVB_USB_DEBUG is not set
+CONFIG_DVB_USB_A800=m
+CONFIG_DVB_USB_DIBUSB_MB=m
+# CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not set
+CONFIG_DVB_USB_DIBUSB_MC=m
+CONFIG_DVB_USB_DIB0700=m
+CONFIG_DVB_USB_UMT_010=m
+CONFIG_DVB_USB_CXUSB=m
+CONFIG_DVB_USB_M920X=m
+CONFIG_DVB_USB_DIGITV=m
+CONFIG_DVB_USB_VP7045=m
+CONFIG_DVB_USB_VP702X=m
+CONFIG_DVB_USB_GP8PSK=m
+CONFIG_DVB_USB_NOVA_T_USB2=m
+CONFIG_DVB_USB_TTUSB2=m
+CONFIG_DVB_USB_DTT200U=m
+CONFIG_DVB_USB_OPERA1=m
+CONFIG_DVB_USB_AF9005=m
+CONFIG_DVB_USB_AF9005_REMOTE=m
+CONFIG_DVB_USB_PCTV452E=m
+CONFIG_DVB_USB_DW2102=m
+CONFIG_DVB_USB_CINERGY_T2=m
+CONFIG_DVB_USB_DTV5100=m
+CONFIG_DVB_USB_FRIIO=m
+CONFIG_DVB_USB_AZ6027=m
+CONFIG_DVB_USB_TECHNISAT_USB2=m
+CONFIG_DVB_USB_V2=m
+CONFIG_DVB_USB_CYPRESS_FIRMWARE=m
+CONFIG_DVB_USB_AF9015=m
+CONFIG_DVB_USB_AF9035=m
+CONFIG_DVB_USB_ANYSEE=m
+CONFIG_DVB_USB_AU6610=m
+CONFIG_DVB_USB_AZ6007=m
+CONFIG_DVB_USB_CE6230=m
+CONFIG_DVB_USB_EC168=m
+CONFIG_DVB_USB_GL861=m
+CONFIG_DVB_USB_IT913X=m
+CONFIG_DVB_USB_LME2510=m
+CONFIG_DVB_USB_MXL111SF=m
+CONFIG_DVB_USB_RTL28XXU=m
+CONFIG_DVB_TTUSB_BUDGET=m
+CONFIG_DVB_TTUSB_DEC=m
+CONFIG_SMS_USB_DRV=m
+CONFIG_DVB_B2C2_FLEXCOP_USB=m
+# CONFIG_DVB_B2C2_FLEXCOP_USB_DEBUG is not set
+
+#
+# Webcam, TV (analog/digital) USB devices
+#
+CONFIG_VIDEO_EM28XX=m
+CONFIG_VIDEO_EM28XX_ALSA=m
+CONFIG_VIDEO_EM28XX_DVB=m
+CONFIG_VIDEO_EM28XX_RC=m
diff --git a/meta/cfg/kernel-cache/features/media/usb_tv.scc 
b/meta/cfg/kernel-cache/features/media/usb_tv.scc
new file mode 100644
index 000..c7417ac
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/usb_tv.scc
@@ -0,0 +1,8 @@
+define KFEATURE_DESCRIPTION "Enable Configuration For USB TV adapters"
+define KFEATURE_COMPATIBILITY all
+
+include usb.scc
+include ../i2c/i2c.scc
+include common.scc
+
+kconf hardware usb_tv.cfg
-- 
1.8.1.4

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

[linux-yocto] [PATCH 02/16] firmware.scc/cfg : Feature for firmware loading

[nitin . a . kamble]

From: Nitin A Kamble 

This enables the kernel configuration for firmware loading.

Signed-off-by: Nitin A Kamble 
---
 meta/cfg/kernel-cache/features/firmware/firmware.cfg | 8 
 meta/cfg/kernel-cache/features/firmware/firmware.scc | 4 
 2 files changed, 12 insertions(+)
 create mode 100644 meta/cfg/kernel-cache/features/firmware/firmware.cfg
 create mode 100644 meta/cfg/kernel-cache/features/firmware/firmware.scc

diff --git a/meta/cfg/kernel-cache/features/firmware/firmware.cfg 
b/meta/cfg/kernel-cache/features/firmware/firmware.cfg
new file mode 100644
index 000..7331ab3
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/firmware/firmware.cfg
@@ -0,0 +1,8 @@
+CONFIG_FW_LOADER=m
+CONFIG_FIRMWARE_IN_KERNEL=y
+CONFIG_EXTRA_FIRMWARE=""
+
+#
+# Altera FPGA firmware download module
+#
+CONFIG_ALTERA_STAPL=m
diff --git a/meta/cfg/kernel-cache/features/firmware/firmware.scc 
b/meta/cfg/kernel-cache/features/firmware/firmware.scc
new file mode 100644
index 000..09432a8
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/firmware/firmware.scc
@@ -0,0 +1,4 @@
+define KFEATURE_DESCRIPTION "Firmware loading support"
+define KFEATURE_COMPATIBILITY all
+
+kconf non-hardware firmware.cfg
-- 
1.8.1.4

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

[linux-yocto] [PATCH 09/16] media/platform : A feature for platform media devices

[nitin . a . kamble]

From: Nitin A Kamble 

This enables kernel configuration for bunch of media devices which
are generally part of some platforms. Many of these devices are
webcam devices built into platforms.

Signed-off-by: Nitin A Kamble 
---
 meta/cfg/kernel-cache/features/media/platform.cfg | 15 +++
 meta/cfg/kernel-cache/features/media/platform.scc |  6 ++
 2 files changed, 21 insertions(+)
 create mode 100644 meta/cfg/kernel-cache/features/media/platform.cfg
 create mode 100644 meta/cfg/kernel-cache/features/media/platform.scc

diff --git a/meta/cfg/kernel-cache/features/media/platform.cfg 
b/meta/cfg/kernel-cache/features/media/platform.cfg
new file mode 100644
index 000..b7484e7
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/platform.cfg
@@ -0,0 +1,15 @@
+#
+# Media Platform Configuration
+#
+# CONFIG_V4L_PLATFORM_DRIVERS is not set
+
+CONFIG_V4L_MEM2MEM_DRIVERS=y
+CONFIG_VIDEO_MEM2MEM_DEINTERLACE=m
+
+# CONFIG_V4L_TEST_DRIVERS is not set
+
+
+#
+# Media MMC Support
+#
+# CONFIG_SMS_SDIO_DRV is not set
diff --git a/meta/cfg/kernel-cache/features/media/platform.scc 
b/meta/cfg/kernel-cache/features/media/platform.scc
new file mode 100644
index 000..b3a7e01
--- /dev/null
+++ b/meta/cfg/kernel-cache/features/media/platform.scc
@@ -0,0 +1,6 @@
+define KFEATURE_DESCRIPTION "Enable Configuration For Platform Media Devices"
+define KFEATURE_COMPATIBILITY all
+
+include media.scc
+
+kconf hardware platform.cfg
-- 
1.8.1.4

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

[linux-yocto] [PATCH 16/16] common-pc-64.scc: update as per changes in the media config fragments

[nitin . a . kamble]

From: Nitin A Kamble 

Some of the media config fragments are replaced by more extensive media
fragments. Changes this BSP config accordingly.

Signed-off-by: Nitin A Kamble 
---
 meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc 
b/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc
index 936df98..7d6eb2a 100644
--- a/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc
+++ b/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc
@@ -21,8 +21,7 @@ include features/power/intel.scc
 include cfg/8250.scc
 
 # webcam
-include features/usb/usb-uvcvideo.scc
-include features/media/v4l2.scc
+include features/media/usb.scc
 
 # sugarbay graphics
 include features/i915/i915.scc
-- 
1.8.1.4

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

[linux-yocto] [PATCH 00/16] linux-yocto-3.10: config fragments for minnow BSP

[nitin . a . kamble]

From: Nitin A Kamble 


This patch series imports the 500 line media.cfg from the kernel recipe
in to the linux-yocto-3.10 meta branch, by splitting it into many
fragments.

It replaces some of the existing webcam media fragments, and hence BSPs
configs using the old media fragments is changed accordingly.


This has been tested the following way.
* It gives the same minnow kernel config as with the big media.cfg on SRC_URI
* This changes the kernel config for sugarbay and genericx86-64 BSPs, and
  the sugarbay BSP is validated to work as expected with this change.

Thanks,
Nitin

The following changes since commit 4a04774a6562ab37a769404920e070b70acf3c4c:

  minnow: Remove branch statements from minnow scc files (2013-11-14 22:56:03 
-0500)

are available in the git repository at:

  git://git.yoctoproject.org/linux-yocto-contrib nitin/meta
  http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=nitin/meta

Nitin A Kamble (16):
  minnow.cfg: Enable TEA575X sound driver
  firmware.scc/cfg : Feature for firmware loading
  remove old MEDIA config fragments
  media.scc : A feature for Media infrastructure
  media/common : A feature for common media support
  media/usb: A feature for USB media devices.
  media/i2c: A feature for i2c media devices
  media/pci-capture : A feature for PCI media capture devices
  media/platform : A feature for platform media devices
  media/radio : A feature for AM/FM radio devices
  media/rc : A feature for remote control media devices
  media/tuners: A feature for tuner media devices
  media/usb_tv: A feature for usb tv media adapters
  media/dvb-frontends : A feature for Digital Video Broadcast Devices
  minnow.scc: enable media & firmware features
  common-pc-64.scc: update as per changes in the media config fragments

 .../kernel-cache/bsp/common-pc-64/common-pc-64.scc |   3 +-
 meta/cfg/kernel-cache/bsp/minnow/minnow.cfg|   1 +
 meta/cfg/kernel-cache/bsp/minnow/minnow.scc|   9 ++
 .../kernel-cache/features/firmware/firmware.cfg|   8 ++
 .../kernel-cache/features/firmware/firmware.scc|   4 +
 meta/cfg/kernel-cache/features/media/common.cfg|  15 +++
 meta/cfg/kernel-cache/features/media/common.scc|   6 ++
 .../kernel-cache/features/media/dvb_frontends.cfg  | 116 +
 .../kernel-cache/features/media/dvb_frontends.scc  |   6 ++
 meta/cfg/kernel-cache/features/media/i2c.cfg   |  74 +
 meta/cfg/kernel-cache/features/media/i2c.scc   |   7 ++
 .../kernel-cache/features/media/media-camera.cfg   |   4 -
 .../kernel-cache/features/media/media-camera.scc   |   4 -
 meta/cfg/kernel-cache/features/media/media.cfg |  54 ++
 meta/cfg/kernel-cache/features/media/media.scc |   4 +
 .../kernel-cache/features/media/pci-capture.cfg|  80 ++
 .../kernel-cache/features/media/pci-capture.scc|   8 ++
 meta/cfg/kernel-cache/features/media/platform.cfg  |  15 +++
 meta/cfg/kernel-cache/features/media/platform.scc  |   6 ++
 meta/cfg/kernel-cache/features/media/radio.cfg |  24 +
 meta/cfg/kernel-cache/features/media/radio.scc |   6 ++
 meta/cfg/kernel-cache/features/media/rc.cfg|  18 
 meta/cfg/kernel-cache/features/media/rc.scc|   6 ++
 meta/cfg/kernel-cache/features/media/tuners.cfg|  30 ++
 meta/cfg/kernel-cache/features/media/tuners.scc|   7 ++
 meta/cfg/kernel-cache/features/media/usb.cfg   |  76 ++
 meta/cfg/kernel-cache/features/media/usb.scc   |   7 ++
 meta/cfg/kernel-cache/features/media/usb_tv.cfg|  82 +++
 meta/cfg/kernel-cache/features/media/usb_tv.scc|   8 ++
 meta/cfg/kernel-cache/features/media/v4l2.cfg  |  21 
 meta/cfg/kernel-cache/features/media/v4l2.scc  |   6 --
 .../cfg/kernel-cache/features/usb/usb-uvcvideo.cfg |   3 -
 .../cfg/kernel-cache/features/usb/usb-uvcvideo.scc |   7 --
 33 files changed, 678 insertions(+), 47 deletions(-)
 create mode 100644 meta/cfg/kernel-cache/features/firmware/firmware.cfg
 create mode 100644 meta/cfg/kernel-cache/features/firmware/firmware.scc
 create mode 100644 meta/cfg/kernel-cache/features/media/common.cfg
 create mode 100644 meta/cfg/kernel-cache/features/media/common.scc
 create mode 100644 meta/cfg/kernel-cache/features/media/dvb_frontends.cfg
 create mode 100644 meta/cfg/kernel-cache/features/media/dvb_frontends.scc
 create mode 100644 meta/cfg/kernel-cache/features/media/i2c.cfg
 create mode 100644 meta/cfg/kernel-cache/features/media/i2c.scc
 delete mode 100644 meta/cfg/kernel-cache/features/media/media-camera.cfg
 delete mode 100644 meta/cfg/kernel-cache/features/media/media-camera.scc
 create mode 100644 meta/cfg/kernel-cache/features/media/media.cfg
 create mode 100644 meta/cfg/kernel-cache/features/media/media.scc
 create mode 100644 meta/cfg/kernel-cache/features/media/pci-capture.cfg
 create mode 100644 meta/cfg/kernel-cache/features/media/pci-capture.scc
 create mode 100644 meta/cfg/kernel-cache/features/media/platform

Re: [linux-yocto] [PATCH 00/16] linux-yocto-3.10: config fragments for minnow BSP

[Kamble, Nitin A]

> -Original Message-
> From: Hart, Darren
> Sent: Friday, November 22, 2013 12:48 PM
> To: Kamble, Nitin A
> Cc: linux-yo...@yoctoproject.org; bruce.ashfi...@windriver.com
> Subject: Re: [PATCH 00/16] linux-yocto-3.10: config fragments for minnow
> BSP
> 
> On Fri, 2013-11-22 at 11:36 -0800, nitin.a.kam...@intel.com wrote:
> > From: Nitin A Kamble 
> >
> >
> > This patch series imports the 500 line media.cfg from the kernel
> > recipe in to the linux-yocto-3.10 meta branch, by splitting it into
> > many fragments.
> >
> > It replaces some of the existing webcam media fragments, and hence
> > BSPs configs using the old media fragments is changed accordingly.
> >
> >
> > This has been tested the following way.
> > * It gives the same minnow kernel config as with the big media.cfg on
> > SRC_URI
> > * This changes the kernel config for sugarbay and genericx86-64 BSPs, and
> >   the sugarbay BSP is validated to work as expected with this change.
> 
> Fantastic, thank you Nitin.
> 
> Did you also verify that no new issues are reported by the config validation
> task and logged in the .meta/standard/$KMACHINE/* log files?
> missing, etc?


 I did verify that there are no errors in those log file.
Nitin

> 
> --
> Darren
> 
> >
> > Thanks,
> > Nitin
> >
> > The following changes since commit
> 4a04774a6562ab37a769404920e070b70acf3c4c:
> >
> >   minnow: Remove branch statements from minnow scc files (2013-11-14
> > 22:56:03 -0500)
> >
> > are available in the git repository at:
> >
> >   git://git.yoctoproject.org/linux-yocto-contrib nitin/meta
> >
> > http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=nitin/
> > meta
> >
> > Nitin A Kamble (16):
> >   minnow.cfg: Enable TEA575X sound driver
> >   firmware.scc/cfg : Feature for firmware loading
> >   remove old MEDIA config fragments
> >   media.scc : A feature for Media infrastructure
> >   media/common : A feature for common media support
> >   media/usb: A feature for USB media devices.
> >   media/i2c: A feature for i2c media devices
> >   media/pci-capture : A feature for PCI media capture devices
> >   media/platform : A feature for platform media devices
> >   media/radio : A feature for AM/FM radio devices
> >   media/rc : A feature for remote control media devices
> >   media/tuners: A feature for tuner media devices
> >   media/usb_tv: A feature for usb tv media adapters
> >   media/dvb-frontends : A feature for Digital Video Broadcast Devices
> >   minnow.scc: enable media & firmware features
> >   common-pc-64.scc: update as per changes in the media config
> > fragments
> >
> >  .../kernel-cache/bsp/common-pc-64/common-pc-64.scc |   3 +-
> >  meta/cfg/kernel-cache/bsp/minnow/minnow.cfg|   1 +
> >  meta/cfg/kernel-cache/bsp/minnow/minnow.scc|   9 ++
> >  .../kernel-cache/features/firmware/firmware.cfg|   8 ++
> >  .../kernel-cache/features/firmware/firmware.scc|   4 +
> >  meta/cfg/kernel-cache/features/media/common.cfg|  15 +++
> >  meta/cfg/kernel-cache/features/media/common.scc|   6 ++
> >  .../kernel-cache/features/media/dvb_frontends.cfg  | 116
> +
> >  .../kernel-cache/features/media/dvb_frontends.scc  |   6 ++
> >  meta/cfg/kernel-cache/features/media/i2c.cfg   |  74 +
> >  meta/cfg/kernel-cache/features/media/i2c.scc   |   7 ++
> >  .../kernel-cache/features/media/media-camera.cfg   |   4 -
> >  .../kernel-cache/features/media/media-camera.scc   |   4 -
> >  meta/cfg/kernel-cache/features/media/media.cfg |  54 ++
> >  meta/cfg/kernel-cache/features/media/media.scc |   4 +
> >  .../kernel-cache/features/media/pci-capture.cfg|  80 ++
> >  .../kernel-cache/features/media/pci-capture.scc|   8 ++
> >  meta/cfg/kernel-cache/features/media/platform.cfg  |  15 +++
> >  meta/cfg/kernel-cache/features/media/platform.scc  |   6 ++
> >  meta/cfg/kernel-cache/features/media/radio.cfg |  24 +
> >  meta/cfg/kernel-cache/features/media/radio.scc |   6 ++
> >  meta/cfg/kernel-cache/features/media/rc.cfg|  18 
> >  meta/cfg/kernel-cache/features/media/rc.scc|   6 ++
> >  meta/cfg/kernel-cache/features/media/tuners.cfg|  30 ++
> >  meta/cfg/kernel-cache/features/media/tuners.scc|   7 ++
> >  meta/cfg/kernel-cache/features/media/usb.cfg   |  76 ++
> >  meta/cfg/kernel-cache/features/media/usb.scc   |   7 ++
> >  meta/cfg/kernel-cache/featu

Re: [linux-yocto] [PATCH 01/16] minnow.cfg: Enable TEA575X sound driver

[Kamble, Nitin A]

> -Original Message-
> From: Darren Hart [mailto:dvh...@linux.intel.com]
> Sent: Friday, November 22, 2013 12:50 PM
> To: Kamble, Nitin A
> Cc: linux-yo...@yoctoproject.org; bruce.ashfi...@windriver.com
> Subject: Re: [PATCH 01/16] minnow.cfg: Enable TEA575X sound driver
> 
> On Fri, 2013-11-22 at 11:35 -0800, nitin.a.kam...@intel.com wrote:
> > From: Nitin A Kamble 
> >
> > The TEA575X sound driver configuration is relocated from the kernel
> > recipe's media.cfg to here.
> 
> This isn't required for the minnowboard, it uses an HDA. This should be part
> of a more generic sound fragment that can be included by BSPs like
> genericx86*.

The only reason for adding this was, because minnow board used it in it's 
media.cfg. If it is not needed for minnow, then why to keep it?

Nitin



> 
> --
> Darren
> 
> >
> > Signed-off-by: Nitin A Kamble 
> > ---
> >  meta/cfg/kernel-cache/bsp/minnow/minnow.cfg | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg
> > b/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg
> > index 2be4ea4..b08f411 100644
> > --- a/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg
> > +++ b/meta/cfg/kernel-cache/bsp/minnow/minnow.cfg
> > @@ -8,6 +8,7 @@ CONFIG_MTRR=y
> >  # Basic hardware support for the box - network, USB, PCI, sound
> > CONFIG_PCI=y  CONFIG_PCIEPORTBUS=y
> > +CONFIG_SND_TEA575X=m
> >
> >  # Ensure we can boot over MMC
> >  CONFIG_MMC=y
> 
> --
> Darren Hart
> Intel Open Source Technology Center
> Yocto Project - Linux Kernel
> 

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

Re: [linux-yocto] [PATCH 03/16] remove old MEDIA config fragments

[Kamble, Nitin A]

> -Original Message-
> From: Darren Hart [mailto:dvh...@linux.intel.com]
> Sent: Friday, November 22, 2013 12:53 PM
> To: Kamble, Nitin A
> Cc: linux-yo...@yoctoproject.org; bruce.ashfi...@windriver.com
> Subject: Re: [PATCH 03/16] remove old MEDIA config fragments
> 
> On Fri, 2013-11-22 at 11:35 -0800, nitin.a.kam...@intel.com wrote:
> > From: Nitin A Kamble 
> >
> > These are getting replaced with newer extensive MEDIA config fragments.
> >
> 
> OK, but this should come last, after the others are in place and used by the
> BSPs.
> 
The commit can be shifted easily. As you can guess, I was not concerned about
for couple of reasons. The pull request bunches all the concerned commits 
together. 
And BSPs would not get affected unless one intends to break, by setting random 
commit
IDs without testing. 
  Anyway it is a quick fix so I won't argue.
Nitin


> --
> Darren
> 
> > Signed-off-by: Nitin A Kamble 
> > ---
> >  .../kernel-cache/features/media/media-camera.cfg|  4 
> >  .../kernel-cache/features/media/media-camera.scc|  4 
> >  meta/cfg/kernel-cache/features/media/v4l2.cfg   | 21 
> > -
> >  meta/cfg/kernel-cache/features/media/v4l2.scc   |  6 --
> >  meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg |  3 ---
> > meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc |  7 ---
> >  6 files changed, 45 deletions(-)
> >  delete mode 100644
> > meta/cfg/kernel-cache/features/media/media-camera.cfg
> >  delete mode 100644
> > meta/cfg/kernel-cache/features/media/media-camera.scc
> >  delete mode 100644 meta/cfg/kernel-cache/features/media/v4l2.cfg
> >  delete mode 100644 meta/cfg/kernel-cache/features/media/v4l2.scc
> >  delete mode 100644
> > meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg
> >  delete mode 100644
> > meta/cfg/kernel-cache/features/usb/usb-uvcvideo.scc
> >
> > diff --git a/meta/cfg/kernel-cache/features/media/media-camera.cfg
> > b/meta/cfg/kernel-cache/features/media/media-camera.cfg
> > deleted file mode 100644
> > index 6e173a9..000
> > --- a/meta/cfg/kernel-cache/features/media/media-camera.cfg
> > +++ /dev/null
> > @@ -1,4 +0,0 @@
> > -# Enable Multimedia and Camera Device support -
> CONFIG_MEDIA_SUPPORT=m
> > -CONFIG_MEDIA_CAMERA_SUPPORT=y -
> CONFIG_MEDIA_SUBDRV_AUTOSELECT=y diff
> > --git a/meta/cfg/kernel-cache/features/media/media-camera.scc
> > b/meta/cfg/kernel-cache/features/media/media-camera.scc
> > deleted file mode 100644
> > index 15d04e4..0000000
> > --- a/meta/cfg/kernel-cache/features/media/media-camera.scc
> > +++ /dev/null
> > @@ -1,4 +0,0 @@
> > -define KFEATURE_DESCRIPTION "Enable camera media device as a
> module"
> > -define KFEATURE_COMPATIBILITY all
> > -
> > -kconf non-hardware media-camera.cfg
> > diff --git a/meta/cfg/kernel-cache/features/media/v4l2.cfg
> > b/meta/cfg/kernel-cache/features/media/v4l2.cfg
> > deleted file mode 100644
> > index 614886c..000
> > --- a/meta/cfg/kernel-cache/features/media/v4l2.cfg
> > +++ /dev/null
> > @@ -1,21 +0,0 @@
> > -# Enable the V4L2 core and API
> > -CONFIG_VIDEO_DEV=m
> > -CONFIG_VIDEO_V4L2=m
> > -VIDEO_V4L2_SUBDEV_API=y
> > -
> > -# Used by drivers that need v4l2-mem2mem.ko -
> V4L2_MEM2MEM_DEV=m
> > -
> > -# Used by drivers that need Videobuf modules -VIDEOBUF_GEN=m
> > -VIDEOBUF_DMA_SG=m -VIDEOBUF_VMALLOC=m -
> VIDEOBUF_DMA_CONTIG=m
> > -VIDEOBUF_DVB=m
> > -
> > -# Used by drivers that need Videobuf2 modules
> > -CONFIG_VIDEOBUF2_CORE=m -CONFIG_VIDEOBUF2_MEMOPS=m
> > -CONFIG_VIDEOBUF2_VMALLOC=m -VIDEOBUF2_DMA_CONTIG=m
> > -VIDEOBUF2_DMA_SG=m diff --git
> > a/meta/cfg/kernel-cache/features/media/v4l2.scc
> > b/meta/cfg/kernel-cache/features/media/v4l2.scc
> > deleted file mode 100644
> > index 09ab7d6..000
> > --- a/meta/cfg/kernel-cache/features/media/v4l2.scc
> > +++ /dev/null
> > @@ -1,6 +0,0 @@
> > -define KFEATURE_DESCRIPTION "Enable Video for Linux 2 as a module"
> > -define KFEATURE_COMPATIBILITY all
> > -
> > -include media-camera.scc
> > -
> > -kconf non-hardware v4l2.cfg
> > diff --git a/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg
> > b/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg
> > deleted file mode 100644
> > index 366f08b..000
> > --- a/meta/cfg/kernel-cache/features/usb/usb-uvcvideo.cfg
> > +++ /dev/null
> > @@ -1,3 +0,0 @@
> > -# Enable USB Video Class camera support -
> CONFIG_MEDIA_USB_SUPPO

Re: [linux-yocto] [PATCH 04/16] media.scc : A feature for Media infrastructure

[Kamble, Nitin A]

> -Original Message-
> From: Hart, Darren
> Sent: Friday, November 22, 2013 12:56 PM
> To: Kamble, Nitin A
> Cc: linux-yo...@yoctoproject.org; bruce.ashfi...@windriver.com
> Subject: Re: [PATCH 04/16] media.scc : A feature for Media infrastructure
> 
> On Fri, 2013-11-22 at 11:35 -0800, nitin.a.kam...@intel.com wrote:
> > From: Nitin A Kamble 
> >
> > This replaces the previous limited media config fragments.
> > Other hardware media features depends on this feature.
> 
> Please include the intent of this particular feature here. This adds the
> infrastructure V4L2, tuner, camera, and radio, to be included by driver-
> specific features.
> 
Ack. Makes sense.
BTW, the real intent is to covert the minnow's media.cfg,  ;)
Nitin


> But, yes, good abstraction.
> 
> --
> Darren
> 
> >
> > Signed-off-by: Nitin A Kamble 
> > ---
> >  meta/cfg/kernel-cache/features/media/media.cfg | 54
> > ++
> > meta/cfg/kernel-cache/features/media/media.scc |  4 ++
> >  2 files changed, 58 insertions(+)
> >  create mode 100644 meta/cfg/kernel-cache/features/media/media.cfg
> >  create mode 100644 meta/cfg/kernel-cache/features/media/media.scc
> >
> > diff --git a/meta/cfg/kernel-cache/features/media/media.cfg
> > b/meta/cfg/kernel-cache/features/media/media.cfg
> > new file mode 100644
> > index 000..b7b5f5e
> > --- /dev/null
> > +++ b/meta/cfg/kernel-cache/features/media/media.cfg
> > @@ -0,0 +1,54 @@
> > +#
> > +# Enable support for multimedia devices such as webcams and Video
> > +grabber devices # CONFIG_MEDIA_SUPPORT=m
> > +CONFIG_MEDIA_CAMERA_SUPPORT=y
> CONFIG_MEDIA_ANALOG_TV_SUPPORT=y
> > +CONFIG_MEDIA_DIGITAL_TV_SUPPORT=y
> > +CONFIG_MEDIA_RADIO_SUPPORT=y
> > +CONFIG_MEDIA_CONTROLLER=y
> > +
> > +#
> > +# Enable the V4L2 core and API
> > +#
> > +CONFIG_VIDEO_DEV=m
> > +CONFIG_VIDEO_V4L2=m
> > +CONFIG_VIDEO_V4L2_SUBDEV_API=y
> > +
> > +#
> > +# Used by drivers that need v4l2-mem2mem.ko #
> > +CONFIG_V4L2_MEM2MEM_DEV=m
> > +
> > +#
> > +# Used by drivers that need Videobuf modules #
> CONFIG_VIDEOBUF_GEN=m
> > +CONFIG_VIDEOBUF_DMA_SG=m CONFIG_VIDEOBUF_DMA_CONTIG=m
> > +CONFIG_VIDEOBUF_VMALLOC=m CONFIG_VIDEOBUF_DVB=m
> > +
> > +#
> > +# Used by drivers that need Videobuf2 modules #
> > +CONFIG_VIDEOBUF2_CORE=m CONFIG_VIDEOBUF2_MEMOPS=m
> > +CONFIG_VIDEOBUF2_DMA_SG=m
> CONFIG_VIDEOBUF2_DMA_CONTIG=m
> > +CONFIG_VIDEOBUF2_VMALLOC=m
> > +
> > +#
> > +# Digital Video Broadcast support
> > +#
> > +CONFIG_DVB_CORE=y
> > +CONFIG_DVB_NET=y
> > +CONFIG_DVB_MAX_ADAPTERS=8
> > +CONFIG_DVB_DYNAMIC_MINORS=y
> > +
> > +#
> > +# Autoselect ancillary drivers (tuners, sensors, i2c, frontends) #
> > +CONFIG_MEDIA_SUBDRV_AUTOSELECT=y
> > +
> > +CONFIG_MEDIA_ATTACH=y
> > diff --git a/meta/cfg/kernel-cache/features/media/media.scc
> > b/meta/cfg/kernel-cache/features/media/media.scc
> > new file mode 100644
> > index 000..838782d
> > --- /dev/null
> > +++ b/meta/cfg/kernel-cache/features/media/media.scc
> > @@ -0,0 +1,4 @@
> > +define KFEATURE_DESCRIPTION "Enable support for multimedia devices
> such as webcams and Video grabber devices"
> > +define KFEATURE_COMPATIBILITY all
> > +
> > +kconf non-hardware media.cfg
> 
> --
> Darren Hart
> Intel Open Source Technology Center
> Yocto Project - Linux Kernel

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

[yocto] How to use pre-built external Yocto toolchain

[Thornburg, Christopher A]

I must be missing something obvious. It's easy for me to build and install a 
toolchain package using
bitbake meta-toolchain
The resulting toolchain package shows up at...
./tmp/deploy/sdk/poky-eglibc-i686-meta-toolchain-core2-toolchain-1.5.sh
...which is easy to install.

It seems the proper way to use such an external toolchain would be to set 
TCMODE, but TCMODE only seems to support 'default' (i.e. build an internal 
toolchain) and 'external-sourcery' (i.e. use an external sourcery toolchain). :S

How do I use an external toolchain built as above?

Thanks!

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

Re: [yocto] [meta-intel] [common][dora][PATCH] emgd-driver-bin: limit build to x86*

[Kamble, Nitin A]

> -Original Message-
> From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-
> boun...@yoctoproject.org] On Behalf Of Darren Hart
> Sent: Friday, February 14, 2014 9:26 AM
> To: Koen Kooi; meta-in...@lists.yoctoproject.org
> Cc: yo...@lists.yoctoproject.org
> Subject: Re: [meta-intel] [common][dora][PATCH] emgd-driver-bin: limit
> build to x86*
> 
> On 2/14/14, 7:21, "Koen Kooi"  wrote:
> 
> >When building GL apps for non-x86 machines (e.g. raspberrypi)
> >emgd-driver-bin is being dragged in as a valid provider. To avoid build
> >breakage fix it at the source by limiting emgd-driver-bin to x86
> >architectures.
> >
> >Signed-off-by: Koen Kooi 
> >---
> > common/recipes-graphics/xorg-driver/emgd-driver-bin_1.16.bb | 2 ++
> >common/recipes-graphics/xorg-driver/emgd-driver-bin_1.18.bb | 2 ++
> > 2 files changed, 4 insertions(+)
> >
> >diff --git
> >a/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.16.bb
> >b/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.16.bb
> >index c8ca726..8cb088e 100644
> >--- a/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.16.bb
> >+++ b/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.16.bb
> >@@ -9,6 +9,8 @@ LICENSE = "Intel-software-license-emgd-1.16 &
> >Intel-user-space-graphics-driver-b
> > LICENSE_FLAGS = "license_${PN}_${PV}"
> > PR = "r0"
> >
> >+COMPATIBLE_HOST = "(i.86|x86_64).*-linux"
> 
> And you can drop the x86_64 as well as this is a 32bit only driver.


Agreed.
Nitin

> 
> --
> Darren Hart
> Yocto Project - Linux Kernel
> Intel Open Source Technology Center
> 
> 
> 
> 
> ___
> meta-intel mailing list
> meta-in...@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-intel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-intel][common][dora][PATCHv2] emgd-driver-bin: limit build to x86

[Kamble, Nitin A]

On 2/14/2014 10:24 AM, Koen Kooi wrote:

When building GL apps for non-x86 machines (e.g. raspberrypi) emgd-driver-bin 
is being
dragged in as a valid provider. To avoid build breakage fix it at the
source by limiting emgd-driver-bin to x86 architectures.

Signed-off-by: Koen Kooi 


Acked-By: Nitin A Kamble 


---
  common/recipes-graphics/xorg-driver/emgd-driver-bin_1.16.bb | 2 ++
  common/recipes-graphics/xorg-driver/emgd-driver-bin_1.18.bb | 2 ++
  2 files changed, 4 insertions(+)

diff --git a/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.16.bb 
b/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.16.bb
index c8ca726..8cb088e 100644
--- a/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.16.bb
+++ b/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.16.bb
@@ -9,6 +9,8 @@ LICENSE = "Intel-software-license-emgd-1.16 & 
Intel-user-space-graphics-driver-b
  LICENSE_FLAGS = "license_${PN}_${PV}"
  PR = "r0"
  
+COMPATIBLE_HOST = "(i.86).*-linux"

+
  EMGD_LIC_DIR = "IEMGD_HEAD_Linux/License"
  EMGD_RPM_DIR = "IEMGD_HEAD_Linux/MeeGo1.2"
  EMGD_VIDEO_PLUGIN_DIR = "../common/video_plugin"
diff --git a/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.18.bb 
b/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.18.bb
index b3bf0d2..cf6d855 100644
--- a/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.18.bb
+++ b/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.18.bb
@@ -9,6 +9,8 @@ LICENSE = "Intel-software-license-emgd-1.18 & 
Intel-user-space-graphics-driver-b
  LICENSE_FLAGS = "license_${PN}_${PV}"
  PR = "r1"
  
+COMPATIBLE_HOST = "(i.86).*-linux"

+
  EMGD_LIC_DIR = "IEMGD_HEAD_Linux/License"
  EMGD_RPM_DIR = "IEMGD_HEAD_Linux/MeeGo1.2"
  EMGD_VIDEO_PLUGIN_DIR = "../common/video_plugin"


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

Re: [yocto] [meta-intel][common][dora][PATCHv2] emgd-driver-bin: limit build to x86

[Kamble, Nitin A]

On 2/14/2014 1:13 PM, Khem Raj wrote:


-Khem
On Feb 14, 2014 10:25 AM, "Koen Kooi" <mailto:k...@dominion.thruhere.net>> wrote:

>
> When building GL apps for non-x86 machines (e.g. raspberrypi) 
emgd-driver-bin is being

> dragged in as a valid provider. To avoid build breakage fix it at the
> source by limiting emgd-driver-bin to x86 architectures.
>
> Signed-off-by: Koen Kooi <mailto:k...@dominion.thruhere.net>>

> ---
>  common/recipes-graphics/xorg-driver/emgd-driver-bin_1.16.bb 
<http://emgd-driver-bin_1.16.bb> | 2 ++
>  common/recipes-graphics/xorg-driver/emgd-driver-bin_1.18.bb 
<http://emgd-driver-bin_1.18.bb> | 2 ++

>  2 files changed, 4 insertions(+)
>
> diff --git 
a/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.16.bb 
<http://emgd-driver-bin_1.16.bb> 
b/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.16.bb 
<http://emgd-driver-bin_1.16.bb>

> index c8ca726..8cb088e 100644
> --- a/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.16.bb 
<http://emgd-driver-bin_1.16.bb>
> +++ b/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.16.bb 
<http://emgd-driver-bin_1.16.bb>
> @@ -9,6 +9,8 @@ LICENSE = "Intel-software-license-emgd-1.16 & 
Intel-user-space-graphics-driver-b

>  LICENSE_FLAGS = "license_${PN}_${PV}"
>  PR = "r0"
>
> +COMPATIBLE_HOST = "(i.86).*-linux"

is it not valid for x86_64 ?

No, it's not. The EMGD binary files are 32bit files, and BSPs using it 
are all 32bit.


Nitin


> +
>  EMGD_LIC_DIR = "IEMGD_HEAD_Linux/License"
>  EMGD_RPM_DIR = "IEMGD_HEAD_Linux/MeeGo1.2"
>  EMGD_VIDEO_PLUGIN_DIR = "../common/video_plugin"
> diff --git 
a/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.18.bb 
<http://emgd-driver-bin_1.18.bb> 
b/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.18.bb 
<http://emgd-driver-bin_1.18.bb>

> index b3bf0d2..cf6d855 100644
> --- a/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.18.bb 
<http://emgd-driver-bin_1.18.bb>
> +++ b/common/recipes-graphics/xorg-driver/emgd-driver-bin_1.18.bb 
<http://emgd-driver-bin_1.18.bb>
> @@ -9,6 +9,8 @@ LICENSE = "Intel-software-license-emgd-1.18 & 
Intel-user-space-graphics-driver-b

>  LICENSE_FLAGS = "license_${PN}_${PV}"
>  PR = "r1"
>
> +COMPATIBLE_HOST = "(i.86).*-linux"
> +
>  EMGD_LIC_DIR = "IEMGD_HEAD_Linux/License"
>  EMGD_RPM_DIR = "IEMGD_HEAD_Linux/MeeGo1.2"
>  EMGD_VIDEO_PLUGIN_DIR = "../common/video_plugin"
> --
> 1.8.3.4
>
> ___
> yocto mailing list
> yocto@yoctoproject.org <mailto: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

[yocto] [PATCH 0/1] Misc Fixes

[nitin . a . kamble]

From: Nitin A Kamble 

The following changes since commit a5afc58319d3c7e082a090f5fad7f89bd6e588c9:

  connman-gnome: fix segfault on connect (2012-04-16 22:53:00 +0100)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib nitin/bugfixes
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/bugfixes

Nitin A Kamble (1):
  poky-tiny: fix eglibc configuration

 meta-yocto/conf/distro/poky-tiny.conf |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

-- 
1.7.7

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

[yocto] [PATCH 1/1] poky-tiny: fix eglibc configuration

[nitin . a . kamble]

From: Nitin A Kamble 

eglibc needs libc-posix-regexp-glibc & libc-libm-big enabled in it's
configuration to avoid following eglibc build issue.

...
| In file included from xregex.c:634:0:
| xregex.c: In function 'byte_regex_compile':
| xregex.c:3395:8: error: too few arguments to function 'findidx'
| ../locale/weight.h:23:1: note: declared here
...

This fixes bug [YOCTO #2295]

Signed-off-by: Nitin A Kamble 
---
 meta-yocto/conf/distro/poky-tiny.conf |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta-yocto/conf/distro/poky-tiny.conf 
b/meta-yocto/conf/distro/poky-tiny.conf
index 58d64ec..626b2d0 100644
--- a/meta-yocto/conf/distro/poky-tiny.conf
+++ b/meta-yocto/conf/distro/poky-tiny.conf
@@ -62,7 +62,7 @@ ASSUME_PROVIDED += "pkgconfig$"
 
 # Reconfigure eglibc for a smaller installation
 # Comment out any of the lines below to disable them in the build
-DISTRO_FEATURES_LIBC_TINY = "libc-libm libc-crypt"
+DISTRO_FEATURES_LIBC_TINY = "libc-libm libc-libm-big libc-crypt"
 # for gettext
 DISTRO_FEATURES_LIBC_TINY += "libc-posix-clang-wchar"
 # for m4
@@ -71,7 +71,7 @@ DISTRO_FEATURES_LIBC_TINY += "libc-spawn libc-locale-code"
 DISTRO_FEATURES_LIBC_TINY += "libc-ftraverse"
 # Required for "who"
 DISTRO_FEATURES_LIBC_MINIMAL = "libc-utmp libc-getlogin"
-DISTRO_FEATURES_LIBC_REGEX = "libc-posix-regexp"
+DISTRO_FEATURES_LIBC_REGEX = "libc-posix-regexp libc-posix-regexp-glibc"
 DISTRO_FEATURES_LIBC_NET = "libc-inet libc-nis"
 
 DISTRO_FEATURES_LIBC = "${DISTRO_FEATURES_LIBC_TINY} \
-- 
1.7.7

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

[yocto] [PATCH 0/1] a fix for poky-tiny

[nitin . a . kamble]

From: Nitin A Kamble 

The following changes since commit 0612cf3fcb3365e7721a2d5c331f8cd2647ae60b:

  hob2: create a standalone deploy image tool (2012-06-08 12:13:43 +0100)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib master+work
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=master+work

Nitin A Kamble (1):
  eglibc: remove runtime dependency of perl from eglibc-mtrace

 meta/recipes-core/eglibc/eglibc-package.inc |1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

-- 
1.7.3.4

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

[yocto] [PATCH 1/1] eglibc: remove runtime dependency of perl from eglibc-mtrace

[nitin . a . kamble]

From: Nitin A Kamble 

perl needs eglibc to build. The presence of runtime dependency of
perl for eglibc-mtrace caused bitbake to build perl before eglibc,
which causes build failure of perl with poky-tiny distro

  This fixes bug: [YOCTO #2523]

Signed-off-by: Nitin A Kamble 
---
 meta/recipes-core/eglibc/eglibc-package.inc |1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/meta/recipes-core/eglibc/eglibc-package.inc 
b/meta/recipes-core/eglibc/eglibc-package.inc
index ce37155..423729a 100644
--- a/meta/recipes-core/eglibc/eglibc-package.inc
+++ b/meta/recipes-core/eglibc/eglibc-package.inc
@@ -55,7 +55,6 @@ FILES_${PN}-dbg += "${libexecdir}/*/.debug 
${libdir}/audit/.debug"
 FILES_catchsegv${PKGSUFFIX} = "${bindir}/catchsegv"
 RDEPENDS_catchsegv${PKGSUFFIX} = "libsegfault"
 RDEPENDS_${PN}-utils += "bash"
-RDEPENDS_${PN}-mtrace += "perl"
 FILES_${PN}-pcprofile = "${base_libdir}/libpcprofile.so"
 FILES_eglibc-thread-db${PKGSUFFIX} = "${base_libdir}/libthread_db.so.* 
${base_libdir}/libthread_db-*.so"
 RPROVIDES_${PN}-dev += "libc-dev"
-- 
1.7.3.4

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

[yocto] [PATCH 0/1] a fix for poky-tiny

[nitin . a . kamble]

From: Nitin A Kamble 

resending with corrected contrib branch.

The following changes since commit 0612cf3fcb3365e7721a2d5c331f8cd2647ae60b:

  hob2: create a standalone deploy image tool (2012-06-08 12:13:43 +0100)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib master+work
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/master+work

Nitin A Kamble (1):
  eglibc: remove runtime dependency of perl from eglibc-mtrace

 meta/recipes-core/eglibc/eglibc-package.inc |1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

-- 
1.7.3.4

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

[yocto] [PATCH 1/1] eglibc: remove runtime dependency of perl from eglibc-mtrace

[nitin . a . kamble]

From: Nitin A Kamble 

perl needs eglibc to build. The presence of runtime dependency of
perl for eglibc-mtrace caused bitbake to build perl before eglibc,
which causes build failure of perl with poky-tiny distro

  This fixes bug: [YOCTO #2523]

Signed-off-by: Nitin A Kamble 
---
 meta/recipes-core/eglibc/eglibc-package.inc |1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/meta/recipes-core/eglibc/eglibc-package.inc 
b/meta/recipes-core/eglibc/eglibc-package.inc
index ce37155..423729a 100644
--- a/meta/recipes-core/eglibc/eglibc-package.inc
+++ b/meta/recipes-core/eglibc/eglibc-package.inc
@@ -55,7 +55,6 @@ FILES_${PN}-dbg += "${libexecdir}/*/.debug 
${libdir}/audit/.debug"
 FILES_catchsegv${PKGSUFFIX} = "${bindir}/catchsegv"
 RDEPENDS_catchsegv${PKGSUFFIX} = "libsegfault"
 RDEPENDS_${PN}-utils += "bash"
-RDEPENDS_${PN}-mtrace += "perl"
 FILES_${PN}-pcprofile = "${base_libdir}/libpcprofile.so"
 FILES_eglibc-thread-db${PKGSUFFIX} = "${base_libdir}/libthread_db.so.* 
${base_libdir}/libthread_db-*.so"
 RPROVIDES_${PN}-dev += "libc-dev"
-- 
1.7.3.4

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

[yocto] [PATCH 0/1] remove snb rc6 patches from v3.4 kernel repository

[nitin . a . kamble]

From: Nitin A Kamble 

These patches are already part of v3.4 kernel sources. So there is no need to 
maintain them in the yocto linux 3.4 repository.

Thanks,
Nitin

The following changes since commit 3fd089debe624c642d7b4d9363f853021d1675b2:

  checkpoint dir: meta (2012-06-06 16:24:42 -0400)

are available in the git repository at:
  git://git.yoctoproject.org/linux-yocto-2.6.37-contrib nitin/meta
  
http://git.yoctoproject.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=nitin/meta

Nitin A Kamble (1):
  rc6: remove rc6 patches for snb

 .../features/tmp/rc6/rc6-kernel-params.patch   |   81 
 meta/cfg/kernel-cache/features/tmp/rc6/rc6.scc |5 -
 .../tmp/rc6/snb-disable-rc6p-fix-precedence.patch  |   26 --
 .../features/tmp/rc6/snb-disable-rc6p.patch|   39 --
 .../features/tmp/rc6/snb-enable-rc6.patch  |   54 -
 5 files changed, 0 insertions(+), 205 deletions(-)
 delete mode 100644 
meta/cfg/kernel-cache/features/tmp/rc6/rc6-kernel-params.patch
 delete mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/rc6.scc
 delete mode 100644 
meta/cfg/kernel-cache/features/tmp/rc6/snb-disable-rc6p-fix-precedence.patch
 delete mode 100644 
meta/cfg/kernel-cache/features/tmp/rc6/snb-disable-rc6p.patch
 delete mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/snb-enable-rc6.patch

-- 
1.7.3.4

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

[yocto] [PATCH 1/1] rc6: remove rc6 patches for snb

[nitin . a . kamble]

From: Nitin A Kamble 

The sandybridge rc6 patches are part of the released v3.4 kernel.
Hence there is no need to keep these patches in the 3.4 linux
yocto kernel repository.

Signed-off-by: Nitin A Kamble 
---
 .../features/tmp/rc6/rc6-kernel-params.patch   |   81 
 meta/cfg/kernel-cache/features/tmp/rc6/rc6.scc |5 -
 .../tmp/rc6/snb-disable-rc6p-fix-precedence.patch  |   26 --
 .../features/tmp/rc6/snb-disable-rc6p.patch|   39 --
 .../features/tmp/rc6/snb-enable-rc6.patch  |   54 -
 5 files changed, 0 insertions(+), 205 deletions(-)
 delete mode 100644 
meta/cfg/kernel-cache/features/tmp/rc6/rc6-kernel-params.patch
 delete mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/rc6.scc
 delete mode 100644 
meta/cfg/kernel-cache/features/tmp/rc6/snb-disable-rc6p-fix-precedence.patch
 delete mode 100644 
meta/cfg/kernel-cache/features/tmp/rc6/snb-disable-rc6p.patch
 delete mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/snb-enable-rc6.patch

diff --git a/meta/cfg/kernel-cache/features/tmp/rc6/rc6-kernel-params.patch 
b/meta/cfg/kernel-cache/features/tmp/rc6/rc6-kernel-params.patch
deleted file mode 100644
index f1f7c08..000
--- a/meta/cfg/kernel-cache/features/tmp/rc6/rc6-kernel-params.patch
+++ /dev/null
@@ -1,81 +0,0 @@
-From 83b7f9ac9126f0532ca34c14e4f0582c565c6b0d Mon Sep 17 00:00:00 2001
-From: Eugeni Dodonov 
-Date: Fri, 23 Mar 2012 11:57:18 -0300
-Subject: [PATCH] drm/i915: allow to select rc6 modes via kernel parameter
-
-This allows to select which rc6 modes are to be used via kernel parameter,
-via a bitmask parameter. E.g.:
-
-- to enable rc6, i915_enable_rc6=1
-- to enable rc6 and deep rc6, i915_enable_rc6=3
-- to enable rc6 and deepest rc6, use i915_enable_rc6=5
-- to enable rc6, deep and deepest rc6, use i915_enable_rc6=7
-
-Please keep in mind that the deepest RC6 state really should NOT be used
-by default, as it could potentially worsen the issues with deep RC6. So do
-enable it only when you know what you are doing. However, having it around
-could help solving possible future rc6-related issues and their debugging
-on user machines.
-
-Note that this changes behavior - previously, value of 1 would enable both
-RC6 and deep RC6. Now it should only enable RC6 and deep/deepest RC6
-stages must be enabled manually.
-
-v2: address Chris Wilson comments and clean up the code.
-
-References: https://bugs.freedesktop.org/show_bug.cgi?id=42579
-Reviewed-by: Chris Wilson 
-Reviewed-by: Ben Widawsky 
-Signed-off-by: Eugeni Dodonov 
-Signed-off-by: Daniel Vetter 
-Integrated-by: Tom Zanussi 
-
-Index: linux/drivers/gpu/drm/i915/i915_drv.c
-===
 linux.orig/drivers/gpu/drm/i915/i915_drv.c 2012-05-24 15:21:16.216263416 
-0500
-+++ linux/drivers/gpu/drm/i915/i915_drv.c  2012-05-24 15:21:42.386496572 
-0500
-@@ -66,7 +66,11 @@
- int i915_enable_rc6 __read_mostly = -1;
- module_param_named(i915_enable_rc6, i915_enable_rc6, int, 0600);
- MODULE_PARM_DESC(i915_enable_rc6,
--  "Enable power-saving render C-state 6 (default: -1 (use 
per-chip default)");
-+  "Enable power-saving render C-state 6. "
-+  "Different stages can be selected via bitmask values "
-+  "(0 = disable; 1 = enable rc6; 2 = enable deep rc6; 4 = enable 
deepest rc6). "
-+  "For example, 3 would enable rc6 and deep rc6, and 7 would 
enable everything. "
-+  "default: -1 (use per-chip default)");
- 
- int i915_enable_fbc __read_mostly = -1;
- module_param_named(i915_enable_fbc, i915_enable_fbc, int, 0600);
-Index: linux/drivers/gpu/drm/i915/i915_drv.h
-===
 linux.orig/drivers/gpu/drm/i915/i915_drv.h 2012-05-24 15:21:23.926268189 
-0500
-+++ linux/drivers/gpu/drm/i915/i915_drv.h  2012-05-24 15:21:42.396308725 
-0500
-@@ -1003,6 +1003,27 @@
- 
- #include "i915_trace.h"
- 
-+/**
-+ * RC6 is a special power stage which allows the GPU to enter an very
-+ * low-voltage mode when idle, using down to 0V while at this stage.  This
-+ * stage is entered automatically when the GPU is idle when RC6 support is
-+ * enabled, and as soon as new workload arises GPU wakes up automatically as 
well.
-+ *
-+ * There are different RC6 modes available in Intel GPU, which differentiate
-+ * among each other with the latency required to enter and leave RC6 and
-+ * voltage consumed by the GPU in different states.
-+ *
-+ * The combination of the following flags define which states GPU is allowed
-+ * to enter, while RC6 is the normal RC6 state, RC6p is the deep RC6, and
-+ * RC6pp is deepest RC6. Their support by hardware varies according to the
-+ * GPU, BIOS, chipset and platform. RC6 is usually the safest one and the one
-+ * which brings the most power savings; deeper states save more power, but

[yocto] [KERNEL 0/1] remove rc6 patches from meta branch

[nitin . a . kamble]

From: Nitin A Kamble 

These patches are already part of v3.4 kernel sources. So there is no need to
maintain them in the yocto linux 3.4 repository.

Thanks,
Nitin
PS: this is resend of earlier pull request with proper email formats.

The following changes since commit 3fd089debe624c642d7b4d9363f853021d1675b2:

  checkpoint dir: meta (2012-06-06 16:24:42 -0400)

are available in the git repository at:
  git://git.yoctoproject.org/linux-yocto-2.6.37-contrib nitin/meta
  
http://git.yoctoproject.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=nitin/meta

Nitin A Kamble (1):
  meta: remove rc6 patches for snb

 .../features/tmp/rc6/rc6-kernel-params.patch   |   81 
 meta/cfg/kernel-cache/features/tmp/rc6/rc6.scc |5 -
 .../tmp/rc6/snb-disable-rc6p-fix-precedence.patch  |   26 --
 .../features/tmp/rc6/snb-disable-rc6p.patch|   39 --
 .../features/tmp/rc6/snb-enable-rc6.patch  |   54 -
 5 files changed, 0 insertions(+), 205 deletions(-)
 delete mode 100644 
meta/cfg/kernel-cache/features/tmp/rc6/rc6-kernel-params.patch
 delete mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/rc6.scc
 delete mode 100644 
meta/cfg/kernel-cache/features/tmp/rc6/snb-disable-rc6p-fix-precedence.patch
 delete mode 100644 
meta/cfg/kernel-cache/features/tmp/rc6/snb-disable-rc6p.patch
 delete mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/snb-enable-rc6.patch

-- 
1.7.3.4

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

[yocto] [KERNEL 1/1] meta: remove rc6 patches for snb

[nitin . a . kamble]

From: Nitin A Kamble 

The sandybridge rc6 patches are part of the released v3.4 kernel.
Hence there is no need to keep these patches in the 3.4 linux
yocto kernel repository.

Signed-off-by: Nitin A Kamble 
---
 .../features/tmp/rc6/rc6-kernel-params.patch   |   81 
 meta/cfg/kernel-cache/features/tmp/rc6/rc6.scc |5 -
 .../tmp/rc6/snb-disable-rc6p-fix-precedence.patch  |   26 --
 .../features/tmp/rc6/snb-disable-rc6p.patch|   39 --
 .../features/tmp/rc6/snb-enable-rc6.patch  |   54 -
 5 files changed, 0 insertions(+), 205 deletions(-)
 delete mode 100644 
meta/cfg/kernel-cache/features/tmp/rc6/rc6-kernel-params.patch
 delete mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/rc6.scc
 delete mode 100644 
meta/cfg/kernel-cache/features/tmp/rc6/snb-disable-rc6p-fix-precedence.patch
 delete mode 100644 
meta/cfg/kernel-cache/features/tmp/rc6/snb-disable-rc6p.patch
 delete mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/snb-enable-rc6.patch

diff --git a/meta/cfg/kernel-cache/features/tmp/rc6/rc6-kernel-params.patch 
b/meta/cfg/kernel-cache/features/tmp/rc6/rc6-kernel-params.patch
deleted file mode 100644
index f1f7c08..000
--- a/meta/cfg/kernel-cache/features/tmp/rc6/rc6-kernel-params.patch
+++ /dev/null
@@ -1,81 +0,0 @@
-From 83b7f9ac9126f0532ca34c14e4f0582c565c6b0d Mon Sep 17 00:00:00 2001
-From: Eugeni Dodonov 
-Date: Fri, 23 Mar 2012 11:57:18 -0300
-Subject: [PATCH] drm/i915: allow to select rc6 modes via kernel parameter
-
-This allows to select which rc6 modes are to be used via kernel parameter,
-via a bitmask parameter. E.g.:
-
-- to enable rc6, i915_enable_rc6=1
-- to enable rc6 and deep rc6, i915_enable_rc6=3
-- to enable rc6 and deepest rc6, use i915_enable_rc6=5
-- to enable rc6, deep and deepest rc6, use i915_enable_rc6=7
-
-Please keep in mind that the deepest RC6 state really should NOT be used
-by default, as it could potentially worsen the issues with deep RC6. So do
-enable it only when you know what you are doing. However, having it around
-could help solving possible future rc6-related issues and their debugging
-on user machines.
-
-Note that this changes behavior - previously, value of 1 would enable both
-RC6 and deep RC6. Now it should only enable RC6 and deep/deepest RC6
-stages must be enabled manually.
-
-v2: address Chris Wilson comments and clean up the code.
-
-References: https://bugs.freedesktop.org/show_bug.cgi?id=42579
-Reviewed-by: Chris Wilson 
-Reviewed-by: Ben Widawsky 
-Signed-off-by: Eugeni Dodonov 
-Signed-off-by: Daniel Vetter 
-Integrated-by: Tom Zanussi 
-
-Index: linux/drivers/gpu/drm/i915/i915_drv.c
-===
 linux.orig/drivers/gpu/drm/i915/i915_drv.c 2012-05-24 15:21:16.216263416 
-0500
-+++ linux/drivers/gpu/drm/i915/i915_drv.c  2012-05-24 15:21:42.386496572 
-0500
-@@ -66,7 +66,11 @@
- int i915_enable_rc6 __read_mostly = -1;
- module_param_named(i915_enable_rc6, i915_enable_rc6, int, 0600);
- MODULE_PARM_DESC(i915_enable_rc6,
--  "Enable power-saving render C-state 6 (default: -1 (use 
per-chip default)");
-+  "Enable power-saving render C-state 6. "
-+  "Different stages can be selected via bitmask values "
-+  "(0 = disable; 1 = enable rc6; 2 = enable deep rc6; 4 = enable 
deepest rc6). "
-+  "For example, 3 would enable rc6 and deep rc6, and 7 would 
enable everything. "
-+  "default: -1 (use per-chip default)");
- 
- int i915_enable_fbc __read_mostly = -1;
- module_param_named(i915_enable_fbc, i915_enable_fbc, int, 0600);
-Index: linux/drivers/gpu/drm/i915/i915_drv.h
-===
 linux.orig/drivers/gpu/drm/i915/i915_drv.h 2012-05-24 15:21:23.926268189 
-0500
-+++ linux/drivers/gpu/drm/i915/i915_drv.h  2012-05-24 15:21:42.396308725 
-0500
-@@ -1003,6 +1003,27 @@
- 
- #include "i915_trace.h"
- 
-+/**
-+ * RC6 is a special power stage which allows the GPU to enter an very
-+ * low-voltage mode when idle, using down to 0V while at this stage.  This
-+ * stage is entered automatically when the GPU is idle when RC6 support is
-+ * enabled, and as soon as new workload arises GPU wakes up automatically as 
well.
-+ *
-+ * There are different RC6 modes available in Intel GPU, which differentiate
-+ * among each other with the latency required to enter and leave RC6 and
-+ * voltage consumed by the GPU in different states.
-+ *
-+ * The combination of the following flags define which states GPU is allowed
-+ * to enter, while RC6 is the normal RC6 state, RC6p is the deep RC6, and
-+ * RC6pp is deepest RC6. Their support by hardware varies according to the
-+ * GPU, BIOS, chipset and platform. RC6 is usually the safest one and the one
-+ * which brings the most power savings; deeper states save more power, but

Re: [yocto] [PATCH 0/1] remove snb rc6 patches from v3.4 kernel repository

[Kamble, Nitin A]

> -Original Message-
> From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
> Sent: Monday, June 11, 2012 1:20 PM
> To: Kamble, Nitin A
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] [PATCH 0/1] remove snb rc6 patches from v3.4 kernel
> repository
> 
> On 12-06-11 03:38 PM, nitin.a.kam...@intel.com wrote:
> > From: Nitin A Kamble
> >
> > These patches are already part of v3.4 kernel sources. So there is no
> > need to maintain them in the yocto linux 3.4 repository.
> 
> dropped. They obviously weren't reference anyway.
> 
> I assume you'll be doing an associated meta-intel commit to remove the
> reference in:
> 
> ./meta-sugarbay/recipes-kernel/linux/linux-yocto_3.2.bbappend
> 

Bruce,
I think these rc6 patches are still needed for linux-yocto_3.2.bbappend. And 
they are referenced in the sugarbay bsp 3.2 Yocto kernel as you note above. The 
commit I sent is for for v3.4 yocto kernel tree. 
Are you saying about dropping rc6 patches from the 3.2 kernel tree as well?

Nitin

> Cheers,
> 
> Bruce
> 
> >
> > Thanks,
> > Nitin
> >
> > The following changes since commit
> 3fd089debe624c642d7b4d9363f853021d1675b2:
> >
> >checkpoint dir: meta (2012-06-06 16:24:42 -0400)
> >
> > are available in the git repository at:
> >git://git.yoctoproject.org/linux-yocto-2.6.37-contrib nitin/meta
> >
> > http://git.yoctoproject.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h
> > =nitin/meta
> >
> > Nitin A Kamble (1):
> >rc6: remove rc6 patches for snb
> >
> >   .../features/tmp/rc6/rc6-kernel-params.patch   |   81 
> > 
> >   meta/cfg/kernel-cache/features/tmp/rc6/rc6.scc |5 -
> >   .../tmp/rc6/snb-disable-rc6p-fix-precedence.patch  |   26 --
> >   .../features/tmp/rc6/snb-disable-rc6p.patch|   39 --
> >   .../features/tmp/rc6/snb-enable-rc6.patch  |   54 -
> >   5 files changed, 0 insertions(+), 205 deletions(-)
> >   delete mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/rc6-
> kernel-params.patch
> >   delete mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/rc6.scc
> >   delete mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/snb-
> disable-rc6p-fix-precedence.patch
> >   delete mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/snb-
> disable-rc6p.patch
> >   delete mode 100644
> > meta/cfg/kernel-cache/features/tmp/rc6/snb-enable-rc6.patch
> >

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

Re: [yocto] [PATCH 0/1] remove snb rc6 patches from v3.4 kernel repository

[Kamble, Nitin A]

> > Bruce,
> > I think these rc6 patches are still needed for linux-yocto_3.2.bbappend.
> And they are referenced in the sugarbay bsp 3.2 Yocto kernel as you note
> above. The commit I sent is for for v3.4 yocto kernel tree.
> 
> Yes, of course it's for 3.4 .. that's where I merged it :)
> 
> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.4/log/?h=meta
> 
> > Are you saying about dropping rc6 patches from the 3.2 kernel tree as well?
> 
> I was more reminding for any updates to the BSP to 3.4 .. i.e. don't forget to
> drop it from the recipes when updating, sine it will thrown an error during
> patching.
> 
> Cheers,
> 
> Bruce
   I see your point now.  I have dropped them from 3.4 kernel recipe 1st to 
avoid patch application errors. Then we realized that these patches are not 
needed in the v3.4 kernel repository.

Nitin

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

Re: [yocto] [PATCH x32 Edison 0/2] Fixes for meta-x32 edison branch

[Kamble, Nitin A]

> -Original Message-
> From: Joshua Lock [mailto:joshua.l...@intel.com]
> Sent: Tuesday, June 05, 2012 5:46 PM
> To: yocto@yoctoproject.org
> Cc: Joshua Lock; Kamble, Nitin A
> Subject: [PATCH x32 Edison 0/2] Fixes for meta-x32 edison branch
> 
> The following patches are required to use the edison branch of meta-x32
> with the current edison branch of Poky.
> 
> The first change is required because the edison branch updated its openssl
> version some time ago for security fixes.
> 
> The gmp change is required so that gmp-native can be used by ppl.
> 
> Regards,
> Joshua
> 
> CC: Nitin Kamble 
> 
> The following changes since commit
> 78a8f65718b7ad7c93103a82026575687271cf5d:
> 
>   gmp: also built libgmpxx for gmp-native (2011-10-14 10:30:03 -0700)
> 
> are available in the git repository at:
>   git://github.com/incandescant/meta-x32.git josh/edison
>   https://github.com/incandescant/meta-x32
> 
> Joshua Lock (2):
>   openssl: update bbappend to match version in poky edison
>   gmp: Fix EXTRA_OECONF for native target
> 


Merged these 2 commits in to Edison branch of the meta-x32 layer.

Nitin

>  gmp/gmp_5.0.2.bbappend |2 +-
>  ...ssl_0.9.8r.bbappend => openssl_0.9.8s.bbappend} |0
>  2 files changed, 1 insertions(+), 1 deletions(-)  rename
> openssl/{openssl_0.9.8r.bbappend => openssl_0.9.8s.bbappend} (100%)
> 
> --
> 1.7.7.6

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

[yocto] [PATCH 0/7] move intel bsps to v3.4 kernel

[nitin . a . kamble]

From: Nitin A Kamble 

These commits move Intel BSPs to v3.4 kernel.
The crownbay v3.4 kernel is not quet ready yet, so for crown bay the default 
kerenl is still v3.2

The following changes since commit f5dcebe57832551219da048945237a7cf7bda369:

  linux-firmware: Fix FILESEXTRAPATHS typo (2012-06-20 13:12:12 -0700)

are available in the git repository at:
  git://git.yoctoproject.org/meta-intel-contrib nitin/work
  http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=nitin/work

Nitin A Kamble (7):
  FishRiver: add recipe extention for linux-yocto_3.4
  FishRiver: set v3.4 as the default kernel recipe version
  emenlow: add recipe extention for linux-yocto_3.4
  emenlow: set v3.4 as the default kernel recipe version
  sugarbay: add recipe extention for linux-yocto_3.4
  sugarbay: set v3.4 as the default kernel recipe version
  crownbay: add recipe extention for linux-yocto-3.4

 .../recipes-kernel/linux/linux-yocto_3.4.bbappend  |   15 +++
 meta-emenlow/conf/machine/emenlow.conf |2 +-
 .../recipes-kernel/linux/linux-yocto_3.4.bbappend  |8 
 meta-fishriver/conf/machine/fishriver.conf |2 +-
 .../recipes-kernel/linux/linux-yocto_3.4.bbappend  |8 
 meta-sugarbay/conf/machine/sugarbay.conf   |2 +-
 .../recipes-kernel/linux/linux-yocto_3.4.bbappend  |9 +
 7 files changed, 43 insertions(+), 3 deletions(-)
 create mode 100644 meta-crownbay/recipes-kernel/linux/linux-yocto_3.4.bbappend
 create mode 100644 meta-emenlow/recipes-kernel/linux/linux-yocto_3.4.bbappend
 create mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend
 create mode 100644 meta-sugarbay/recipes-kernel/linux/linux-yocto_3.4.bbappend

-- 
1.7.3.4

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

[yocto] [PATCH 1/7] FishRiver: add recipe extention for linux-yocto_3.4

[nitin . a . kamble]

From: Nitin A Kamble 

Tested this on FishRiver hardware, and it works as expected.

Signed-off-by: Nitin A Kamble 
---
 .../recipes-kernel/linux/linux-yocto_3.4.bbappend  |8 
 1 files changed, 8 insertions(+), 0 deletions(-)
 create mode 100644 meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend

diff --git a/meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend 
b/meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend
new file mode 100644
index 000..eaa6229
--- /dev/null
+++ b/meta-fishriver/recipes-kernel/linux/linux-yocto_3.4.bbappend
@@ -0,0 +1,8 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+COMPATIBLE_MACHINE_fishriver = "fishriver"
+KMACHINE_fishriver  = "fishriver"
+KBRANCH_fishriver  = "standard/fishriver"
+
+SRCREV_machine_pn-linux-yocto_fishriver ?= 
"49f1599b2ce0288599805b5364b895f5a9febb3e"
+SRCREV_meta_pn-linux-yocto_fishriver ?= 
"a8cf77018b0faa0d29f1483ff4e5a2034dc8edd5"
-- 
1.7.3.4

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

[yocto] [PATCH 2/7] FishRiver: set v3.4 as the default kernel recipe version

[nitin . a . kamble]

From: Nitin A Kamble 

Signed-off-by: Nitin A Kamble 
---
 meta-fishriver/conf/machine/fishriver.conf |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/meta-fishriver/conf/machine/fishriver.conf 
b/meta-fishriver/conf/machine/fishriver.conf
index 289e41d..ec2e87f 100644
--- a/meta-fishriver/conf/machine/fishriver.conf
+++ b/meta-fishriver/conf/machine/fishriver.conf
@@ -4,7 +4,7 @@
 #@DESCRIPTION: Machine configuration for Fish River Island systems
 # i.e. Z530/E660 + EG20T
 
-PREFERRED_VERSION_linux-yocto ?= "3.2%"
+PREFERRED_VERSION_linux-yocto ?= "3.4%"
 
 require conf/machine/include/tune-atom.inc
 require conf/machine/include/ia32-base.inc
-- 
1.7.3.4

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

[yocto] [PATCH 3/7] emenlow: add recipe extention for linux-yocto_3.4

[nitin . a . kamble]

From: Nitin A Kamble 

This is tested on the emenlow hardware, and it works as expected.

Signed-off-by: Nitin A Kamble 
---
 .../recipes-kernel/linux/linux-yocto_3.4.bbappend  |8 
 1 files changed, 8 insertions(+), 0 deletions(-)
 create mode 100644 meta-emenlow/recipes-kernel/linux/linux-yocto_3.4.bbappend

diff --git a/meta-emenlow/recipes-kernel/linux/linux-yocto_3.4.bbappend 
b/meta-emenlow/recipes-kernel/linux/linux-yocto_3.4.bbappend
new file mode 100644
index 000..2146864
--- /dev/null
+++ b/meta-emenlow/recipes-kernel/linux/linux-yocto_3.4.bbappend
@@ -0,0 +1,8 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+COMPATIBLE_MACHINE_emenlow = "emenlow"
+KMACHINE_emenlow  = "emenlow"
+KBRANCH_emenlow  = "standard/emenlow"
+
+SRCREV_machine_pn-linux-yocto_emenlow ?= 
"1ed16752ff068c2a3f33d78d8a53be32416fb56e"
+SRCREV_meta_pn-linux-yocto_emenlow ?= 
"a8cf77018b0faa0d29f1483ff4e5a2034dc8edd5"
-- 
1.7.3.4

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

[yocto] [PATCH 4/7] emenlow: set v3.4 as the default kernel recipe version

[nitin . a . kamble]

From: Nitin A Kamble 

Signed-off-by: Nitin A Kamble 
---
 meta-emenlow/conf/machine/emenlow.conf |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/meta-emenlow/conf/machine/emenlow.conf 
b/meta-emenlow/conf/machine/emenlow.conf
index 26ca43b..afb3866 100644
--- a/meta-emenlow/conf/machine/emenlow.conf
+++ b/meta-emenlow/conf/machine/emenlow.conf
@@ -4,7 +4,7 @@
 #@DESCRIPTION: Machine configuration for eMenlow based systems, like the
 # Webs-2120 box.
 
-PREFERRED_VERSION_linux-yocto ?= "3.2%"
+PREFERRED_VERSION_linux-yocto ?= "3.4%"
 
 require conf/machine/include/tune-atom.inc
 require conf/machine/include/ia32-base.inc
-- 
1.7.3.4

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