Re: [meta-freescale] [Documentation][PATCH 4/5] RN: Update version to 2.2 (Morty)

[Thomas Thorne]

More strange new-line additions here too:

diff --git a/release-notes/source/known-issues.rst 
b/release-notes/source/known-issues.rst
index 71e71ed..0d34019 100644
--- a/release-notes/source/known-issues.rst
+++ b/release-notes/source/known-issues.rst
@@ -40,7 +40,7 @@ Known Issues
Open

In order to see the current bug list, please use following URL:
-   https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=meta-fsl-arm
+   
+ https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=meta-freesca
+ le

This also removes an indent.  Was an editor trying to automcatically fit C/C++ 
styling to non-source code?  

Thomas A. F. Thorne  Software Engineer  Net2Edge

-Original Message-
From: meta-freescale-boun...@yoctoproject.org 
[mailto:meta-freescale-boun...@yoctoproject.org] On Behalf Of Fabio Berton
Sent: 09 November 2016 17:30
To: meta-freescale@yoctoproject.org
Subject: [meta-freescale] [Documentation][PATCH 4/5] RN: Update version to 2.2 
(Morty)

  - Update FSL layers names
  - Update Yocto Project Bugzilla url address
  - Add FSLC distros description

Signed-off-by: Fabio Berton 
---
 release-notes/README  |  4 ++--
 release-notes/source/bsp-scope.rst| 24 
 release-notes/source/conf.py  |  6 +++---
 release-notes/source/distros.inc  |  4 
 release-notes/source/introduction.rst |  7 ---  
release-notes/source/known-issues.rst |  4 ++--  
release-notes/source/source-code.rst  |  9 +  
release-notes/source/test-results.rst |  2 +-
 release-notes/source/variables.inc|  2 +-
 9 files changed, 38 insertions(+), 24 deletions(-)  create mode 100644 
release-notes/source/distros.inc

diff --git a/release-notes/README b/release-notes/README index e1b7c9e..9665ea3 
100644
--- a/release-notes/README
+++ b/release-notes/README
@@ -37,8 +37,8 @@ Here's an example:
   $ ./bitbake-metadata2doc.sh ~/src/fsl-community-bsp ~/src/gitdm 1.5 1.6
 
 By default, bitbake-metadata2doc.sh collects data out of bitbake's -metadata 
for all machines it can find in the meta-fsl-arm and -meta-fsl-arm-extra 
layers.  You can restrict the machines to collect
+metadata for all machines it can find in the meta-freescale and 
+meta-freescale-3erparty. You can restrict the machines to collect
 data from by setting the MACHINES variable in your environment.
 
 bitbake-metadata2doc.sh will write its output to release-note's `source'
diff --git a/release-notes/source/bsp-scope.rst 
b/release-notes/source/bsp-scope.rst
index f0f0f74..97ca49d 100644
--- a/release-notes/source/bsp-scope.rst
+++ b/release-notes/source/bsp-scope.rst
@@ -4,14 +4,14 @@
 ***
 The scope of the |project_name| includes the meta layers:
 
- * `meta-fsl-arm 
`_:
-   provides the base support and Freescale ARM reference boards;
- * `meta-fsl-arm-extra 
`_:
+ * `meta-freescale 
`_:
+   provides the base support and Freescale ARM and PPC reference 
+ boards;
+ * `meta-freescale-3rdparty 
`_:
provides support for 3rd party and partner boards;
- * `meta-fsl-demos 
`_:
-   provides images recipes, demo recipes, and packagegroups used to easy the
-   development with Yocto Project.
- * `Documentation `_:
+ * `meta-freescale-distro 
`_:
+   provides distros support, images recipes, demo recipes, and packagegroups
+   used to easy the development with Yocto Project.
+ * `Documentation `_:
provides the source code for |project_name| Release Notes (RN), User Guide
(UG) and Frequently Asked Questions (FAQ)
 
@@ -36,8 +36,8 @@ regular open source licenses (GPLv2 for example).
 
 The close sourced packages are released under the Freescale License (known as  
EULA). Each package has a copy of EULA inside itself and a copy of the EULA 
text -is also included inside **meta-fsl-arm** root dir 
-(``sources/meta-fsl-arm/EULA``).
+is also included inside **meta-freescale** root dir 
+(``sources/meta-freescale/EULA``).
 
 The |project_name| handles the EULA acceptance by prompting user to read and  
accept EULA text at the very first environment setup. It is user's duty to read 
@@ -107,8 +107,8 @@ Machine Maintainers
 ---
 
 Since |project_name| Release 1.6 (Daisy), the maintainer field in machine 
-configuration files of **meta-fsl-arm** and **meta-fsl-arm-extra** is 
mandatory -for any new board to be added.
+configuration files of **meta-freescale** and 
+**meta-freescale-3rdparty** is mandatory for any new board to be 

Re: [meta-freescale] [Documentation][PATCH 1/5] scripts: Update to version 2.2 (Morty)

[Thomas Thorne]

Patch looks OK at link.

I wonder were the extra line breaks came from.  As long as the committed code 
ends up OK that is what matters but it is a bit confusing.

Thomas A. F. Thorne<mailto:thomas.tho...@net2edge.com>  Software Engineer  
Net2Edge<http://www.net2edge.com/>

From: Fabio Berton [mailto:fabio.ber...@ossystems.com.br]
Sent: 10 November 2016 11:57
To: Thomas Thorne <thomas.tho...@net2edge.com>
Cc: meta-freescale@yoctoproject.org
Subject: Re: [meta-freescale] [Documentation][PATCH 1/5] scripts: Update to 
version 2.2 (Morty)

Hi Thomas,
Check this link https://patchwork.openembedded.org/patch/133740/

I don't know what happened, but my patch is fine and your answer has line 
breaks. Anyway, check patchwork link.

On Thu, Nov 10, 2016 at 8:03 AM, Thomas Thorne 
<thomas.tho...@net2edge.com<mailto:thomas.tho...@net2edge.com>> wrote:
I am almost certain this line change breaks the Python code:

--- a/scripts/bitbake-metadata2doc.py
+++ b/scripts/bitbake-metadata2doc.py
@@ -112,8 +112,8 @@ def write_fsl_community_bsp_supported_kernels(data, 
out_dir):
 kernel = board_data['recipes']['virtual/kernel']
 recipe = kernel['recipe']
 recipe_file = kernel['file']
-if (('/sources/meta-fsl-arm/' in recipe_file) or \
-('/sources/meta-fsl-arm-extra/' in recipe_file)) and \
+if (('/sources/meta-freescale/' in recipe_file) or \
+('/sources/meta-freescale-3rdparty/' in recipe_file))
+ and \

That looks like \ are used for line continuation but an extra new line is being 
added before the "and \"


I am more confident about the .sh files:
$machines; do
 cd $yocto_dir
 echo "Using $build_dir as build directory"
-MACHINE=$machine . ./setup-environment `basename $build_dir`
+MACHINE=$machine DISTRO=fslc-framebuffer . ./setup-environment
+ `basename $build_dir`

-MACHINE=$machine python3 $anchor/extract-bitbake-metadata.py \
+MACHINE=$machine DISTRO=fslc-framebuffer python3
+ $anchor/extract-bitbake-metadata.py \
 $anchor/$marshalled_data_file \
 apptrk \
 barebox \

That will behave differently.

Thomas A. F. Thorne  Software Engineer  Net2Edge

-Original Message-
From: 
meta-freescale-boun...@yoctoproject.org<mailto:meta-freescale-boun...@yoctoproject.org>
 
[mailto:meta-freescale-boun...@yoctoproject.org<mailto:meta-freescale-boun...@yoctoproject.org>]
 On Behalf Of Fabio Berton
Sent: 09 November 2016 17:30
To: meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>
Subject: [meta-freescale] [Documentation][PATCH 1/5] scripts: Update to version 
2.2 (Morty)

  - Update FSL layers names
  - Add DISTRO and MACHINE to run setup-environment
  - Update Yocto Project Bugzilla url address

Signed-off-by: Fabio Berton 
<fabio.ber...@ossystems.com.br<mailto:fabio.ber...@ossystems.com.br>>
---
 scripts/bitbake-metadata2doc.py | 18 +-  
scripts/bitbake-metadata2doc.sh |  6 +++---  scripts/generate-bugs-table.py  |  
6 +++---
 scripts/output-machine-list |  2 +-
 scripts/test-sheet-parser.py|  2 +-
 5 files changed, 17 insertions(+), 17 deletions(-)

diff --git a/scripts/bitbake-metadata2doc.py b/scripts/bitbake-metadata2doc.py 
index 98af3f8..001d59d 100644
--- a/scripts/bitbake-metadata2doc.py
+++ b/scripts/bitbake-metadata2doc.py
@@ -112,8 +112,8 @@ def write_fsl_community_bsp_supported_kernels(data, 
out_dir):
 kernel = board_data['recipes']['virtual/kernel']
 recipe = kernel['recipe']
 recipe_file = kernel['file']
-if (('/sources/meta-fsl-arm/' in recipe_file) or \
-('/sources/meta-fsl-arm-extra/' in recipe_file)) and \
+if (('/sources/meta-freescale/' in recipe_file) or \
+('/sources/meta-freescale-3rdparty/' in recipe_file))
+ and \
 recipe not in kernel_recipes:
 kernels += [[recipe, kernel['description']]]
 kernel_recipes.append(recipe) @@ -128,8 +128,8 @@ def 
write_fsl_community_bsp_supported_bootloaders_descr(data, out_dir):
 bootloader = board_data['recipes'][bootloader_software]
 recipe = bootloader['recipe']
 recipe_file = bootloader['file']
-if (('/sources/meta-fsl-arm/' in recipe_file) or \
-('/sources/meta-fsl-arm-extra/' in recipe_file)) and \
+if (('/sources/meta-freescale/' in recipe_file) or \
+('/sources/meta-freescale-3rdparty/' in
+ recipe_file)) and \
 recipe not in bootloader_recipes:
 bootloaders += [[recipe, bootloader['description']]]
 bootloader_recipes.append(recipe) @@ -305,14 +305,14 @@ 
def write_soc_pkg(data, out_dir):


 def write_maintainers_tables(data, out_dir, bsp_dir):
