[yocto] /boot/dtbs/4.4.54-ti-r93/am335x-boneblack.dtb

2017-07-04 Thread Riko Ho 

Dear Yocto Team Member,

Is it possible that I use this dtb with beagle yocto kernel ? if it is, 
how to do that ?


loading */boot/dtbs/4.4.54-ti-r93/am335x-boneblack.dtb *

--
*

/***/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/***/

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

Re: [yocto] /poky/meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb =>how to update the newest version ?

2017-07-04 Thread Riko Ho 

When I upgrade poky, will it delete all the configuration I had done?


On 04/07/17 17:51, Takuro Ashie wrote:


On 2017年07月04日 17:06, Riko Ho wrote:


Still in error :

| 
/home/bianchi77/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/firefox/52.1.2esr-r0/firefox-52.1.2esr/firefox-build-dir/dist/system_wrappers/pk11pub.h:3:26: 
fatal error: pk11pub.h: No such file or directory

|  #include_next 
|   ^
| compilation terminated.



I confirmed it.
Hmm, there are some issues which prevent using built-in nss & nspr.
I can't resolve it soon.

It seems that upgrading poky is a easier way to build firefox if it's 
acceptable for you.




--
*

/***/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/***/

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

Re: [yocto] Update SRCREV doesn't work?

2017-07-04 Thread Ngọc Thi Huỳnh 
Hi,

I guess I'll remove build/tmp directory and rebuild everything from scratch.
I'll post the result later then.

BTW, thank you so much for writing swupdate.

Best Regards,
Thi Huynh

Huỳnh Ngọc Thi
-so61pi

On Wed, Jul 5, 2017 at 12:08 AM, Stefano Babic  wrote:

> Hi,
>
> On 04/07/2017 18:13, Ngọc Thi Huỳnh wrote:
> > Hi everyone,
> >
> > I'm using poky pyro to build a beaglebone image with swupdate.
> >
> > First time I built swupdate (by bitbake swupdate), it used the latest
> > git version and I encountered an make error which related to swupdate
> only.
> >
> > Then I changed swupdate version to 2017.04 (by using
> > PREFERRED_VERSION_swupdate = "2017.04") but the bitbake still used the
> > latest git version and I had the make error again.
> >
>
> I cannot confirm this. I have built a custom board and setting
> PREFERRED_VERSION_swupdate works without issues.
>
> > But when I used devshell and changed the git revision to 2017.04 then
> > do_configure and do_compile, everything went fine.
> >
> > My question is, is there a simple way to solve this problem?
> >
> > /Note:/
> > The swupdate recipes for beaglebone that I'm using are from
> > https://github.com/sbabic/meta-swupdate
> >
> > Content of swupdate_2017.04.bb :
> >
> > require swupdate.inc
> >
> > SRCREV = "d344ec10b71293d2aaf96816266d4e6ed1d3bf6a"
> >
> >
> > Content of swupdate_git.bb 
> >
> > require swupdate.inc
> >
> > DEFAULT_PREFERENCE = "-1"
> >
> >
> > A snippet of swupdate.inc
> >
> > SRCREV = "${AUTOREV}"
> >
> >
>
> Best regards,
> Stefano Babic
>
>
> --
> =
> 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

[yocto] Kernel image and dts

2017-07-04 Thread Riko Ho 

Hello Yocto Team Member,

I have a question related with *.dtbo,

Can I use *.dtbo for beaglebone directly with linux yocto kernel, 
without using ti mainline kernel ?


I want to use SPI port.

One example I can read : arch/arm/boot/dts/sun7i-a20-pcduino3.dts, where 
can I find those source files on yocto ? ==> build/tmp/ .??


Thanks


--
*

/***/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/***/

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

[yocto-announce] Oryx Linux 0.2.0 Released

2017-07-04 Thread Beth 'pidge' Flanagan 
Back in May, we introduced our Oryx Linux project and let you know about our 
ambitions for the v0.2.0 release. We’re now pleased to announce that v0.2.0 has 
been released!

Introduction
---

Oryx Linux is an embedded Linux® distribution based around the Yocto Project 
and OpenEmbedded. It incorporates a lightweight container runtime engine to 
bring the benefits of containerisation to the embedded sector without 
disrupting existing developer workflows. Please see our previous blog post at 
http://oryx-linux.org/2017/05/03/overview for more details.

Key Features and Supported Platforms
---

Oryx Linux v0.2.0 consists of the following components:

- Host system images for all supported platforms which are ready for 
installation and usage. These images include the usual selection of command 
line tools and services which make up a simple Linux distribution. They are 
kept lightweight so as not to impose a burden on memory and storage usage in 
embedded devices.
- Two example guest container images for each supported platform:
- A minimal image consisting of only those components required to 
provide a functional guest container.
- A full-cmdline image consisting of those same components plus 
additional convenience packages found in more desktop-oriented command line 
environments.
- The oryxcmd tool, included in the host images, to manage guest 
containers. This tool supports the configuration of sources from which guest 
container images may be obtained. Guest containers are then created by fetching 
an available image from a registered source and configuring the container 
runtime engine. Both guests and sources may be removed when they are no longer 
needed.
- A source release consisting of a snapshot of Bitbake and the OpenEmbedded 
metadata layers which were used to produce the above images. This source 
release may be used to re-build Oryx Linux images as needed but also to extend 
Oryx Linux to support new devices and new guest container images.

In this release, Oryx Linux images are provided for the Raspberry Pi and 
Raspberry Pi 3 devices, as well as the emulated qemux86 platform.

Oryx Lite
---

Oryx Lite is a stripped down configuration of Oryx Linux for platforms which do 
not support all containerisation features of the full Oryx Linux distribution. 
Instead, a selection of application-focused native images are made available.

In this release, Oryx Lite consists of a minimal image and a full-cmdline image 
for the Arduino Yún platform. As the feature set of Oryx Linux is expanded in 
upcoming releases, all features which do not depend on the container runtime 
will be made available as part of Oryx Lite.

Further Details
For further details please see the release notes at 
https://downloads.toganlabs.com/oryx/distro/0.2.0/RELEASE_NOTES.txt or the full 
documentation at https://downloads.toganlabs.com/oryx/docs/0.2.0/html/

For support requests, bug reports or other feedback please open an issue in the 
Togán Labs bug tracker at https://bugs.toganlabs.com/ or contact us at 
supp...@toganlabs.com

Raspberry Pi is a trademark of the Raspberry Pi Foundation. Linux® is the 
registered trademark of Linus Torvalds in the U.S. and other countries.


Beth 'pidge' Flanagan
CTO/CEO Togán Labs Ltd.
www.toganlabs.com | pi...@toganlabs.com

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

[yocto] [qa-tools][PATCH 4/4] utils/wikimaker: Add default values

2017-07-04 Thread jose . perez . carranza 
From: Jose Perez Carranza 

Add default values for section of “performance” and “pTest” to avoid use
old data on new reports.

Signed-off-by: Jose Perez Carranza 
---
 testopia_update/utils/wikimaker.py | 12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/testopia_update/utils/wikimaker.py 
b/testopia_update/utils/wikimaker.py
index 96fdfc0..b3cce60 100644
--- a/testopia_update/utils/wikimaker.py
+++ b/testopia_update/utils/wikimaker.py
@@ -99,18 +99,18 @@ def wiki_perf_tests(file_name):
 '.html GDC Charts]\n\nBelow chars are showing the latest' + \
 'performance results taken from the current milestone.\n\n' + \
 '== Performance Charts==\n\nFor Bitbake core-image-sato with' 
+ \
-'rm_work\n\n[[File:Ww19-2k17 - rmwork.png | 1280px | ' + \
+'rm_work\n\n[[File:Ww##-2k17 - rmwork.png | 1280px | ' + \
 'link=https://wiki.yoctoproject.org/charts/perf_milestone_' + \
 'GDC/bitbake-core-image-sato-rmwork.html ]]\n\nBuilding the ' 
