[linux-yocto][v5.10/standard/preempt-rt/*][PATCH 2/2] Revert "printk: declare printk_deferred_{enter,safe}() in include/linux/printk.h"

2023-05-22 Thread Li Wang via lists.yoctoproject.org
For rt kernel, remove printk_deferred_{enter,safe}().

This reverts upstream commit 85e3e7fbbb720b9897fba9a99659e31cbd1c082e.

Signed-off-by: Li Wang 
---
 include/linux/printk.h | 19 ---
 1 file changed, 19 deletions(-)

diff --git a/include/linux/printk.h b/include/linux/printk.h
index 83c7734e9802..7e4352467d83 100644
--- a/include/linux/printk.h
+++ b/include/linux/printk.h
@@ -609,23 +609,4 @@ static inline void print_hex_dump_debug(const char 
*prefix_str, int prefix_type,
 #define print_hex_dump_bytes(prefix_str, prefix_type, buf, len)\
print_hex_dump_debug(prefix_str, prefix_type, 16, 1, buf, len, true)
 
-#ifdef CONFIG_PRINTK
-extern void __printk_safe_enter(void);
-extern void __printk_safe_exit(void);
-/*
- * The printk_deferred_enter/exit macros are available only as a hack for
- * some code paths that need to defer all printk console printing. Interrupts
- * must be disabled for the deferred duration.
- */
-#define printk_deferred_enter __printk_safe_enter
-#define printk_deferred_exit __printk_safe_exit
-#else
-static inline void printk_deferred_enter(void)
-{
-}
-static inline void printk_deferred_exit(void)
-{
-}
-#endif
-
 #endif
-- 
2.39.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#12641): 
https://lists.yoctoproject.org/g/linux-yocto/message/12641
Mute This Topic: https://lists.yoctoproject.org/mt/99079887/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][v5.10/standard/preempt-rt/*][PATCH 1/2] mm/page_alloc: Drop the deferred printing

2023-05-22 Thread Li Wang via lists.yoctoproject.org
From: Kevin Hao 

For rt kernel, the console printing occurs either atomically or from
the printing kthread, all the printk defer functions have been dropped
by commit 25f13bd1d07b ("printk: remove deferred printing"). This patch
drops the new one which is introduced by stable commit 0431e1323f42
("mm/page_alloc: fix potential deadlock on zonelist_update_seq seqlock").

Signed-off-by: Kevin Hao 
Signed-off-by: Bruce Ashfield 
Signed-off-by: Li Wang 
---
 mm/page_alloc.c | 8 
 1 file changed, 8 deletions(-)

diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index 5f1c50a6bebc..44f5c69b2ded 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -6051,13 +6051,6 @@ static void __build_all_zonelists(void *data)
 * (e.g. GFP_ATOMIC) that could hit zonelist_iter_begin and livelock.
 */
local_irq_save(flags);
-   /*
-* Explicitly disable this CPU's synchronous printk() before taking
-* seqlock to prevent any printk() from trying to hold port->lock, for
-* tty_insert_flip_string_and_push_buffer() on other CPU might be
-* calling kmalloc(GFP_ATOMIC | __GFP_NOWARN) with port->lock held.
-*/
-   printk_deferred_enter();
write_seqlock(_update_seq);
 
 #ifdef CONFIG_NUMA
@@ -6092,7 +6085,6 @@ static void __build_all_zonelists(void *data)
}
 
write_sequnlock(_update_seq);
-   printk_deferred_exit();
local_irq_restore(flags);
 }
 
-- 
2.39.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#12640): 
https://lists.yoctoproject.org/g/linux-yocto/message/12640
Mute This Topic: https://lists.yoctoproject.org/mt/99079886/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][v5.10/standard/preempt-rt/*] fix preempt-rt compile error

2023-05-22 Thread Li Wang via lists.yoctoproject.org
Hi Bruce,

I think the 2 patches should also merge to:
https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git/log/?h=v5.10-rt-next