-meta_fsl_arm_machines_dir = os.path.join(bsp_dir, 'sources', 
'meta-

Re: [meta-freescale] [Documentation][PATCH 4/5] RN: Update version to 2.2 (Morty)

[Thomas Thorne]

Patch looks OK at that link.

Thomas A. F. Thorne<mailto:thomas.tho...@net2edge.com>  Software Engineer  
Net2Edge<http://www.net2edge.com/>

From: Fabio Berton [mailto:fabio.ber...@ossystems.com.br]
Sent: 10 November 2016 10:57
To: Thomas Thorne <thomas.tho...@net2edge.com>
Cc: meta-freescale@yoctoproject.org
Subject: Re: [meta-freescale] [Documentation][PATCH 4/5] RN: Update version to 
2.2 (Morty)

Same here,
https://patchwork.openembedded.org/patch/133743/

On Thu, Nov 10, 2016 at 7:59 AM, Thomas Thorne 
<thomas.tho...@net2edge.com<mailto:thomas.tho...@net2edge.com>> wrote:
More strange new-line additions here too:

diff --git a/release-notes/source/known-issues.rst 
b/release-notes/source/known-issues.rst
index 71e71ed..0d34019 100644
--- a/release-notes/source/known-issues.rst
+++ b/release-notes/source/known-issues.rst
@@ -40,7 +40,7 @@ Known Issues
Open

In order to see the current bug list, please use following URL:
-   https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=meta-fsl-arm
+
+ https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=meta-freesca
+ le

This also removes an indent.  Was an editor trying to automcatically fit C/C++ 
styling to non-source code?

Thomas A. F. Thorne  Software Engineer  Net2Edge

-Original Message-
From: 
meta-freescale-boun...@yoctoproject.org<mailto:meta-freescale-boun...@yoctoproject.org>
 
[mailto:meta-freescale-boun...@yoctoproject.org<mailto:meta-freescale-boun...@yoctoproject.org>]
 On Behalf Of Fabio Berton
Sent: 09 November 2016 17:30
To: meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>
Subject: [meta-freescale] [Documentation][PATCH 4/5] RN: Update version to 2.2 
(Morty)

  - Update FSL layers names
  - Update Yocto Project Bugzilla url address
  - Add FSLC distros description

Signed-off-by: Fabio Berton 
<fabio.ber...@ossystems.com.br<mailto:fabio.ber...@ossystems.com.br>>
---
 release-notes/README  |  4 ++--
 release-notes/source/bsp-scope.rst| 24 
 release-notes/source/conf.py  |  6 +++---
 release-notes/source/distros.inc  |  4 
 release-notes/source/introduction.rst |  7 ---  
release-notes/source/known-issues.rst |  4 ++--  
release-notes/source/source-code.rst  |  9 +  
release-notes/source/test-results.rst |  2 +-
 release-notes/source/variables.inc|  2 +-
 9 files changed, 38 insertions(+), 24 deletions(-)  create mode 100644 
release-notes/source/distros.inc

diff --git a/release-notes/README b/release-notes/README index e1b7c9e..9665ea3 
100644
--- a/release-notes/README
+++ b/release-notes/README
@@ -37,8 +37,8 @@ Here's an example:
   $ ./bitbake-metadata2doc.sh ~/src/fsl-community-bsp ~/src/gitdm 1.5 1.6

 By default, bitbake-metadata2doc.sh collects data out of bitbake's -metadata 
for all machines it can find in the meta-fsl-arm and -meta-fsl-arm-extra 
layers.  You can restrict the machines to collect
+metadata for all machines it can find in the meta-freescale and
+meta-freescale-3erparty. You can restrict the machines to collect
 data from by setting the MACHINES variable in your environment.

 bitbake-metadata2doc.sh will write its output to release-note's `source'
diff --git a/release-notes/source/bsp-scope.rst 
b/release-notes/source/bsp-scope.rst
index f0f0f74..97ca49d 100644
--- a/release-notes/source/bsp-scope.rst
+++ b/release-notes/source/bsp-scope.rst
@@ -4,14 +4,14 @@
 ***
 The scope of the |project_name| includes the meta layers:

- * `meta-fsl-arm 
<http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/?h=krogoth>`_:
-   provides the base support and Freescale ARM reference boards;
- * `meta-fsl-arm-extra 
<https://github.com/Freescale/meta-fsl-arm-extra/tree/krogoth>`_:
+ * `meta-freescale 
<http://git.yoctoproject.org/cgit/cgit.cgi/meta-freescale/?h=morty>`_:
+   provides the base support and Freescale ARM and PPC reference
+ boards;
+ * `meta-freescale-3rdparty 
<https://github.com/Freescale/meta-freescale-3rdparty/tree/morty>`_:
provides support for 3rd party and partner boards;
- * `meta-fsl-demos 
<https://github.com/Freescale/meta-fsl-demos/tree/krogoth>`_:
-   provides images recipes, demo recipes, and packagegroups used to easy the
-   development with Yocto Project.
- * `Documentation <https://github.com/Freescale/Documentation/tree/krogoth>`_:
+ * `meta-freescale-distro 
<https://github.com/Freescale/meta-freescale-distro/tree/morty>`_:
+   provides distros support, images recipes, demo recipes, and packagegroups
+   used to easy the development with Yocto Project.
+ * `Documentation <https://github.com/Freescale/Documentation/tree/morty>`_:
provides the source code for |project_name| Release Notes (RN), User Guide
(UG) and Frequently Asked Questions (FAQ)

@@ -36,8 +36,8 @@ regular open source licenses (GPLv2 for example).

 The close 

Re: [meta-freescale] [Documentation][PATCH 5/5] UG: Update version to 2.2 (Morty)

[Thomas Thorne]

Lots of the changes in this patch seem to add extra line breaks to example 
commands.  E.g. 
1. To have access to Yocto scripts, run the setup environment script under your 
``BASE``
directory::
 
-fsl-community-bsp $ . setup-environment build
+fsl-community-bsp $ MACHINE=wandboard DISTRO=fslc-framebuffer 
+ source setup-environment build

Will that extra line break not stop copy and pasting of example commands from 
working? 

Thomas A. F. Thorne  Software Engineer  Net2Edge

-Original Message-
From: meta-freescale-boun...@yoctoproject.org 
[mailto:meta-freescale-boun...@yoctoproject.org] On Behalf Of Fabio Berton
Sent: 09 November 2016 17:30
To: meta-freescale@yoctoproject.org
Subject: [meta-freescale] [Documentation][PATCH 5/5] UG: Update version to 2.2 
(Morty)

  - Update FSL layers names
  - Add DISTRO and MACHINE to run setup-environment
  - Update devtasks, nsteps and metadata to use Morty branch and distro
fslc-framebuffer
  - Remove qt-in-use-image and qte-in-use-image from image list
  - Add FSLC distros description
  - Use DISTRO fslc-wayland in weston example

Signed-off-by: Fabio Berton 
---
 user-guide/source/conf.py |  4 +-
 user-guide/source/devtasks.rst| 58 ---
 user-guide/source/distro-list.inc |  4 ++
 user-guide/source/distros.rst | 10 
 user-guide/source/image-list.inc  |  2 -
 user-guide/source/index.rst   |  1 +
 user-guide/source/metadata.rst| 99 ---
 user-guide/source/nsteps.rst  |  6 +--
 user-guide/source/weston.rst  | 13 +++--
 9 files changed, 121 insertions(+), 76 deletions(-)  create mode 100644 
user-guide/source/distro-list.inc  create mode 100644 
user-guide/source/distros.rst

diff --git a/user-guide/source/conf.py b/user-guide/source/conf.py index 
7c9f536..850f1ce 100644
--- a/user-guide/source/conf.py
+++ b/user-guide/source/conf.py
@@ -48,9 +48,9 @@ copyright = u'2014, Freescale Community BSP Team'
 # built documents.
 #
 # The short X.Y version or version name if applicable. 
-version = 'krogoth'
+version = 'morty'
 # The full version, including alpha/beta/rc tags.
-release = '2.1'
+release = '2.2'
 
 # The language for content autogenerated by Sphinx. Refer to documentation  # 
for a list of supported languages.
diff --git a/user-guide/source/devtasks.rst b/user-guide/source/devtasks.rst 
index 2c195d2..dfd7675 100644
--- a/user-guide/source/devtasks.rst
+++ b/user-guide/source/devtasks.rst
@@ -15,7 +15,7 @@ before proceeding check the main `Layer Index`_.
 1. To have access to Yocto scripts, run the setup environment script under 
your ``BASE``
directory::
 
-fsl-community-bsp $ . setup-environment build
+fsl-community-bsp $ MACHINE=wandboard DISTRO=fslc-framebuffer 
+ source setup-environment build
 
 2. Move to the place you want to create your layer and choose a name
(e.g. ``fsl-custom``)::
@@ -50,14 +50,14 @@ package development. However, if the need does arise, 
follow the steps listed be  that you have already built the package you want to 
patch.
 
 * Create the patch or patches. In this example we are patching the
-  Linux kernel for `wandboard-dual machine `_;
+  Linux kernel for `wandboard machine `_;
   in other words, the value of ``MACHINE`` in ``build/conf/local.conf`` is
-  ``MACHINE ??= 'wandboard-dual'``
+  ``MACHINE ??= 'wandboard'``
 
 * If you already have the patches available, make sure they can be applied 
cleanly with
   the commands ``git apply --check ``. To create new or additional 
patches::
 
-build $ cd 
tmp/work/wandboard_dual-poky-linux-gnueabi/linux-wandboard/3.0.35-r0/git
+build $ cd 
+ tmp/work/wandboard-fslc-linux-gnueabi/linux-wandboard/4.1.15-r0/git
 # Edit any files you want to change
 $ git add   ..
 $ git commit -s -m '' # Create the commit
@@ -69,8 +69,8 @@ that you have already built the package you want to patch.
   and the ```.bbfile``::
 
 sources $ mkdir -p \
-   
meta-fsl-custom/recipes-kernel/linux/linux-wandboard-3.0.35/
-sources $ cat > 
meta-fsl-custom/recipes-kernel/linux/linux-wandboard_3.0.35.bbappend << EOF
+   
meta-fsl-custom/recipes-kernel/linux/linux-wandboard-4.1.15/
+sources $ cat > 
+ meta-fsl-custom/recipes-kernel/linux/linux-wandboard_4.1.15.bbappend 
+ << EOF
 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
 SRC_URI += "file://0001-calibrate-Add-printk-example.patch"
 PRINC := "${@int(PRINC) + 1}"
@@ -78,12 +78,12 @@ that you have already built the package you want to patch.
 
 * Move the patch to the new layer::
 
-sources $ cp 
../build/tmp/work/wandboard_dual-poky-linux-gnueabi/linux-wandboard/3.0.35-r0/git/0001-calibrate-Add-printk-example.patch
 \
- meta-fsl-custom/recipes-kernel/linux/linux-wandboard-3.0.35
+sources $ cp 

Re: [meta-freescale] [Documentation][PATCH 3/5] FAQ: Update version to 2.2 (Morty)

[Thomas Thorne]

Patch at link looks OK.

I have not eyeballed all 5 patches.

All 5 look wrong in the text emails.
All 5 look fine at the links provided by Fario.

Thomas A. F. Thorne<mailto:thomas.tho...@net2edge.com>  Software Engineer  
Net2Edge<http://www.net2edge.com/>

From: Fabio Berton [mailto:fabio.ber...@ossystems.com.br]
Sent: 10 November 2016 11:57
To: Thomas Thorne <thomas.tho...@net2edge.com>
Cc: meta-freescale@yoctoproject.org
Subject: Re: [meta-freescale] [Documentation][PATCH 3/5] FAQ: Update version to 
2.2 (Morty)

Same problem here, please check https://patchwork.openembedded.org/patch/133741/

On Thu, Nov 10, 2016 at 8:01 AM, Thomas Thorne 
<thomas.tho...@net2edge.com<mailto:thomas.tho...@net2edge.com>> wrote:
More lines split where it seems they should not be.  I am only eyeballing 
these.  Maybe I am mistaken and new lines in .rst files do not matter?

Example from this file would include:
-* Packages `needed 
<http://www.yoctoproject.org/docs/1.5.1/ref-manual/ref-manual.html#required-packages-for-the-host-development-system>`_
+* Packages `needed
+<http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#re
+quired-packages-for-the-host-development-system>`_



Thomas A. F. Thorne  Software Engineer  Net2Edge

-Original Message-
From: 
meta-freescale-boun...@yoctoproject.org<mailto:meta-freescale-boun...@yoctoproject.org>
 
[mailto:meta-freescale-boun...@yoctoproject.org<mailto:meta-freescale-boun...@yoctoproject.org>]
 On Behalf Of Fabio Berton
Sent: 09 November 2016 17:30
To: meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>
Subject: [meta-freescale] [Documentation][PATCH 3/5] FAQ: Update version to 2.2 
(Morty)

  - Update documentation url address to use current realease
  - Update Yocto Project Bugzilla url address
  - Update copyright year

Signed-off-by: Fabio Berton 
<fabio.ber...@ossystems.com.br<mailto:fabio.ber...@ossystems.com.br>>
---
 FAQ/source/all.rst | 6 +++---
 FAQ/source/conf.py | 6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/FAQ/source/all.rst b/FAQ/source/all.rst index 7fc4532..a41aea9 
100644
--- a/FAQ/source/all.rst
+++ b/FAQ/source/all.rst
@@ -116,9 +116,9 @@ How do I create a layer?
 What are the host packages needed for Yocto Project?
 

-* Make sure your Linux host / distribution is `supported 
<http://www.yoctoproject.org/docs/1.5.1/ref-manual/ref-manual.html#detailed-supported-distros>`_
 by the Yocto Project.
+* Make sure your Linux host / distribution is `supported 
<http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#detailed-supported-distros>`_
 by the Yocto Project.

-* Packages `needed 
<http://www.yoctoproject.org/docs/1.5.1/ref-manual/ref-manual.html#required-packages-for-the-host-development-system>`_
+* Packages `needed
+<http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#re
+quired-packages-for-the-host-development-system>`_


 How can I save space after a build?
@@ -135,7 +135,7 @@ How can I save space after a build?
 Where do I check for known bugs?
 

-The known bugs are tracked using `Yocto Project Bugzilla 
<https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=meta-fsl-arm>`_
+The known bugs are tracked using `Yocto Project Bugzilla
+<https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=meta-freesca
+le>`_


 Are there prebuilt images available?
diff --git a/FAQ/source/conf.py b/FAQ/source/conf.py index 00eaebd..b9bfce6 
100644
--- a/FAQ/source/conf.py
+++ b/FAQ/source/conf.py
@@ -41,16 +41,16 @@ master_doc = 'index'

 # General information about the project.
 project = u'Freescale Community BSP FAQ'
-copyright = u'2014, Freescale Community BSP Team'
+copyright = u'2014-2016, Freescale Community BSP Team'

 # The version info for the project you're documenting, acts as replacement for 
 # |version| and |release|, also used in various other places throughout the  # 
built documents.
 #
 # The short X.Y version or version name if applicable.
-version = 'krogoth'
+version = 'morty'
 # The full version, including alpha/beta/rc tags.
-release = '2.1'
+release = '2.2'

 # The language for content autogenerated by Sphinx. Refer to documentation  # 
for a list of supported languages.
--
2.1.4

--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>
https://lists.yoctoproject.org/listinfo/meta-freescale

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

Re: [meta-freescale] [Documentation][PATCH 5/5] UG: Update version to 2.2 (Morty)

[Thomas Thorne]

Hi Fabio,

It did looks so systemic that something automated must have been doing it.  I 
am pleased to confirm that the patch you linked to looks fine.


Ø  I think Gmail breaks the lines
I am not using Gmail?

Thomas A. F. Thorne<mailto:thomas.tho...@net2edge.com>  Software Engineer  
Net2Edge<http://www.net2edge.com/>

From: Fabio Berton [mailto:fabio.ber...@ossystems.com.br]
Sent: 10 November 2016 10:53
To: Thomas Thorne <thomas.tho...@net2edge.com>
Cc: meta-freescale@yoctoproject.org
Subject: Re: [meta-freescale] [Documentation][PATCH 5/5] UG: Update version to 
2.2 (Morty)


​Hi ​Thomas!

On Thu, Nov 10, 2016 at 7:58 AM, Thomas Thorne 
<thomas.tho...@net2edge.com<mailto:thomas.tho...@net2edge.com>> wrote:
Lots of the changes in this patch seem to add extra line breaks to example 
commands.  E.g.
1. To have access to Yocto scripts, run the setup environment script under your 
``BASE``
directory::

-fsl-community-bsp $ . setup-environment build
+fsl-community-bsp $ MACHINE=wandboard DISTRO=fslc-framebuffer
+ source setup-environment build

Will that extra line break not stop copy and pasting of example commands from 
working?
​My git log doesn't show line break, and final PDF ​
neither
​.
I think Gmail breaks the lines, look patch here 
https://patchwork.openembedded.org/patch/133744/

​
Thomas A. F. Thorne  Software Engineer  Net2Edge

-Original Message-
From: 
meta-freescale-boun...@yoctoproject.org<mailto:meta-freescale-boun...@yoctoproject.org>
 
[mailto:meta-freescale-boun...@yoctoproject.org<mailto:meta-freescale-boun...@yoctoproject.org>]
 On Behalf Of Fabio Berton
Sent: 09 November 2016 17:30
To: meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>
Subject: [meta-freescale] [Documentation][PATCH 5/5] UG: Update version to 2.2 
(Morty)

  - Update FSL layers names
  - Add DISTRO and MACHINE to run setup-environment
  - Update devtasks, nsteps and metadata to use Morty branch and distro
fslc-framebuffer
  - Remove qt-in-use-image and qte-in-use-image from image list
  - Add FSLC distros description
  - Use DISTRO fslc-wayland in weston example

Signed-off-by: Fabio Berton 
<fabio.ber...@ossystems.com.br<mailto:fabio.ber...@ossystems.com.br>>
---
 user-guide/source/conf.py |  4 +-
 user-guide/source/devtasks.rst| 58 ---
 user-guide/source/distro-list.inc |  4 ++
 user-guide/source/distros.rst | 10 
 user-guide/source/image-list.inc  |  2 -
 user-guide/source/index.rst   |  1 +
 user-guide/source/metadata.rst| 99 ---
 user-guide/source/nsteps.rst  |  6 +--
 user-guide/source/weston.rst  | 13 +++--
 9 files changed, 121 insertions(+), 76 deletions(-)  create mode 100644 
user-guide/source/distro-list.inc  create mode 100644 
user-guide/source/distros.rst

diff --git a/user-guide/source/conf.py b/user-guide/source/conf.py index 
7c9f536..850f1ce 100644
--- a/user-guide/source/conf.py
+++ b/user-guide/source/conf.py
@@ -48,9 +48,9 @@ copyright = u'2014, Freescale Community BSP Team'
 # built documents.
 #
 # The short X.Y version or version name if applicable.
-version = 'krogoth'
+version = 'morty'
 # The full version, including alpha/beta/rc tags.
-release = '2.1'
+release = '2.2'

 # The language for content autogenerated by Sphinx. Refer to documentation  # 
for a list of supported languages.
diff --git a/user-guide/source/devtasks.rst b/user-guide/source/devtasks.rst 
index 2c195d2..dfd7675 100644
--- a/user-guide/source/devtasks.rst
+++ b/user-guide/source/devtasks.rst
@@ -15,7 +15,7 @@ before proceeding check the main `Layer Index`_.
 1. To have access to Yocto scripts, run the setup environment script under 
your ``BASE``
directory::

-fsl-community-bsp $ . setup-environment build
+fsl-community-bsp $ MACHINE=wandboard DISTRO=fslc-framebuffer
+ source setup-environment build

 2. Move to the place you want to create your layer and choose a name
(e.g. ``fsl-custom``)::
@@ -50,14 +50,14 @@ package development. However, if the need does arise, 
follow the steps listed be  that you have already built the package you want to 
patch.

 * Create the patch or patches. In this example we are patching the
-  Linux kernel for `wandboard-dual machine <http://www.wandboard.org/>`_;
+  Linux kernel for `wandboard machine <http://www.wandboard.org/>`_;
   in other words, the value of ``MACHINE`` in ``build/conf/local.conf`` is
-  ``MACHINE ??= 'wandboard-dual'``
+  ``MACHINE ??= 'wandboard'``

 * If you already have the patches available, make sure they can be applied 
cleanly with
   the commands ``git apply --check ``. To create new or additional 
patches::

-build $ cd 
tmp/work/wandboard_dual-poky-linux-gnueabi/linux-wandboard/3.0.35-r0/git
+build $ cd
+ tmp/work/wandboard-fslc-linux-gnueabi/linux-wandboard/4.1.15-r0/git
 # Edit any files you want to change
 $ gi

Re: [meta-freescale] [Documentation][PATCH 1/5] scripts: Update to version 2.2 (Morty)

[Thomas Thorne]

I am almost certain this line change breaks the Python code:

--- a/scripts/bitbake-metadata2doc.py
+++ b/scripts/bitbake-metadata2doc.py
@@ -112,8 +112,8 @@ def write_fsl_community_bsp_supported_kernels(data, 
out_dir):
 kernel = board_data['recipes']['virtual/kernel']
 recipe = kernel['recipe']
 recipe_file = kernel['file']
-if (('/sources/meta-fsl-arm/' in recipe_file) or \
-('/sources/meta-fsl-arm-extra/' in recipe_file)) and \
+if (('/sources/meta-freescale/' in recipe_file) or \
+('/sources/meta-freescale-3rdparty/' in recipe_file)) 
+ and \

That looks like \ are used for line continuation but an extra new line is being 
added before the "and \"


I am more confident about the .sh files: 
$machines; do
 cd $yocto_dir
 echo "Using $build_dir as build directory"
-MACHINE=$machine . ./setup-environment `basename $build_dir`
+MACHINE=$machine DISTRO=fslc-framebuffer . ./setup-environment 
+ `basename $build_dir`
 
-MACHINE=$machine python3 $anchor/extract-bitbake-metadata.py \
+MACHINE=$machine DISTRO=fslc-framebuffer python3 
+ $anchor/extract-bitbake-metadata.py \
 $anchor/$marshalled_data_file \
 apptrk \
 barebox \

That will behave differently. 

Thomas A. F. Thorne  Software Engineer  Net2Edge

-Original Message-
From: meta-freescale-boun...@yoctoproject.org 
[mailto:meta-freescale-boun...@yoctoproject.org] On Behalf Of Fabio Berton
Sent: 09 November 2016 17:30
To: meta-freescale@yoctoproject.org
Subject: [meta-freescale] [Documentation][PATCH 1/5] scripts: Update to version 
2.2 (Morty)

  - Update FSL layers names
  - Add DISTRO and MACHINE to run setup-environment
  - Update Yocto Project Bugzilla url address

Signed-off-by: Fabio Berton 
---
 scripts/bitbake-metadata2doc.py | 18 +-  
scripts/bitbake-metadata2doc.sh |  6 +++---  scripts/generate-bugs-table.py  |  
6 +++---
 scripts/output-machine-list |  2 +-
 scripts/test-sheet-parser.py|  2 +-
 5 files changed, 17 insertions(+), 17 deletions(-)

diff --git a/scripts/bitbake-metadata2doc.py b/scripts/bitbake-metadata2doc.py 
index 98af3f8..001d59d 100644
--- a/scripts/bitbake-metadata2doc.py
+++ b/scripts/bitbake-metadata2doc.py
@@ -112,8 +112,8 @@ def write_fsl_community_bsp_supported_kernels(data, 
out_dir):
 kernel = board_data['recipes']['virtual/kernel']
 recipe = kernel['recipe']
 recipe_file = kernel['file']
-if (('/sources/meta-fsl-arm/' in recipe_file) or \
-('/sources/meta-fsl-arm-extra/' in recipe_file)) and \
+if (('/sources/meta-freescale/' in recipe_file) or \
+('/sources/meta-freescale-3rdparty/' in recipe_file)) 
+ and \
 recipe not in kernel_recipes:
 kernels += [[recipe, kernel['description']]]
 kernel_recipes.append(recipe) @@ -128,8 +128,8 @@ def 
write_fsl_community_bsp_supported_bootloaders_descr(data, out_dir):
 bootloader = board_data['recipes'][bootloader_software]
 recipe = bootloader['recipe']
 recipe_file = bootloader['file']
-if (('/sources/meta-fsl-arm/' in recipe_file) or \
-('/sources/meta-fsl-arm-extra/' in recipe_file)) and \
+if (('/sources/meta-freescale/' in recipe_file) or \
+('/sources/meta-freescale-3rdparty/' in 
+ recipe_file)) and \
 recipe not in bootloader_recipes:
 bootloaders += [[recipe, bootloader['description']]]
 bootloader_recipes.append(recipe) @@ -305,14 +305,14 @@ 
def write_soc_pkg(data, out_dir):
 
 
 def write_maintainers_tables(data, out_dir, bsp_dir):
-meta_fsl_arm_machines_dir = os.path.join(bsp_dir, 'sources', 
'meta-fsl-arm', 'conf', 'machine')
-meta_fsl_arm_extra_machines_dir = os.path.join(bsp_dir, 'sources', 
'meta-fsl-arm-extra', 'conf', 'machine')
-get_maintainer_script = os.path.join(bsp_dir, 'sources', 'meta-fsl-arm', 
'scripts', 'get-maintainer')
+meta_freescale_machines_dir = os.path.join(bsp_dir, 'sources', 
'meta-freescale', 'conf', 'machine')
+meta_freescale_3rdparty_machines_dir = os.path.join(bsp_dir, 'sources', 
'meta-freescale-3rdparty', 'conf', 'machine')
+get_maintainer_script = os.path.join(bsp_dir, 'sources', 
+ 'meta-freescale', 'scripts', 'get-maintainer')
 try:
 get_maintainer_pipe = subprocess.Popen([get_maintainer_script,
 '--dump',
-meta_fsl_arm_machines_dir,
-
meta_fsl_arm_extra_machines_dir],
+meta_freescale_machines_dir,
+
+ meta_freescale_3rdparty_machines_dir],
  

Re: [meta-freescale] [Documentation][PATCH 3/5] FAQ: Update version to 2.2 (Morty)

[Thomas Thorne]

More lines split where it seems they should not be.  I am only eyeballing 
these.  Maybe I am mistaken and new lines in .rst files do not matter?  

Example from this file would include: 
-* Packages `needed 
`_
+* Packages `needed 
+`_



Thomas A. F. Thorne  Software Engineer  Net2Edge

-Original Message-
From: meta-freescale-boun...@yoctoproject.org 
[mailto:meta-freescale-boun...@yoctoproject.org] On Behalf Of Fabio Berton
Sent: 09 November 2016 17:30
To: meta-freescale@yoctoproject.org
Subject: [meta-freescale] [Documentation][PATCH 3/5] FAQ: Update version to 2.2 
(Morty)

  - Update documentation url address to use current realease
  - Update Yocto Project Bugzilla url address
  - Update copyright year

Signed-off-by: Fabio Berton 
---
 FAQ/source/all.rst | 6 +++---
 FAQ/source/conf.py | 6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/FAQ/source/all.rst b/FAQ/source/all.rst index 7fc4532..a41aea9 
100644
--- a/FAQ/source/all.rst
+++ b/FAQ/source/all.rst
@@ -116,9 +116,9 @@ How do I create a layer?
 What are the host packages needed for Yocto Project?
 
 
-* Make sure your Linux host / distribution is `supported 
`_
 by the Yocto Project.
+* Make sure your Linux host / distribution is `supported 
`_
 by the Yocto Project.
 
-* Packages `needed 
`_
+* Packages `needed 
+`_
 
 
 How can I save space after a build?
@@ -135,7 +135,7 @@ How can I save space after a build?
 Where do I check for known bugs?
 
 
-The known bugs are tracked using `Yocto Project Bugzilla 
`_
+The known bugs are tracked using `Yocto Project Bugzilla 
+`_
 
 
 Are there prebuilt images available?
diff --git a/FAQ/source/conf.py b/FAQ/source/conf.py index 00eaebd..b9bfce6 
100644
--- a/FAQ/source/conf.py
+++ b/FAQ/source/conf.py
@@ -41,16 +41,16 @@ master_doc = 'index'
 
 # General information about the project.
 project = u'Freescale Community BSP FAQ'
-copyright = u'2014, Freescale Community BSP Team'
+copyright = u'2014-2016, Freescale Community BSP Team'
 
 # The version info for the project you're documenting, acts as replacement for 
 # |version| and |release|, also used in various other places throughout the  # 
built documents.
 #
 # The short X.Y version or version name if applicable. 
-version = 'krogoth'
+version = 'morty'
 # The full version, including alpha/beta/rc tags.
-release = '2.1'
+release = '2.2'
 
 # The language for content autogenerated by Sphinx. Refer to documentation  # 
for a list of supported languages.
--
2.1.4

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

Re: [meta-freescale] ANN: New layout for FSL Community BSP and BSP layers

[Thomas Thorne]

> Speaking in renaming: why don't we use NXP instead of FSL?

Perhaps after yesterday's announcement you should delay the rename a few months 
and use Qualcomm instead of NXP?  Or perhaps plan to move directly from FSL to 
Qualcomm in a couple of years depending how it all pans out.  


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

Re: [meta-freescale] Help using toaster

[Thomas Thorne]

I continued trying to get Toaster to work last week. 

I found that by cloning a fresh poky work area directly from the yocto project 
main repository I was able to include the meta-fsl-arm layer from their servers 
(which I think is a direct mirror of the GitHub one) and build an image.  I 
targeted the ls1021atwr machine in my toaster build.  

I am sure that with some manipulation of the toasterconf.json file, it would be 
possible to use the freescale work area layout as generated by repo.  If I make 
progress in that area I will update this thread or possibly generate a patch 
for the toasterconf.json file.  

Thomas A. F. Thorne  Software Engineer  Net2Edge

-Original Message-
From: Thomas Thorne 
Sent: 19 October 2016 12:45
To: Thomas Thorne <thomas.tho...@net2edge.com>; Daiane Angolini 
<daiane.l...@gmail.com>; Gustavo Ramon Arambula Aguilar 
<gustavo.aramb...@nxp.com>
Cc: meta-freescale@yoctoproject.org
Subject: RE: [meta-freescale] Help using toaster

After reading more of the toaster-manual I found the section on "4.1.1.2. 
Configuring Toaster to Hook Into Your Layer Index"

In there it is mentioned that after editing your toasterconf.json file there 
are two commands you should run from your toaster environment to pick up 
changes from your modified file.  To load the changes you run something like: 
$ bitbake/lib/toaster/manage.py loadconf 
/home/scottrif/poky/meta-poky/conf/toasterconf.json
If that was successful you then run:
$ bitbake/lib/toaster/manage.py lsupdates to update your Toaster databse.  

When I run the loadconf command I get a lot of errors out of it, even with the 
default toasterconf.json:

~/work/fsl-community-bsp/ls1021atwr$ 
../sources/poky/bitbake/lib/toaster/manage.py loadconf -v 2 
/home/thomasthorne/work/fsl-community-bsp/sources/poky/meta-poky/conf/toasterconf.json
 
WARNING:root:Error while looking for remote "origin" in "yocto  
https://git.yoctoproject.org/git/poky (fetch)
yocto   https://git.yoctoproject.org/git/poky (push)
"
2016-10-19 11:54:17,691 ERROR The toaster config file references the local git 
repo, but Toaster cannot detect it.
Your local configuration for bitbake version jethro is invalid. Make sure that 
the toasterconf.json file is correct.
ERROR:toaster:The toaster config file references the local git repo, but 
Toaster cannot detect it.
Your local configuration for bitbake version jethro is invalid. Make sure that 
the toasterconf.json file is correct.
WARNING:root:Error while looking for remote "origin" in "yocto  
https://git.yoctoproject.org/git/poky (fetch)
yocto   https://git.yoctoproject.org/git/poky (push)
"
2016-10-19 11:54:17,696 ERROR The toaster config file references the local git 
repo, but Toaster cannot detect it.
Your local configuration for bitbake version krogoth is invalid. Make sure that 
the toasterconf.json file is correct.
ERROR:toaster:The toaster config file references the local git repo, but 
Toaster cannot detect it.
Your local configuration for bitbake version krogoth is invalid. Make sure that 
the toasterconf.json file is correct.
WARNING:root:Error while looking for remote "origin" in "yocto  
https://git.yoctoproject.org/git/poky (fetch)
yocto   https://git.yoctoproject.org/git/poky (push)
"
2016-10-19 11:54:17,699 ERROR The toaster config file references the local git 
repo, but Toaster cannot detect it.
Your local configuration for bitbake version HEAD is invalid. Make sure that 
the toasterconf.json file is correct.
ERROR:toaster:The toaster config file references the local git repo, but 
Toaster cannot detect it.
Your local configuration for bitbake version HEAD is invalid. Make sure that 
the toasterconf.json file is correct.
WARNING:root:Error while looking for remote "origin" in "yocto  
https://git.yoctoproject.org/git/poky (fetch)
yocto   https://git.yoctoproject.org/git/poky (push)
"
2016-10-19 11:54:17,705 ERROR The toaster config file references the local git 
repo, but Toaster cannot detect it.
Your local configuration for layer openembedded-core is invalid. Make sure that 
the toasterconf.json file is correct.
ERROR:toaster:The toaster config file references the local git repo, but 
Toaster cannot detect it.
Your local configuration for layer openembedded-core is invalid. Make sure that 
the toasterconf.json file is correct.
WARNING:root:Error while looking for remote "origin" in "yocto  
https://git.yoctoproject.org/git/poky (fetch)
yocto   https://git.yoctoproject.org/git/poky (push)
"
2016-10-19 11:54:17,711 ERROR The toaster config file references the local git 
repo, but Toaster cannot detect it.
Your local configuration for layer meta-poky is invalid. Make sure that the 
toasterconf.json file is correct.
ERROR:toaster:The toaster config file references the local git repo, but 
Toaster cannot detect it.
Your local configuration for layer meta-poky is inval

Re: [meta-freescale] [PATCH] README: Remove subject-prefix from git format-patch command

[Thomas Thorne]

You may wish to update the same are for the documentation repo.  Currently that 
adds a "documentation]" tag in where this code added "meta-freescale]"

Thomas A. F. Thorne  Software Engineer  Net2Edge

-Original Message-
From: meta-freescale-boun...@yoctoproject.org 
[mailto:meta-freescale-boun...@yoctoproject.org] On Behalf Of Fabio Berton
Sent: 21 October 2016 13:08
To: meta-freescale@yoctoproject.org
Subject: [meta-freescale] [PATCH] README: Remove subject-prefix from git 
format-patch command

Removing --subject-prefix='meta-freescale][PATCH']' from git format-patch the 
generated patch will be created with default subject as shown bellow:

Subject: [PATCH] README: Remove subject-prefix from git format-patch command

Signed-off-by: Fabio Berton 
---
 README | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README b/README
index 33d4c08..1f40864 100644
--- a/README
+++ b/README
@@ -31,7 +31,7 @@ Source code:
 
 When creating patches, please use something like:
 
-git format-patch -s --subject-prefix='meta-freescale][PATCH' origin
+git format-patch -s origin
 
 When sending patches, please use something like:
 
--
2.1.4

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

Re: [meta-freescale] [distro][PATCH] README: Update to use new repository names

[Thomas Thorne]

May I ask what has motivated the change of repository name?  

I am not questioning the validity of this patch.  I am trying to find out the 
bit of history that I must be missing which explains why these changes are 
happening: 

meta-fsl-arm renamed to meta-freescale
meta-fsl-demos renamed to meta-freescale-distro
meta-fsl-arm-extra renamed to meta-freescale-3rdparty

Are there any other repositories changing names soon?  

Thomas A. F. Thorne  Software Engineer  Net2Edge

-Original Message-
From: meta-freescale-boun...@yoctoproject.org 
[mailto:meta-freescale-boun...@yoctoproject.org] On Behalf Of Fabio Berton
Sent: 21 October 2016 13:07
To: meta-freescale@yoctoproject.org
Subject: [meta-freescale] [distro][PATCH] README: Update to use new repository 
names

  - Update title description
  - Update to new layers names
  - Update git format-patch subject-prefix