+ \
-'Virtual kernel\n\n[[File:Ww19-2k17 - kernel.png | 1280px | ' 
+ \
+'Virtual kernel\n\n[[File:WwXX-2k17 - kernel.png | 1280px | ' 
+ \
 'link=https://wiki.yoctoproject.org/charts/perf_milestone_' + \
 'GDC/bitbake-virtual-kernel.html]]\n\nBuilding the rootfs\n' + 
\
-'\n[[File:Ww19-2k17_-_rootfs.png | 1280px | link=https://' + \
+'\n[[File:WwXX-2k17_-_rootfs.png | 1280px | link=https://' + \
 'wiki.yoctoproject.org/charts/perf_milestone_GDC/bitbake-' + \
 'core-image-sato-rootfs.html]]\n\nBuilding core-image-sato' + \
-'\n\n[[File:Ww19-2k17_-_sato.png | 1280px | link=https://' + \
+'\n\n[[File:WwXX-2k17_-_sato.png | 1280px | link=https://' + \
 'wiki.yoctoproject.org/charts/perf_milestone_GDC/bitbake-' + \
-'core-image-sato.html]]\n\neSDK Deploy time\n\n[[File:Ww19' + \
+'core-image-sato.html]]\n\neSDK Deploy time\n\n[[File:WwXX' + \
 '-2k17_-_esdk.png | 1280px | link=https://wiki.yoctoproject' + 
\
 '.org/charts/perf_milestone_GDC/bitbake-eSDK.html]]\n'
 
@@ -123,7 +123,7 @@ def wic_ptest_results(file_name):
 'milestone,status,resolution,cf_regression_type,created\n' + \
 '|noresultsmessage="None"\n|sort=status\n' + \
 '|group=product\n|id=\n}}\n\n== results ==\n\n' + \
-'{{:Ptest 381897c64069ea43d595380a3ae913bcc79cf7e1}}\n'
+'{{:Ptest }}\n'
 
 with open(file_name, 'a') as f:
 f.write(perf_data)
-- 
2.11.0

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

[yocto] [qa-tools][PATCH 3/4] testopia_update: Add validation for empty sub parameters on setup

2017-07-04 Thread jose . perez . carranza 
From: Jose Perez Carranza 

Add an error message for the cases when “setup” is selected and no sub
parameters are given.

Signed-off-by: Jose Perez Carranza 
---
 testopia_update.py | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/testopia_update.py b/testopia_update.py
index 0015d69..8080256 100755
--- a/testopia_update.py
+++ b/testopia_update.py
@@ -72,7 +72,6 @@ def connect_to_testopia():
 config = None
 opts = Options()
 
-#testopia_config = ['url', 'username', 'password', 'store_location']
 testopia_config = ['url', 'username', 'password']
 
 if not args.config and os.path.exists(DEFAULT_CONFIG_FILE):
@@ -270,6 +269,9 @@ if __name__ == '__main__':
 print(wikivars)
 create_wiki(wikivars, wikivars_list)
 
+else:
+logger.error("Sub arguments --clone-templates or --create-wiki 
should be given")
+
 sys.exit(0)
 
 
-- 
2.11.0

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

[yocto] [qa-tools][PATCH 1/4] poduct/init: Add support for PackageManagement component

2017-07-04 Thread jose . perez . carranza 
From: Jose Perez Carranza 

Create package_management_issues.py product and add support to use this
product on init file.

Signed-off-by: Jose Perez Carranza 
---
 testopia_update/product/__init__.py  | 2 ++
 testopia_update/product/package_management_issues.py | 4 
 2 files changed, 6 insertions(+)
 create mode 100644 testopia_update/product/package_management_issues.py

diff --git a/testopia_update/product/__init__.py 
b/testopia_update/product/__init__.py
index 8d31a1e..30b2201 100644
--- a/testopia_update/product/__init__.py
+++ b/testopia_update/product/__init__.py
@@ -262,6 +262,7 @@ def get_products(testopia, opts, config, logger, **kwargs):
 from . import esdk
 from . import kernel
 from . import general_runtime
+from . import package_management_issues
 
 products = []
 
@@ -277,6 +278,7 @@ def get_products(testopia, opts, config, logger, **kwargs):
 products.append(esdk.eSDKProduct(testopia, opts, logger, config, **kwargs))
 products.append(kernel.KernelProduct(testopia, opts, logger, config, 
**kwargs))
 products.append(general_runtime.GeneralRuntimeProduct(testopia, opts, 
logger, config, **kwargs))
+
products.append(package_management_issues.PackageManagementIssues(testopia, 
opts, logger, config, **kwargs))
 products.append(DummyProduct(testopia, opts, logger, config, **kwargs))
 
 
diff --git a/testopia_update/product/package_management_issues.py 
b/testopia_update/product/package_management_issues.py
new file mode 100644
index 000..1f3ecc7
--- /dev/null
+++ b/testopia_update/product/package_management_issues.py
@@ -0,0 +1,4 @@
+from testopia_update.product import Product
+
+class PackageManagementIssues(Product):
+name = 'Package Management Issues'
-- 
2.11.0

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

Re: [yocto] Update SRCREV doesn't work?

2017-07-04 Thread Stefano Babic 
Hi,

On 04/07/2017 18:13, Ngọc Thi Huỳnh wrote:
> Hi everyone,
> 
> I'm using poky pyro to build a beaglebone image with swupdate.
> 
> First time I built swupdate (by bitbake swupdate), it used the latest
> git version and I encountered an make error which related to swupdate only.
> 
> Then I changed swupdate version to 2017.04 (by using
> PREFERRED_VERSION_swupdate = "2017.04") but the bitbake still used the
> latest git version and I had the make error again.
> 

I cannot confirm this. I have built a custom board and setting
PREFERRED_VERSION_swupdate works without issues.

> But when I used devshell and changed the git revision to 2017.04 then
> do_configure and do_compile, everything went fine.
> 
> My question is, is there a simple way to solve this problem?
> 
> /Note:/
> The swupdate recipes for beaglebone that I'm using are from
> https://github.com/sbabic/meta-swupdate
> 
> Content of swupdate_2017.04.bb :
> 
> require swupdate.inc
> 
> SRCREV = "d344ec10b71293d2aaf96816266d4e6ed1d3bf6a"
> 
> 
> Content of swupdate_git.bb 
> 
> require swupdate.inc
> 
> DEFAULT_PREFERENCE = "-1"
> 
> 
> A snippet of swupdate.inc
> 
> SRCREV = "${AUTOREV}"
> 
> 

Best regards,
Stefano Babic


-- 
=
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

[yocto] Update SRCREV doesn't work?

2017-07-04 Thread Ngọc Thi Huỳnh 
Hi everyone,

I'm using poky pyro to build a beaglebone image with swupdate.

First time I built swupdate (by bitbake swupdate), it used the latest git
version and I encountered an make error which related to swupdate only.

Then I changed swupdate version to 2017.04 (by using
PREFERRED_VERSION_swupdate = "2017.04") but the bitbake still used the
latest git version and I had the make error again.

But when I used devshell and changed the git revision to 2017.04 then
do_configure and do_compile, everything went fine.

My question is, is there a simple way to solve this problem?

*Note:*
The swupdate recipes for beaglebone that I'm using are from
https://github.com/sbabic/meta-swupdate

Content of swupdate_2017.04.bb:

> require swupdate.inc
>
> SRCREV = "d344ec10b71293d2aaf96816266d4e6ed1d3bf6a"
>

Content of swupdate_git.bb

> require swupdate.inc
>
> DEFAULT_PREFERENCE = "-1"
>

A snippet of swupdate.inc

> SRCREV = "${AUTOREV}"
>

Thanks,
Huỳnh Ngọc Thi
-so61pi
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] AppArmor

