date:20170303


  jsut one of those things that starts to grate on me after a while
... while reading BSP guide, the text bounces back and forth between
"BSP Layer" and "BSP layer."

  personally, i'm not a huge fan of upper case (quelle surprise!), so
unless it's being used as a proper name, i think "BSP layer" is by far
the preferred style, and i'm happy to tweak the guide as i'm going
through it, unless there are massive objections.

  pretty sure i'm going to find at least a few things to adjust so i
can just fold that in with the rest. thoughts?

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


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

[yocto] BSP "sub-layer" examples -- better example than meta-intel?


  in current BSP Guide:

"Some layers function as a layer to hold other BSP layers. An example
of this type of layer is the meta-intel layer, which contains a number
of individual BSP sub-layers, as well as a directory named common/
full of common content across those layers. Another example is the
meta-yocto-bsp layer mentioned earlier."

  first, it seems meta-intel is not a great example anymore given its
restructuring -- it's just two layers:

  * meta-intel
  * meta-intel/meta-tlk

unlike what it used to be, so anyone want to suggest a better example
for that? (it *used* to be a great example of that, of course.)

  also, not sure how meta-yocto-bsp fits that description. it neither
contains sub-layers, nor is itself a sub-layer of a higher-level
layer. sure, it comes along as part of the checkout of "poky", but the
poky checkout itself is not a layer.

  so ... thoughts?

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


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