Signed-off-by: Fabio Berton 
---
 README | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/README b/README
index eb24b90..321d112 100644
--- a/README
+++ b/README
@@ -1,4 +1,4 @@
-OpenEmbedded/Yocto layer for Freescale's Demonstration images
+OpenEmbedded/Yocto layer for Freescale's Distribution images
 =
 
 This layer provides support for Freescale's Demonstration images for @@ -14,7 
+14,7 @@ URI: git://git.openembedded.org/meta-openembedded
 branch: master
 revision: HEAD
 
-URI: git://git.yoctoproject.org/meta-fsl-arm
+URI: git://git.yoctoproject.org/meta-freescale
 branch: master
 revision: HEAD
 
@@ -30,11 +30,11 @@ Mailing list:
 
 Source code:
 
-https://github.com/Freescale/meta-fsl-demos
+https://github.com/Freescale/meta-freescale-distro
 
 When creating a patch of the last commit, use
 
-git format-patch -s --subject-prefix='meta-fsl-demos][PATCH' -1
+git format-patch -s --subject-prefix='distro][PATCH' -1
 
 To send it to the community, use
 
--
2.1.4

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

Re: [meta-freescale] Help using toaster

[Thomas Thorne]

After reading more of the toaster-manual I found the section on "4.1.1.2. 
Configuring Toaster to Hook Into Your Layer Index"