2017-07-04 Thread Tom Rini 
On Thu, Jun 29, 2017 at 09:35:06PM -0400, Tom Rini wrote:
> On Thu, Jun 29, 2017 at 01:56:22PM +0300, Anders Montonen wrote:
> > Hi Tom,
> > 
> > On Thu, 22 Jun 2017, Tom Rini wrote:
> > >
> > >I did fix the latter of these (along with the perl problem), but I'm
> > >using sysvinit and needed apache2 in my project anyhow.
> > 
> > Your commit fixes most of the problems, but /usr/bin/aa-easyprof
> > still gets installed with a shebang referring to the host python3
> > interpreter. The script is processed and installed by
> > utils/python-tools-setup.py, which captures whatever $PYTHON is set
> > to at the time.
> 
> Oh thanks!  I'll v2 things shortly with that fixed up.

So, FYI all, here's where I'm at.  Fixing up aa-easyprof for the shebang
part is easy as there's a few other cases around of "manually correct a
shebang".  But this exposes another problem of needing to basically
RDEPEND on python3-modules as not only does apparmor depend on a few
different core modules but the core modules themselves do not have
correct interdependencies.  As it stand today for perl this is handled
by some very fragile looking shell expressions that get re-run per perl
upgrade.  I don't think I can come up with the equivalent for python.
So my local version also has this just saying we need all of
python3-modules to be installed, and then it works.

I've also fixed up some minor logging issues in the sysvinit script
(which I know isn't a concern for Anders as he's using systemd, but just
being complete).  I will post another version in a few days just so
others can have functioning apparmor if they want it, at least until
Armin speaks up.

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

[linux-yocto] [kernel-cache][RFC PATCH 7/7] features/debug/debug-dyndbg: Add feature to enable dynamic debug

2017-07-04 Thread Nathan Rossi 
Add a feature to enable the kernel DYNAMIC_DEBUG config which allows for
dynamic printing of debug messages. Kernel debug messages are normally
not enabled in the kernel unless manually defining DEBUG in code files.
Dynamic debug allows for the messages to be embedded but toggled
dynamically during run time (via boot parameters or from a sysfs
interface).

Enabling this option is useful when debugging multiple parts of the
kernel as well as to allow for enabling of debug messages without
needing to modify the source.

Signed-off-by: Nathan Rossi 
---
 features/debug/debug-dyndbg.cfg | 1 +
 features/debug/debug-dyndbg.scc | 4 
 2 files changed, 5 insertions(+)
 create mode 100644 features/debug/debug-dyndbg.cfg
 create mode 100644 features/debug/debug-dyndbg.scc

diff --git a/features/debug/debug-dyndbg.cfg b/features/debug/debug-dyndbg.cfg
new file mode 100644
index 00..5698f5ebf6
--- /dev/null
+++ b/features/debug/debug-dyndbg.cfg
@@ -0,0 +1 @@
+CONFIG_DYNAMIC_DEBUG=y
diff --git a/features/debug/debug-dyndbg.scc b/features/debug/debug-dyndbg.scc
new file mode 100644
index 00..b48de2d32b
--- /dev/null
+++ b/features/debug/debug-dyndbg.scc
@@ -0,0 +1,4 @@
+define KFEATURE_DESCRIPTION "Enable dynamic debug printk"
+define KFEATURE_COMPATIBILITY all
+
+kconf non-hardware debug-dyndbg.cfg
-- 
2.13.2

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

[linux-yocto] [kernel-cache][RFC PATCH 5/7] bsp/qemumicroblazeeb: Add BSP configs for qemumicroblazeeb

2017-07-04 Thread Nathan Rossi 
Create configs for the qemumicroblazeeb machine. This includes both
-standard and -tiny configs.

Signed-off-by: Nathan Rossi 
---
 bsp/qemumicroblaze/qemumicroblazeeb-standard.scc | 15 +++
 bsp/qemumicroblaze/qemumicroblazeeb-tiny.scc | 12 
 bsp/qemumicroblaze/qemumicroblazeeb.cfg  | 15 +++
 3 files changed, 42 insertions(+)
 create mode 100644 bsp/qemumicroblaze/qemumicroblazeeb-standard.scc
 create mode 100644 bsp/qemumicroblaze/qemumicroblazeeb-tiny.scc
 create mode 100644 bsp/qemumicroblaze/qemumicroblazeeb.cfg

diff --git a/bsp/qemumicroblaze/qemumicroblazeeb-standard.scc 
b/bsp/qemumicroblaze/qemumicroblazeeb-standard.scc
new file mode 100644
index 00..ae93b49a11
--- /dev/null
+++ b/bsp/qemumicroblaze/qemumicroblazeeb-standard.scc
@@ -0,0 +1,15 @@
+define KMACHINE qemumicroblazeeb
+define KTYPE standard
+define KARCH microblaze
+
+include ktypes/standard/standard.scc
+
+include arch/microblaze/microblaze.scc
+kconf hardware qemumicroblazeeb.cfg
+
+include bsp/xilinx/soc/drivers-softip.scc
+include bsp/xilinx/board-common.scc
+
+# default policy for standard kernels
+include features/latencytop/latencytop.scc
+include features/profiling/profiling.scc
diff --git a/bsp/qemumicroblaze/qemumicroblazeeb-tiny.scc 
b/bsp/qemumicroblaze/qemumicroblazeeb-tiny.scc
new file mode 100644
index 00..2d1bb74132
--- /dev/null
+++ b/bsp/qemumicroblaze/qemumicroblazeeb-tiny.scc
@@ -0,0 +1,12 @@
+define KMACHINE qemumicroblazeeb
+define KTYPE tiny
+define KARCH microblaze
+
+include ktypes/tiny/tiny.scc
+
+include arch/microblaze/microblaze.scc
+kconf hardware qemumicroblazeeb.cfg
+
+include bsp/xilinx/soc/drivers-softip.scc
+include bsp/xilinx/board-common.scc
+
diff --git a/bsp/qemumicroblaze/qemumicroblazeeb.cfg 
b/bsp/qemumicroblaze/qemumicroblazeeb.cfg
new file mode 100644
index 00..0f635c1652
--- /dev/null
+++ b/bsp/qemumicroblaze/qemumicroblazeeb.cfg
@@ -0,0 +1,15 @@
+
+CONFIG_XILINX_MICROBLAZE0_FAMILY="spartan3"
+
+# CPU ISA Config
+CONFIG_XILINX_MICROBLAZE0_USE_MSR_INSTR=1
+CONFIG_XILINX_MICROBLAZE0_USE_PCMP_INSTR=1
+CONFIG_XILINX_MICROBLAZE0_USE_BARREL=1
+CONFIG_XILINX_MICROBLAZE0_USE_DIV=0
+CONFIG_XILINX_MICROBLAZE0_USE_HW_MUL=1
+CONFIG_XILINX_MICROBLAZE0_USE_FPU=0
+CONFIG_XILINX_MICROBLAZE0_HW_VER="7.10.d"
+
+# Memory Base Address
+CONFIG_KERNEL_BASE_ADDR=0x9000
+
-- 
2.13.2

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

[linux-yocto] [kernel-cache][RFC PATCH 6/7] bsp/xilinx/zynq: Add a general purpose KMACHINE for Zynq targets

2017-07-04 Thread Nathan Rossi 
Add a general purpose KMACHINE that can be used for general purpose Zynq
BSPs. The main configuration of the Zynq SoC can be configured via
device tree, allowing for a common kernel config. This allows for a
single KMACHINE to target multiple BSPs without needing to be directly
configured for the platform/soc.

This adds configs for -standard and -tiny.

