Re: [yocto] thud, beaglebone-yocto.conf: SERIAL_CONSOLES setting

[Heiko Schocher]

Hello Kevin, Robert,

Am 05.11.2018 um 06:26 schrieb Kevin Hao:

On Sun, Nov 04, 2018 at 12:10:00PM +0200, Robert Berger wrote:

Hi,

On 02.11.18 16:27, Khem Raj wrote:


omap serial is obsolete why does linux-yocto keeps using it.
seondly, machine config should enable both consoles ttyO0 and ttyS0 if
you know that at least one kernel is using ttyO0


How about picking whatever works for you in the kernel conf and in machine
conf?

SERIAL_CONSOLES = "115200;ttyS0 115200;ttyO0"
SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"

Like this on the first boot either ttyO0 or ttyS0 should be picked
automatically.


Yes, this is doable. Would you mind send a patch?


Sorry for answering so late... good hint, I missed SERIAL_CONSOLES_CHECK

I try this change and report, give me some time...

bye,
Heiko
--
DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-52   Fax: +49-8142-66989-80   Email: h...@denx.de
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH pseudo 1/2] pseudo_db: add missing stdint include

[Ross Burton]

---
 pseudo_db.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/pseudo_db.c b/pseudo_db.c
index 0994048..31f4dc4 100644
--- a/pseudo_db.c
+++ b/pseudo_db.c
@@ -18,6 +18,7 @@
  *
  */
 #include 
+#include 
 #include 
 #include 
 #include 
-- 
2.11.0

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

[yocto] [PATCH pseudo 2/2] pseudo_client: move fallthrough comment to silence compiler warning

[Ross Burton]

---
 pseudo_client.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/pseudo_client.c b/pseudo_client.c