In there it is mentioned that after editing your toasterconf.json file there 
are two commands you should run from your toaster environment to pick up 
changes from your modified file.  To load the changes you run something like: 
$ bitbake/lib/toaster/manage.py loadconf 
/home/scottrif/poky/meta-poky/conf/toasterconf.json
If that was successful you then run:
$ bitbake/lib/toaster/manage.py lsupdates
to update your Toaster databse.  

When I run the loadconf command I get a lot of errors out of it, even with the 
default toasterconf.json:

~/work/fsl-community-bsp/ls1021atwr$ 
../sources/poky/bitbake/lib/toaster/manage.py loadconf -v 2 
/home/thomasthorne/work/fsl-community-bsp/sources/poky/meta-poky/conf/toasterconf.json
 
WARNING:root:Error while looking for remote "origin" in "yocto  
https://git.yoctoproject.org/git/poky (fetch)
yocto   https://git.yoctoproject.org/git/poky (push)
"
2016-10-19 11:54:17,691 ERROR The toaster config file references the local git 
repo, but Toaster cannot detect it.
Your local configuration for bitbake version jethro is invalid. Make sure that 
the toasterconf.json file is correct.
ERROR:toaster:The toaster config file references the local git repo, but 
Toaster cannot detect it.
Your local configuration for bitbake version jethro is invalid. Make sure that 
the toasterconf.json file is correct.
WARNING:root:Error while looking for remote "origin" in "yocto  
https://git.yoctoproject.org/git/poky (fetch)
yocto   https://git.yoctoproject.org/git/poky (push)
"
2016-10-19 11:54:17,696 ERROR The toaster config file references the local git 
repo, but Toaster cannot detect it.
Your local configuration for bitbake version krogoth is invalid. Make sure that 
the toasterconf.json file is correct.
ERROR:toaster:The toaster config file references the local git repo, but 
Toaster cannot detect it.
Your local configuration for bitbake version krogoth is invalid. Make sure that 
the toasterconf.json file is correct.
WARNING:root:Error while looking for remote "origin" in "yocto  
https://git.yoctoproject.org/git/poky (fetch)
yocto   https://git.yoctoproject.org/git/poky (push)
"
2016-10-19 11:54:17,699 ERROR The toaster config file references the local git 
repo, but Toaster cannot detect it.
Your local configuration for bitbake version HEAD is invalid. Make sure that 
the toasterconf.json file is correct.
ERROR:toaster:The toaster config file references the local git repo, but 
Toaster cannot detect it.
Your local configuration for bitbake version HEAD is invalid. Make sure that 
the toasterconf.json file is correct.
WARNING:root:Error while looking for remote "origin" in "yocto  
https://git.yoctoproject.org/git/poky (fetch)
yocto   https://git.yoctoproject.org/git/poky (push)
"
2016-10-19 11:54:17,705 ERROR The toaster config file references the local git 
repo, but Toaster cannot detect it.
Your local configuration for layer openembedded-core is invalid. Make sure that 
the toasterconf.json file is correct.
ERROR:toaster:The toaster config file references the local git repo, but 
Toaster cannot detect it.
Your local configuration for layer openembedded-core is invalid. Make sure that 
the toasterconf.json file is correct.
WARNING:root:Error while looking for remote "origin" in "yocto  
https://git.yoctoproject.org/git/poky (fetch)
yocto   https://git.yoctoproject.org/git/poky (push)
"
2016-10-19 11:54:17,711 ERROR The toaster config file references the local git 
repo, but Toaster cannot detect it.
Your local configuration for layer meta-poky is invalid. Make sure that the 
toasterconf.json file is correct.
ERROR:toaster:The toaster config file references the local git repo, but 
Toaster cannot detect it.
Your local configuration for layer meta-poky is invalid. Make sure that the 
toasterconf.json file is correct.
WARNING:root:Error while looking for remote "origin" in "yocto  
https://git.yoctoproject.org/git/poky (fetch)
yocto   https://git.yoctoproject.org/git/poky (push)
"
2016-10-19 11:54:17,716 ERROR The toaster config file references the local git 
repo, but Toaster cannot detect it.
Your local configuration for layer meta-yocto-bsp is invalid. Make sure that 
the toasterconf.json file is correct.
ERROR:toaster:The toaster config file references the local git repo, but 
Toaster cannot detect it.
Your local configuration for layer meta-yocto-bsp is invalid. Make sure that 
the toasterconf.json file is correct.


So either there is a problem with the script doing the checking or with the 
default config file.  
$ ../sources/poky/bitbake/lib/toaster/manage.py loadconf --version
1.8.15
Who know what is really wants to see in that file.  I will try either working 
out how to write a new toasterconf.json file that does not generate a bunch of 
complains or see if getting the /admin/ web interface working suggests 
something helpful.  I can see the login 

Re: [meta-freescale] Help using toaster

[Thomas Thorne]

I have just tried to use toaster and also got the remote loaning error:

command: git clone "remote:origin" 
"/home/thomasthorne/work/fsl-community-bsp/_toaster_clones/_remote_origin_krogoth"
 
Cloning into 
'/home/thomasthorne/work/fsl-community-bsp/_toaster_clones/_remote_origin_krogoth'...
ssh: Could not resolve hostname remote: Temporary failure in name resolution
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.


Did anyone get this working recently?  It seems that It is not that 
straightforward.  Here is my working so far, I will keep plugging away in the 
morning.   


Now when I look back at the console that I started toaster from I can see a lot 
of errors output:

(venv) thomasthorne@thorne-ul-dt:~/work/fsl-community-bsp/ls1021atwr$ source 
../sources/poky/bitbake/bin/toaster
The system will start.
Check if toaster can listen on 0.0.0.0:8000
OK
Operations to perform:
  Synchronize unmigrated apps: staticfiles, messages, toastermain, 
bldcollector, toastergui, humanize
  Apply all migrations: sessions, admin, auth, contenttypes, orm, bldcontrol
Synchronizing apps without migrations:
  Creating tables...
Running deferred SQL...
  Installing custom SQL...
Running migrations:
  Rendering model states... DONE
  Applying contenttypes.0001_initial... OK
  Applying auth.0001_initial... OK
  Applying admin.0001_initial... OK
  Applying contenttypes.0002_remove_content_type_name... OK
  Applying auth.0002_alter_permission_name_max_length... OK
  Applying auth.0003_alter_user_email_max_length... OK
  Applying auth.0004_alter_user_username_opts... OK
  Applying auth.0005_alter_user_last_login_null... OK
  Applying auth.0006_require_contenttypes_0002... OK
  Applying orm.0001_initial... OK
  Applying bldcontrol.0001_initial... OK
  Applying bldcontrol.0002_auto_20160120_1250... OK
  Applying bldcontrol.0003_add_cancelling_state... OK
  Applying orm.0002_customimagerecipe... OK
  Applying orm.0003_customimagepackage... OK
  Applying orm.0004_provides... OK
  Applying orm.0005_task_field_separation... OK
  Applying orm.0006_add_cancelled_state... OK
  Applying sessions.0001_initial... OK

 -- Validation: The layers checkout directory must be set.

 -- Validation: The build directory must be set.