Signed-off-by: Nathan Rossi 
---
 bsp/xilinx/soc/drivers-zynq.cfg | 75 +
 bsp/xilinx/soc/zynq.cfg | 43 +++
 bsp/xilinx/soc/zynq.scc | 10 ++
 bsp/xilinx/zynq-standard.scc| 15 +
 bsp/xilinx/zynq-tiny.scc|  9 +
 5 files changed, 152 insertions(+)
 create mode 100644 bsp/xilinx/soc/drivers-zynq.cfg
 create mode 100644 bsp/xilinx/soc/zynq.cfg
 create mode 100644 bsp/xilinx/soc/zynq.scc
 create mode 100644 bsp/xilinx/zynq-standard.scc
 create mode 100644 bsp/xilinx/zynq-tiny.scc

diff --git a/bsp/xilinx/soc/drivers-zynq.cfg b/bsp/xilinx/soc/drivers-zynq.cfg
new file mode 100644
index 00..daffe670b3
--- /dev/null
+++ b/bsp/xilinx/soc/drivers-zynq.cfg
@@ -0,0 +1,75 @@
+
+# UART
+CONFIG_TTY=y
+CONFIG_SERIAL_EARLYCON=y
+CONFIG_SERIAL_XILINX_PS_UART=y
+CONFIG_SERIAL_XILINX_PS_UART_CONSOLE=y
+
+# SRAM
+CONFIG_SRAM=y
+
+# EDAC
+CONFIG_EDAC=y
+CONFIG_EDAC_MM_EDAC=y
+CONFIG_EDAC_SYNOPSYS=y
+
+# DMA
+CONFIG_DMADEVICES=y
+CONFIG_PL330_DMA=y
+
+# PL310
+CONFIG_CACHE_L2X0=y
+CONFIG_PL310_ERRATA_588369=y
+CONFIG_PL310_ERRATA_727915=y
+CONFIG_PL310_ERRATA_769419=y
+
+# Watchdog
+CONFIG_WATCHDOG=y
+CONFIG_CADENCE_WATCHDOG=y
+
+# Ethernet
+CONFIG_NET_CADENCE=y
+CONFIG_MACB=y
+
+# GPIO
+CONFIG_GPIO_SYSFS=y
+CONFIG_GPIO_ZYNQ=y
+
+# I2C
+CONFIG_I2C=y
+CONFIG_I2C_CADENCE=y
+
+# SPI
+CONFIG_SPI=y
+CONFIG_SPI_CADENCE=y
+
+# CAN
+CONFIG_CAN=y
+CONFIG_CAN_DEV=y
+CONFIG_CAN_XILINXCAN=y
+
+# MMC/SD
+CONFIG_MMC=y
+CONFIG_MMC_BLOCK=y
+CONFIG_MMC_SDHCI=y
+CONFIG_MMC_SDHCI_PLTFM=y
+CONFIG_MMC_SDHCI_OF_ARASAN=y
+
+# USB
+CONFIG_USB_SUPPORT=y
+CONFIG_USB=y
+CONFIG_USB_EHCI_HCD=y
+CONFIG_USB_CHIPIDEA=y
+CONFIG_USB_CHIPIDEA_UDC=y
+CONFIG_USB_CHIPIDEA_HOST=y
+CONFIG_USB_ULPI=y
+CONFIG_NOP_USB_XCEIV=y
+CONFIG_USB_OTG=y
+CONFIG_USB_GADGET=y
+
+# FPGA
+CONFIG_FPGA=y
+CONFIG_FPGA_MGR_ZYNQ_FPGA=y
+CONFIG_FPGA_REGION=y
+CONFIG_FPGA_BRIDGE=y
+
diff --git a/bsp/xilinx/soc/zynq.cfg b/bsp/xilinx/soc/zynq.cfg
new file mode 100644
index 00..bfc74460fb
--- /dev/null
+++ b/bsp/xilinx/soc/zynq.cfg
@@ -0,0 +1,43 @@
+
+# Arch Feature Selections
+CONFIG_MMU=y
+CONFIG_ARCH_MULTI_V7=y
+CONFIG_ARCH_VEXPRESS=y
+CONFIG_ARCH_ZYNQ=y
+CONFIG_VFP=y
+CONFIG_NEON=y
+CONFIG_AEABI=y
+
+# CPU Erratas
+CONFIG_ARM_ERRATA_754322=y
+CONFIG_ARM_ERRATA_754327=y
+CONFIG_ARM_ERRATA_764369=y
+CONFIG_ARM_ERRATA_775420=y
+
+# SMP
+CONFIG_SMP=y
+CONFIG_ARM_CPU_TOPOLOGY=y
+CONFIG_SCHED_MC=y
+CONFIG_SCHED_SMT=y
+
+# Memory
+CONFIG_HIGHMEM=y
+
+# Thermal
+CONFIG_THERMAL=y
+CONFIG_THERMAL_OF=y
+CONFIG_CPU_THERMAL=y
+
+# CPU Frequency
+CONFIG_CPU_FREQ=y
+CONFIG_CPU_FREQ_STAT=y
+CONFIG_CPU_FREQ_STAT_DETAILS=y
+CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
+CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
+CONFIG_CPU_FREQ_GOV_POWERSAVE=y
+CONFIG_CPU_FREQ_GOV_ONDEMAND=y
+CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
+CONFIG_CPUFREQ_DT=y
+CONFIG_CPU_IDLE=y
+CONFIG_ARM_ZYNQ_CPUIDLE=y
+
diff --git a/bsp/xilinx/soc/zynq.scc b/bsp/xilinx/soc/zynq.scc
new file mode 100644
index 00..9a0e88b903
--- /dev/null
+++ b/bsp/xilinx/soc/zynq.scc
@@ -0,0 +1,10 @@
+define KFEATURE_DESCRIPTION "Xilinx Zynq 7000 SoC"
+define KFEATURE_COMPATIBILITY board
+
+include features/net/net.scc
+include cfg/timer/no_hz.scc
+
+kconf hardware zynq.cfg
+kconf hardware drivers-zynq.cfg
+include bsp/xilinx/soc/drivers-softip.scc
+
diff --git a/bsp/xilinx/zynq-standard.scc b/bsp/xilinx/zynq-standard.scc
new file mode 100644
index 00..b58461ae86
--- /dev/null
+++ b/bsp/xilinx/zynq-standard.scc
@@ -0,0 +1,15 @@
+define KMACHINE zynq
+define KTYPE standard
+define KARCH arm
+
+include ktypes/standard/standard.scc
+
+include bsp/xilinx/soc/zynq.scc
+include bsp/xilinx/board-common.scc
+
+include features/input/input.scc
+include cfg/usb-mass-storage.scc
+
+# default policy for standard kernels
+include features/latencytop/latencytop.scc
+include features/profiling/profiling.scc
diff --git a/bsp/xilinx/zynq-tiny.scc b/bsp/xilinx/zynq-tiny.scc
new file mode 100644
index 00..eeb7db1ebe
--- /dev/null
+++ b/bsp/xilinx/zynq-tiny.scc
@@ -0,0 +1,9 @@
+define KMACHINE zynq
+define KTYPE tiny
+define KARCH arm
+
+include ktypes/tiny/tiny.scc
+
+include bsp/xilinx/soc/zynq.scc
+include bsp/xilinx/board-common.scc
+
-- 
2.13.2

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

[linux-yocto] [kernel-cache][RFC PATCH 4/7] bsp/qemumicroblazeel: Add BSP configs for qemumicroblazeel

2017-07-04 Thread Nathan Rossi 
Create configs for the qemumicroblazeel machine. This includes both
-standard and -tiny configs.