Re: [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi: Fix uImage build on 4.9.y and later

2017-03-03 Thread Paul Barker

On Sun, 19 Feb 2017 09:29:24 +
Paul Barker  wrote:

> On Sat, 18 Feb 2017 20:13:07 -0800
> Andrei Gherzan  wrote:
> 
> > On Sat, Feb 18, 2017 at 07:39:13PM +, p...@paulbarker.me.uk wrote:  
> > > From: Paul Barker 
> > >
> > > Signed-off-by: Paul Barker 
> > > ---
> > >  recipes-kernel/linux/linux-raspberrypi_4.9.bb | 5 +
> > >  recipes-kernel/linux/linux-raspberrypi_dev.bb | 5 +
> > >  2 files changed, 10 insertions(+)
> > >
> > > diff --git a/recipes-kernel/linux/linux-raspberrypi_4.9.bb 
> > > b/recipes-kernel/linux/linux-raspberrypi_4.9.bb
> > > index dcca369..b113674 100644
> > > --- a/recipes-kernel/linux/linux-raspberrypi_4.9.bb
> > > +++ b/recipes-kernel/linux/linux-raspberrypi_4.9.bb
> > > @@ -7,3 +7,8 @@ SRC_URI = 
> > > "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.9.y
> > > 
> > > file://0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch \
> > >  "
> > >  require linux-raspberrypi.inc
> > > +
> > > +# A LOADADDR is needed when building a uImage format kernel. This value 
> > > is not
> > > +# set by default in rpi-4.8.y and later branches so we need to provide it
> > > +# manually. This value unused if KERNEL_IMAGETYPE is not uImage.
> > > +KERNEL_EXTRA_ARGS += "LOADADDR=0x8000"
> > > diff --git a/recipes-kernel/linux/linux-raspberrypi_dev.bb 
> > > b/recipes-kernel/linux/linux-raspberrypi_dev.bb
> > > index bec0d23..e45903b 100644
> > > --- a/recipes-kernel/linux/linux-raspberrypi_dev.bb
> > > +++ b/recipes-kernel/linux/linux-raspberrypi_dev.bb
> > > @@ -7,3 +7,8 @@ SRC_URI = 
> > > "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.10.y
> > > 
> > > file://0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch \
> > >  "
> > >  require linux-raspberrypi.inc
> > > +
> > > +# A LOADADDR is needed when building a uImage format kernel. This value 
> > > is not
> > > +# set by default in rpi-4.8.y and later branches so we need to provide it
> > > +# manually. This value unused if KERNEL_IMAGETYPE is not uImage.
> > > +KERNEL_EXTRA_ARGS += "LOADADDR=0x8000"
> > 
> > Any reason not to set this in the machine configuration file?
> >   
> 
> It's not needed for the 4.4.y kernel series and I haven't tested it
> with that.
> 
> I've also opened an upstream bug which may lead to futher changes down
> the line: https://github.com/raspberrypi/linux/issues/1850
> 
> So I think for now I'd just keep the setting in the affected recipes.
> We can tidy it up in the future if we drop 4.4.y and based on any
> response to the upstream bug.

Ping on this. I don't feel strongly about where KERNEL_EXTRA_ARGS is
set so we can either merge this as-is or I can move it to the machine
conf file and test with the 4.4.y kernel.

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

[yocto] purpose of "README.sources" file, and why does meta-intel have one?


  still in BSP Guide:

"Note
  If the BSP's binary directory is missing or the directory has no
  images, an existing README.sources file is meaningless."

yet the meta-intel layer has that file but no binary/ directory, so is
the above the proper explanation of README.sources?

  i have about 20 layers checked out, and *very* few of them have a
README.sources file although, to be fair, they also don't have
"binary" directories. it seems like not a lot of layers take advantage
of that feature.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


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

[yocto] BSP Guide: what means "bsp_name.conf"?


  in section 1.2.9:

"Suppose you are using the linux-yocto_4.4.bb recipe to build the
kernel. In other words, you have selected the kernel in your
bsp_name.conf file by adding these types of statements: ..."
^

  um ... what? and just below that:

"Note
 When the preferred provider is assumed by default, the
 PREFERRED_PROVIDER statement does not appear in the bsp_name.conf
 file.   ^

  can i assume those should read "machine.conf"? because i have no
idea what "bsp_name.conf" refers to as it is.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


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

[yocto] [PATCH] yocto-docs: Various cleanup/tweaking to BSP Guide


Collection of minor cleanups to BSP Guide:

* Standardize on spelling of "BSP layer" rather than "BSP Layer"
* Describe YP reference boards in more detail (architecture, ...)
* Bump up several references to kernel "4.4" to "4.9"
* Replace meaningless "bsp_name.conf" with "machine.conf"
* Add a few more sample components to the BSP layer structure

Signed-off-by: Robert P. J. Day 

---

diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index 4d0ace0..d81cb46 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -19,7 +19,7 @@
 

 
-This guide presents information about BSP Layers, defines a 
structure for components
+This guide presents information about BSP layers, defines a 
structure for components
 so that BSPs follow a commonly understood layout, discusses how to 
customize
 a recipe for a BSP, addresses BSP licensing, and provides 
information that
 shows you how to create and manage a
@@ -33,7 +33,7 @@
 
 A BSP consists of a file structure inside a base directory.
 Collectively, you can think of the base directory, its file 
structure,
-and the contents as a BSP Layer.
+and the contents as a BSP layer.
 Although not a strict requirement, layers in the Yocto Project 
use the
 following well-established naming convention:
 
@@ -77,8 +77,10 @@
 meta-yocto-bsp layer is part of the
 shipped poky repository.
 The meta-yocto-bsp layer maintains several
-BSPs such as the Beaglebone, EdgeRouter, and generic versions 
of
-both 32 and 64-bit IA machines.
+BSPs such as the ARM-based Beaglebone,
+MIPS64-based Ubiquiti Networks EdgeRouter,
+PowerPC-based Freescale MPC8315E-RDB,
+and generic versions of both 32 and 64-bit IA machines.
 

 
@@ -94,7 +96,7 @@
 
 The layer's base directory
 (meta-bsp_name)
-is the root of the BSP Layer.
+is the root of the BSP layer.
 This root is what you add to the
 BBLAYERS
 variable in the conf/bblayers.conf file 
found in the
@@ -189,7 +191,7 @@

 
 Below is the common form for the file structure inside a BSP 
Layer.
-While you can use this basic form for the standard, realize 
that the actual structures
+While you can use this basic form as your standard, realize 
that the actual structures
 for specific BSPs could differ.

 
@@ -200,6 +202,9 @@
  
meta-bsp_name/binary/bootable_images
  meta-bsp_name/conf/layer.conf
  meta-bsp_name/conf/machine/*.conf
+ meta-bsp_name/conf/machine/include/*
+ meta-bsp_name/files/*
+ meta-bsp_name/classes/*
  meta-bsp_name/recipes-bsp/*
  meta-bsp_name/recipes-core/*
  meta-bsp_name/recipes-graphics/*
@@ -663,21 +668,21 @@
 the 
meta-bsp_name/recipes-kernel/linux
 directory).
 
 
-Suppose you are using the 
linux-yocto_4.4.bb recipe to build
+Suppose you are using the 
linux-yocto_4.9.bb recipe to build
 the kernel.
 In other words, you have selected the kernel in your
-bsp_name.conf 
file by adding these types
+machine.conf 
file by adding these types
 of statements:
 
  PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
- PREFERRED_VERSION_linux-yocto ?= "4.4%"
+ PREFERRED_VERSION_linux-yocto ?= "4.9%"
 
 
 When the preferred provider is assumed by default, the
 PREFERRED_PROVIDER statement does not 
appear in the
-
bsp_name.conf file.
+
machine.conf file.
 
-You would use the linux-yocto_4.4.bbappend
+You would then create a 
linux-yocto_4.9.bbappend
 file to append specific BSP settings to the kernel, thus
 configuring the kernel for your particular BSP.
 
@@ -686,7 +691,7 @@
 As an example, consider the following append file
 used by the BSPs in meta-yocto-bsp:
 
- meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend
+ meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.9.bbappend
 
 The following listing shows the file.
 Be aware that the actual commit ID strings in this

-- 


Robert P. J. Day

[yocto] any rumblings about a newer YP powerpc reference board than mpc8315e-rdb?


  it seems of limited value for YP to have a powerpc reference board,
mpc8315e-rdb, that is essentially impossible to procure. is there any
effort being made to look around for a newer powerpc reference board
that people could actually buy?

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


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

Re: [yocto] any rumblings about a newer YP powerpc reference board than mpc8315e-rdb?

On 3 March 2017 at 13:24, Robert P. J. Day  wrote:

>   it seems of limited value for YP to have a powerpc reference board,
> mpc8315e-rdb, that is essentially impossible to procure. is there any
> effort being made to look around for a newer powerpc reference board
> that people could actually buy?
>

Do you have any suggestions?

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

Re: [yocto] BSP "sub-layer" examples -- better example than meta-intel?

On 3 March 2017 at 10:59, Robert P. J. Day  wrote:

>   also, not sure how meta-yocto-bsp fits that description. it neither
> contains sub-layers, nor is itself a sub-layer of a higher-level
> layer. sure, it comes along as part of the checkout of "poky", but the
> poky checkout itself is not a layer.
>

meta-yocto-bsp being a sub-layer in the meta-yocto repository, I guess.

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

Re: [yocto] BSP "sub-layer" examples -- better example than meta-intel?

On Fri, 3 Mar 2017, Burton, Ross wrote:

> On 3 March 2017 at 10:59, Robert P. J. Day  wrote:
>     also, not sure how meta-yocto-bsp fits that description. it neither
>   contains sub-layers, nor is itself a sub-layer of a higher-level
>   layer. sure, it comes along as part of the checkout of "poky", but the
>   poky checkout itself is not a layer.
>
>
> meta-yocto-bsp being a sub-layer in the meta-yocto repository, I guess.

  oh, i understand how the poky layers are structured, but i was
quoting from the para in the bsp guide that starts, "Some layers
function as a layer to hold other BSP layers." and, technically
speaking, that is not what is happening there.

rday

-- 

Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] any rumblings about a newer YP powerpc reference board than mpc8315e-rdb?

On Fri, 3 Mar 2017, Burton, Ross wrote:

> On 3 March 2017 at 13:24, Robert P. J. Day  wrote:
>     it seems of limited value for YP to have a powerpc reference
>   board, mpc8315e-rdb, that is essentially impossible to
>   procure. is there any effort being made to look around for a
>   newer powerpc reference board that people could actually buy?
>
> Do you have any suggestions?

  not at the moment ... perhaps the powerpc or freescale folks can
weigh in. i'm not a powerpc expert, but it does seem pointless to have
a reference board that no one can get.

rday

-- 

Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] any rumblings about a newer YP powerpc reference board than mpc8315e-rdb?

2017-03-03 Thread Bruce Ashfield


On 2017-03-03 8:41 AM, Burton, Ross wrote:


On 3 March 2017 at 13:24, Robert P. J. Day mailto:rpj...@crashcourse.ca>> wrote:

  it seems of limited value for YP to have a powerpc reference board,
mpc8315e-rdb, that is essentially impossible to procure. is there any
effort being made to look around for a newer powerpc reference board
that people could actually buy?


Do you have any suggestions?


Indeed.

I've looked, Josh looked at one point, and we even met with various
companies about their upcoming boards.

Nothing has ever panned out, so we stick with the existing reference
BSP.

Assuming we could acquire a new board, I'd be happy to replace the
existing reference.

Bruce



Ross




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

[yocto] [PATCH] deprecated.bbclass: Document PNDEPRECATED variable

2017-03-03 Thread Joe MacDonald

Based on the blacklist behaviour, recipes can be tagged as deprecated.
Such recipes will produce a warning message when included in a build but
unlike blacklisted recipes, the build will continue.  Update the
documentation to support this new variable.

Signed-off-by: Joe MacDonald 
---

This should only be added if or when the bbclass is merged into meta/

-J.

 documentation/ref-manual/ref-classes.xml   | 28 
 documentation/ref-manual/ref-variables.xml | 28 
 2 files changed, 56 insertions(+)

diff --git a/documentation/ref-manual/ref-classes.xml 
b/documentation/ref-manual/ref-classes.xml
index f7b1126..6088b44 100644
--- a/documentation/ref-manual/ref-classes.xml
+++ b/documentation/ref-manual/ref-classes.xml
@@ -632,6 +632,34 @@
 
 
 
+
+deprecated.bbclass
+
+
+The deprecated class identifies recipes
+that for one reason or another are being considered for removal
+from their current layer. It may be due to persistent, known
+issues with the package, that there are newer, more feature-rich
+alternatives available in the same layer or that the recipe is
+no longer needed.  The recipe should provide a reason for the
+depercation and a suggestion to consumers of the recipe as to how
+to proceed.
+To use this class, inherit the class globally and set
+PNDEPRECATED
+for each recipe you intend to deprecate.
+Specify the PN
+value as a variable flag (varflag) and provide a reason, which is
+reported, if the package is requested to be built as the value.
+For example, if you want to deprecate a recipe called "exoticware",
+you add the following to your local.conf
+or distribution configuration:
+
+ INHERIT += "deprecated"
+ PNDEPRECATED[exoticware] = "'exoticware' is considered obsolete and has 
been replaced by 'standardware'.  'exoticware' may not appear in future 
releases."
+
+
+
+
 
 devshell.bbclass
 
diff --git a/documentation/ref-manual/ref-variables.xml 
b/documentation/ref-manual/ref-variables.xml
index f79cdd2..629d167 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -9920,6 +9920,34 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = 
"${INC_PR}.3"
 
 
 
+PNDEPRECATED
+
+PNDEPRECATED[doc] = "Lists recipes that may be removed in a 
future release or have more actively maintained alternatives."
+
+
+
+
+Lists recipes that may be removed in a future release or
+have more actively maintained alternatives.
+This variable works in conjunction with the
+deprecated
+class, which the recipe must inherit globally.
+
+
+
+To identify a recipe as deprecated, inherit the class
+globally and use the variable in your
+local.conf file.
+Here is an example that will show a warning when
+myrecipe is included in a project:
+
+ INHERIT += "deprecated"
+ PNDEPRECATED[myrecipe] = "Recipe is no longer actively maintained, you 
should consider using 'mynewrecipe' as an alternative."
+
+
+
+
+
 POPULATE_SDK_POST_HOST_COMMAND
 
 POPULATE_SDK_POST_HOST_COMMAND[doc] = "Specifies a list of 
functions to call once the OpenEmbedded build system has created host part of 
the SDK."
-- 
1.9.1

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

Re: [yocto] any rumblings about a newer YP powerpc reference board than mpc8315e-rdb?

On Fri, 3 Mar 2017, Andy Pont wrote:

> Ross Burton wrote...
>
> >> it seems of limited value for YP to have a powerpc reference board,
> >> mpc8315e-rdb, that is essentially impossible to procure. is there any
> >> effort being made to look around for a newer powerpc reference board
> >> that people could actually buy?
> >
> >Do you have any suggestions?
>
> If we are being strictly pedantic then is isn't PowerPC (at least in
> the world that is Freescale / NXP / Whoever they are this week).
>
> I would look at one of the P10xx series QorIQ boards.  Digi-Key list
> the P1021RDB-PC-ND and P1024RDB-PA-ND as being active parts which
> are either single or dual e500 cores.

  i would start with the machine definition files in the meta-fsl-ppc
layer:

http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc/tree/conf/machine

and see what looks promising. however, IIRC, one of the properties of
a YP reference board is that it shouldn't be stupid, crazy expensive,
no? so anything climbing above $500 (USD) might not be an option.
people used to spending $60 for a beaglebone black might have a
seizure to suddenly realize they need $500 for a powerpc reference
board.

rday

-- 

Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

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

Re: [yocto] any rumblings about a newer YP powerpc reference board than mpc8315e-rdb?

2017-03-03 Thread Andy Pont

Ross Burton wrote...

>> it seems of limited value for YP to have a powerpc reference board,
>> mpc8315e-rdb, that is essentially impossible to procure. is there any
>> effort being made to look around for a newer powerpc reference board
>> that people could actually buy?
>
>Do you have any suggestions?

If we are being strictly pedantic then is isn't PowerPC (at least in the world 
that is Freescale / NXP / Whoever they are this week).

I would look at one of the P10xx series QorIQ boards.  Digi-Key list the 
P1021RDB-PC-ND and P1024RDB-PA-ND as being active parts which are either single 
or dual e500 cores.

-Andy

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

Re: [yocto] any rumblings about a newer YP powerpc reference board than mpc8315e-rdb?

2017-03-03 Thread Bruce Ashfield

On Fri, Mar 3, 2017 at 9:07 AM, Robert P. J. Day 
wrote:

> On Fri, 3 Mar 2017, Andy Pont wrote:
>
> > Ross Burton wrote...
> >
> > >> it seems of limited value for YP to have a powerpc reference board,
> > >> mpc8315e-rdb, that is essentially impossible to procure. is there any
> > >> effort being made to look around for a newer powerpc reference board
> > >> that people could actually buy?
> > >
> > >Do you have any suggestions?
> >
> > If we are being strictly pedantic then is isn't PowerPC (at least in
> > the world that is Freescale / NXP / Whoever they are this week).
> >
> > I would look at one of the P10xx series QorIQ boards.  Digi-Key list
> > the P1021RDB-PC-ND and P1024RDB-PA-ND as being active parts which
> > are either single or dual e500 cores.
>
>   i would start with the machine definition files in the meta-fsl-ppc
> layer:
>
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc/tree/conf/machine
>
> and see what looks promising. however, IIRC, one of the properties of
> a YP reference board is that it shouldn't be stupid, crazy expensive,
> no? so anything climbing above $500 (USD) might not be an option.
>

Correct. Being around 100 bucks USD was always our bar in the past, since
even if you can buy one .. not being able to afford it doesn't help.

Not that we expect a lot of people are out buying these reference boards,
but even companies were balking at buying expensive options ... so forget
individuals ever getting one.

Bruce


> people used to spending $60 for a beaglebone black might have a
> seizure to suddenly realize they need $500 for a powerpc reference
> board.
>
> rday
>
> --
>
> 
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
>
> Twitter:   http://twitter.com/rpjday
> LinkedIn:   http://ca.linkedin.com/in/rpjday
> 
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] any rumblings about a newer YP powerpc reference board than mpc8315e-rdb?

2017-03-03 Thread Andy Pont

Robert wrote...

> > I would look at one of the P10xx series QorIQ boards.  Digi-Key list
> > the P1021RDB-PC-ND and P1024RDB-PA-ND as being active parts which
> > are either single or dual e500 cores.
> 
>   i would start with the machine definition files in the meta-fsl-ppc
> layer:
> 
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc/tree/conf/machine
> 
> and see what looks promising. however, IIRC, one of the properties of
> a YP reference board is that it shouldn't be stupid, crazy expensive,
> no? so anything climbing above $500 (USD) might not be an option.
> people used to spending $60 for a beaglebone black might have a
> seizure to suddenly realize they need $500 for a powerpc reference
> board.

Using Digi-Key UK as my reference, they list the MPC8308-RDB-ND and
MPC8313E-RDBC-ND as being available for less than £250 which makes them sub
$300 which is probably the best price I have seen for Power Architecture
reference boards.

Granted, they are still more expensive than a BBB, RPi or something like
that but cheap compared to >$2,000 reference boards we used to have to buy
in the old days!

-Andy



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

Re: [yocto] any rumblings about a newer YP powerpc reference board than mpc8315e-rdb?

On Fri, 3 Mar 2017, Andy Pont wrote:

> Robert wrote...
>
> > > I would look at one of the P10xx series QorIQ boards.  Digi-Key list
> > > the P1021RDB-PC-ND and P1024RDB-PA-ND as being active parts which
> > > are either single or dual e500 cores.
> >
> >   i would start with the machine definition files in the meta-fsl-ppc
> > layer:
> >
> > http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc/tree/conf/machine
> >
> > and see what looks promising. however, IIRC, one of the properties of
> > a YP reference board is that it shouldn't be stupid, crazy expensive,
> > no? so anything climbing above $500 (USD) might not be an option.
> > people used to spending $60 for a beaglebone black might have a
> > seizure to suddenly realize they need $500 for a powerpc reference
> > board.
>
> Using Digi-Key UK as my reference, they list the MPC8308-RDB-ND and
> MPC8313E-RDBC-ND as being available for less than £250 which makes
> them sub $300 which is probably the best price I have seen for Power
> Architecture reference boards.
>
> Granted, they are still more expensive than a BBB, RPi or something
> like that but cheap compared to >$2,000 reference boards we used to
> have to buy in the old days!

  in canada, distributors are charging over $400 (CAD) for either of
those, which you'd normally think would be outside the bounds for a YP
reference board, but it may be that that's what you have to accept for
even an inexpensive PPC dev kit.

  a better question is, what PPC platform are people working with
these days? it seems pointless to select an older technology just
because it's cheaper, only to have no one buy it because it's useless.
so who out there is working with powerpc, and what PPC platform would
have enough general interest that it would be worth making the YP
reference board?

  or, perhaps (god forbid) there's no actual point in even *having* a
powerpc reference board?

rday

-- 

Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] any rumblings about a newer YP powerpc reference board than mpc8315e-rdb?

2017-03-03 Thread Stefano Babic

Hi Robert,

On 03/03/2017 15:53, Robert P. J. Day wrote:
> On Fri, 3 Mar 2017, Andy Pont wrote:
> 
>> Robert wrote...
>>
 I would look at one of the P10xx series QorIQ boards.  Digi-Key list
 the P1021RDB-PC-ND and P1024RDB-PA-ND as being active parts which
 are either single or dual e500 cores.
>>>
>>>   i would start with the machine definition files in the meta-fsl-ppc
>>> layer:
>>>
>>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc/tree/conf/machine
>>>
>>> and see what looks promising. however, IIRC, one of the properties of
>>> a YP reference board is that it shouldn't be stupid, crazy expensive,
>>> no? so anything climbing above $500 (USD) might not be an option.
>>> people used to spending $60 for a beaglebone black might have a
>>> seizure to suddenly realize they need $500 for a powerpc reference
>>> board.
>>
>> Using Digi-Key UK as my reference, they list the MPC8308-RDB-ND and
>> MPC8313E-RDBC-ND as being available for less than £250 which makes
>> them sub $300 which is probably the best price I have seen for Power
>> Architecture reference boards.
>>
>> Granted, they are still more expensive than a BBB, RPi or something
>> like that but cheap compared to >$2,000 reference boards we used to
>> have to buy in the old days!
> 
>   in canada, distributors are charging over $400 (CAD) for either of
> those, which you'd normally think would be outside the bounds for a YP
> reference board, but it may be that that's what you have to accept for
> even an inexpensive PPC dev kit.
> 
>   a better question is, what PPC platform are people working with
> these days? it seems pointless to select an older technology just
> because it's cheaper, only to have no one buy it because it's useless.
> so who out there is working with powerpc, and what PPC platform would
> have enough general interest that it would be worth making the YP
> reference board?
> 

One more question is regarding the EOL of some of these processors.
P1010/14 reaches EOL next year, P1021/23 in two years. It should be also
avoided to take a board that has a very short life time. The MPC8313
reached EOL last year :-(.

>   or, perhaps (god forbid) there's no actual point in even *having* a
> powerpc reference board?

IMHO it was always a good point for me to have a reference for e500. I
mainly had projects with P202x, QorIQ.

Best regards,
Stefano

-- 
Meet DENX at the Embedded World Trade Show
14 Mar - 16 Mar 2017, Nuremberg Trade Fair Centre, Hall 4, Booth 581
--
=
DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
=
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto's framebuffer-vncserver

On 3 March 2017 at 16:04, Peter Balazovic  wrote:

> I am not successfull to include it into my image, here is a part of a log
> build:
>
> | ../git/configure: line 13581: syntax error near unexpected token `GTK,'
> | ../git/configure: line 13581: `PKG_CHECK_MODULES(GTK, gtk+-2.0,,:)'
> | NOTE: The following config.log files may provide further information.
> | WARNING: exit code 1 from a shell command.
> | NOTE: /mnt/work/Linux/build-fb/tmp/work/aarch64-poky-linux/
> libvncserver/git-r1+gitrAUTOINC+5b322f523f/build/config.log
> | ERROR: configure failed
> | ERROR: Function failed: do_configure (log file is located at
> /mnt/work/Linux//build-fb/tmp/work/aarch64-poky-linux/libvncserver/git-r1+
> gitrAUTOINC+5b322f523f/temp/log.do_configure.11798)
> ERROR: Task 866 (/mnt/work/Linu//sources/meta-
> openembedded/meta-oe/recipes-graphics/famebuffer-vnc/libvncserver_git.bb,
> do_configure) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 5407 tasks of which 5406 didn't need to be
> rerun and 1 failed.
>
> Does anybode have idea where problem might be?
>

Inherit pkgconfig in your recipe.

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

[yocto] Yocto's framebuffer-vncserver

Hello all,

I have a question to Yocto experts here. I have an OpenGL application which
runs on embedded Yotco Linux with framebuffer graphical backend.
I''d like to run and display application remotely on local Desktop. For X11
graphical backend I use x11vnc and now I am looking for a way to do it
similarly for framebuffer backend.

I found only this https://gist.github.com/gkos/9ed87cad62d72c599761
framebuffer-vncserver. Is there any other Yocto recipe for vnc server for
framebuffer backend than this?

I am not successfull to include it into my image, here is a part of a log
build:

| ../git/configure: line 13581: syntax error near unexpected token `GTK,'
| ../git/configure: line 13581: `PKG_CHECK_MODULES(GTK, gtk+-2.0,,:)'
| NOTE: The following config.log files may provide further information.
| WARNING: exit code 1 from a shell command.
| NOTE:
/mnt/work/Linux/build-fb/tmp/work/aarch64-poky-linux/libvncserver/git-r1+gitrAUTOINC+5b322f523f/build/config.log
| ERROR: configure failed
| ERROR: Function failed: do_configure (log file is located at
/mnt/work/Linux//build-fb/tmp/work/aarch64-poky-linux/libvncserver/git-r1+gitrAUTOINC+5b322f523f/temp/log.do_configure.11798)
ERROR: Task 866
(/mnt/work/Linu//sources/meta-openembedded/meta-oe/recipes-graphics/famebuffer-vnc/
libvncserver_git.bb, do_configure) failed with exit code '1'
NOTE: Tasks Summary: Attempted 5407 tasks of which 5406 didn't need to be
rerun and 1 failed.

Does anybode have idea where problem might be?

Thank you.

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

Re: [yocto] Yocto's framebuffer-vncserver

actually thare are two recpies:

framebuffer-vncserver_git.bb

...
inherit cmake
...

libvncserver_git.bb

...
inherit autotools
...


where to "inherit" ?




On Fri, Mar 3, 2017 at 5:06 PM, Burton, Ross  wrote:

>
> On 3 March 2017 at 16:04, Peter Balazovic 
> wrote:
>
>> I am not successfull to include it into my image, here is a part of a log
>> build:
>>
>> | ../git/configure: line 13581: syntax error near unexpected token `GTK,'
>> | ../git/configure: line 13581: `PKG_CHECK_MODULES(GTK, gtk+-2.0,,:)'
>> | NOTE: The following config.log files may provide further information.
>> | WARNING: exit code 1 from a shell command.
>> | NOTE: /mnt/work/Linux/build-fb/tmp/work/aarch64-poky-linux/libvncs
>> erver/git-r1+gitrAUTOINC+5b322f523f/build/config.log
>> | ERROR: configure failed
>> | ERROR: Function failed: do_configure (log file is located at
>> /mnt/work/Linux//build-fb/tmp/work/aarch64-poky-linux/libvnc
>> server/git-r1+gitrAUTOINC+5b322f523f/temp/log.do_configure.11798)
>> ERROR: Task 866 (/mnt/work/Linu//sources/meta-
>> openembedded/meta-oe/recipes-graphics/famebuffer-vnc/libvncserver_git.bb,
>> do_configure) failed with exit code '1'
>> NOTE: Tasks Summary: Attempted 5407 tasks of which 5406 didn't need to be
>> rerun and 1 failed.
>>
>> Does anybode have idea where problem might be?
>>
>
> Inherit pkgconfig in your recipe.
>
> Ross
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto's framebuffer-vncserver

I inherited for

libvncserver_git.bb

...
inherit autotools pkgconfig


| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_open'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_read'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_get_algo_dlen'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_write'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_ctl'
| collect2: error: ld returned 1 exit status
| Makefile:510: recipe for target 'filetransfer' failed
| make[3]: *** [filetransfer] Error 1
| make[3]: *** Waiting for unfinished jobs
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_open'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_read'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_get_algo_dlen'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_write'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_ctl'
| collect2: error: ld returned 1 exit status
| Makefile:542: recipe for target 'simple' failed
| make[3]: *** [simple] Error 1
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_open'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_read'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_get_algo_dlen'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_write'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_ctl'
| collect2: error: ld returned 1 exit status
| Makefile:550: recipe for target 'storepasswd' failed
| make[3]: *** [storepasswd] Error 1
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_open'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_read'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_get_algo_dlen'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_write'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_ctl'
| collect2: error: ld returned 1 exit status
| Makefile:502: recipe for target 'colourmaptest' failed
| make[3]: *** [colourmaptest] Error 1
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_open'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_read'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_get_algo_dlen'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_write'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_ctl'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_open'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_read'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_get_algo_dlen'
| ../libvncserver/.libs/libvncserver.so:collect2: error: ld returned 1 exit
status
|  undefined reference to `gcry_md_write'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_ctl'
| collect2: error: ld returned 1 exit status
| Makefile:534: recipe for target 'repeater' failed
| make[3]: *** [repeater] Error 1
| Makefile:546: recipe for target 'simple15' failed
| make[3]: *** [simple15] Error 1
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_open'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_read'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_get_algo_dlen'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_write'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_ctl'
| collect2: error: ld returned 1 exit status
| Makefile:526: recipe for target 'pnmshow24' failed
| make[3]: *** [pnmshow24] Error 1
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_open'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_read'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_get_algo_dlen'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_write'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_ctl'
| collect2: error: ld returned 1 exit status
| Makefile:498: recipe for target 'camera' failed
| make[3]: *** [camera] Error 1
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_open'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_read'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_get_algo_dlen'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_write'
| ../libvncserver/.libs/libvncserver.so: undefined reference to
`gcry_md_ctl'
| collect2: error: ld returned 1 exit status
| Makefile:490: recipe for target 'backchannel' failed
| make[3]: *** [backchannel] Error 1
| ../libvncserver/.libs/libvncserver.so:

Re: [yocto] Yocto's framebuffer-vncserver

On 3 March 2017 at 16:23, Peter Balazovic  wrote:

> | ../libvncserver/.libs/libvncserver.so: undefined reference to
> `gcry_md_open'
>

So many possibilities.  Is gcry_* something that is also built by
libvncserver? If so then it's link order related and you'll need to fix the
makefiles.  If it's an external library then you'll need to add that to
DEPENDS.

It looks like you're using a very old meta-oe though, the current meta-oe
has libvncserver 0.9.10:

http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-graphics/libvncserver/libvncserver_0.9.10.bb

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

[yocto] [meta-raspberrypi][PATCH V2] linux-raspberrypi_4.9.bb: Update to 4.9.13

2017-03-03 Thread Khem Raj

Signed-off-by: Khem Raj 
---
 recipes-kernel/linux/linux-raspberrypi_4.9.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-kernel/linux/linux-raspberrypi_4.9.bb 
b/recipes-kernel/linux/linux-raspberrypi_4.9.bb
index dcca369..effa859 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.9.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.9.bb
@@ -1,8 +1,8 @@
 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
 
-LINUX_VERSION ?= "4.9.10"
+LINUX_VERSION ?= "4.9.13"
 
-SRCREV = "095c4480e1f623bdc8a221a171ef13b2223706b1"
+SRCREV = "935c7ce84c982a26f567a03a58a1537424569938"
 SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.9.y \

file://0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch \
 "
-- 
2.12.0

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

Re: [yocto] Yocto's framebuffer-vncserver