index 5604cbf..e2ea715 100644
--- a/pseudo_client.c
+++ b/pseudo_client.c
@@ -1783,7 +1783,8 @@ pseudo_client_op(pseudo_op_t op, int access, int fd, int 
dirfd, const char *path
break;
case OP_OPEN:
pseudo_client_path(fd, path);
-   case OP_EXEC: /* fallthrough */
+   /* fallthrough */
+   case OP_EXEC:
do_request = pseudo_client_logging;
break;
case OP_CLOSE:
-- 
2.11.0

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

[yocto] [PATCH pseudo] Makefile: add -lm when linking to sqlite3

[Ross Burton]

If sqlite3 is built with FTS5 then it needs log() from libm.so.  This is pulled
in automatically when dynamically linking as usual, or if static linking via
pkg-config. However as pseudo will link directly to libsqlite3.a this potential
linkage is lost and the build will fail with undefined symbols.

Solve this by always linking to libm.
---
 Makefile.in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Makefile.in b/Makefile.in
index ad6541b..28b5ecb 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -73,7 +73,7 @@ WRAPOBJS=pseudo_wrappers.o
 
 # needed for anything that links with pseduo_client.o, pretty much
 CLIENT_LDFLAGS=-ldl -lpthread
-DB_LDFLAGS=@SQLITE_LDARG@ -lpthread
+DB_LDFLAGS=@SQLITE_LDARG@ -lpthread -lm
 
 PSEUDO=$(BIN)/pseudo
 PSEUDODB=$(BIN)/pseudodb
-- 
2.11.0

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

Re: [yocto] Fwd: [meta-raspberrypi] Problem with adding udev rules

[Outback Dingo]

On Tue, Nov 6, 2018 at 11:57 AM Markus W  wrote:
>
> Hi!
>
> I want to append the rules in the
> recipe-core/udev/udev-rules-rpi/99-com.rules with the rules below from
> within my own recipe. I can´t figure out how to do that.
>
> I have tried to add those rules as separate rules file in a recipe in
> my own layer. After the build I can see that the rules file is in the
> correct directory /etc/udev/rules.d (next to 99-com.rules) but the
> rules didn't get applied. The groups below I have created by
> inheriting the useradd class (GROUPADD_PARAM_${PN} = "-r spi; -r i2c;
> -r gpio") in a different layer with a higher priority than the layer
> with the rules recipe.
>
> Not sure why this is not working. Any suggestions?
>
> 90-interfaces.rules file:
>
> SUBSYSTEM=="input", GROUP="input", MODE="0660"
> SUBSYSTEM=="i2c-dev", GROUP="i2c", MODE="0660"
> SUBSYSTEM=="spidev", GROUP="spi", MODE="0660"
> SUBSYSTEM=="bcm2835-gpiomem", GROUP="gpio", MODE="0660"
>
> SUBSYSTEM=="gpio", GROUP="gpio", MODE="0660"
> SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c '\
> chown -R root:gpio /sys/class/gpio && chmod -R 770 /sys/class/gpio;\
> chown -R root:gpio /sys/devices/virtual/gpio && chmod -R 770
> /sys/devices/virtual/gpio;\
> chown -R root:gpio /sys$devpath && chmod -R 770 /sys$devpath\
> '"
>

might help to post the recipe used.


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

[yocto] [poky] bug #8729 grub bootloader

[Dimitris Tassopoulos]

Hi all.

I'm working on bug #8729 and I'm trying to implement the multi-boot
functionality for grub.

I've partially done and I've created a virtual/grub-bootconf that can be
used like that:
PREFERRED_RPROVIDER_virtual/grub-bootconf = "grub-multibootconf"

That's working ok and installs the proper grub cfg script and the
environment files used for
the boot counter and other stuff.

The problem is that I've just hit the wall because it seems there are two
different facilities that
create the grub config file. One is the grub-efi & virtual/grub-bootconf.
But when an wic image is
build then this is overridden and a new partition is created which is also
mounted in the /boot
when the OS boots. The second facility is triggered by setting this in the
wks file:

--source bootimg-efi --sourceparams="loader=grub-efi"

In this case the bootimg-efi.py script creates the extra partition, a
different grub.cfg and also
edits the /etc/fstab and mounts this partition over /boot and therefore
virtual/grub-bootconf
becomes unused.

This raises the following questions:
- Why there are two different facilities to achieve the same thing?
- Why the second overrides the first one, instead of sharing the same files?
- How to proceed from now on?

In my opinion there should be only one facility that creates this and there
should be a common shared way for all the use cases.

I have a working example if anyone is interested.

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

[yocto] Yocto Project Status WW45’18

[Jolley, Stephen K]

Current Dev Position: YP 2.6 M4 is in QA.

Next Deadline: YP 2.6 M4 Release Target was Oct. 26, 2018


SWAT Team Rotation:

· SWAT lead is currently: Chen

· SWAT team rotation: Chen  -> Armin on Nov. 9, 2018

· SWAT team rotation: Armin -> Paul on Nov. 16, 2018

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


Key Status/Updates:

· YP 2.6 M4 rc1 is in QA, 95% completed, and the current status can be 
viewed at: 
https://wiki.yoctoproject.org/wiki/index.php?title=WW44_-_2018-10-30_-_Full_Test_Cycle_2.6_M4_RC1

· There are a number of good bug and CVE fixes queued in master-next 
which makes an rc2 possible although its likely these would merge to thud 
immediately after release instead due to how far behind schedule we now are.

· A problem with the way the Yocto Project Compatibility tests are 
being run was identified as it was possible to fail the BSP compatibility tests 
if the machine option was specified. There is a fix for OE-Core in master-next 
but we need to likely improve the way the test is being run for that to ensure 
everyone is using it consistently.

· At ELC-E/OEDEM, issues were mentioned to do with the completeness of 
the source mirror. Issues were identified by Michael and Richard and the source 
mirroring should be working properly again, including supporting http only 
builds. A new test has been added to the autobuilder to ensure this does not 
regress.

· Patches are queuing up in master-next right now, ready for when we 
start taking patches for the 2.7 development cycle, but a number will also 
likely merge to the thud branch as they’re useful bug or CVE fixes.


Planned Releases for YP 2.6:

· YP 2.6 M4 Build is in QA

· YP 2.6 M4 Release Target was Oct. 26, 2018


Planned upcoming dot releases:

· YP 2.4.4 (Rocko) will be targeted after YP 2.6 M4 is done.

· YP 2.5.2 (Sumo) will be targeted after YP 2.4.4 is done.


Tracking Metrics:

· WDD 2369 (last week 23867) 
(https://wiki.yoctoproject.org/charts/combo.html)

· Poky Patch Metrics

oTotal patches found: 1692 (last week 1690)

oPercentage of patches in the Pending State: 739 (44%) [last week 739 (44%)]


Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.6_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.6_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.6_Features

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features


The Status reports are now stored on the wiki at: 
https://wiki.yoctoproject.org/wiki/Weekly_Status


[If anyone has suggestions for other information you’d like to see on this 
weekly status update, let us know!]

Thanks,

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

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

[yocto] How to compute SRCREV for a github project

[Laurentiu-Cristian Duca]

Dear yocto community,

  A basic question regarding yocto and git.
How to compute the SRCREV for the linux-raspberrypi_4.14.bb recipe:
$ cat meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.14.bb
LINUX_VERSION ?= "4.14.68"
SRCREV = "8c8666ff6c1254d325cfa300d16f9928b3f31fc0"
SRC_URI = "git://github.com/raspberrypi/linux.git;branch=rpi-4.14.y"
...

  If I want to change to LINUX_VERSION 4.14.74 (for example),
how will I compute or get the SRCREV for this version
(please note that I am not interested in AUTOREV)?
The command "git log -50" lists the latest 50 commits
and a 40-bit signature for each commit, but does not show the kernel version.

  I have searched google but no response found.

Thank you and best regards,
Laurentiu-Cristian Duca
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Notes: Yocto Project Technical Team Meeting @ Monthly from 8am to 8:30am on the first Tuesday (PDT) (stephen.k.jol...@intel.com)

[Jolley, Stephen K]

The notes are at google doc: 
https://docs.google.com/document/d/15jB6nUJU2wrtnu6w07L9RZpNlj6AoxSTPEX5aELts1g/edit?usp=sharing
 and pasted below.  If you want access to the link, please request access.


Attendees: Armin, Stephen, Joshua, Randy, Amanda, Lewis, Jon, Tim, Mark, Nick, 
Alejandro, Richard, Michael, Tracey, Rich, Ross,
Proposed release schedule for YP 2.7 timeframe.  We discussed and agreed these 
were reasonable.

Milestone   Start YMD   Cutoff YMD  Release YMD Working Days
YP 2.4.42018/6/12   2018/11/5   2018/11/16  146
YP 2.5.22018/8/16   2018/11/19  2018/11/30  95
YP 2.7 M1   2018/10/29  2018/12/10  2018/12/21  42
YP 2.7 M2   2018/12/10  2019/01/21  2019/02/01  42
YP 2.6.12018/10/26  2019/01/07  2019/01/18  59
YP 2.7 M3   2019/01/21  2019/02/25  2019/03/08  35
YP 2.7 M4   2019/02/25  2019/04/01  2019/04/26  35
YP 2.5.32018/11/19  2019/05/10  2019/05/21  161
YP 2.6.22019/02/15  2019/05/24  2019/06/04  130

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features

Discussed testing numbering scheme. The current numbers map to the Testopia 
test case, but we are getting rid of Testopia, so the current numbers don’t 
have good meaning anymore.

Discussed that a new patch Richard has sent, will break up the ptest tests into 
individual test and give individual results for each test. Do we want to 
separate endurance/stress tests from functional tests.  Currently they are 
either disabled or not.  Currently no capability exists to make these tests 
just occasional tests, not on or off.

Note: that in YP 2.7 and later, most manual testing will not happen until some 
level of automation is developed to do this testing.

YP 2.6 M4 rc1 is in QA, 95% completed, and the current status can be viewed at: 
https://wiki.yoctoproject.org/wiki/index.php?title=WW44_-_2018-10-30_-_Full_Test_Cycle_2.6_M4_RC1

Discussed with the number of CVE’s that have come out since YP 2.6 was built, 
do we want to do an rc2.  Decided to release  and add known CVE’s to the 
release notes.

Discussed the transition of QA from Intel to the community.  Progress is being 
made.

Discussed the length of time for QA, it was 3-4 days and is now more like 2 
weeks.

Discussed bisecting poky, need to validate it is still able to be done. Randy 
will do so.

Ran through and discussed the proposed ideas for YP 2.7, adding a few below.

AR: Stephen - Set up extra meeting for 11/27 to continue discussion.
AR All – Please review the below items and start creating Bugzilla items for 
them.

Ideas for 2.7:
•   Python 3.7 [RP, Ross, Alejandro]
•   Perl recipe cleanup/upgrade (5.28.0)? [RP] - work in progress here 
https://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=akanavin/perl-sanity
 (AlexK)
•   systemd default for poky, needs autobuilder changes. [RP, Kai Kang]
•   Other poky specific config to nodistro?
•   Revise autobuilder test matrix [RP]
o   Ptest
o   Kernel
o   Add multiconfig buildset to AB
o   meta-cgl?
o   meta-oe?
o   YP plat member layers (intel/TI)
•   Revise release artifacts [RP]
•   Capability to run ‘make check’ using qemu user-mode for all packages? 
[Ross]
•   NFS rootfs in test automation {AK}
•   Sstate Hash equivalence (don’t rebuild on gcc patch) {Joshua Watt}
•   Switch to memres bitbake by default? [RP]
•   Rust? [Ross]
•   qemuarm rename to qemuarmv5 and change to v7 as default {Jon Mason}
•   Switch qemuarm to qemu -m virt rather than versatilepb {Jon Mason}
•   Containers: Agree on what belongs in oe-core vs other layers [Randy]
•   Virgl support in qemu {AlexK} (JaMa is now upstreaming this from webos, 
I believe)
•   Multiconfig SDK [Alejandro]

Thanks,

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

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

Re: [yocto] How to compute SRCREV for a github project

[Belisko Marek]

Hi,


On Tue, Nov 6, 2018 at 5:10 PM Laurentiu-Cristian Duca
 wrote:
>
> Dear yocto community,
>
>   A basic question regarding yocto and git.
> How to compute the SRCREV for the linux-raspberrypi_4.14.bb recipe:
> $ cat meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.14.bb
> LINUX_VERSION ?= "4.14.68"
> SRCREV = "8c8666ff6c1254d325cfa300d16f9928b3f31fc0"
> SRC_URI = "git://github.com/raspberrypi/linux.git;branch=rpi-4.14.y"
> ...
>
>   If I want to change to LINUX_VERSION 4.14.74 (for example),
> how will I compute or get the SRCREV for this version
SRCREV is git commit id from 4.14.74 (so if you checkout 4.14.74 tag
just run git log -1 and copy git commit ID to SRCREV and it will
work).
> (please note that I am not interested in AUTOREV)?
> The command "git log -50" lists the latest 50 commits
> and a 40-bit signature for each commit, but does not show the kernel version.
>
>   I have searched google but no response found.
>
> Thank you and best regards,
> Laurentiu-Cristian Duca
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

BR,

marek

-- 
as simple and primitive as possible
-
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Add Layer Issue

[nick]

Greetings All,
I am wondering why this error is occuring:
yocto-layer: command not found

as I already sourced into my build with oe-init script and therefore add
wondering why it's not found. I checked the current developer manual and
that should work cleanly.

Thanks,

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

Re: [yocto] Yocto Add Layer Issue

[Mark Hatle]

On 11/6/18 2:25 PM, nick wrote:
> Greetings All,
> I am wondering why this error is occuring:
> yocto-layer: command not found

Do you mean "bitbake-layers"?

--Mark

> as I already sourced into my build with oe-init script and therefore add
> wondering why it's not found. I checked the current developer manual and
> that should work cleanly.
> 
> Thanks,
> 
> Nick
> 

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

[yocto] [yocto-kernel-cache][v4.4][PATCH] kver: bump to v4.4.147

[Armin Kuster]

Signed-off-by: Armin Kuster 
---
 kver | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kver b/kver
index 7b008cd..5ccc572 100644
--- a/kver
+++ b/kver
@@ -1 +1 @@
-v4.4.141
+v4.4.147
-- 
2.7.4

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

Re: [yocto] [yocto-kernel-cache][v4.4][PATCH] kver: bump to v4.4.147

[Khem Raj]

On Tue, Nov 6, 2018 at 1:57 PM Armin Kuster  wrote:
>
> Signed-off-by: Armin Kuster 
> ---
>  kver | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kver b/kver
> index 7b008cd..5ccc572 100644
> --- a/kver
> +++ b/kver
> @@ -1 +1 @@
> -v4.4.141
> +v4.4.147

why not 4.4.162

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

Re: [yocto] [yocto-kernel-cache][v4.4][PATCH] kver: bump to v4.4.147

[akuster808]

On 11/6/18 2:05 PM, Khem Raj wrote:
> On Tue, Nov 6, 2018 at 1:57 PM Armin Kuster  wrote:
>> Signed-off-by: Armin Kuster 
>> ---
>>  kver | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/kver b/kver
>> index 7b008cd..5ccc572 100644
>> --- a/kver
>> +++ b/kver
>> @@ -1 +1 @@
>> -v4.4.141
>> +v4.4.147
> why not 4.4.162

because linux-yocto-4.4
 is not at
4.4.162. I am just trying to use the latest in that kernel repo.


- armin

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

Re: [yocto] [yocto-kernel-cache][v4.4][PATCH] kver: bump to v4.4.147

[Bruce Ashfield]

On 2018-11-06 5:10 PM, akuster808 wrote:


On 11/6/18 2:05 PM, Khem Raj wrote:

On Tue, Nov 6, 2018 at 1:57 PM Armin Kuster  wrote:

Signed-off-by: Armin Kuster
---
  kver | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kver b/kver
index 7b008cd..5ccc572 100644
--- a/kver
+++ b/kver
@@ -1 +1 @@
-v4.4.141
+v4.4.147

why not 4.4.162


because linux-yocto-4.4 
 is not at 
4.4.162. I am just trying to use the latest in that kernel repo.


Did you want .162 ? I have a whole set of -stable updates staged
here, but haven't pushed anything since releases are imminent.

But in the case of 4.4, I could lift my freeze, given that the kernel
recipe isn't active in master, hence the release schedule is
different.

Bruce




- armin


--
2.7.4

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


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

Re: [yocto] [poky] bug #8729 grub bootloader

[Mittal, Anuj]

Hi Dimitris

On Tue, 2018-11-06 at 16:12 +0100, Dimitris Tassopoulos wrote:
> 
> In this case the bootimg-efi.py script creates the extra partition, a
> different grub.cfg and also
> edits the /etc/fstab and mounts this partition over /boot and
> therefore virtual/grub-bootconf
> becomes unused.
> 
> This raises the following questions:
> - Why there are two different facilities to achieve the same thing?
> - Why the second overrides the first one, instead of sharing the same
> files?
> - How to proceed from now on?
> 

I think this needed --exclude-path in wks to be used to take effect.
Please see:


http://lists.openembedded.org/pipermail/openembedded-core/2018-February/147837.html

and bug:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=10073
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-kernel-cache][v4.4][PATCH] kver: bump to v4.4.147

[akuster808]

On 11/6/18 2:42 PM, Bruce Ashfield wrote:
> On 2018-11-06 5:10 PM, akuster808 wrote:
>>
>> On 11/6/18 2:05 PM, Khem Raj wrote:
>>> On Tue, Nov 6, 2018 at 1:57 PM Armin Kuster 
>>> wrote:
 Signed-off-by: Armin Kuster
 ---
   kver | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)

 diff --git a/kver b/kver
 index 7b008cd..5ccc572 100644
 --- a/kver
 +++ b/kver
 @@ -1 +1 @@
 -v4.4.141
 +v4.4.147
>>> why not 4.4.162
>>
>> because linux-yocto-4.4
>>  is not
>> at 4.4.162. I am just trying to use the latest in that kernel repo.
>
> Did you want .162 ? I have a whole set of -stable updates staged
> here, but haven't pushed anything since releases are imminent.

We are a day or two away from freezing for a Rocko QA run so if I can
get it sometime tomorrow, I should be able to  get some runtime on that
update otherwise no need to rush things.

- armin

>
> But in the case of 4.4, I could lift my freeze, given that the kernel
> recipe isn't active in master, hence the release schedule is
> different.
>

> Bruce
>
>>
>>
>> - armin
>>
 -- 
 2.7.4

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

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

Re: [yocto] [yocto-kernel-cache][v4.4][PATCH] kver: bump to v4.4.147

[Khem Raj]

On Tue, Nov 6, 2018 at 2:42 PM Bruce Ashfield
 wrote:
>
> On 2018-11-06 5:10 PM, akuster808 wrote:
> >
> > On 11/6/18 2:05 PM, Khem Raj wrote:
> >> On Tue, Nov 6, 2018 at 1:57 PM Armin Kuster  wrote:
> >>> Signed-off-by: Armin Kuster
> >>> ---
> >>>   kver | 2 +-
> >>>   1 file changed, 1 insertion(+), 1 deletion(-)
> >>>
> >>> diff --git a/kver b/kver
> >>> index 7b008cd..5ccc572 100644
> >>> --- a/kver
> >>> +++ b/kver
> >>> @@ -1 +1 @@
> >>> -v4.4.141
> >>> +v4.4.147
> >> why not 4.4.162
> >
> > because linux-yocto-4.4
> >  is not at
> > 4.4.162. I am just trying to use the latest in that kernel repo.
>
> Did you want .162 ? I have a whole set of -stable updates staged
> here, but haven't pushed anything since releases are imminent.
>
> But in the case of 4.4, I could lift my freeze, given that the kernel
> recipe isn't active in master, hence the release schedule is
> different.

No, we can wait and backport if needed.

>
> Bruce
>
> >
> >
> > - armin
> >
> >>> --
> >>> 2.7.4
> >>>
> >>> --
> >>> ___
> >>> yocto mailing list
> >>> yocto@yoctoproject.org
> >>> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-kernel-cache][v4.4][PATCH] kver: bump to v4.4.147