Signed-off-by: Nathan Rossi 
---
 bsp/qemumicroblaze/qemumicroblazeel-standard.scc | 15 +++
 bsp/qemumicroblaze/qemumicroblazeel-tiny.scc | 12 
 bsp/qemumicroblaze/qemumicroblazeel.cfg  | 15 +++
 3 files changed, 42 insertions(+)
 create mode 100644 bsp/qemumicroblaze/qemumicroblazeel-standard.scc
 create mode 100644 bsp/qemumicroblaze/qemumicroblazeel-tiny.scc
 create mode 100644 bsp/qemumicroblaze/qemumicroblazeel.cfg

diff --git a/bsp/qemumicroblaze/qemumicroblazeel-standard.scc 
b/bsp/qemumicroblaze/qemumicroblazeel-standard.scc
new file mode 100644
index 00..f992d9a5e1
--- /dev/null
+++ b/bsp/qemumicroblaze/qemumicroblazeel-standard.scc
@@ -0,0 +1,15 @@
+define KMACHINE qemumicroblazeel
+define KTYPE standard
+define KARCH microblaze
+
+include ktypes/standard/standard.scc
+
+include arch/microblaze/microblaze.scc
+kconf hardware qemumicroblazeel.cfg
+
+include bsp/xilinx/soc/drivers-softip.scc
+include bsp/xilinx/board-common.scc
+
+# default policy for standard kernels
+include features/latencytop/latencytop.scc
+include features/profiling/profiling.scc
diff --git a/bsp/qemumicroblaze/qemumicroblazeel-tiny.scc 
b/bsp/qemumicroblaze/qemumicroblazeel-tiny.scc
new file mode 100644
index 00..199e62cf7f
--- /dev/null
+++ b/bsp/qemumicroblaze/qemumicroblazeel-tiny.scc
@@ -0,0 +1,12 @@
+define KMACHINE qemumicroblazeel
+define KTYPE tiny
+define KARCH microblaze
+
+include ktypes/tiny/tiny.scc
+include arch/microblaze/microblaze.scc
+
+kconf hardware qemumicroblazeel.cfg
+
+include bsp/xilinx/soc/drivers-softip.scc
+include bsp/xilinx/board-common.scc
+
diff --git a/bsp/qemumicroblaze/qemumicroblazeel.cfg 
b/bsp/qemumicroblaze/qemumicroblazeel.cfg
new file mode 100644
index 00..771aec069c
--- /dev/null
+++ b/bsp/qemumicroblaze/qemumicroblazeel.cfg
@@ -0,0 +1,15 @@
+
+CONFIG_XILINX_MICROBLAZE0_FAMILY="virtex6"
+
+# CPU ISA Config
+CONFIG_XILINX_MICROBLAZE0_USE_MSR_INSTR=1
+CONFIG_XILINX_MICROBLAZE0_USE_PCMP_INSTR=1
+CONFIG_XILINX_MICROBLAZE0_USE_BARREL=1
+CONFIG_XILINX_MICROBLAZE0_USE_DIV=1
+CONFIG_XILINX_MICROBLAZE0_USE_HW_MUL=2
+CONFIG_XILINX_MICROBLAZE0_USE_FPU=1
+CONFIG_XILINX_MICROBLAZE0_HW_VER="8.50.a"
+
+# Memory Base Address
+CONFIG_KERNEL_BASE_ADDR=0x5000
+
-- 
2.13.2

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

[linux-yocto] [kernel-cache][RFC PATCH 3/7] bsp/xilinx/soc/drivers: Add Xilinx Soft IP drivers fragment

2017-07-04 Thread Nathan Rossi 
Add a fragment to enable drivers for Xilinx Soft IP (FPGA devices) which
are used in a number of BSPs including custom MicroBlaze designs.

This fragment has two .cfg files, one is specific to MicroBlaze (kernel
configs have dependency on CONFIG_MICROBLAZE).

Signed-off-by: Nathan Rossi 
---
 bsp/xilinx/soc/drivers-softip-microblaze.cfg |  8 +
 bsp/xilinx/soc/drivers-softip.cfg| 45 
 bsp/xilinx/soc/drivers-softip.scc| 12 
 3 files changed, 65 insertions(+)
 create mode 100644 bsp/xilinx/soc/drivers-softip-microblaze.cfg
 create mode 100644 bsp/xilinx/soc/drivers-softip.cfg
 create mode 100644 bsp/xilinx/soc/drivers-softip.scc

diff --git a/bsp/xilinx/soc/drivers-softip-microblaze.cfg 
b/bsp/xilinx/soc/drivers-softip-microblaze.cfg
new file mode 100644
index 00..f671f7d516
--- /dev/null
+++ b/bsp/xilinx/soc/drivers-softip-microblaze.cfg
@@ -0,0 +1,8 @@
+# MicroBlaze only Xilinx Soft IP drivers
+
+# Xilinx SYSACE
+CONFIG_XILINX_SYSACE=y
+
+# Xilinx HW-ICAP
+CONFIG_XILINX_HWICAP=y
+
diff --git a/bsp/xilinx/soc/drivers-softip.cfg 
b/bsp/xilinx/soc/drivers-softip.cfg
new file mode 100644
index 00..5098d9b2b9
--- /dev/null
+++ b/bsp/xilinx/soc/drivers-softip.cfg
@@ -0,0 +1,45 @@
+# Serial/UART
+CONFIG_TTY=y
+CONFIG_SERIAL_8250=y
+CONFIG_SERIAL_8250_CONSOLE=y
+CONFIG_SERIAL_UARTLITE=y
+CONFIG_SERIAL_UARTLITE_CONSOLE=y
+CONFIG_SERIAL_OF_PLATFORM=y
+
+# DMA
+CONFIG_DMADEVICES=y
+CONFIG_XILINX_DMA=y
+CONFIG_XILINX_VDMA=y
+
+# Watchdog
+CONFIG_WATCHDOG=y
+CONFIG_XILINX_WATCHDOG=y
+
+# Ethernet
+CONFIG_NET_VENDOR_XILINX=y
+CONFIG_XILINX_EMACLITE=y
+CONFIG_XILINX_AXI_EMAC=y
+
+# GPIO
+CONFIG_GPIOLIB=y
+CONFIG_OF_GPIO=y
+CONFIG_GPIO_SYSFS=y
+CONFIG_GPIO_XILINX=y
+
+# I2C
+CONFIG_I2C=y
+CONFIG_I2C_XILINX=y
+
+# SPI
+CONFIG_SPI=y
+CONFIG_SPI_XILINX=y
+
+# Xilinx XADC
+CONFIG_IIO=y
+CONFIG_XILINX_XADC=y
+
+# Xilinx AXI USB2 Device
+CONFIG_USB_SUPPORT=y
+CONFIG_USB_GADGET=y
+CONFIG_USB_GADGET_XILINX=y
+
diff --git a/bsp/xilinx/soc/drivers-softip.scc 
b/bsp/xilinx/soc/drivers-softip.scc
new file mode 100644
index 00..cd6475650f
--- /dev/null
+++ b/bsp/xilinx/soc/drivers-softip.scc
@@ -0,0 +1,12 @@
+define KFEATURE_DESCRIPTION "Xilinx Soft IP Core Drivers"
+define KFEATURE_COMPATIBILITY board
+
+include features/net/net.scc
+
+kconf hardware drivers-softip.cfg
+
+# MicroBlaze only Soft IP drivers
+if [ "$KARCH" = "microblaze" ]; then
+   kconf hardware drivers-softip-microblaze.cfg
+fi
+
-- 
2.13.2

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

[linux-yocto] [kernel-cache][RFC PATCH 2/7] bsp/xilinx/board-common: Add Xilinx common board fragment for BSPs

2017-07-04 Thread Nathan Rossi 
Add a config fragment that enables commonly used configs for Xilinx
boards and systems. This includes a number of board level devices (e.g.
I2C, MTD, Ethernet PHYs, etc.)