x86_64-wrs-linux-ld.bfd: mm/page_alloc.o: in function `__build_all_zonelists':
/usr/src/kernel/mm/page_alloc.c:6060: undefined reference to 
`__printk_safe_enter'
x86_64-wrs-linux-ld.bfd: /usr/src/kernel/mm/page_alloc.c:6095: undefined 
reference to `__printk_safe_exit'

Thanks,
LiWang.


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#12639): 
https://lists.yoctoproject.org/g/linux-yocto/message/12639
Mute This Topic: https://lists.yoctoproject.org/mt/99079885/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Enhancements/Bugs closed WW20!

2023-05-22 Thread Stephen Jolley
All,

The below were the owners of enhancements or bugs closed during the last
week!


Who

Count


randy.macl...@windriver.com

2


ross.bur...@arm.com

1


alex.kana...@gmail.com

1


Grand Total

4

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60089): https://lists.yoctoproject.org/g/yocto/message/60089
Mute This Topic: https://lists.yoctoproject.org/mt/99077691/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Current high bug count owners for Yocto Project 4.3

2023-05-22 Thread Stephen Jolley
All,

Below is the list as of top 34 bug owners as of the end of WW20 of who have
open medium or higher bugs and enhancements against YP 4.3. There are 109
possible work days left until the final release candidates for YP 4.3 needs
to be released.


Who

Count


ross.bur...@arm.com

33


michael.opdenac...@bootlin.com

31


david.re...@windriver.com

27


richard.pur...@linuxfoundation.org

26


randy.macl...@windriver.com

25


bruce.ashfi...@gmail.com

25


jpewhac...@gmail.com

11


pa...@zhukoff.net

9


sakib.sa...@windriver.com

6


sundeep.kokko...@windriver.com

5


tim.orl...@konsulko.com

4


pi...@pidge.org

4


yash.shi...@windriver.com

3


p.lob...@welotec.com

2


jon.ma...@arm.com

2


alexis.loth...@bootlin.com

2


tvgamb...@gmail.com

1


thr...@amazon.de

1


thomas.per...@bootlin.com

1


naveen.kumar.sa...@intel.com

1


mathew.pro...@gmail.com

1


martin.ja...@gmail.com

1


mark.ha...@kernel.crashing.org

1


mark.asselst...@windriver.com

1


louis.ran...@syslinbit.com

1


johannes.schri...@blueye.no

1


jens.ge...@desy.de

1


geissona...@yahoo.com

1


frederic.martins...@gmail.com

1


frank.wo...@smile.fr

1


fawzi.kha...@smile.fr

1


fathi.bou...@linaro.org

1


anuj.mit...@intel.com

1


alexandre.bell...@bootlin.com

1


Grand Total

233

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60088): https://lists.yoctoproject.org/g/yocto/message/60088
Mute This Topic: https://lists.yoctoproject.org/mt/99077598/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2023-05-22 Thread Stephen Jolley
All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:

https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 430
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now,  "4.2", "4.3", "4.99" and "Future", the more pressing/urgent
issues being in "4.2" and then "4.3".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60087): https://lists.yoctoproject.org/g/yocto/message/60087
Mute This Topic: https://lists.yoctoproject.org/mt/99077580/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] [opkg-utils PATCH V2] opkg-feed: Fix adding feeds with same name as architecture

2023-05-22 Thread Alex Stewart

ACK; looks good to me.

I'll pull this tomorrow, if there are no objections.

On 5/22/23 12:48, Petar Koynov wrote:

 Attempting to add feeds with some special names that match
 architecture names was returning an error:
 "5   The named feed already exists"
 Make sourceTypePattern in createFeedLineRegex only match
 feed configuration lines src or dist

Signed-off-by: Petar Koynov 
---
  opkg-feed | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/opkg-feed b/opkg-feed
index 25ef879..36d4463 100755
--- a/opkg-feed
+++ b/opkg-feed
@@ -171,7 +171,7 @@ createFeedLineRegex()
#   1 = full source type with any quotes
#   2 = source type without quotes if quoted
#   3 = source type if unquoted
-   sourceTypePattern='("([^"]*)"|(\S+))\s+';
+   sourceTypePattern='("([^"](src|dist)(/gz)?)"|(src|dist)(/gz)?)\s+';
  
  	# Feed name capture groups (4, 5, 6)

#   4 = full feed name with any quotes


--
Alex Stewart
Software Engineer - NI Real-Time OS
NI (National Instruments)

alex.stew...@ni.com


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60086): https://lists.yoctoproject.org/g/yocto/message/60086
Mute This Topic: https://lists.yoctoproject.org/mt/99070322/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] [opkg-utils PATCH V2] opkg-feed: Fix adding feeds with same name as architecture

2023-05-22 Thread Petar Koynov
Attempting to add feeds with some special names that match
architecture names was returning an error:
"5   The named feed already exists"
Make sourceTypePattern in createFeedLineRegex only match
feed configuration lines src or dist

Signed-off-by: Petar Koynov 
---
 opkg-feed | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/opkg-feed b/opkg-feed
index 25ef879..36d4463 100755
--- a/opkg-feed
+++ b/opkg-feed
@@ -171,7 +171,7 @@ createFeedLineRegex()
#   1 = full source type with any quotes
#   2 = source type without quotes if quoted
#   3 = source type if unquoted
-   sourceTypePattern='("([^"]*)"|(\S+))\s+';
+   sourceTypePattern='("([^"](src|dist)(/gz)?)"|(src|dist)(/gz)?)\s+';
 
# Feed name capture groups (4, 5, 6)
#   4 = full feed name with any quotes
-- 
2.32.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60085): https://lists.yoctoproject.org/g/yocto/message/60085
Mute This Topic: https://lists.yoctoproject.org/mt/99070322/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] core-image-weston mickledore

2023-05-22 Thread Khem Raj
On Mon, May 22, 2023 at 5:26 AM Marek Belisko  wrote:
>
> Hi,
>
> I'm using core-image-weston and adding chromium to the final image.
> Weston is properly started on the hdmi monitor. I'm trying to start
> chromium when weston starts with following:
>
> [Unit]
> Description="Chromium browser start"
> Requires=weston.service
> After=weston.service
>
>
> [Service]
> Type=simple
> Environment=XDG_RUNTIME_DIR="/run/user/0"

Make it Environment=XDG_RUNTIME_DIR="/run/user/`id -u`"

also add

Environment=WAYLAND_DISPLAY="`ls -1 /run/user/`id -u`/ | egrep
'wayland-[0-9]+$'`"

> ExecStart=/usr/bin/chromium https://google.com
> Restart=always
> RestartSec=5
>
> User=weston
> Group=weston
>
>
> [Install]
> WantedBy=multi-user.target
>
> but getting this:
>
> May 22 12:23:26 orange-pi-pc2 sh[254]:
> [250:250:0522/122326.671204:ERROR:wayland_connection.cc(186)] Failed
> to connect
> to Wayland display: Permission denied (13)
> May 22 12:23:26 orange-pi-pc2 sh[254]:
> [250:250:0522/122326.674692:ERROR:ozone_platform_wayland.cc(233)]
> Failed to init
> ialize Wayland platform
> May 22 12:23:26 orange-pi-pc2 sh[254]:
> [250:250:0522/122326.674738:ERROR:env.cc(255)] The platform failed to
> initialize
> .  Exiting.
>
> When running the terminal from wayland desktop chromium works fine. Am
> I missing something to start it properly?
>
> Thanks and 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
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60084): https://lists.yoctoproject.org/g/yocto/message/60084
Mute This Topic: https://lists.yoctoproject.org/mt/99063456/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] Final reminder: CFP for Yocto Project Developer Day in Prague, June 26th 2023

2023-05-22 Thread Josef Holzmayr
Hello there!

Time is running out for you if you'd like to speak at the Yocto Project
Developer Day in Prague on June 26th, 2023 in Prague, neatly colocated with
EOSS.

You have exactly...*checks clock* 3 hours and 44 minutes left to let us
know about the cool things you built, the riddles you solved, or just how
you use or support the Yocto Project.

So hurry up!

Greetz,
Josef of on behalf of the organization team

PS: 3 hours and 42 minutes now, sorry.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60083): https://lists.yoctoproject.org/g/yocto/message/60083
Mute This Topic: https://lists.yoctoproject.org/mt/99068285/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] rustfmt error when trying to build a rust application

2023-05-22 Thread Guenther Meyer
Hi,

I'm trying to add a rust application to my distro based on kirkstone, and 
created a recipe with cargo-bitbake.
The build fails with:

error running rustfmt: Os { code: 2, kind: NotFound, message: "No such file 
or directory" }

I also tried to add the meta-lts-mixins layer - same result.

Any ideas, did I miss something? I'm not really a rust developer.






signature.asc
Description: This is a digitally signed message part.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60082): https://lists.yoctoproject.org/g/yocto/message/60082
Mute This Topic: https://lists.yoctoproject.org/mt/99067117/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.2.1)

2023-05-22 Thread Jing Hui Tham
Hi all,
 
Intel and WR YP QA is planning for QA execution for YP build yocto-4.2.1. We 
are planning to execute following tests for this cycle:
 
OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw
 
Runtime auto test for following platforms:
1. MinnowBoard Turbot - 32bit
2. Kaby Lake (7th Generation Intel(r) Core(tm) Processors)
3. Tiger Lake (11th Generation Intel(r) Core(tm) Processors)
4. Alder Lake-S (12th Generation Intel(r) Core(tm) Processors)
5. Raptor Lake-P (13th Generation Intel(r) Core(tm) Processors)
6. Edgerouter
7. Beaglebone

 
ETA for completion Thursday, 25 May 2023.
 
Best regards,
Jing Hui

> -Original Message-
> From: qa-build-notificat...@lists.yoctoproject.org  notificat...@lists.yoctoproject.org> On Behalf Of Pokybuild User
> Sent: Saturday, May 20, 2023 7:22 AM
> To: yocto@lists.yoctoproject.org
> Cc: qa-build-notificat...@lists.yoctoproject.org
> Subject: [qa-build-notification] QA notification for completed autobuilder
> build (yocto-4.2.1)
> 
> 
> A build flagged for QA (yocto-4.2.1) was completed on the autobuilder and
> is available at:
> 
> 
> https://autobuilder.yocto.io/pub/releases/yocto-4.2.1
> 
> 
> Build hash information:
> 
> bitbake: d97d62e2cbe4bae17f0886f3b4759e8f9ba6d38c
> meta-agl: 09135164a21a216c6e3e75d7decce896b92962f0
> meta-arm: 68509775774d9cf304e2b422927f2a9636525155
> meta-aws: 98efcdaf375df31c53d0f8d28240a079dae7b4d9
> meta-intel: a0ea4e5d395579e70f1057f1f1222c8a2b55bd96
> meta-mingw: cc9fd0a988dc1041035a6a6cafb2d1237ef38d8e
> meta-openembedded: 54b177f4acb3048d21a68f180fc183d0fdf47a94
> meta-virtualization: 1e338cbfd80dc34f90f13f92fba2e810f6858ed6
> oecore: 20cd64812d286c920bd766145ab1cd968e72667e
> poky: c5c69f78fc7ce4ba361363c14352e4264ce7813f
> 
> 
> 
> This is an automated message from the Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder2
> Email: richard.pur...@linuxfoundation.org
> 
> 
> 
> 
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60081): https://lists.yoctoproject.org/g/yocto/message/60081
Mute This Topic: https://lists.yoctoproject.org/mt/99065804/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [yocto] [meta-security][PATCH] libhoth_git.bb:SRCREV bump 1622e8a04..d769296220d

2023-05-22 Thread Armin Kuster



On 5/17/23 1:27 PM, John Broadbent via lists.yoctoproject.org wrote:

From: John Edward Broadbent 


merged thanks.

-armin


Updating libhoth to match version in openbmc
https://gerrit.openbmc.org/c/openbmc/openbmc/+/63424

libhoth detailed changes:

Willy Tu
 Expose header files expose USB APIs

aranikam
 Add flash_spi_info command
 Add address mode flag for spi update/read

Chris Evans
 Rename ec_ commands; permit old command names as an alias.
 Apply clang-format, and enable it as a check action. (#24)

Sui Chen
 Add payload status
 Add console snapshot

Daimeng Wang
 libhoth: automated mtd mailbox discovery
 libhoth: implement MTD transport
 libhoth: add MTD backend boilerplate API

Yoan Andreev
 Dont check for non-snapshot console params
 Extern c wrap (#22)
 Build improvements (#18)
 Add basic abstraction to libhoth and SPIDEV support (#17)

Vidya Satyamsetti
 Add extern

Kor Nielsen
 htool console: Don't leave O_NONBLOCK set on stdin
 [fix] In legacy mailbox protocol, look at response size.
 [fix] Support legacy response buffers larger than 62 bytes.
 [feat] htool: Support Hoth-B devices.
 Add --baud_rate flag to "htool console".
 Setup github workflow to build project.
 Rename "htool console -l" to "htool console -n".
 Add --onlcr flag to "htool console".
 Make example visibility public.
 Fix BUILD file formatting.
 Remove out-of-date :enumerate and :ec_hello.
 Add libusb to bazel WORKSPACE.
 Fix undefined behavior in htool command handling.

Signed-off-by: John Edward Broadbent 
---
  meta-tpm/recipes-tpm1/hoth/libhoth_git.bb | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-tpm/recipes-tpm1/hoth/libhoth_git.bb 
b/meta-tpm/recipes-tpm1/hoth/libhoth_git.bb
index a3ebce7..0485afc 100644
--- a/meta-tpm/recipes-tpm1/hoth/libhoth_git.bb
+++ b/meta-tpm/recipes-tpm1/hoth/libhoth_git.bb
@@ -7,7 +7,7 @@ LICENSE = "Apache-2.0"
  LIC_FILES_CHKSUM = "file://LICENSE;md5=3b83ef96387f14655fc854ddc3c6bd57"
  
  SRC_URI = "git://github.com/google/libhoth;protocol=https;branch=main"

-SRCREV = "1622e8a040d21dd564fdc1cb4df5eda01688c197"
+SRCREV = "769296220dc88df33f4726aa11e39e049257b3c4"
  
  DEPENDS += "libusb1"
  







-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60080): https://lists.yoctoproject.org/g/yocto/message/60080
Mute This Topic: https://lists.yoctoproject.org/mt/98953266/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[yocto] core-image-weston mickledore

2023-05-22 Thread Marek Belisko
Hi,

I'm using core-image-weston and adding chromium to the final image.
Weston is properly started on the hdmi monitor. I'm trying to start
chromium when weston starts with following:

[Unit]
Description="Chromium browser start"
Requires=weston.service
After=weston.service


[Service]
Type=simple
Environment=XDG_RUNTIME_DIR="/run/user/0"
ExecStart=/usr/bin/chromium https://google.com
Restart=always
RestartSec=5

User=weston
Group=weston


[Install]
WantedBy=multi-user.target

but getting this:

May 22 12:23:26 orange-pi-pc2 sh[254]:
[250:250:0522/122326.671204:ERROR:wayland_connection.cc(186)] Failed
to connect
to Wayland display: Permission denied (13)
May 22 12:23:26 orange-pi-pc2 sh[254]:
[250:250:0522/122326.674692:ERROR:ozone_platform_wayland.cc(233)]
Failed to init
ialize Wayland platform
May 22 12:23:26 orange-pi-pc2 sh[254]:
[250:250:0522/122326.674738:ERROR:env.cc(255)] The platform failed to
initialize
.  Exiting.

When running the terminal from wayland desktop chromium works fine. Am
I missing something to start it properly?

Thanks and 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

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60079): https://lists.yoctoproject.org/g/yocto/message/60079
Mute This Topic: https://lists.yoctoproject.org/mt/99063456/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[linux-yocto][v5.10/standard/nxp-sdk-5.10/nxp-soc & v5.10/standard/preempt-rt/nxp-sdk-5.10/nxp-soc][PATCH] qoriq_thermal.c: crash of error device pointer value

2023-05-22 Thread Li Wang via lists.yoctoproject.org
qoriq_tmu_probe ->
qoriq_tmu_register_tmu_zone ->
devfreq_cooling_register: return 0
sensor->cdev->type: crash

the fix codes come from:
https://github.com/nxp-imx/linux-imx/blob/lf-6.1.y/include/linux/device_cooling.h

Unable to handle kernel NULL pointer dereference at virtual address 
0008
pc : qoriq_tmu_probe+0x568/0x5b0
lr : qoriq_tmu_probe+0x440/0x5b0
Call trace:
qoriq_tmu_probe+0x568/0x5b0
...
Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b

Signed-off-by: Li Wang 
---
 include/linux/device_cooling.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/linux/device_cooling.h b/include/linux/device_cooling.h
index 18d9e3b90ed9..f318e22c1472 100644
--- a/include/linux/device_cooling.h
+++ b/include/linux/device_cooling.h
@@ -33,7 +33,7 @@ int unregister_devfreq_cooling_notifier(struct notifier_block 
*nb)
 static inline
 struct thermal_cooling_device *devfreq_cooling_register(void)
 {
-   return NULL;
+   return ERR_PTR(-EINVAL);
 }
 
 static inline
-- 
2.35.5


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#12638): 
https://lists.yoctoproject.org/g/linux-yocto/message/12638
Mute This Topic: https://lists.yoctoproject.org/mt/99063446/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-