Build configuration saved

Importing file: 
/home/thomasthorne/work/fsl-community-bsp/sources/poky/meta-poky/conf/toasterconf.json
WARNING:root:Error while looking for remote "origin" in "yocto  
https://git.yoctoproject.org/git/poky (fetch)
yocto   https://git.yoctoproject.org/git/poky (push)
"
2016-10-18 15:47:59,765 ERROR The toaster config file references the local git 
repo, but Toaster cannot detect it.
Your local configuration for bitbake version jethro is invalid. Make sure that 
the toasterconf.json file is correct.
ERROR:toaster:The toaster config file references the local git repo, but 
Toaster cannot detect it.
Your local configuration for bitbake version jethro is invalid. Make sure that 
the toasterconf.json file is correct.
WARNING:root:Error while looking for remote "origin" in "yocto  
https://git.yoctoproject.org/git/poky (fetch)
yocto   https://git.yoctoproject.org/git/poky (push)
"
2016-10-18 15:47:59,770 ERROR The toaster config file references the local git 
repo, but Toaster cannot detect it.
Your local configuration for bitbake version krogoth is invalid. Make sure that 
the toasterconf.json file is correct.
ERROR:toaster:The toaster config file references the local git repo, but 
Toaster cannot detect it.
Your local configuration for bitbake version krogoth is invalid. Make sure that 
the toasterconf.json file is correct.
WARNING:root:Error while looking for remote "origin" in "yocto  
https://git.yoctoproject.org/git/poky (fetch)
yocto   https://git.yoctoproject.org/git/poky (push)
"
2016-10-18 15:47:59,775 ERROR The toaster config file references the local git 
repo, but Toaster cannot detect it.
Your local configuration for bitbake version HEAD is invalid. Make sure that 
the toasterconf.json file is correct.
ERROR:toaster:The toaster config file references the local git repo, but 
Toaster cannot detect it.
Your local configuration for bitbake version HEAD is invalid. Make sure that 
the toasterconf.json file is correct.
WARNING:root:Error while looking for remote "origin" in "yocto  
https://git.yoctoproject.org/git/poky (fetch)
yocto   https://git.yoctoproject.org/git/poky (push)
"
2016-10-18 15:47:59,781 ERROR The toaster config file references the local git 
repo, but Toaster cannot detect it.
Your local configuration for layer openembedded-core is invalid. Make sure that 
the toasterconf.json file is correct.
ERROR:toaster:The toaster config file references the local git repo, but 
Toaster cannot detect it.
Your local configuration for layer openembedded-core is invalid. Make sure that 
the toasterconf.json file is correct.
WARNING:root:Error while looking for remote "origin" in "yocto  

Re: [meta-freescale] Build issue in Qoriq SDK-v2.0 for TWR-LS1021A-PB (meta-freescale)

[Thomas Thorne]

>> Is there any official announcement on release of stable qoriq SDK 
>> fsl-sdk-v2.0-1609 ? If yes then, can we switch to this kernel from sdk-v2.0 
>> kernel (4.1.8-rt8) ?
> [Zhenhua Luo] The SDK-v2.0-1609 is released in the end of Sep, we will 
> upstream the recipes to meta-freescale layer in Oct.

This is good news for me.  I will make a note of it on our development 
timelines.  
Thank you for the info.  

> Can anyone confirm that If we can still build Qoriq SDK-v2.0 for 
> TWR-LS1021A-PB
If the TWR-LS1021A-PB, TWR-LS1021A or LS1021A-TWR are all the same thing then I 
am sure I build for the tower board last month.  I am currently trying to use 
the fsl community edition as a base instead though, rather than the freescale 
issued SDK from the nxp.com website. If I switch back I will be very pleased to 
know about the patch.  
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

[meta-freescale] [Documentation][PATCH] Include rootfs.tar.gz Method In Build and boot steps

[Thomas . Thorne]

From: Thomas Thorne <thomas.tho...@net2edge.com>

Many Yocto build systems, including the one for the ls1021a-twr do not
generate .sdcard bianry images.  This changeset adds some instructions
on inflaiting a tar'ed and gzip'ed root filesystem image onto an SD card
and then copying over the kernel and device tree bianry files too.

I think this also reflects the more recent documentation from the Yocto
project.

Signed-off-by: Thomas Thorne <thomas.tho...@net2edge.com>
---
 user-guide/source/nsteps.rst | 52 +---
 1 file changed, 39 insertions(+), 13 deletions(-)

diff --git a/user-guide/source/nsteps.rst b/user-guide/source/nsteps.rst
index a64cca7..63b2f6b 100644
--- a/user-guide/source/nsteps.rst
+++ b/user-guide/source/nsteps.rst
@@ -29,19 +29,45 @@ Build and boot in *N*-steps
 build $ bitbake-layers show-recipes "*image*" | grep ':'  # To list all 
possible images
 build $ bitbake# Bake! The first time can take several 
hours
 
-6. Flash your SD card::
-
-# Insert your SD Card
-# Type '$ dmesg | tail' to see the device node being used, e.g /dev/sdb
-# In case the SD to be flashed has already some partitions, the host 
system may have 
-# mounted these, so unmount them, e.g. '$ sudo umount /dev/sdb?'.
-build $ ls -la 'tmp/deploy/images//*.sdcard'
-
-# Flash the soft link one
-build $ sudo dd if=tmp/deploy/images//-.sdcard \
-of=/dev/sdX \
-bs=1M \
-conv=fsync
+6. Flash your SD card:
+
+a) With a pre-formed sdcard image::
+
+# Insert your SD Card
+# Type '$ dmesg | tail' to see the device node being used, e.g /dev/sdb
+# In case the SD to be flashed has already some partitions, the host 
system may have 
+# mounted these, so unmount them, e.g. '$ sudo umount /dev/sdb?'.
+build $ ls -la 'tmp/deploy/images//*.sdcard'
+
+# Flash the soft link .sdcard image
+build $ sudo dd \
+  if=tmp/deploy/images//-.sdcard \
+  of=/dev/sdX \
+  bs=1M \
+  conv=fsync
+
+b) With a pre-formed root filesystem archive, kernel and device tree 
binary image::
+
+# Insert your SD Card
+# Check your card is mounted ls /media//
+build $ ls -la 'tmp/deploy/images//*.tar.gz'
+
+# Inflate the the soft link .tar.gz onto the cards filesystem
+build $ sudo tar -zxvf \
+  tmp/deploy/images//-.tar.gz \
+  -C /media//
+
+# Copy over the kernel
+build $ ls -la 'tmp/deploy/images//uImage*.bin'
+build $ sudo cp \
+  'tmp/deploy/images//uImage-.bin' \
+  /media///boot/
+
+# Copy over the device tree binary
+build $ ls -la 'tmp/deploy/images//uImage*.dtb'
+build $ sudo cp \
+  'tmp/deploy/images//uImage-.dtb' \
+  /media///boot/
 
 7. Place your SD Card in the correct board's slot and boot!
 
-- 
2.7.4

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

[meta-freescale] [Documentation][PATCH] Update to Krogoth

[Thomas . Thorne]

From: Thomas Thorne <thomas.tho...@net2edge.com>

Replace 'Jethro' with 'Krogoth' and '2.0' with '2.1'

Signed-off-by: Thomas Thorne <thomas.tho...@net2edge.com>
---
 FAQ/source/conf.py   | 6 +++---
 release-notes/source/conf.py | 2 +-
 user-guide/source/conf.py| 6 +++---
 user-guide/source/nsteps.rst | 2 +-
 4 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/FAQ/source/conf.py b/FAQ/source/conf.py
index a2792a6..00eaebd 100644
--- a/FAQ/source/conf.py
+++ b/FAQ/source/conf.py
@@ -47,10 +47,10 @@ copyright = u'2014, Freescale Community BSP Team'
 # |version| and |release|, also used in various other places throughout the
 # built documents.
 #
-# The short X.Y version.
-version = '1.5'
+# The short X.Y version or version name if applicable. 
+version = 'krogoth'
 # The full version, including alpha/beta/rc tags.
-release = '1.5'
+release = '2.1'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.
diff --git a/release-notes/source/conf.py b/release-notes/source/conf.py
index 6115217..0ea97f1 100644
--- a/release-notes/source/conf.py
+++ b/release-notes/source/conf.py
@@ -50,7 +50,7 @@ copyright = u'2013-2016, FSL Community BSP Team'
 # |version| and |release|, also used in various other places throughout the
 # built documents.
 #
-# The short X.Y version.
+# The short X.Y version or version name if applicable. 
 version = 'krogoth'
 # The full version, including alpha/beta/rc tags.
 release = '2.1'
diff --git a/user-guide/source/conf.py b/user-guide/source/conf.py
index 558f919..7c9f536 100644
--- a/user-guide/source/conf.py
+++ b/user-guide/source/conf.py
@@ -47,10 +47,10 @@ copyright = u'2014, Freescale Community BSP Team'
 # |version| and |release|, also used in various other places throughout the
 # built documents.
 #
-# The short X.Y version.
-version = '1.6'
+# The short X.Y version or version name if applicable. 
+version = 'krogoth'
 # The full version, including alpha/beta/rc tags.
-release = '1.6'
+release = '2.1'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.
diff --git a/user-guide/source/nsteps.rst b/user-guide/source/nsteps.rst
index df1c107..a64cca7 100644
--- a/user-guide/source/nsteps.rst
+++ b/user-guide/source/nsteps.rst
@@ -16,7 +16,7 @@ Build and boot in *N*-steps
 $ cd fsl-community-bsp
 fsl-community-bsp $ repo init \
 -u 
https://github.com/Freescale/fsl-community-bsp-platform \
--b jethro
+-b krogoth
 fsl-community-bsp $ repo sync 
 
 4. Select your machine (:ref:`machines`) and prepare the environment for 
bitbake::
-- 
2.7.4

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

[meta-freescale] [Documentation][PATCH] Include rootfs.tar.gz Method In Build and boot steps

[Thomas . Thorne]

From: Thomas Thorne <thomas.tho...@net2edge.com>

Many Yocto build systems, including the one for the ls1021a-twr do not
generate .sdcard bianry images.  This changeset adds some instructions
on inflaiting a tar'ed and gzip'ed root filesystem image onto an SD card
and then copying over the kernel and device tree bianry files too.

I think this also reflects the more recent documentation from the Yocto
project.

Signed-off-by: Thomas Thorne <thomas.tho...@net2edge.com>
---
 user-guide/source/nsteps.rst | 52 +---
 1 file changed, 39 insertions(+), 13 deletions(-)