Signed-off-by: Nathan Rossi 
---
 bsp/xilinx/board-common.cfg | 71 +
 bsp/xilinx/board-common.scc |  7 +
 2 files changed, 78 insertions(+)
 create mode 100644 bsp/xilinx/board-common.cfg
 create mode 100644 bsp/xilinx/board-common.scc

diff --git a/bsp/xilinx/board-common.cfg b/bsp/xilinx/board-common.cfg
new file mode 100644
index 00..935f8ff7bf
--- /dev/null
+++ b/bsp/xilinx/board-common.cfg
@@ -0,0 +1,71 @@
+# Common Board Drivers
+
+# Ethernet PHYs
+CONFIG_PHYLIB=y
+CONFIG_AMD_PHY=y
+CONFIG_AT803X_PHY=y
+CONFIG_BCM7XXX_PHY=y
+CONFIG_BCM87XX_PHY=y
+CONFIG_BROADCOM_PHY=y
+CONFIG_CICADA_PHY=y
+CONFIG_DAVICOM_PHY=y
+CONFIG_DP83867_PHY=y
+CONFIG_FIXED_PHY=y
+CONFIG_ICPLUS_PHY=y
+CONFIG_LSI_ET1011C_PHY=y
+CONFIG_LXT_PHY=y
+CONFIG_MARVELL_PHY=y
+CONFIG_MICREL_PHY=y
+CONFIG_NATIONAL_PHY=y
+CONFIG_QSEMI_PHY=y
+CONFIG_REALTEK_PHY=y
+CONFIG_SMSC_PHY=y
+CONFIG_VITESSE_PHY=y
+
+# I2C
+CONFIG_I2C=y
+CONFIG_I2C_CHARDEV=y
+CONFIG_I2C_MUX=y
+CONFIG_I2C_MUX_PCA954x=y
+CONFIG_I2C_MUX_PCA9541=y
+CONFIG_GPIO_PCA953X=y
+CONFIG_GPIO_PCA953X_IRQ=y
+
+# EEPROM
+CONFIG_EEPROM_AT24=y
+CONFIG_EEPROM_AT25=y
+
+# MTD
+CONFIG_MTD=y
+CONFIG_MTD_SPI_NOR=y
+# CONFIG_MTD_SPI_NOR_USE_4K_SECTORS is not set
+CONFIG_MTD_M25P80=y
+CONFIG_MTD_CFI=y
+CONFIG_MTD_CFI_AMDSTD=y
+
+# Hardware monitors
+CONFIG_HWMON=y
+CONFIG_PMBUS=y
+CONFIG_SENSORS_PMBUS=y
+# Power
+CONFIG_SENSORS_UCD9000=y
+CONFIG_SENSORS_UCD9200=y
+CONFIG_SENSORS_INA2XX=y
+CONFIG_SENSORS_MAX20751=y
+
+# Regulators
+CONFIG_REGULATOR=y
+CONFIG_REGULATOR_GPIO=y
+CONFIG_REGULATOR_FIXED_VOLTAGE=y
+
+# Reset/power-off GPIO
+CONFIG_POWER_RESET=y
+CONFIG_POWER_RESET_LTC2952=y
+
+# RTC drivers
+CONFIG_RTC_CLASS=y
+CONFIG_RTC_DRV_PCF8563=y
+
+# SI570 I2C Device
+CONFIG_COMMON_CLK_SI570=y
+
diff --git a/bsp/xilinx/board-common.scc b/bsp/xilinx/board-common.scc
new file mode 100644
index 00..589b1dab7b
--- /dev/null
+++ b/bsp/xilinx/board-common.scc
@@ -0,0 +1,7 @@
+define KFEATURE_DESCRIPTION "Devices/drivers commonly used on Xilinx 
systems/boards"
+define KFEATURE_COMPATIBILITY board
+
+kconf hardware board-common.cfg
+
+include features/leds/leds.scc
+
-- 
2.13.2

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

[linux-yocto] [kernel-cache][RFC PATCH 1/7] arch/microblaze: Add config fragments for the MicroBlaze architecture

2017-07-04 Thread Nathan Rossi 
Add the baseline configuration for the MicroBlaze architecture. This
only enables two configs, and sets up the default tick as 100 hz.

MicroBlaze is available in the mainline kernel and requires no
additional patches.

Signed-off-by: Nathan Rossi 
---
 arch/microblaze/microblaze.cfg | 18 ++
 arch/microblaze/microblaze.scc |  6 ++
 2 files changed, 24 insertions(+)
 create mode 100644 arch/microblaze/microblaze.cfg
 create mode 100644 arch/microblaze/microblaze.scc

diff --git a/arch/microblaze/microblaze.cfg b/arch/microblaze/microblaze.cfg
new file mode 100644
index 00..c4dd6bf58c
--- /dev/null
+++ b/arch/microblaze/microblaze.cfg
@@ -0,0 +1,18 @@
+
+CONFIG_MICROBLAZE=y
+
+# Memory
+CONFIG_MMU=y
+CONFIG_HIGHMEM=y
+
+# Default Arch Configuration
+CONFIG_XILINX_MICROBLAZE0_USE_MSR_INSTR=1
+CONFIG_XILINX_MICROBLAZE0_USE_PCMP_INSTR=1
+CONFIG_XILINX_MICROBLAZE0_USE_BARREL=1
+CONFIG_XILINX_MICROBLAZE0_USE_DIV=0
+CONFIG_XILINX_MICROBLAZE0_USE_HW_MUL=0
+CONFIG_XILINX_MICROBLAZE0_USE_FPU=0
+
+# Disable FTRACE, does not work with MicroBlaze
+# CONFIG_FTRACE is not set
+
diff --git a/arch/microblaze/microblaze.scc b/arch/microblaze/microblaze.scc
new file mode 100644
index 00..2b3aba2c08
--- /dev/null
+++ b/arch/microblaze/microblaze.scc
@@ -0,0 +1,6 @@
+
+if [ "$KARCH" = "microblaze" ]; then
+   kconf hardware microblaze.cfg
+   include cfg/timer/hz_100.scc
+fi
+
-- 
2.13.2

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

[linux-yocto] [kernel-cache][RFC PATCH 0/7] MicroBlaze and Zynq BSP configuration

2017-07-04 Thread Nathan Rossi 
Most of this configuration has existed in the meta-xilinx layer for
quite some time for use with linux-yocto and Xilinx's vendor tree
kernel, linux-xlnx.

The goal is to enable the use of the MicroBlaze architecture in OE-Core
including the addition of QEMU machines (qemumicroblazeel,
qemumicroblazeeb), this relies on having configuration for the BSPs in
linux-yocto. This series adds the BSP configs for these machines
including both standard and tiny kernel types, as well as fragments for
configuring Xilinx Soft IP drivers.

Also included are Zynq SoC configuration fragments and a generalised
machine config (targeting the SoC for both standard and tiny kernel
types).

Support for MicroBlaze and Zynq has been available in upstream and
linux-yocto for a number of releases. This series does not require any
patching of the kernel source to enable any functionality of the target
BSPs and is purely kernel configuration.

Additionally included in this series is a fragment for debug purposes
that enables the kernels DEBUG_DYNAMIC feature.

Nathan Rossi (7):
  arch/microblaze: Add config fragments for the MicroBlaze architecture
  bsp/xilinx/board-common: Add Xilinx common board fragment for BSPs
  bsp/xilinx/soc/drivers: Add Xilinx Soft IP drivers fragment
  bsp/qemumicroblazeel: Add BSP configs for qemumicroblazeel
  bsp/qemumicroblazeeb: Add BSP configs for qemumicroblazeeb
  bsp/xilinx/zynq: Add a general purpose KMACHINE for Zynq targets
  features/debug/debug-dyndbg: Add feature to enable dynamic debug

 arch/microblaze/microblaze.cfg   | 18 ++
 arch/microblaze/microblaze.scc   |  6 ++
 bsp/qemumicroblaze/qemumicroblazeeb-standard.scc | 15 +
 bsp/qemumicroblaze/qemumicroblazeeb-tiny.scc | 12 
 bsp/qemumicroblaze/qemumicroblazeeb.cfg  | 15 +
 bsp/qemumicroblaze/qemumicroblazeel-standard.scc | 15 +
 bsp/qemumicroblaze/qemumicroblazeel-tiny.scc | 12 
 bsp/qemumicroblaze/qemumicroblazeel.cfg  | 15 +
 bsp/xilinx/board-common.cfg  | 71 ++
 bsp/xilinx/board-common.scc  |  7 +++
 bsp/xilinx/soc/drivers-softip-microblaze.cfg |  8 +++
 bsp/xilinx/soc/drivers-softip.cfg| 45 ++
 bsp/xilinx/soc/drivers-softip.scc| 12 
 bsp/xilinx/soc/drivers-zynq.cfg  | 75 
 bsp/xilinx/soc/zynq.cfg  | 43 ++
 bsp/xilinx/soc/zynq.scc  | 10 
 bsp/xilinx/zynq-standard.scc | 15 +
 bsp/xilinx/zynq-tiny.scc |  9 +++
 features/debug/debug-dyndbg.cfg  |  1 +
 features/debug/debug-dyndbg.scc  |  4 ++
 20 files changed, 408 insertions(+)
 create mode 100644 arch/microblaze/microblaze.cfg
 create mode 100644 arch/microblaze/microblaze.scc
 create mode 100644 bsp/qemumicroblaze/qemumicroblazeeb-standard.scc
 create mode 100644 bsp/qemumicroblaze/qemumicroblazeeb-tiny.scc
 create mode 100644 bsp/qemumicroblaze/qemumicroblazeeb.cfg
 create mode 100644 bsp/qemumicroblaze/qemumicroblazeel-standard.scc
 create mode 100644 bsp/qemumicroblaze/qemumicroblazeel-tiny.scc
 create mode 100644 bsp/qemumicroblaze/qemumicroblazeel.cfg
 create mode 100644 bsp/xilinx/board-common.cfg
 create mode 100644 bsp/xilinx/board-common.scc
 create mode 100644 bsp/xilinx/soc/drivers-softip-microblaze.cfg
 create mode 100644 bsp/xilinx/soc/drivers-softip.cfg
 create mode 100644 bsp/xilinx/soc/drivers-softip.scc
 create mode 100644 bsp/xilinx/soc/drivers-zynq.cfg
 create mode 100644 bsp/xilinx/soc/zynq.cfg
 create mode 100644 bsp/xilinx/soc/zynq.scc
 create mode 100644 bsp/xilinx/zynq-standard.scc
 create mode 100644 bsp/xilinx/zynq-tiny.scc
 create mode 100644 features/debug/debug-dyndbg.cfg
 create mode 100644 features/debug/debug-dyndbg.scc

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

Re: [yocto] How to make changes and build u-boot source code in yocto

2017-07-04 Thread Prasoon Kumar 
It worked with devtool .

Thanks for the help.

On 04-Jul-2017 1:43 AM, "Khem Raj"  wrote:

>
>
> On 7/2/17 11:26 PM, Prasoon Kumar wrote:
>
> Hi,
>
> I am trying to make some changes in u-boot code and using bitbake u-boot
> to build. But it doesn't build.
> I also tried bitbake u-boot -c compile and bitbake u-boot deploy. This
> also didn't work.
>
> Can I Get some help on how to change and build u-boot.
>
>
> you should share more information about errors for someone to effectively
> help you.
>
>
> Thanks,
> Prasoon
>
>
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] File system optimization in yocto

2017-07-04 Thread Esponde, Joel 
Hi Prasoon,

What do you mean by file system loading?
Are you talking about file system mounting time?

Joël Esponde
Honeywell | Safety and Productivity Solutions

De : yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] De 
la part de Prasoon Kumar
Envoyé : lundi 3 juillet 2017 16:34
À : yocto@yoctoproject.org
Objet : [yocto] File system optimization in yocto

Hi,

I am trying to optimise the file system. I have removed the packages which are 
not required using PACKAGE_EXCLUDE. It still take around 8 seconds to load the 
file system.

How can I optimization so that my file system loading take less time. Is there 
any way to load files in a multi-threaded way so that loading is faster.

Any suggestions on optimising the file system in terms of size or time will be 
helpful.


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

Re: [yocto] /poky/meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb =>how to update the newest version ?

2017-07-04 Thread Takuro Ashie 


On 2017年07月04日 17:06, Riko Ho wrote:


Still in error :

| 
/home/bianchi77/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/firefox/52.1.2esr-r0/firefox-52.1.2esr/firefox-build-dir/dist/system_wrappers/pk11pub.h:3:26: 
fatal error: pk11pub.h: No such file or directory

|  #include_next 
|   ^
| compilation terminated.



I confirmed it.
Hmm, there are some issues which prevent using built-in nss & nspr.
I can't resolve it soon.

It seems that upgrading poky is a easier way to build firefox if it's 
acceptable for you.


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

Re: [yocto] /poky/meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb =>how to update the newest version ?

2017-07-04 Thread Riko Ho 

Still in error :

| 
/home/bianchi77/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/firefox/52.1.2esr-r0/firefox-52.1.2esr/firefox-build-dir/dist/system_wrappers/pk11pub.h:3:26: 
fatal error: pk11pub.h: No such file or directory

|  #include_next 
|   ^
| compilation terminated.


On 04/07/17 15:03, Takuro Ashie wrote:

> so which one is the right one ? :)

This is the correct one:

ac_add_options --with-system-nss
ac_add_options --with-system-nspr

Regards,



--
*

/***/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/***/

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

Re: [yocto] /poky/meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb =>how to update the newest version ?

2017-07-04 Thread Riko Ho 

It's compiling now..


On 04/07/17 15:03, Takuro Ashie wrote:

> so which one is the right one ? :)

This is the correct one:

ac_add_options --with-system-nss
ac_add_options --with-system-nspr

Regards,



--
*

/***/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/***/

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

Re: [yocto] /poky/meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb =>how to update the newest version ?

2017-07-04 Thread Riko Ho 

These lines :

# System libraries
#ac_add_options --with-system-nss #comment out for nss bug
#ac_add_options --with-system-nspr

Let me try...


On 04/07/17 15:03, Takuro Ashie wrote:

> so which one is the right one ? :)

This is the correct one:

ac_add_options --with-system-nss
ac_add_options --with-system-nspr

Regards,



--
*

/***/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/***/

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

Re: [yocto] /poky/meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb =>how to update the newest version ?

2017-07-04 Thread Takuro Ashie 

> so which one is the right one ? :)

This is the correct one:

ac_add_options --with-system-nss
ac_add_options --with-system-nspr

Regards,

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

Re: [yocto] /poky/meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb =>how to update the newest version ?

2017-07-04 Thread Riko Ho 

so which one is the right one ? :)


On 04/07/17 14:43, Takuro Ashie wrote:

ac_add_options --with-system-nss
  ac_add_options --with-system-jpeg

Oops, it's wrong.

  ac_add_options --with-system-nss
  ac_add_options --with-system-nspr


On 2017年07月04日 15:34, Takuro Ashie wrote:

You need latest poky (current master branch is needed).
But upgrading poky may also introduce unexpected changes for you.

Another solution is using built-in nss & nspr instead of system's one.
To use it remove or comment out following lines in your 
meta-browser/recipes-mozilla/firefox/firefox/mozconfig


  ac_add_options --with-system-nss
  ac_add_options --with-system-jpeg

Regards,




--
*

/***/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/***/

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

Re: [yocto] /poky/meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb =>how to update the newest version ?

2017-07-04 Thread Takuro Ashie 

  ac_add_options --with-system-nss
  ac_add_options --with-system-jpeg

Oops, it's wrong.

  ac_add_options --with-system-nss
  ac_add_options --with-system-nspr


On 2017年07月04日 15:34, Takuro Ashie wrote:

You need latest poky (current master branch is needed).
But upgrading poky may also introduce unexpected changes for you.

Another solution is using built-in nss & nspr instead of system's one.
To use it remove or comment out following lines in your 
meta-browser/recipes-mozilla/firefox/firefox/mozconfig


  ac_add_options --with-system-nss
  ac_add_options --with-system-jpeg

Regards,


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

Re: [yocto] /poky/meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb =>how to update the newest version ?

2017-07-04 Thread Takuro Ashie 

You need latest poky (current master branch is needed).
But upgrading poky may also introduce unexpected changes for you.

Another solution is using built-in nss & nspr instead of system's one.
To use it remove or comment out following lines in your 
meta-browser/recipes-mozilla/firefox/firefox/mozconfig


  ac_add_options --with-system-nss
  ac_add_options --with-system-jpeg

Regards,

On 2017年07月04日 14:40, Riko Ho wrote:


another bug :

checking for NSS - version >= 3.28.4... no
| configure: error: you don't have NSS installed or your version is 
too old

| DEBUG: 
| DEBUG: #include 
| DEBUG:   #include 
| DEBUG:   size_t malloc_usable_size(const void *ptr);
| DEBUG: int main() {
| DEBUG: return malloc_usable_size(0);
| DEBUG: ; return 0; }
| DEBUG: configure:9923: checking for valloc in malloc.h
| DEBUG: configure:9948: checking for valloc in unistd.h
| DEBUG: configure:10103: checking NSPR selection
| DEBUG: configure:10203: checking for nspr-config
| DEBUG: configure:10238: checking for NSPR - version >= 4.13.1
| DEBUG: configure:10314: 
/home/bianchi77/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/firefox/52.1.2esr-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc 
-march=armv7-a -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a8 
--sysroot=/home/bianchi77/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/firefox/52.1.2esr-r0/recipe-sysroot 
-std=gnu99 -c -fno-lifetime-dse  -Os -fsigned-char 
-fno-strict-aliasing -fno-strict-aliasing -fno-math-errno -pthread   
conftest.c 1>&5| DEBUG: configure:10333: 
/home/bianchi77/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/firefox/52.1.2esr-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc 
-march=armv7-a -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a8 
--sysroot=/home/bianchi77/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/firefox/52.1.2esr-r0/recipe-sysroot 
-std=gnu99 -c -fno-lifetime-dse  -Os -fsigned-char 
-fno-strict-aliasing -fno-strict-aliasing -fno-math-errno -pthread   
conftest.c 1>&5
| DEBUG: configure:10381: 
/home/bianchi77/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/firefox/52.1.2esr-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc 
-march=armv7-a -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a8 
--sysroot=/home/bianchi77/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/firefox/52.1.2esr-r0/recipe-sysroot 
-std=gnu99 -c -fno-lifetime-dse  -Os -fsigned-char 
-fno-strict-aliasing -fno-strict-aliasing -fno-math-errno -pthread   
conftest.c 1>&5

| DEBUG: configure:10420: checking for libevent
| DEBUG: configure:10427: checking MOZ_LIBEVENT_CFLAGS
| DEBUG: configure:10432: checking MOZ_LIBEVENT_LIBS
| DEBUG: configure:10605: checking for nss-config
| DEBUG: configure:10640: checking for NSS - version >= 3.28.4
| DEBUG: configure: error: you don't have NSS installed or your 
version is too old

| ERROR: old-configure failed
| *** Fix above errors and then restart with\
|"make -f client.mk build"
| client.mk:375: recipe for target 'configure' failed
| make: *** [configure] Error 1
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_configure (log file is located at 
/home/bianchi77/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/firefox/52.1.2esr-r0/temp/log.do_configure.9904)
ERROR: Task 
(/home/bianchi77/poky/meta-browser/recipes-mozilla/firefox/firefox_52.1.2esr.bb:do_configure) 
failed with exit code '1'



Let me see my NSS

On 04/07/17 13:33, Takuro Ashie wrote:

|HOSTTOOLS += "autoconf2.13"|


--
*

/***/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/***/

*


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

Re: [yocto] /poky/meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb =>how to update the newest version ?

2017-07-04 Thread Riko Ho 

another bug :

checking for NSS - version >= 3.28.4... no
| configure: error: you don't have NSS installed or your version is too old
| DEBUG: 
| DEBUG: #include 
| DEBUG:   #include 
| DEBUG:   size_t malloc_usable_size(const void *ptr);
| DEBUG: int main() {
| DEBUG: return malloc_usable_size(0);
| DEBUG: ; return 0; }
| DEBUG: configure:9923: checking for valloc in malloc.h
| DEBUG: configure:9948: checking for valloc in unistd.h
| DEBUG: configure:10103: checking NSPR selection
| DEBUG: configure:10203: checking for nspr-config
| DEBUG: configure:10238: checking for NSPR - version >= 4.13.1
| DEBUG: configure:10314: 
/home/bianchi77/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/firefox/52.1.2esr-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc 
-march=armv7-a -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a8 
--sysroot=/home/bianchi77/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/firefox/52.1.2esr-r0/recipe-sysroot 
-std=gnu99 -c -fno-lifetime-dse  -Os -fsigned-char -fno-strict-aliasing 
-fno-strict-aliasing -fno-math-errno -pthread   conftest.c 1>&5| DEBUG: 
configure:10333: 
/home/bianchi77/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/firefox/52.1.2esr-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc 
-march=armv7-a -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a8 
--sysroot=/home/bianchi77/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/firefox/52.1.2esr-r0/recipe-sysroot 
-std=gnu99 -c -fno-lifetime-dse  -Os -fsigned-char -fno-strict-aliasing 
-fno-strict-aliasing -fno-math-errno -pthread   conftest.c 1>&5
| DEBUG: configure:10381: 
/home/bianchi77/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/firefox/52.1.2esr-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc 
-march=armv7-a -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a8 
--sysroot=/home/bianchi77/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/firefox/52.1.2esr-r0/recipe-sysroot 
-std=gnu99 -c -fno-lifetime-dse  -Os -fsigned-char -fno-strict-aliasing 
-fno-strict-aliasing -fno-math-errno -pthread   conftest.c 1>&5

| DEBUG: configure:10420: checking for libevent
| DEBUG: configure:10427: checking MOZ_LIBEVENT_CFLAGS
| DEBUG: configure:10432: checking MOZ_LIBEVENT_LIBS
| DEBUG: configure:10605: checking for nss-config
| DEBUG: configure:10640: checking for NSS - version >= 3.28.4
| DEBUG: configure: error: you don't have NSS installed or your version 
is too old

| ERROR: old-configure failed
| *** Fix above errors and then restart with\
|"make -f client.mk build"
| client.mk:375: recipe for target 'configure' failed
| make: *** [configure] Error 1
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_configure (log file is located at 
/home/bianchi77/poky/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/firefox/52.1.2esr-r0/temp/log.do_configure.9904)
ERROR: Task 
(/home/bianchi77/poky/meta-browser/recipes-mozilla/firefox/firefox_52.1.2esr.bb:do_configure) 
failed with exit code '1'



Let me see my NSS

On 04/07/17 13:33, Takuro Ashie wrote:

|HOSTTOOLS += "autoconf2.13"|


--
*

/***/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/***/

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