[Bruce Ashfield]

On 2018-11-06 8:07 p.m., akuster808 wrote:


On 11/6/18 2:42 PM, Bruce Ashfield wrote:

On 2018-11-06 5:10 PM, akuster808 wrote:


On 11/6/18 2:05 PM, Khem Raj wrote:

On Tue, Nov 6, 2018 at 1:57 PM Armin Kuster
wrote:

Signed-off-by: Armin Kuster
---
   kver | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kver b/kver
index 7b008cd..5ccc572 100644
--- a/kver
+++ b/kver
@@ -1 +1 @@
-v4.4.141
+v4.4.147

why not 4.4.162


because linux-yocto-4.4
 is not
at 4.4.162. I am just trying to use the latest in that kernel repo.


Did you want .162 ? I have a whole set of -stable updates staged
here, but haven't pushed anything since releases are imminent.


We are a day or two away from freezing for a Rocko QA run so if I can
get it sometime tomorrow, I should be able to  get some runtime on that
update otherwise no need to rush things.


If you check the 4.4 tree, and the kernel-cache, I've pushed the
latest set of -stable updates.

Up to you if you want to bump the SRCREVs to pick them up, but I've
validated them with my builds/boots.

Bruce



- armin



But in the case of 4.4, I could lift my freeze, given that the kernel
recipe isn't active in master, hence the release schedule is
different.