diff --git a/user-guide/source/nsteps.rst b/user-guide/source/nsteps.rst
index a64cca7..63b2f6b 100644
--- a/user-guide/source/nsteps.rst
+++ b/user-guide/source/nsteps.rst
@@ -29,19 +29,45 @@ Build and boot in *N*-steps
 build $ bitbake-layers show-recipes "*image*" | grep ':'  # To list all 
possible images
 build $ bitbake# Bake! The first time can take several 
hours
 
-6. Flash your SD card::
-
-# Insert your SD Card
-# Type '$ dmesg | tail' to see the device node being used, e.g /dev/sdb
-# In case the SD to be flashed has already some partitions, the host 
system may have 
-# mounted these, so unmount them, e.g. '$ sudo umount /dev/sdb?'.
-build $ ls -la 'tmp/deploy/images//*.sdcard'
-
-# Flash the soft link one
-build $ sudo dd if=tmp/deploy/images//-.sdcard \
-of=/dev/sdX \
-bs=1M \
-conv=fsync
+6. Flash your SD card:
+
+a) With a pre-formed sdcard image::
+
+# Insert your SD Card
+# Type '$ dmesg | tail' to see the device node being used, e.g /dev/sdb
+# In case the SD to be flashed has already some partitions, the host 
system may have 
+# mounted these, so unmount them, e.g. '$ sudo umount /dev/sdb?'.
+build $ ls -la 'tmp/deploy/images//*.sdcard'
+
+# Flash the soft link .sdcard image
+build $ sudo dd \
+  if=tmp/deploy/images//-.sdcard \
+  of=/dev/sdX \
+  bs=1M \
+  conv=fsync
+
+b) With a pre-formed root filesystem archive, kernel and device tree 
binary image::
+
+# Insert your SD Card
+# Check your card is mounted ls /media//
+build $ ls -la 'tmp/deploy/images//*.tar.gz'
+
+# Inflate the the soft link .tar.gz onto the cards filesystem
+build $ sudo tar -zxvf \
+  tmp/deploy/images//-.tar.gz \
+  -C /media//
+
+# Copy over the kernel
+build $ ls -la 'tmp/deploy/images//uImage*.bin'
+build $ sudo cp \
+  'tmp/deploy/images//uImage-.bin' \
+  /media///boot/
+
+# Copy over the device tree binary
+build $ ls -la 'tmp/deploy/images//uImage*.dtb'
+build $ sudo cp \
+  'tmp/deploy/images//uImage-.dtb' \
+  /media///boot/
 
 7. Place your SD Card in the correct board's slot and boot!
 
-- 
2.7.4

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

Re: [meta-freescale] [<Documentation][PATCH] Update to Krogoth

[Thomas Thorne]

I did render all the guides. The only problem I can remember facing is that one 
of the suggested formats did not work for me.  I think I did a PDF in letter 
size instead of A4 or something.  

make latexpdf -t a4twoside

I think it was the a4twoside which did not work. That is suggested in the 
README file though.  

Thomas A. F. Thorne  Software Engineer  Net2Edge

-Original Message-
From: angol...@gmail.com [mailto:angol...@gmail.com] On Behalf Of Daiane 
Angolini
Sent: 21 September 2016 17:40
To: Thomas Thorne <thomas.tho...@net2edge.com>
Cc: Otavio Salvador <otavio.salva...@ossystems.com.br>; 
meta-freescale@yoctoproject.org
Subject: Re: [meta-freescale] [<Documentation][PATCH] Update to Krogoth

On Wed, Sep 21, 2016 at 1:06 PM, Thomas Thorne <thomas.tho...@net2edge.com> 
wrote:
> I can generate pull requests on GitHub for future document patches if that 
> will make things easier. I will also try and follow up with the Exchange 
> administrators about correcting our strange configuration.
>

Yes, please ask your administrator, if it's going to take too long, send the 
pull request with the changes.

Have you rendered the User Guide? Have you faced any problem during this 
process?


> Thomas A. F. Thorne  Software Engineer  Net2Edge
>
> -Original Message-
> From: angol...@gmail.com [mailto:angol...@gmail.com] On Behalf Of 
> Daiane Angolini
> Sent: 21 September 2016 16:47
> To: Thomas Thorne <thomas.tho...@net2edge.com>
> Cc: Otavio Salvador <otavio.salva...@ossystems.com.br>; 
> meta-freescale@yoctoproject.org
> Subject: Re: [meta-freescale] [<Documentation][PATCH] Update to 
> Krogoth
>
> On Wed, Sep 21, 2016 at 9:26 AM, Thomas A. F. Thorne MEng AUS MIET 
> <thomas.tho...@net2edge.com> wrote:
>> The three patches are attached:
>>
>> 0001-Add-Freescale-LS1021A-Tower-System-to-machine-list.i.patch

This patch adds only LS1021A-Tower to the table. Can you, please try to update 
that table using the same content we have in Release Notes?

/code/yocto/master/sources/Documentation$ find -name *machine-list.inc 
./user-guide/source/machine-list.inc
./release-notes/source/machine-list.inc

I think only copying over the file would be enough.

>>
>> 0001-Include-rootfs.tar.gz-Method-In-Build-and-boot-steps.patch

I link this patch! Thanks for documenting this.

I would only add a note saying the sdcard may not be partitioned, and which 
would be the expected partition table to your procedure (would it be 2 
partitions, one for rootfs and one for kernel?)

Another point, you don't copy any bootloader, would it be a problem?

>>
>> 0001-Update-to-Krogoth.patch
>

The only change needed on this patch would be the commit log saying
2.0 -> 2.1 and in fact the patch change a lot of older versions to 2.1. So I 
would only way in commit log the patch "upgrades the versions to 2.1"

Daiane
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

Re: [meta-freescale] [<Documentation][PATCH] Update to Krogoth

[Thomas Thorne]

I can generate pull requests on GitHub for future document patches if that will 
make things easier. I will also try and follow up with the Exchange 
administrators about correcting our strange configuration.  

Thomas A. F. Thorne  Software Engineer  Net2Edge

-Original Message-
From: angol...@gmail.com [mailto:angol...@gmail.com] On Behalf Of Daiane 
Angolini
Sent: 21 September 2016 16:47
To: Thomas Thorne <thomas.tho...@net2edge.com>
Cc: Otavio Salvador <otavio.salva...@ossystems.com.br>; 
meta-freescale@yoctoproject.org
Subject: Re: [meta-freescale] [<Documentation][PATCH] Update to Krogoth

On Wed, Sep 21, 2016 at 9:26 AM, Thomas A. F. Thorne MEng AUS MIET 
<thomas.tho...@net2edge.com> wrote:
> The three patches are attached:
>
> 0001-Add-Freescale-LS1021A-Tower-System-to-machine-list.i.patch
>
> 0001-Include-rootfs.tar.gz-Method-In-Build-and-boot-steps.patch
>
> 0001-Update-to-Krogoth.patch

Let me review your patches and provide feedback.

An alternative way to send patches would be using pull request on github.


Daiane
>
> Thomas Thorne  Software Engineer  Net2Edge Limited
>
> On 21/09/16 13:03, Otavio Salvador wrote:
>> On Wed, Sep 21, 2016 at 8:51 AM, Thomas Thorne 
>> <thomas.tho...@net2edge.com> wrote:
>>> I have attempted to test if it is my client failing to send or my mail 
>>> server refusing to deliver outside.  To do so I hand edited one of my patch 
>>> files into a new email and used the same git command to send the message.  
>>> I received a copy of the email almost instantly in Outlook, which is 
>>> running on another machine.  I am confident that a message made it at least 
>>> as far as the Exchange server for my office.
>> ...
>>
>> It seems your e-mail is not right. Please send the patches attached 
>> so we can review them but would be great if you could talk to your 
>> admin people so your email settings could be fixed.
>>
>>
>>
>
>
> --
> ___
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

Re: [meta-freescale] [<Documentation][PATCH] Update to Krogoth

[Thomas Thorne]

How strange.  

I have attempted to test if it is my client failing to send or my mail server 
refusing to deliver outside.  To do so I hand edited one of my patch files into 
a new email and used the same git command to send the message.  I received a 
copy of the email almost instantly in Outlook, which is running on another 
machine.  I am confident that a message made it at least as far as the Exchange 
server for my office.  

The email I received was:
-Original Message-
From: Thomas Thorne [mailto:thomas.tho...@net2edge.com] 
Sent: 21 September 2016 12:34
To: meta-freescale@yoctoproject.org
Cc: Thomas Thorne <thomas.tho...@net2edge.com>; otavio.salva...@ossystems.com.br
Subject: [Documentation][PATCH] Not Really - This is a hand made test

Try and make a message body by hand.  

Signed-off-by: Thomas Thorne <thomas.tho...@net2edge.com>

I'll drop the diff stuff for now. 

I will attempt to send this using the following command:

$ git send-email --to meta-freescale@yoctoproject.org --cc 
thomas.tho...@net2edge.com --cc otavio.salva...@ossystems.com.br 
0001-Hand-Made-Test.patch

Maybe I cannot send emails externally through git or something weird like that. 
 CCing Otavio Salvador and myself to check whether it is the list that fails to 
get this or everthing. I kept the [Documentation][PATCH] bit of the Subject as 
that was all that was common between the patches.  Also update the Date: field 
by hand.  

-

The terminal output when I executed the command was:
$ git send-email --to meta-freescale@yoctoproject.org --cc 
thomas.tho...@net2edge.com --cc otavio.salva...@ossystems.com.br 
0001-Hand-Made-Test.patch
0001-Hand-Made-Test.patch
(mbox) Adding cc: Thomas Thorne <thomas.tho...@net2edge.com> from line 'From: 
Thomas Thorne <thomas.tho...@net2edge.com>'
(body) Adding cc: Thomas Thorne <thomas.tho...@net2edge.com> from line 
'Signed-off-by: Thomas Thorne <thomas.tho...@net2edge.com>'

From: Thomas Thorne <thomas.tho...@net2edge.com>
To: meta-freescale@yoctoproject.org
Cc: thomas.tho...@net2edge.com,
otavio.salva...@ossystems.com.br
Subject: [Documentation][PATCH] Not Really - This is a hand made test
Date: Wed, 21 Sep 2016 12:34:07 +0100
Message-Id: <1474457647-16977-1-git-send-email-thomas.tho...@net2edge.com>
X-Mailer: git-send-email 2.7.4

The Cc list above has been expanded by additional
addresses found in the patch commit message. By default
send-email prompts before sending whenever this occurs.
This behavior is controlled by the sendemail.confirm
configuration setting.

For additional information, run 'git send-email --help'.
To retain the current behavior, but squelch this message,
run 'git config --global sendemail.confirm auto'.

Send this email? ([y]es|[n]o|[q]uit|[a]ll): yes
OK. Log says:
Sendmail: /usr/sbin/sendmail -i meta-freescale@yoctoproject.org 
thomas.tho...@net2edge.com otavio.salva...@ossystems.com.br
From: Thomas Thorne <thomas.tho...@net2edge.com>
To: meta-freescale@yoctoproject.org
Cc: thomas.tho...@net2edge.com,
otavio.salva...@ossystems.com.br
Subject: [Documentation][PATCH] Not Really - This is a hand made test
Date: Wed, 21 Sep 2016 12:34:07 +0100
Message-Id: <1474457647-16977-1-git-send-email-thomas.tho...@net2edge.com>
X-Mailer: git-send-email 2.7.4

Result: OK

-

Ahh I may have found something.  When I check the syslog of my machine I can 
see a rejection message: 
...
Sep 21 11:56:04 thorne-ul-dt postfix/qmgr[5645]: 427121963DE6: 
from=<thomasthorne@thorne-ul-dt.transition.internal>, size=4069, nrcpt=2 (queue 
active)
Sep 21 11:56:04 thorne-ul-dt postfix/qmgr[5645]: D45561963DE4: 
from=<thomasthorne@thorne-ul-dt.transition.internal>, size=3214, nrcpt=2 (queue 
active)
Sep 21 11:56:04 thorne-ul-dt postfix/qmgr[5645]: 6FC201963DE1: 
from=<thomasthorne@thorne-ul-dt.transition.internal>, size=2085, nrcpt=2 (queue 
active)
Sep 21 11:56:06 thorne-ul-dt postfix/smtp[12052]: 6FC201963DE1: 
to=<meta-freescale@yoctoproject.org>, 
relay=yocto-www.yoctoproject.org[140.211.169.56]:25, delay=92753, 
delays=92751/0.03/1.2/0.2, dsn=4.1.8, status=deferred (host 
yocto-www.yoctoproject.org[140.211.169.56] said: 450 4.1.8 
<thomasthorne@thorne-ul-dt.transition.internal>: Sender address rejected: 
Domain not found (in reply to RCPT TO command))
Sep 21 11:56:06 thorne-ul-dt postfix/smtp[12050]: 427121963DE6: 
to=<meta-freescale@yoctoproject.org>, 
relay=yocto-www.yoctoproject.org[140.211.169.56]:25, delay=92726, 
delays=92724/0.01/1.2/0.2, dsn=4.1.8, status=deferred (host 
yocto-www.yoctoproject.org[140.211.169.56] said: 450 4.1.8 
<thomasthorne@thorne-ul-dt.transition.internal>: Sender address rejected: 
Domain not found (in reply to RCPT TO command))
Sep 21 11:56:06 thorne-ul-dt postfix/smtp[12051]: D45561963DE4: 
to=<meta-freescale@yoctoproject.org>, 
relay=yocto-www.yoctoproject.org[140.211.169.56]:25, delay=92

Re: [meta-freescale] [<Documentation][PATCH] Update to Krogoth

[Thomas Thorne]

There seem to be no further changes to the documentation repository so I have 
resent the old patches.  I have copies of the 3 emails in my inbox as I CCed 
myself this time.  All three patches that I submitted this morning start their 
subject line with "[Documentation][PATCH]"

On Thu, Sep 8, 2016 at 3:40 PM, Thomas Thorne <thomas.tho...@net2edge.com> 
wrote:
> Even if I was not subscribed, I'd expect to see them in the archive. I 
> have looked but not found them so far.

Only if it was accepted; it may have been discarded due to the mailing list 
setup.

Please rebase the patches and resend them once you are back to work.

-- 
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

Re: [meta-freescale] Cellular modem support for IMX7 Linux distribution

[Thomas Thorne]

Hi Johan,

I am looking into something similar for the LS1021 IOT and TWR systems.  If you 
have found any general Linux tools that might be useful I would be interested 
to hear about them (possibly by direct email if discussing such things is bit 
off topic for this email list).

I reached the same conclusion as you; that connecting the device over USB, PCIe 
and UART to with a socket that could be accesses via an application or command 
line should be possible.  Most Modems I was looking it used an AT command set.  
I am not aware of any widely availed AT command libraries, so if further 
research does not reveal any I will implement the handful of commands I need in 
my own application code.

I have got such a modem to work under desktop Linux as a USB device.  This 
seems build in to the standard Ubuntu desktop.  I can see a series of UARTs and 
a new Network point.  From there I have mounted the modem onto the USB port of 
a LS1021-TWR board and got the community build firmware to come up.  I just got 
back from holiday and cannot recall if I saw the new UARTs and a network device 
on the target.  Whether I get that working or not my next step will probably be 
to try getting things working with the modem connected via Mini PCI.

Regards,
Thomas A. F. Thorne  Software Engineer  
Net2Edge

From: meta-freescale-boun...@yoctoproject.org 
[mailto:meta-freescale-boun...@yoctoproject.org] On Behalf Of Lantz Johan
Sent: 30 August 2016 12:51
To: meta-freescale@yoctoproject.org
Subject: [meta-freescale] Cellular modem support for IMX7 Linux distribution

Hi,

I'm looking for any software support for a Cellular modem connected to IMX7 
platform using a Linux distribution. Anyone having any knowledge about what is 
already supported regarding API's and interfaces such as USB, PCIe and UART to 
connect an external modem with a socket that could be accesses via an 
application or command line. I guess that UART will be preferred and use of AT 
commands.

BR,
/Johan
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

Re: [meta-freescale] [<Documentation][PATCH] Update to Krogoth

[Thomas Thorne]

I've been subscribed for weeks. I can resend again once I return to work in 
about one weeks time.

Even if I was not subscribed, I'd expect to see them in the archive. I have 
looked but not found them so far.

Thomas Thorne - Software Engineer - Net2Edge
Sent from my Xperia Z3 Compact

 Otavio Salvador wrote 

On Thu, Sep 1, 2016 at 11:28 AM, Thomas A. F. Thorne MEng AUS MIET
<thomas.tho...@net2edge.com> wrote:
> Should I be able to see patches submitted to the
> meta-freescale@yoctoproject.org in the meta-freescale Archives or in my
> inbox once they are published to the list?

Yes but you need to subscribe.

> Do patches go through some kind of review before they are posted to the
> wider distribution list?

No; once you subscribe you can send the patches.

> I tried to send a patch for some of user guide documentation last week
> but have not seen anything of it yet.  I did notice that by copy and
> pasting my way through the documentation instructions I ended up with
> [<Documentation] in my subject, which looked a bit odd. I tried to
> submit the patch again on the 31st with an adjusted subject that started
> [Documentation] but I have not seen anything of that either.  My
> non-patch message made it out within 3 hours.

Please subscribe and resend.

--
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
-- 
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

Re: [meta-freescale] Getting Started With A New freescale / NXP LS1021-TWR

[Thomas Thorne]

Hi Bob,

I am pleased to report that using the latest community BSP I have been able to 
get an LS1021A-TWR-PB to boot and provide a login prompt.

Poky (Yocto Project Reference Distro) 2.1.1 ls1021atwr /dev/ttyS0

ls1021atwr login: root
root@ls1021atwr:~#
root@ls1021atwr:~# uname -a
Linux ls1021atwr 3.12.37-rt51+ls1+gf488de6 #1 SMP Wed Aug 31 13:13:11 BST 2016 
armv7l armv7l armv7l GNU/Linux

My original problem was an issue with the command I had saves as an environment 
variable in u-boot. Once that was corrected things started to work much better. 
My next hiccup was trying to do an NFS boot when the kernel does not seem to 
like starting with a static IP address.  Now I am up and rolling the IP stack 
is at least working for a local loopback ping.

> There are older versions of the Tower board with earlier (rev 1 ) silicon.  I 
> have one of these, but it's on the shelf.
Do you know if there is a way to determine which version of silicon the chip 
is?  As I have got this all up and working with the latest code, I take it that 
I am looking at a board with the more recent silicon version on it.

Regards,

Thomas A. F. Thorne<mailto:thomas.tho...@net2edge.com>  Software Engineer  
Net2Edge<http://www.net2edge.com/>

From: Bob Cochran [mailto:yo...@mindchasers.com]
Sent: 26 August 2016 21:16
To: Thomas Thorne <thomas.tho...@net2edge.com>; Zhenhua Luo 
<zhenhua@nxp.com>
Cc: meta-freescale@yoctoproject.org
Subject: Re: [meta-freescale] Getting Started With A New freescale / NXP 
LS1021-TWR

Hi Tom,

Yes, I can get an LS1021A-TWR-PB to boot Linux and also run CodeWarrior using 
all master branches.   I'm doing a fresh build now and can re-confirm this a 
little later.

Which repo are you using for meta-freescale and linux-qoriq?

I think using github.com/Freescale/meta-freescale.git will give workable 
results now.

There are older versions of the Tower board with earlier (rev 1 ) silicon.  I 
have one of these, but it's on the shelf.

Bob



On 08/26/2016 03:55 AM, Thomas A. F. Thorne MEng AUS MIET wrote:

Hello Zhenhua,



Thank you for your help, setting that missing variable soleved my

issue!  I did:



=> setenv consoledev ttyS0



After that I was able to get the netboot command I had working!  Linux

started up and then issued a Kernel panic.  At least I have some out put

to work with now though.



To be honest I have no idea which kernel I just booted over NFS, it

could be from the freescale SDK, a neat Yocto Fido or Krogoth with

community or the one build as per the community instructions.  I'll try

booting with something known and see how var I get.



Grateful Regards,



Thomas Thorne  Software Engineer  Net2Edge Limited



On 26/08/16 04:26, Zhenhua Luo wrote:

Hello Thomas,



In u-boot environment, you don't set the "consoledev" variable. Please set this 
variable and try again.





Best Regards,



Zhenhua



-Original Message-

From: 
meta-freescale-boun...@yoctoproject.org<mailto:meta-freescale-boun...@yoctoproject.org>
 [mailto:meta-freescale-

boun...@yoctoproject.org<mailto:boun...@yoctoproject.org>] On Behalf Of Thomas 
A. F. Thorne MEng AUS MIET

Sent: Thursday, August 25, 2016 8:53 PM

To: meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>

Subject: [meta-freescale] Getting Started With A New freescale / NXP LS1021-

TWR



Good afternoon,



Has anyone got a kernel from a recent release to come up on a recently

produced LS1021TWR board?  I have been struggling to get an LS1021-TWR

board booting from images that I have generated using the community

freescale.  I have also tried to use the freescale SDK for the board without

much success, so it seems likely there is some common fault, probably with my

configuration, if not the hardware or pre-loaded binaries.



I ask specifically about it being a recently produced board as it sounds as if 
the

CPU has been updated and may not work as it did before.  This is based off of

some discussions I had with a distributor over the past couple of weeks.

Initially I thought this was something causing an issue with just the LS1021-IOT

boards and their SDKs but it sounds like both Internet Of Things and ToWeR

designs are effected.



I had made a post about my difficulties on the NXP Community site, but not

received any comments on it yet.

https://community.nxp.com/thread/432937  The post includes a summary of

my issue, the environment variables that I have set and the serial output from

the board.  I can provide further details through this mailing list too, but I 
did

not want to generate a huge email full of what might be irrelevant data.  The

short summary is that I get as far as the "Starting kernel ..." message and then

see no further output from the board.  This is true when trying to boot from

the SD card or over NFS.



If anyone can provide any suggestions or pointers I would be very grateful to

hear the