Bruce




- armin


--
2.7.4

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






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

Re: [yocto] thud, beaglebone-yocto.conf: SERIAL_CONSOLES setting

[Heiko Schocher]

Hello Kevin, Robert,

Am 06.11.2018 um 09:10 schrieb Heiko Schocher:

Hello Kevin, Robert,

Am 05.11.2018 um 06:26 schrieb Kevin Hao:

On Sun, Nov 04, 2018 at 12:10:00PM +0200, Robert Berger wrote:

Hi,

On 02.11.18 16:27, Khem Raj wrote:


omap serial is obsolete why does linux-yocto keeps using it.
seondly, machine config should enable both consoles ttyO0 and ttyS0 if
you know that at least one kernel is using ttyO0


How about picking whatever works for you in the kernel conf and in machine
conf?

SERIAL_CONSOLES = "115200;ttyS0 115200;ttyO0"
SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"

Like this on the first boot either ttyO0 or ttyS0 should be picked
automatically.


Yes, this is doable. Would you mind send a patch?


Sorry for answering so late... good hint, I missed SERIAL_CONSOLES_CHECK

I try this change and report, give me some time...



diff --git a/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf 
b/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf

index e911e75004..def3a2ae06 100644
--- a/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
+++ b/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
@@ -20,7 +20,8 @@ WKS_FILE ?= "beaglebone-yocto.wks"
 IMAGE_INSTALL_append = " kernel-devicetree kernel-image-zimage"
 do_image_wic[depends] += "mtools-native:do_populate_sysroot 
dosfstools-native:do_populate_sysroot"

-SERIAL_CONSOLES = "115200;ttyO0"
+SERIAL_CONSOLES = "115200;ttyS0 115200;ttyO0"
+SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"

 PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
 PREFERRED_VERSION_linux-yocto ?= "4.18%"

and on my beagleboneblack linux kernels with 8250 serial driver enabled
(console ttyS0) and kernel omap_serial driver enabled (console ttyO0)
are booting.

Unfortunately it took me some time, until I realized that my settings
in auto.conf do not work, because in beaglebone-yocto.conf

SERIAL_CONSOLES = "115200;ttyO0"

is set ... May a

SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyO0"

is friendlier ?

Should I send a formal patch?

bye,
Heiko
--
DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-52   Fax: +49-8142-66989-80   Email: h...@denx.de
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto