Re: 64-bit time_t transition in progress
Il 02/02/2024 17:43, Steve Langasek ha scritto: Hello, debian-devel-announce wouldn't let me attach the file, but for those on debian-devel at least, you can find the dd-list of to-be-NMUed source packages attached. Thanks, Sorry to bother you (or anyone else who wants to answer) with a question that might be stupid, maybe I didn't understand something. From what I understand, for most of the packages involved a rebuild is enough but this rebuild must be done after that of all their dependencies (dependencies of dependencies etc...) involved to avoid unexpected events that could cause crashes on some architectures (in cases ABI changes occurred in the underlying dependencies but the rebuild was done before one of those). Having a package that depends on many and that part of those are themselves involved in various other chains, how do NMU (when needed) to unstable and rebuilds of other packages happen? A single NMU on unstable or rebuild (for each package involved) but with such an order so that when it is done all dependencies are already rebuild, or with multiple rebuilds between the various migration chains involved? Thanks for any reply and sorry for my bad english. OpenPGP_signature.asc Description: OpenPGP digital signature
Re: [PATCH v2 2/3] mx6sabresd: Convert to watchdog driver model
On Fri, Feb 2, 2024 at 1:07 PM Tom Rini wrote: > Can all of this be upstreamed as well? I can try it, but that would go into kernel 6.9 in the best case. For now, let's keep it in u-boot.dtsi.
[PATCH v2 3/3] mx6sabresd: Remove board_phy_config()
From: Fabio Estevam
With Ethernet DM in place, there is no longer the need for having
the board_phy_config() anymore.
Remove it.
Confirmed that TFTP transfer still works fine without board_phy_config().
Signed-off-by: Fabio Estevam
---
Changes since v1:
- Newly introduced.
board/freescale/mx6sabresd/mx6sabresd.c | 34 -
1 file changed, 34 deletions(-)
diff --git a/board/freescale/mx6sabresd/mx6sabresd.c
b/board/freescale/mx6sabresd/mx6sabresd.c
index b558a596dff8..bb066a5d36c3 100644
--- a/board/freescale/mx6sabresd/mx6sabresd.c
+++ b/board/freescale/mx6sabresd/mx6sabresd.c
@@ -7,7 +7,6 @@
#include
#include
-#include
#include
#include
#include
@@ -254,39 +253,6 @@ int board_mmc_init(struct bd_info *bis)
}
#endif
-static int ar8031_phy_fixup(struct phy_device *phydev)
-{
- unsigned short val;
-
- /* To enable AR8031 ouput a 125MHz clk from CLK_25M */
- phy_write(phydev, MDIO_DEVAD_NONE, 0xd, 0x7);
- phy_write(phydev, MDIO_DEVAD_NONE, 0xe, 0x8016);
- phy_write(phydev, MDIO_DEVAD_NONE, 0xd, 0x4007);
-
- val = phy_read(phydev, MDIO_DEVAD_NONE, 0xe);
- val &= 0xffe3;
- val |= 0x18;
- phy_write(phydev, MDIO_DEVAD_NONE, 0xe, val);
-
- /* introduce tx clock delay */
- phy_write(phydev, MDIO_DEVAD_NONE, 0x1d, 0x5);
- val = phy_read(phydev, MDIO_DEVAD_NONE, 0x1e);
- val |= 0x0100;
- phy_write(phydev, MDIO_DEVAD_NONE, 0x1e, val);
-
- return 0;
-}
-
-int board_phy_config(struct phy_device *phydev)
-{
- ar8031_phy_fixup(phydev);
-
- if (phydev->drv->config)
- phydev->drv->config(phydev);
-
- return 0;
-}
-
#if defined(CONFIG_VIDEO_IPUV3)
static void disable_lvds(struct display_info_t const *dev)
{
--
2.34.1
[PATCH v2 2/3] mx6sabresd: Convert to watchdog driver model
From: Fabio Estevam
Commit 68dcbdd594d4 ("ARM: imx: Add weak default reset_cpu()") caused
the 'reset' command in U-Boot to not cause a board reset.
Fix it by switching to the watchdog driver model via sysreset, which
is the preferred method for implementing the watchdog reset.
Signed-off-by: Fabio Estevam
---
Changes since v1:
- None.
arch/arm/dts/imx6qdl-sabresd-u-boot.dtsi | 9 +
configs/mx6sabresd_defconfig | 3 +++
2 files changed, 12 insertions(+)
diff --git a/arch/arm/dts/imx6qdl-sabresd-u-boot.dtsi
b/arch/arm/dts/imx6qdl-sabresd-u-boot.dtsi
index 5c4101b76da2..9e9c4422f00e 100644
--- a/arch/arm/dts/imx6qdl-sabresd-u-boot.dtsi
+++ b/arch/arm/dts/imx6qdl-sabresd-u-boot.dtsi
@@ -9,6 +9,11 @@
aliases {
mmc1 =
};
+ wdt-reboot {
+ compatible = "wdt-reboot";
+ wdt = <>;
+ bootph-pre-ram;
+ };
};
{
@@ -18,3 +23,7 @@
_usdhc3 {
bootph-pre-ram;
};
+
+ {
+ bootph-pre-ram;
+};
diff --git a/configs/mx6sabresd_defconfig b/configs/mx6sabresd_defconfig
index f19df607e7ae..69685f12eb10 100644
--- a/configs/mx6sabresd_defconfig
+++ b/configs/mx6sabresd_defconfig
@@ -103,6 +103,8 @@ CONFIG_DM_REGULATOR_FIXED=y
CONFIG_DM_REGULATOR_GPIO=y
CONFIG_DM_SERIAL=y
CONFIG_MXC_UART=y
+CONFIG_SYSRESET=y
+CONFIG_SYSRESET_WATCHDOG=y
CONFIG_SPI=y
CONFIG_DM_SPI=y
CONFIG_MXC_SPI=y
@@ -129,3 +131,4 @@ CONFIG_IMX_HDMI=y
CONFIG_SPLASH_SCREEN=y
CONFIG_SPLASH_SCREEN_ALIGN=y
CONFIG_BMP_16BPP=y
+CONFIG_IMX_WATCHDOG=y
--
2.34.1
[PATCH v2 1/3] mx6sabresd: Fix U-Boot corruption after saving the environment
From: Fabio Estevam U-Boot binary has grown in such a way that it goes beyond the reserved area for the environment variables. Running "saveenv" and rebooting the board causes U-Boot to hang because of this overlap. Fix this problem by selecting CONFIG_LTO so that the U-Boot proper size can be reduced. Also, to prevent this same problem to happen in the future, use CONFIG_BOARD_SIZE_LIMIT, which can detect the overlap in build-time. CONFIG_BOARD_SIZE_LIMIT is calculated as follows: CONFIG_BOARD_SIZE_LIMIT = CONFIG_ENV_OFFSET - u-boot-img.dtb offset CONFIG_BOARD_SIZE_LIMIT = 0xc000 - 69 * 1024 CONFIG_BOARD_SIZE_LIMIT = 715766 Signed-off-by: Fabio Estevam --- Changes since v1: - Select LTO. (Tom) configs/mx6sabresd_defconfig | 3 +++ 1 file changed, 3 insertions(+) diff --git a/configs/mx6sabresd_defconfig b/configs/mx6sabresd_defconfig index a90efe4a7786..d4fb55622cf1 100644 --- a/configs/mx6sabresd_defconfig +++ b/configs/mx6sabresd_defconfig @@ -21,6 +21,9 @@ CONFIG_SPL_SERIAL=y CONFIG_SPL=y CONFIG_SPL_LIBDISK_SUPPORT=y CONFIG_PCI=y +CONFIG_LTO=y +CONFIG_HAS_BOARD_SIZE_LIMIT=y +CONFIG_BOARD_SIZE_LIMIT=715766 CONFIG_FIT=y CONFIG_SPL_FIT_PRINT=y CONFIG_SPL_LOAD_FIT=y -- 2.34.1
[jira] [Created] (SYNCOPE-1802) Missing delegated SAML2 IdP configuration parameter
Fabio Martelli created SYNCOPE-1802: --- Summary: Missing delegated SAML2 IdP configuration parameter Key: SYNCOPE-1802 URL: https://issues.apache.org/jira/browse/SYNCOPE-1802 Project: Syncope Issue Type: Improvement Components: common, wa Affects Versions: 3.0.6 Reporter: Fabio Martelli Fix For: 3.0.7 Missing parameters serviceProviderMetadataPath and responsesSigned. Missing mapping for KeystorePath and WantsAssertionsSigned. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PATCH 2/2] mx6sabresd: Convert to watchdog driver model
From: Fabio Estevam
Commit 68dcbdd594d4 ("ARM: imx: Add weak default reset_cpu()") caused
the 'reset' command in U-Boot to not cause a board reset.
Fix it by switching to the watchdog driver model via sysreset, which
is the preferred method for implementing the watchdog reset.
Signed-off-by: Fabio Estevam
---
arch/arm/dts/imx6qdl-sabresd-u-boot.dtsi | 9 +
configs/mx6sabresd_defconfig | 3 +++
2 files changed, 12 insertions(+)
diff --git a/arch/arm/dts/imx6qdl-sabresd-u-boot.dtsi
b/arch/arm/dts/imx6qdl-sabresd-u-boot.dtsi
index 5c4101b76da2..9e9c4422f00e 100644
--- a/arch/arm/dts/imx6qdl-sabresd-u-boot.dtsi
+++ b/arch/arm/dts/imx6qdl-sabresd-u-boot.dtsi
@@ -9,6 +9,11 @@
aliases {
mmc1 =
};
+ wdt-reboot {
+ compatible = "wdt-reboot";
+ wdt = <>;
+ bootph-pre-ram;
+ };
};
{
@@ -18,3 +23,7 @@
_usdhc3 {
bootph-pre-ram;
};
+
+ {
+ bootph-pre-ram;
+};
diff --git a/configs/mx6sabresd_defconfig b/configs/mx6sabresd_defconfig
index f19df607e7ae..69685f12eb10 100644
--- a/configs/mx6sabresd_defconfig
+++ b/configs/mx6sabresd_defconfig
@@ -103,6 +103,8 @@ CONFIG_DM_REGULATOR_FIXED=y
CONFIG_DM_REGULATOR_GPIO=y
CONFIG_DM_SERIAL=y
CONFIG_MXC_UART=y
+CONFIG_SYSRESET=y
+CONFIG_SYSRESET_WATCHDOG=y
CONFIG_SPI=y
CONFIG_DM_SPI=y
CONFIG_MXC_SPI=y
@@ -129,3 +131,4 @@ CONFIG_IMX_HDMI=y
CONFIG_SPLASH_SCREEN=y
CONFIG_SPLASH_SCREEN_ALIGN=y
CONFIG_BMP_16BPP=y
+CONFIG_IMX_WATCHDOG=y
--
2.34.1
[PATCH 1/2] mx6sabresd: Fix U-Boot corruption after saving the environment
From: Fabio Estevam
U-Boot binary has grown in such a way that it goes beyond the reserved
area for the environment variables.
Running "saveenv" and rebooting the board causes U-Boot to hang because
of this overlap.
Fix this problem by increasing the CONFIG_ENV_OFFSET.
Also, to prevent this same problem to happen in the future, use
CONFIG_BOARD_SIZE_LIMIT, which can detect the overlap in build-time.
CONFIG_BOARD_SIZE_LIMIT is calculated as follows:
CONFIG_BOARD_SIZE_LIMIT = CONFIG_ENV_OFFSET - u-boot-img.dtb offset
CONFIG_BOARD_SIZE_LIMIT = 0xd000 - 69 * 1024
CONFIG_BOARD_SIZE_LIMIT = 781312
Signed-off-by: Fabio Estevam
---
configs/mx6sabresd_defconfig | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/configs/mx6sabresd_defconfig b/configs/mx6sabresd_defconfig
index a90efe4a7786..f19df607e7ae 100644
--- a/configs/mx6sabresd_defconfig
+++ b/configs/mx6sabresd_defconfig
@@ -9,7 +9,7 @@ CONFIG_SPL_LIBGENERIC_SUPPORT=y
CONFIG_NR_DRAM_BANKS=1
CONFIG_SF_DEFAULT_SPEED=2000
CONFIG_ENV_SIZE=0x2000
-CONFIG_ENV_OFFSET=0xC
+CONFIG_ENV_OFFSET=0xd
CONFIG_MX6QDL=y
CONFIG_TARGET_MX6SABRESD=y
CONFIG_DM_GPIO=y
@@ -24,6 +24,8 @@ CONFIG_PCI=y
CONFIG_FIT=y
CONFIG_SPL_FIT_PRINT=y
CONFIG_SPL_LOAD_FIT=y
+CONFIG_HAS_BOARD_SIZE_LIMIT=y
+CONFIG_BOARD_SIZE_LIMIT=781312
CONFIG_SUPPORT_RAW_INITRD=y
CONFIG_USE_BOOTCOMMAND=y
CONFIG_BOOTCOMMAND="run findfdt;mmc dev ${mmcdev};if mmc rescan; then if run
loadbootscript; then run bootscript; else if run loadimage; then run mmcboot;
else run netboot; fi; fi; else run netboot; fi"
--
2.34.1
Re: Package review ticket status change after approval
On Mon, Jan 29, 2024 at 7:47 PM Mattia Verga via devel wrote: > (snip) > > That said, I'd like to make a request and maybe make all reviewers aware > of a feature which was implemented some time ago. I've noticed many > reviewers change the ticket status from ASSIGNED to POST when they flag > the package as approved: I'd like to request to not do that. > > The Package Review Tracker webpages make a distinction between packages > approved (fedora-review flag set to +) and packages approved AND being > built in Fedora. That distinction relies on the ticket status change to > POST, which is automatically set when the repository is created in src.fp.o. Hum ... am I missing something here? The bot that creates the dist-git repos does *NOT*, in fact, set the bug status to POST: https://bugzilla.redhat.com/show_bug.cgi?id=2260350#c5 Fabio -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Bug#1062060: cinnamon-desktop: NMU diff for 64-bit time_t transition
Hi, today I saw there is an autotransition that check the renamed libraries, so I must keep them? https://release.debian.org/transitions/html/auto-cinnamon-desktop.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1062060: cinnamon-desktop: NMU diff for 64-bit time_t transition
Hi, today I saw there is an autotransition that check the renamed libraries, so I must keep them? https://release.debian.org/transitions/html/auto-cinnamon-desktop.html OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1061952: freerdp2: NMU diff for 64-bit time_t transition
hi, if not already spotted, keep attention that NMU missed needed replaces and breaks. as reported also by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061982 OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1061952: freerdp2: NMU diff for 64-bit time_t transition
hi, if not already spotted, keep attention that NMU missed needed replaces and breaks. as reported also by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061982 OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1062060: cinnamon-desktop: NMU diff for 64-bit time_t transition
Il 31/01/2024 22:24, Steve Langasek ha scritto: On Wed, Jan 31, 2024 at 02:01:06PM +0100, Fabio Fantoni wrote: I'm also making some improvements that I know are needed for the cinnamon packages but slowly so as not to risk coming close to burnout again (spending less time on the PC, at least in my free time), I'll add to the list also to add the missed breaks of reverse deps. Ok, if you handle it this way via additional breaks, then I think that's sufficient for this transition and you can consider this bug resolved once 1) the dpkg change is uploaded to unstable, and 2) there's a subsequent cinnamon transition in unstable with updated breaks. I didn't look carefully about the time_t change as today's is the first notice I've seen regarding one of the packages I maintain and also with immediate NMU. I saw the transition on debian-devel ML I had looked fast at a list of packages involved but there were no packages that I maintain (which is why I didn't look exactly as I didn't have time and thought that there was no were afflicted packages). Well, there were several attempts to include a dd-list for maintainers to review? Your name is in the list here fwiw https://lists.debian.org/debian-devel/2024/01/msg00041.html (Unfortunately lists.debian.org has been silently dropping messages on me throughout the month, so not all of my attempts to notify maintainers via debian-devel succeeded!) I am un-tagging this bug 'pending' so it's clear this isn't a package we as NMUers should be uploading to unstable. On Wed, Jan 31, 2024 at 09:52:42PM +0100, Fabio Fantoni wrote: I applied NMU diff to git experimental (with the work for 6.0 in progress) and I spotted 2 mistake, one important is missed breaks with libcinnamon-desktop4: https://salsa.debian.org/cinnamon-team/cinnamon-desktop/-/commit/b06e59910a83b2252b866d051ffe7c5ea6f6742f This will cause serious issue and must be fixed before upload to unstable FWIK. Indeed, sorry, it looks like the conversion script wasn't able to handle the case where an existing Breaks: field is present, but it's multiline and there are no packages listed on the first line. I'll take a look at fixing the script. But if you prefer to manage the transition with Breaks: rather than a package rename, then you can forgo all of this anyway for your package. About dpkg change to wait before unstable upload is about a version still not uploaded, right? I don't saw new dpkg version in experimental Correct. Since the experimental uploads are just for clearing binary NEW and doing usrmerge analysis, we determined belatedly that no dpkg upload was needed. Thanks, Thanks for your reply. I'm a bit confused, there was an immediate upload in experimental with rename and now you tell me I can do it without but with breaks. so if this weekend I manage to upload all the packages for cinnamon 6.0 to experimental, can I also remove the rename that was done? and then, perhaps after 1-2 weeks, migrate everyone to unstable (barring unforeseen events) and it would be fine or are there specific time ranges to be respected for time_t transition? basically what is needed for this migration is a new upload of cinnamon-desktop and all its inverse dependencies (having strict depends and breaks as if it were a soname bump) and the same should be done with muffin (already included) which I saw in the list that you linked me, right? OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1062060: cinnamon-desktop: NMU diff for 64-bit time_t transition
Il 31/01/2024 22:24, Steve Langasek ha scritto: On Wed, Jan 31, 2024 at 02:01:06PM +0100, Fabio Fantoni wrote: I'm also making some improvements that I know are needed for the cinnamon packages but slowly so as not to risk coming close to burnout again (spending less time on the PC, at least in my free time), I'll add to the list also to add the missed breaks of reverse deps. Ok, if you handle it this way via additional breaks, then I think that's sufficient for this transition and you can consider this bug resolved once 1) the dpkg change is uploaded to unstable, and 2) there's a subsequent cinnamon transition in unstable with updated breaks. I didn't look carefully about the time_t change as today's is the first notice I've seen regarding one of the packages I maintain and also with immediate NMU. I saw the transition on debian-devel ML I had looked fast at a list of packages involved but there were no packages that I maintain (which is why I didn't look exactly as I didn't have time and thought that there was no were afflicted packages). Well, there were several attempts to include a dd-list for maintainers to review? Your name is in the list here fwiw https://lists.debian.org/debian-devel/2024/01/msg00041.html (Unfortunately lists.debian.org has been silently dropping messages on me throughout the month, so not all of my attempts to notify maintainers via debian-devel succeeded!) I am un-tagging this bug 'pending' so it's clear this isn't a package we as NMUers should be uploading to unstable. On Wed, Jan 31, 2024 at 09:52:42PM +0100, Fabio Fantoni wrote: I applied NMU diff to git experimental (with the work for 6.0 in progress) and I spotted 2 mistake, one important is missed breaks with libcinnamon-desktop4: https://salsa.debian.org/cinnamon-team/cinnamon-desktop/-/commit/b06e59910a83b2252b866d051ffe7c5ea6f6742f This will cause serious issue and must be fixed before upload to unstable FWIK. Indeed, sorry, it looks like the conversion script wasn't able to handle the case where an existing Breaks: field is present, but it's multiline and there are no packages listed on the first line. I'll take a look at fixing the script. But if you prefer to manage the transition with Breaks: rather than a package rename, then you can forgo all of this anyway for your package. About dpkg change to wait before unstable upload is about a version still not uploaded, right? I don't saw new dpkg version in experimental Correct. Since the experimental uploads are just for clearing binary NEW and doing usrmerge analysis, we determined belatedly that no dpkg upload was needed. Thanks, Thanks for your reply. I'm a bit confused, there was an immediate upload in experimental with rename and now you tell me I can do it without but with breaks. so if this weekend I manage to upload all the packages for cinnamon 6.0 to experimental, can I also remove the rename that was done? and then, perhaps after 1-2 weeks, migrate everyone to unstable (barring unforeseen events) and it would be fine or are there specific time ranges to be respected for time_t transition? basically what is needed for this migration is a new upload of cinnamon-desktop and all its inverse dependencies (having strict depends and breaks as if it were a soname bump) and the same should be done with muffin (already included) which I saw in the list that you linked me, right? OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1062060: cinnamon-desktop: NMU diff for 64-bit time_t transition
I applied NMU diff to git experimental (with the work for 6.0 in progress) and I spotted 2 mistake, one important is missed breaks with libcinnamon-desktop4: https://salsa.debian.org/cinnamon-team/cinnamon-desktop/-/commit/b06e59910a83b2252b866d051ffe7c5ea6f6742f This will cause serious issue and must be fixed before upload to unstable FWIK. About dpkg change to wait before unstable upload is about a version still not uploaded, right? I don't saw new dpkg version in experimental At the moment I'm not sure how I should proceed. OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1062060: cinnamon-desktop: NMU diff for 64-bit time_t transition
I applied NMU diff to git experimental (with the work for 6.0 in progress) and I spotted 2 mistake, one important is missed breaks with libcinnamon-desktop4: https://salsa.debian.org/cinnamon-team/cinnamon-desktop/-/commit/b06e59910a83b2252b866d051ffe7c5ea6f6742f This will cause serious issue and must be fixed before upload to unstable FWIK. About dpkg change to wait before unstable upload is about a version still not uploaded, right? I don't saw new dpkg version in experimental At the moment I'm not sure how I should proceed. OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1059782: mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter
You can try installing version 24.0.0~rc3-1 in experimental, which should have this issue fixed.
Bug#1059782: mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter
You can try installing version 24.0.0~rc3-1 in experimental, which should have this issue fixed.
Bug#1059782: mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter
You can try installing version 24.0.0~rc3-1 in experimental, which should have this issue fixed.
[MARMAM] Dolphin Research Internship in Sardinia Island (Italy) 2024
MareTerra Onlus (www.mareterra-erc.org) is offering internships to join research projects on the conservation of the bottlenose dolphins and marine environment from May to October 2024 in Sardinia island, a hotspot of biodiversity of the Mediterranean Sea. MareTerra is a non-profit organization created in 2012 by experienced researchers promoting the conservation of nature and sustainable development. On board of our boats, interns will join dolphin-watching activities and learn research methods to monitor the habitat use, abundance, distribution and bioacoustic of the bottlenose dolphins logging data into our database. Interns will collect georeferenced data on dolphins, fishing activities and boat traffic that impact their behaviour. Our research projects aim to implement measures for marine ecosystem conservation and promote a sustainable and responsible management of fishing and tourism activities. Working in an international and multicultural context, our interns will play an active role in environmental education to develop awareness and respect for the marine environment among tourists and locals. Required skills: - Ability to communicate fluently in English (English level > B2). - Self-confidence. - Flexibility, adaptability to an international work environment and punctuality. - Good public relations skills. - Confidence on board a motorboat and ability to swim properly. - Minimum age 20, maximum age 30. We look for people who are highly motivated, responsible and willing to work long hours in the field (Internship (mareterra-erc.org) <https://www.mareterra-erc.org/en/internship>). For any questions and to receive detailed information for applying, please send an email to: i...@mareterra-erc.org Gabriella La Manna, PhD --- Dr Fabio Ronchetti www.mareterragroup.net www.progettonaturasardegna.com www.instagram.com/progetto_natura_ecoturismo www.facebook.com/progettonaturasardegna progettonat...@mareterragroup.net.com Via P. Enrico 42 07041 Alghero (SS) Tel: +393921404069 Research associate *MareTerra ERC* www.mareterra-erc.org ronchettifa...@gmail.com Via P. Enrico 42 07041 Alghero (SS) Tel: +393921404069 ___ MARMAM mailing list MARMAM@lists.uvic.ca https://lists.uvic.ca/mailman/listinfo/marmam
Bug#1062060: cinnamon-desktop: NMU diff for 64-bit time_t transition
Il 31/01/2024 11:06, Steve Langasek ha scritto: I see that there are versioned breaks from libcinnamon-desktop to older versions of a number of its reverse-dependencies. But not all of them! libmuffin0, gir1.2-cinnamondesktop-3.0, and cinnamon itself appear to have versioned depends on libcinnamon-desktop4 without being listed in the Breaks:. Furthermore, the change to the time_t ABI is not fixed to an upstream release cycle; so if you upload the next version to unstable before the dpkg change, you will have to upload again and then ABI skew is still possible? If it's only present in the archive in unstable for a short period of time then you can make the case that it doesn't need a rename and a transition. But for the moment it looks to me like a transition will be needed. Thanks for your reply, unfortunately I don't have much time these days and I was planning to invest it to complete the preparation of cinnamon 6.0 for experimental for the upload of 9 components together (cinnamon-desktop, cinnamon-translations, cinnamon-sessions, cinnamon-screensaver, cinnamon-settings-daemon, cinnamon-control-center, muffin, nemo, cinnamon), after testing and improve it for upload migration before ubuntu 24.04 feature freeze (so take cinnamon 6.0 with autosync from debian). I'm also making some improvements that I know are needed for the cinnamon packages but slowly so as not to risk coming close to burnout again (spending less time on the PC, at least in my free time), I'll add to the list also to add the missed breaks of reverse deps. I didn't look carefully about the time_t change as today's is the first notice I've seen regarding one of the packages I maintain and also with immediate NMU. I saw the transition on debian-devel ML I had looked fast at a list of packages involved but there were no packages that I maintain (which is why I didn't look exactly as I didn't have time and thought that there was no were afflicted packages). in practice only a rebuild would be necessary but does this rebuild have to be done at certain times? Now I see the upload in experimental has been accepted and I have to keep them, right? What I need to know is about uploading to unstable, what I have to wait exactly? and then within what limit must it be done? to understand how to organize the other cinnamon 6.0 uploads that I need to do so as not to create problems for this transition. OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1062060: cinnamon-desktop: NMU diff for 64-bit time_t transition
Il 31/01/2024 11:06, Steve Langasek ha scritto: I see that there are versioned breaks from libcinnamon-desktop to older versions of a number of its reverse-dependencies. But not all of them! libmuffin0, gir1.2-cinnamondesktop-3.0, and cinnamon itself appear to have versioned depends on libcinnamon-desktop4 without being listed in the Breaks:. Furthermore, the change to the time_t ABI is not fixed to an upstream release cycle; so if you upload the next version to unstable before the dpkg change, you will have to upload again and then ABI skew is still possible? If it's only present in the archive in unstable for a short period of time then you can make the case that it doesn't need a rename and a transition. But for the moment it looks to me like a transition will be needed. Thanks for your reply, unfortunately I don't have much time these days and I was planning to invest it to complete the preparation of cinnamon 6.0 for experimental for the upload of 9 components together (cinnamon-desktop, cinnamon-translations, cinnamon-sessions, cinnamon-screensaver, cinnamon-settings-daemon, cinnamon-control-center, muffin, nemo, cinnamon), after testing and improve it for upload migration before ubuntu 24.04 feature freeze (so take cinnamon 6.0 with autosync from debian). I'm also making some improvements that I know are needed for the cinnamon packages but slowly so as not to risk coming close to burnout again (spending less time on the PC, at least in my free time), I'll add to the list also to add the missed breaks of reverse deps. I didn't look carefully about the time_t change as today's is the first notice I've seen regarding one of the packages I maintain and also with immediate NMU. I saw the transition on debian-devel ML I had looked fast at a list of packages involved but there were no packages that I maintain (which is why I didn't look exactly as I didn't have time and thought that there was no were afflicted packages). in practice only a rebuild would be necessary but does this rebuild have to be done at certain times? Now I see the upload in experimental has been accepted and I have to keep them, right? What I need to know is about uploading to unstable, what I have to wait exactly? and then within what limit must it be done? to understand how to organize the other cinnamon 6.0 uploads that I need to do so as not to create problems for this transition. OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1059782: mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter
Hi jim_p, if you are referring to: https://gitlab.archlinux.org/archlinux/packaging/packages/mesa/-/commit/15e037dba159f893360d642e4efa13e09682b080 I don't think is related to this issue. I suggest to report it here: https://gitlab.freedesktop.org/mesa/mesa/-/issues In your log this looks relevant: [ 0.318][v][vo/gpu/vaapi] using EGL dmabuf interop [ 0.319][v][vo/gpu/vaapi] Trying to open a x11 VA display... [ 0.319][d][vo/gpu/vaapi/vaapi] libva: VA-API version 1.20.0 [ 0.319][d][vo/gpu/vaapi/vaapi] libva: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so [ 0.328][d][vo/gpu/vaapi/vaapi] libva: Found init function __vaDriverInit_1_20 [ 0.340][d][vo/gpu/vaapi/vaapi] libva: va_openDriver() returns 0 [ 0.341][v][vo/gpu/vaapi/vaapi] Initialized VAAPI: version 1.20 [ 0.341][d][ffmpeg] AVHWDeviceContext: VAAPI driver: Mesa Gallium driver 23.3.4-1 for AMD CAICOS (DRM 2.50.0 / 6.5.0-5-amd64, LLVM 17.0.6). [ 0.341][d][ffmpeg] AVHWDeviceContext: Driver not found in known nonstandard list, using standard behaviour. [ 0.341][v][vo/gpu/vaapi] Going to probe surface formats (may log bogus errors)... [ 0.344][d][vo/gpu/vaapi] Failed to create mapper [ 0.344][d][vo/gpu/vaapi] Unsupported format: yuyv422 [ 0.345][d][vo/gpu/vaapi] Failed to create mapper [ 0.345][d][vo/gpu/vaapi] Unsupported format: uyvy422 [ 0.346][d][vo/gpu/vaapi] vaExportSurfaceHandle() failed (an unsupported memory type was supplied) [ 0.346][d][vo/gpu/vaapi] Unsupported format: argb [ 0.346][d][vo/gpu/vaapi] Supported formats: [ 0.346][d][vo/gpu/vaapi] nv12 [ 0.346][d][vo/gpu/vaapi] p010 [ 0.346][d][vo/gpu/vaapi] yuv420p [ 0.346][d][vo/gpu/vaapi] gray [ 0.346][d][vo/gpu/vaapi] yuv444p [ 0.346][d][vo/gpu/vaapi] bgra [ 0.346][d][vo/gpu/vaapi] rgba [ 0.346][d][vo/gpu/vaapi] bgr0 [ 0.346][d][vo/gpu/vaapi] rgb0 [ 0.346][v][vo/gpu/vaapi] Done probing surface formats.
Bug#1059782: mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter
Hi jim_p, if you are referring to: https://gitlab.archlinux.org/archlinux/packaging/packages/mesa/-/commit/15e037dba159f893360d642e4efa13e09682b080 I don't think is related to this issue. I suggest to report it here: https://gitlab.freedesktop.org/mesa/mesa/-/issues In your log this looks relevant: [ 0.318][v][vo/gpu/vaapi] using EGL dmabuf interop [ 0.319][v][vo/gpu/vaapi] Trying to open a x11 VA display... [ 0.319][d][vo/gpu/vaapi/vaapi] libva: VA-API version 1.20.0 [ 0.319][d][vo/gpu/vaapi/vaapi] libva: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so [ 0.328][d][vo/gpu/vaapi/vaapi] libva: Found init function __vaDriverInit_1_20 [ 0.340][d][vo/gpu/vaapi/vaapi] libva: va_openDriver() returns 0 [ 0.341][v][vo/gpu/vaapi/vaapi] Initialized VAAPI: version 1.20 [ 0.341][d][ffmpeg] AVHWDeviceContext: VAAPI driver: Mesa Gallium driver 23.3.4-1 for AMD CAICOS (DRM 2.50.0 / 6.5.0-5-amd64, LLVM 17.0.6). [ 0.341][d][ffmpeg] AVHWDeviceContext: Driver not found in known nonstandard list, using standard behaviour. [ 0.341][v][vo/gpu/vaapi] Going to probe surface formats (may log bogus errors)... [ 0.344][d][vo/gpu/vaapi] Failed to create mapper [ 0.344][d][vo/gpu/vaapi] Unsupported format: yuyv422 [ 0.345][d][vo/gpu/vaapi] Failed to create mapper [ 0.345][d][vo/gpu/vaapi] Unsupported format: uyvy422 [ 0.346][d][vo/gpu/vaapi] vaExportSurfaceHandle() failed (an unsupported memory type was supplied) [ 0.346][d][vo/gpu/vaapi] Unsupported format: argb [ 0.346][d][vo/gpu/vaapi] Supported formats: [ 0.346][d][vo/gpu/vaapi] nv12 [ 0.346][d][vo/gpu/vaapi] p010 [ 0.346][d][vo/gpu/vaapi] yuv420p [ 0.346][d][vo/gpu/vaapi] gray [ 0.346][d][vo/gpu/vaapi] yuv444p [ 0.346][d][vo/gpu/vaapi] bgra [ 0.346][d][vo/gpu/vaapi] rgba [ 0.346][d][vo/gpu/vaapi] bgr0 [ 0.346][d][vo/gpu/vaapi] rgb0 [ 0.346][v][vo/gpu/vaapi] Done probing surface formats.
Bug#1059782: mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter
Hi jim_p, if you are referring to: https://gitlab.archlinux.org/archlinux/packaging/packages/mesa/-/commit/15e037dba159f893360d642e4efa13e09682b080 I don't think is related to this issue. I suggest to report it here: https://gitlab.freedesktop.org/mesa/mesa/-/issues In your log this looks relevant: [ 0.318][v][vo/gpu/vaapi] using EGL dmabuf interop [ 0.319][v][vo/gpu/vaapi] Trying to open a x11 VA display... [ 0.319][d][vo/gpu/vaapi/vaapi] libva: VA-API version 1.20.0 [ 0.319][d][vo/gpu/vaapi/vaapi] libva: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so [ 0.328][d][vo/gpu/vaapi/vaapi] libva: Found init function __vaDriverInit_1_20 [ 0.340][d][vo/gpu/vaapi/vaapi] libva: va_openDriver() returns 0 [ 0.341][v][vo/gpu/vaapi/vaapi] Initialized VAAPI: version 1.20 [ 0.341][d][ffmpeg] AVHWDeviceContext: VAAPI driver: Mesa Gallium driver 23.3.4-1 for AMD CAICOS (DRM 2.50.0 / 6.5.0-5-amd64, LLVM 17.0.6). [ 0.341][d][ffmpeg] AVHWDeviceContext: Driver not found in known nonstandard list, using standard behaviour. [ 0.341][v][vo/gpu/vaapi] Going to probe surface formats (may log bogus errors)... [ 0.344][d][vo/gpu/vaapi] Failed to create mapper [ 0.344][d][vo/gpu/vaapi] Unsupported format: yuyv422 [ 0.345][d][vo/gpu/vaapi] Failed to create mapper [ 0.345][d][vo/gpu/vaapi] Unsupported format: uyvy422 [ 0.346][d][vo/gpu/vaapi] vaExportSurfaceHandle() failed (an unsupported memory type was supplied) [ 0.346][d][vo/gpu/vaapi] Unsupported format: argb [ 0.346][d][vo/gpu/vaapi] Supported formats: [ 0.346][d][vo/gpu/vaapi] nv12 [ 0.346][d][vo/gpu/vaapi] p010 [ 0.346][d][vo/gpu/vaapi] yuv420p [ 0.346][d][vo/gpu/vaapi] gray [ 0.346][d][vo/gpu/vaapi] yuv444p [ 0.346][d][vo/gpu/vaapi] bgra [ 0.346][d][vo/gpu/vaapi] rgba [ 0.346][d][vo/gpu/vaapi] bgr0 [ 0.346][d][vo/gpu/vaapi] rgb0 [ 0.346][v][vo/gpu/vaapi] Done probing surface formats.
Bug#1062060: cinnamon-desktop: NMU diff for 64-bit time_t transition
Il 31/01/2024 09:54, Steve Langasek ha scritto: Source: cinnamon-desktop Version: 5.8.0-2 Severity: serious Tags: patch pending Justification: library ABI skew on upgrade User: debian-...@lists.debian.org Usertags: time-t Dear maintainer, As part of the 64-bit time_t transition required to support 32-bit architectures in 2038 and beyond (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified cinnamon-desktop as a source package shipping runtime libraries whose ABI either is affected by the change in size of time_t, or could not be analyzed via abi-compliance-checker (and therefore to be on the safe side we assume is affected). To ensure that inconsistent combinations of libraries with their reverse-dependencies are never installed together, it is necessary to have a library transition, which is most easily done by renaming the runtime library package. Since turning on 64-bit time_t is being handled centrally through a change to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is important that libraries affected by this ABI change all be uploaded close together in time. Therefore I have prepared a 0-day NMU for cinnamon-desktop which will initially be uploaded to experimental if possible, then to unstable after packages have cleared binary NEW. Please find the patch for this NMU attached. If you have any concerns about this patch, please reach out ASAP. Although this package will be uploaded to experimental immediately, there will be a period of several days before we begin uploads to unstable; so if information becomes available that your package should not be included in the transition, there is time for us to amend the planned uploads. Hi, this rename is really needed? Cinnamon upstream don't don't soname bump even when needed and we use strict depends and upload of multiple component together as a workaround every major version, I've almost finished the next one which I would have done within a few days. I don't have much time but I was also trying to reduce the differences and conflicts with the upstream packaging which causes reports of hundreds of users trying to upgrade the cinnamon packages but the upgrade fails due to conflicts. OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1062060: cinnamon-desktop: NMU diff for 64-bit time_t transition
Il 31/01/2024 09:54, Steve Langasek ha scritto: Source: cinnamon-desktop Version: 5.8.0-2 Severity: serious Tags: patch pending Justification: library ABI skew on upgrade User: debian-...@lists.debian.org Usertags: time-t Dear maintainer, As part of the 64-bit time_t transition required to support 32-bit architectures in 2038 and beyond (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified cinnamon-desktop as a source package shipping runtime libraries whose ABI either is affected by the change in size of time_t, or could not be analyzed via abi-compliance-checker (and therefore to be on the safe side we assume is affected). To ensure that inconsistent combinations of libraries with their reverse-dependencies are never installed together, it is necessary to have a library transition, which is most easily done by renaming the runtime library package. Since turning on 64-bit time_t is being handled centrally through a change to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is important that libraries affected by this ABI change all be uploaded close together in time. Therefore I have prepared a 0-day NMU for cinnamon-desktop which will initially be uploaded to experimental if possible, then to unstable after packages have cleared binary NEW. Please find the patch for this NMU attached. If you have any concerns about this patch, please reach out ASAP. Although this package will be uploaded to experimental immediately, there will be a period of several days before we begin uploads to unstable; so if information becomes available that your package should not be included in the transition, there is time for us to amend the planned uploads. Hi, this rename is really needed? Cinnamon upstream don't don't soname bump even when needed and we use strict depends and upload of multiple component together as a workaround every major version, I've almost finished the next one which I would have done within a few days. I don't have much time but I was also trying to reduce the differences and conflicts with the upstream packaging which causes reports of hundreds of users trying to upgrade the cinnamon packages but the upgrade fails due to conflicts. OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#787764: libvpx2: vp9 encoding is significantly slower in 1.4.0 than in 1.3.0
Hi Matt, can you check if the performance regression you noticed with 1.4.0 was resolved with a newer libvpx release? You may also eventually check the upstream issues report at https://bugs.chromium.org/p/webm/issues/list Thanks.
Bug#1015532: libvpx: ftbfs with LTO (link time optimization) enabled
forwarded 1015532 https://bugs.chromium.org/p/webm/issues/detail?id=1736 thanks
Re: [PATCH v2] imx: imx8mp: Add support for Polyhex Debix Model A SBC
Hi Milan,
On Tue, Jan 30, 2024 at 9:22 AM Milan Zamazal wrote:
> Well, after trying both the SD cards again with fresh reinstallations, it
> works
> with a 32 GB card and I get the error above with a 64 GB card. Is it possible
> that there is something wrong with SDXC cards?
Does the change below help?
--- a/arch/arm/dts/imx8mp-debix-model-a-u-boot.dtsi
+++ b/arch/arm/dts/imx8mp-debix-model-a-u-boot.dtsi
@@ -128,6 +128,9 @@
bootph-pre-ram;
sd-uhs-sdr104;
sd-uhs-ddr50;
+ assigned-clocks = < IMX8MP_CLK_USDHC2>;
+ assigned-clock-rates = <4>;
+ assigned-clock-parents = < IMX8MP_SYS_PLL1_400M>;
};
{
Re: [PATCH 3/3] phycore-imx8mp: add support for booting and flashing emmc via UUU
On Mon, Jan 29, 2024 at 4:56 AM Benjamin Hahn wrote: > > add support for Serial Downloader Boot via UUU as well as flashing emmc > via UUU on USB0 Port of phyBOARD Pollux. > > Signed-off-by: Benjamin Hahn Reviewed-by: Fabio Estevam
Re: [PATCH 2/3] phycore-imx8mp: add USB mass storage support
On Mon, Jan 29, 2024 at 4:56 AM Benjamin Hahn wrote:
> +_0 {
> + status = "okay";
> + dr_mode = "peripheral";
> +};
Same comment as patch 1/3. Please sync the dts with Linux.
Re: [PATCH 1/3] phycore-imx8mp: add USB host support
Hi Benjamin,
On Mon, Jan 29, 2024 at 4:56 AM Benjamin Hahn wrote:
> diff --git a/arch/arm/dts/imx8mp-phyboard-pollux-rdk-u-boot.dtsi
> b/arch/arm/dts/imx8mp-phyboard-pollux-rdk-u-boot.dtsi
> index 1c7b250549..5d6974f8fa 100644
> --- a/arch/arm/dts/imx8mp-phyboard-pollux-rdk-u-boot.dtsi
> +++ b/arch/arm/dts/imx8mp-phyboard-pollux-rdk-u-boot.dtsi
> @@ -70,6 +70,19 @@
> bootph-pre-ram;
> };
>
> +_1 {
> + status = "okay";
> + dr_mode = "host";
> +};
> +
> +_dwc3_1 {
> + status = "okay";
> +};
> +
> +_phy1 {
> + status = "okay";
> +};
Why are these USB nodes being added to -u-boot.dtsi?
These nodes are already present in the kernel dts:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/boot/dts/freescale/imx8mp-phyboard-pollux-rdk.dts?h=v6.8-rc2#n169
Please add a patch to the series that syncs
imx8mp-phyboard-pollux-rdk.dts with the upstream version, then you
don't need to touch u-boot.dtsi.
Re: A reminder: you cannot just "revert" package version bumps
On Tue, Jan 30, 2024 at 1:00 AM Sérgio Basto wrote: > (snip) > yes rawhide user should use dnf distro-sync not dnf upgrade It is better, yes, but it is not *required*. > https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/#_rawhide_is_allowed_to_lag_temporarily This is a completely different problem. Package updates that don't build in Rawhide but build on stable branches are permissible as long as the package update will be submitted to Rawhide *eventually*. > you may do a new build with lower EVR No, you may not. That is exactly what Adam's email is about. Fabio -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [PATCH v1 1/2] imx: imxrt1050-evk: Add support for SPI flash booting
On Sun, Jan 28, 2024 at 6:43 PM Jesse Taube wrote: > +++ b/configs/imxrt1050-evk_fspi_defconfig > @@ -0,0 +1,100 @@ > +CONFIG_ARM=y > +CONFIG_SYS_DCACHE_OFF=y Out of curiosity: what are the problems if the D-Cache is turned on?
Re: Improve dircolors accessibility and readability
On Sunday, 28 January 2024 20:50:59 CET Pádraig Brady wrote: > > > > I'm wondering if this can become a new default. > I agree that this is a bit hard to read. >https://www.pixelbeat.org/scripts/l > Given that no particular color combination is significantly better here, > I would err on the side of keeping colors as is for some familiarity at > least. I think your script solve the problem in a brilliant way; it should be part of the default core utils :) -- Best, Fabio signature.asc Description: This is a digitally signed message part.
[ark] [Bug 480476] New: Ark archive extraction issue with special characters in filename
https://bugs.kde.org/show_bug.cgi?id=480476 Bug ID: 480476 Summary: Ark archive extraction issue with special characters in filename Classification: Applications Product: ark Version: 23.08.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: fa...@fabiosirna.com CC: rthoms...@gmail.com Target Milestone: --- SUMMARY I noticed that some rar archives I downloaded from the web are not being opened; checking the file name better, I noticed that some of them contain special characters (e.g.g U+2023, en dash) and Ark gives the following error, where is the special character. I have tried to replicate this by creating archives by assigning special characters to them, but I cannot replicate the bug. OBSERVED RESULT Cannot open /home/user/Downloads/Test Test.ra No such file or directory EXPECTED RESULT To open an extract the files in the archive. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240126 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.7.1-2-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C35 System Version: 2.0 -- You are receiving this mail because: You are watching all bug changes.
Re: [PATCH v1 2/2] imx: imxrt1050-evk: Add documentation for SPI boot
On Sun, Jan 28, 2024 at 6:43 PM Jesse Taube wrote: > > Adds documentation for SPI boot. s/Adds/Add > +How to use U-Boot with SPI flash on NXP i.MXRT1050 EVK > +-- > + > +- Build U-Boot for i.MXRT1050 EVK: > + > +.. code-block:: bash > + > + $ make mrproper > + $ make imxrt1050-evk_spi_defconfig In the previous patch, the new defconfig is called imxrt1050-evk_fspi_defconfig. > + $ make > + > +This will generate SPL, uboot.img, fspi_header.bin, and the final image > (flash.bin). > + > +To boot from SPI flash on other boards you may need to change the flash > header config, > +that is specific to your flash chip, in Kconfig. > +The flash config is 4K in size and is documented on page 217 of the > imxrt1050RM. It would be helpful to mention the SPI NOR flash part number that is used on the i.MXRT1050 EVK.
Re: [PATCH v1 1/2] imx: imxrt1050-evk: Add support for SPI flash booting
Hi Jesse, On Sun, Jan 28, 2024 at 6:43 PM Jesse Taube wrote: > > This add some macros to change addresses to use flexspi. This sentence is not very clear. > This commit adds support for booting the imxrt1050-evk from spi. Please don't use 'This commit adds support' format. Use imperative mood instead: "Add support" > It adds imximage config and the ability for SPL to boot from NOR. > > Signed-off-by: Jesse Taube > --- > arch/arm/dts/imxrt1050-evk-u-boot.dtsi| 31 ++ > arch/arm/mach-imx/imxrt/Kconfig | 1 + > .../freescale/imxrt1050-evk/imximage-nor.cfg | 41 +++ > board/freescale/imxrt1050-evk/imximage.cfg| 10 +- > board/freescale/imxrt1050-evk/imxrt1050-evk.c | 7 +- > configs/imxrt1050-evk_defconfig | 8 +- > configs/imxrt1050-evk_fspi_defconfig | 100 ++ Please add configs/imxrt1050-evk_fspi_defconfig into board/freescale/imxrt1050-evk/MAINTAINERS.
[Git][archlinux/packaging/packages/dbeaver] Pushed new tag 23.3.3-1
Fabio Castelli pushed new tag 23.3.3-1 at Arch Linux / Packaging / Packages / dbeaver -- View it on GitLab: https://gitlab.archlinux.org/archlinux/packaging/packages/dbeaver/-/tree/23.3.3-1 You're receiving this email because of your account on gitlab.archlinux.org.
[Git][archlinux/packaging/packages/dbeaver][main] upgpkg: 23.3.3-1
Fabio Castelli pushed to branch main at Arch Linux / Packaging / Packages /
dbeaver
Commits:
32eb6a48 by Fabio Castelli (Muflone) at 2024-01-28T14:04:48+01:00
upgpkg: 23.3.3-1
- - - - -
2 changed files:
- .SRCINFO
- PKGBUILD
Changes:
=
.SRCINFO
=
@@ -1,6 +1,6 @@
pkgbase = dbeaver
pkgdesc = Free universal SQL Client for developers and database
administrators (community edition)
- pkgver = 23.3.2
+ pkgver = 23.3.3
pkgrel = 1
url = https://dbeaver.io/
install = dbeaver.install
@@ -16,14 +16,14 @@ pkgbase = dbeaver
optdepends = dbeaver-plugin-svg-format: save diagrams in SVG format
conflicts = dbeaver-plugin-sshj-lib
replaces = dbeaver-plugin-sshj-lib
- source =
dbeaver-23.3.2.tar.gz::https://github.com/dbeaver/dbeaver/archive/23.3.2.tar.gz
+ source =
dbeaver-23.3.3.tar.gz::https://github.com/dbeaver/dbeaver/archive/23.3.3.tar.gz
source = io.dbeaver.DBeaver.desktop
source = dbeaver.sh
source = dbeaver.profile.gz
source = dbeaver.hook
source = dbeaver.install
source = tycho_3_0_5.patch
- sha256sums =
ec6e57282d3c97843b605c15ac4e4fe4bc2571726aeb856c3d77f0fccf7ab2f9
+ sha256sums =
88bea41cf0f1f555150c32645903ef7e3f64de52476d9a62eb3bbcd82841169d
sha256sums =
9480a7d08f680e10c399db070c5a04cbabf282442602a2ef83d1159fe7c3e88b
sha256sums =
406a2980806c394670e88b1ae70134900be376c2ea4a4216610591cc8b557526
sha256sums =
1863e74bdcf22b7328e6e8487cbebff7d5360e34bde85c1dd226b168b4737034
=
PKGBUILD
=
@@ -2,7 +2,7 @@
# Contributor: Arne Hoch
pkgname=dbeaver
-pkgver=23.3.2
+pkgver=23.3.3
pkgrel=1
pkgdesc="Free universal SQL Client for developers and database administrators
(community edition)"
arch=('x86_64')
@@ -21,7 +21,7 @@
source=("${pkgname}-${pkgver}.tar.gz"::"https://github.com/dbeaver/dbeaver/archi
"${pkgname}.hook"
"${pkgname}.install"
"tycho_3_0_5.patch")
-sha256sums=('ec6e57282d3c97843b605c15ac4e4fe4bc2571726aeb856c3d77f0fccf7ab2f9'
+sha256sums=('88bea41cf0f1f555150c32645903ef7e3f64de52476d9a62eb3bbcd82841169d'
'9480a7d08f680e10c399db070c5a04cbabf282442602a2ef83d1159fe7c3e88b'
'406a2980806c394670e88b1ae70134900be376c2ea4a4216610591cc8b557526'
'1863e74bdcf22b7328e6e8487cbebff7d5360e34bde85c1dd226b168b4737034'
View it on GitLab:
https://gitlab.archlinux.org/archlinux/packaging/packages/dbeaver/-/commit/32eb6a48e371e0f78c37b4768361a58a236ece2f
--
View it on GitLab:
https://gitlab.archlinux.org/archlinux/packaging/packages/dbeaver/-/commit/32eb6a48e371e0f78c37b4768361a58a236ece2f
You're receiving this email because of your account on gitlab.archlinux.org.
[OE-core] [PATCH] mesa: Upgrade 23.3.3 -> 23.3.4
From: Fabio Estevam
Mesa 23.3.4 release notes:
https://lists.freedesktop.org/archives/mesa-announce/2024-January/000745.html
Signed-off-by: Fabio Estevam
---
.../mesa/{mesa-gl_23.3.3.bb => mesa-gl_23.3.4.bb} | 0
meta/recipes-graphics/mesa/mesa.inc | 2 +-
meta/recipes-graphics/mesa/{mesa_23.3.3.bb => mesa_23.3.4.bb} | 0
3 files changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/mesa/{mesa-gl_23.3.3.bb => mesa-gl_23.3.4.bb}
(100%)
rename meta/recipes-graphics/mesa/{mesa_23.3.3.bb => mesa_23.3.4.bb} (100%)
diff --git a/meta/recipes-graphics/mesa/mesa-gl_23.3.3.bb
b/meta/recipes-graphics/mesa/mesa-gl_23.3.4.bb
similarity index 100%
rename from meta/recipes-graphics/mesa/mesa-gl_23.3.3.bb
rename to meta/recipes-graphics/mesa/mesa-gl_23.3.4.bb
diff --git a/meta/recipes-graphics/mesa/mesa.inc
b/meta/recipes-graphics/mesa/mesa.inc
index e063eb3507..16843b6036 100644
--- a/meta/recipes-graphics/mesa/mesa.inc
+++ b/meta/recipes-graphics/mesa/mesa.inc
@@ -20,7 +20,7 @@ SRC_URI =
"https://mesa.freedesktop.org/archive/mesa-${PV}.tar.xz \
file://0001-gallium-Fix-build-with-llvm-17.patch \
"
-SRC_URI[sha256sum] =
"518307c0057fa3cee8b58df78be431d4df5aafa7edc60d09278b2d7a0a80f3b4"
+SRC_URI[sha256sum] =
"df12d765be4650fe532860b18aa18e6da1d0b07d1a21dfdfe04660e6b7bac39a"
UPSTREAM_CHECK_GITTAGREGEX = "mesa-(?P\d+(\.\d+)+)"
diff --git a/meta/recipes-graphics/mesa/mesa_23.3.3.bb
b/meta/recipes-graphics/mesa/mesa_23.3.4.bb
similarity index 100%
rename from meta/recipes-graphics/mesa/mesa_23.3.3.bb
rename to meta/recipes-graphics/mesa/mesa_23.3.4.bb
--
2.37.3
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#194437):
https://lists.openembedded.org/g/openembedded-core/message/194437
Mute This Topic: https://lists.openembedded.org/mt/104005681/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Bug#1061547: freeipmi: ipmi-sensors - internal IPMI error with kcs driver
unfortunately at the moment there is a regression related to those 2 functions which has caused the build to fail in almost all architectures https://buildd.debian.org/status/package.php?p=freeipmi=sid I also reported upstream: https://github.com/chu11/freeipmi-mirror/issues/70 I tried to do some quick revert tests but unfortunately at the moment I didn't succeed and I don't have enough time to prepare a sufficiently updated Debian on my raspberry (for reproduce the issue) to continue with the tests any help is welcome OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1061547: freeipmi: ipmi-sensors - internal IPMI error with kcs driver
Il 26/01/2024 09:48, Yannick Martin ha scritto: Hello, Since freeipmi-1.6.9, ipmi queries via kcs driver may not work. I opened an issue on upstream project: http://savannah.gnu.org/support/?111010 Is it possible to rebuild bookworm freeipmi packages with this ? Regards Thanks for report, for now I uploaded to unstable. About do a stable proposed update is not easy/fast: https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable If patch is small and risk of regression is small is possible. The fix is only this upstream commit https://github.com/chu11/freeipmi-mirror/commit/379c8569711d808c3366a99d1dfac5e414858800 and not other patch need to be applied to bookworm version? OpenPGP_signature.asc Description: OpenPGP digital signature
Re: [PATCH v1] tools: mkimage: Add support for i.MXRT FlexSPI Header
On Tue, Jan 23, 2024 at 11:15 PM Jesse Taube wrote: > > Modify imx8m Flex SPI Configuration Block to work with imxrt. > Add more Flex SPI configuration options to Kconfig. > > Signed-off-by: Jesse Taube Applied, thanks.
Re: [PATCH] ARM: imx: Enable kaslrseed command on Data Modul i.MX8M Mini/Plus eDM SBC
On Mon, Jan 22, 2024 at 11:56 AM Marek Vasut wrote: > > Linux 6.6.y with KASLR enabled would print the following message on boot: > " > KASLR disabled due to lack of seed > " > Enable the 'kaslrseed' command so a random number seed can be pulled > from CAAM and inserted into the /chosen node 'kaslr-seed' property of > Linux kernel DT before boot, thus letting KASLR work properly. > > Signed-off-by: Marek Vasut Applied, thanks.
Re: [PATCH] toradex: tdx-cfg-block: Add new apalis and colibri pid
On Thu, Jan 25, 2024 at 8:02 AM Francesco Dolcini wrote: > there is some trailing space here at the end of the line. > > Fabio, can you fix this up before applying? Removed the whitespace and applied it, thanks.
Re: pngquant 3.0.3 Debian package
Thanks, I see you uploaded latest C version 2.18.0 anyway. Fabio Il Ven 26 Gen 2024, 20:23 Andreas Tille ha scritto: > Hi Fabio, > > Am Fri, Jan 26, 2024 at 04:57:03PM +0100 schrieb Fabio Pedretti: > > Hi, can you please consider updating pngquant to latest 3.0.3 in Debian? > > I'm very sorry, but I have no capacity for this. Its a completely new > source / build system which I'm not comfortable with. I gave it a try > but it needs new Rust dependencies. Since I have no idea about Rust I > have no sensible chance / resources to packages these. > > I recommend you do > >sudo apt install reportbug >reportbug pngquant > -> Please update to version 3.0.3 > -> Severity wishlist > > I've added the Maintainer list in CC in case someone might like to take > over. > > Kind regards > Andreas. > > -- > http://fam-tille.de >
[kmail2] [Bug 480385] New: Archive shortcut assignment is not retained
https://bugs.kde.org/show_bug.cgi?id=480385 Bug ID: 480385 Summary: Archive shortcut assignment is not retained Classification: Applications Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: fa...@fabiosirna.com Target Milestone: --- SUMMARY I'm trying to assign the shortcut key "\" to the action "Archive" but is not retained. STEPS TO REPRODUCE 1. Settings > Configure Keyboard Shortcuts... 2. Search > search for Archive 3. On the search result list click on "Archive" 4. Select Custom, click on "None" 5. As soon as it change to Input click on a shorcut; in my case key "\" 6. Click Ok, the dialog close 7. Select one email, hit "\" and the mail will be archived 8. Select a second email, and is not archived 9. go back to step 1 and 2 and the shortcut is not assigned. Operating System: openSUSE Tumbleweed 20240125 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.7.1-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C35 System Version: 2.0 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 480385] New: Archive shortcut assignment is not retained
https://bugs.kde.org/show_bug.cgi?id=480385 Bug ID: 480385 Summary: Archive shortcut assignment is not retained Classification: Applications Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: fa...@fabiosirna.com Target Milestone: --- SUMMARY I'm trying to assign the shortcut key "\" to the action "Archive" but is not retained. STEPS TO REPRODUCE 1. Settings > Configure Keyboard Shortcuts... 2. Search > search for Archive 3. On the search result list click on "Archive" 4. Select Custom, click on "None" 5. As soon as it change to Input click on a shorcut; in my case key "\" 6. Click Ok, the dialog close 7. Select one email, hit "\" and the mail will be archived 8. Select a second email, and is not archived 9. go back to step 1 and 2 and the shortcut is not assigned. Operating System: openSUSE Tumbleweed 20240125 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.7.1-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C35 System Version: 2.0 -- You are receiving this mail because: You are watching all bug changes.
Re: [PATCH v1] tools: mkimage: Add support for i.MXRT FlexSPI Header
Hi Adam, On Thu, Jan 25, 2024 at 7:37 PM Adam Ford wrote: > I had to go back in time, because it appears the current version of > 'master' doesn't fully boot the FSPI, but when I applied this patch > against a working version, it still worked when I was done. I'll try > to git bisect the issue when I have time, but for now: > > Tested-by: Adam Ford #imx8mn-beacon Thanks for testing, appreciate it. I will queue this one. Hopefully, we can figure out the cause of the regression.
Re: SSH key management for Guix cloud machines
On 2024-01-20, 20:14 -0800, Felix Lechner wrote: >> How does the publishing happen exactly > > You can query SSH server keys remotely [1] but I would deploy keys I > know already. Hi Felix, Thanks for getting back to me and sorry it took me so long to reply. Querying the SSH server would be a bit of a catch-22 situation though, unless the machine you're querying from is part of the same VPN as the server. While I do like the idea of using a DNS record, by itself this doesn't seem to solve the trust-on-first-use issue. I'd be fine with this solution, if the DNS were part of the same network as the newly installed server, but that's not my case. The other solution that comes to mind would involve: - some kind of cloud-init service that waits until the SSH key pair is generated and then communicates the public key to the cloud provider; - a cloud-init compliant cloud provider, that accepts the public key and then make it available to the user via a web dashboard. I think this is what some providers do with other system images? OTOH, UX-wise, this is much worse than the DNS record as it requires manual intervention. Let's see, maybe someone else might chime in with some other idea at some point. Thanks for now, cheers, Fabio. -- Fabio Natali https://fabionatali.com
[MARMAM] Dolphin Research Internship in Sardinia (Italy) 2024
MareTerra Onlus (www.mareterra-erc.org) is offering internships to join research projects on the conservation of the bottlenose dolphins and marine environment from May to October 2024 in Sardinia island, a hotspot of biodiversity of the Mediterranean Sea. MareTerra is a non-profit organization created in 2012 by experienced researchers promoting the conservation of nature and sustainable development. On board our boats, interns will learn research methods to monitor the habitat use, abundance and distribution of the bottlenose dolphins. Interns will collect georeferenced data on dolphins, fishing activities and boat traffic that impact their behaviour. Our research projects aim to implement measures for marine ecosystem conservation and promote a sustainable and responsible management of fishing and tourism activities. Working in an international and multicultural context, our interns will play an active role in environmental education to develop awareness and respect for the marine environment among tourists and locals on board of our boats. Required skills: - Ability to communicate fluently in English (English level > B2). - Self-confidence. - Flexibility, adaptability to an international work environment and punctuality. - Good public relations skills. - Confidence on board a motorboat and ability to swim properly. - Minimum age 20, maximum age 30. We look for people who are highly motivated, responsible and willing to work long hours in the field. For any questions and to receive detailed information for applying, please send email to: i...@mareterra-erc.org Gabriella La Manna, Ph.D. --- Dr Fabio Ronchetti www.mareterragroup.net www.progettonaturasardegna.com www.instagram.com/progetto_natura_ecoturismo www.facebook.com/progettonaturasardegna progettonat...@mareterragroup.net.com Via P. Enrico 42 07041 Alghero (SS) Tel: +393921404069 Research associate *MareTerra ERC* www.mareterra-erc.org ronchettifa...@gmail.com Via P. Enrico 42 07041 Alghero (SS) Tel: +393921404069 ___ MARMAM mailing list MARMAM@lists.uvic.ca https://lists.uvic.ca/mailman/listinfo/marmam
[jenkinsci/metrics-plugin] 2c5647: Updates metrics documentation (#218)
Branch: refs/heads/gh-readonly-queue/master/pr-218-1761e80f682fd0bfa40422ab9482094e9edcfd4c Home: https://github.com/jenkinsci/metrics-plugin Commit: 2c564715feaa736cbd9a206744006415f87525e5 https://github.com/jenkinsci/metrics-plugin/commit/2c564715feaa736cbd9a206744006415f87525e5 Author: Fabio Pagnotta Date: 2024-01-26 (Fri, 26 Jan 2024) Changed paths: M README.adoc Log Message: --- Updates metrics documentation (#218) -- You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-commits/jenkinsci/metrics-plugin/push/refs/heads/gh-readonly-queue/master/pr-218-1761e80f682fd0bfa40422ab9482094e9edcfd4c/00-2c5647%40github.com.
Re: [PATCH] toradex: tdx-cfg-block: Add new apalis and colibri pid
On Thu, Jan 25, 2024 at 8:02 AM Francesco Dolcini wrote: > there is some trailing space here at the end of the line. > > Fabio, can you fix this up before applying? Sure, but next time just run checkpatch :-)
Re: [PATCH v1] tools: mkimage: Add support for i.MXRT FlexSPI Header
Hi Adam, On Tue, Jan 23, 2024 at 11:15 PM Jesse Taube wrote: > > Modify imx8m Flex SPI Configuration Block to work with imxrt. > Add more Flex SPI configuration options to Kconfig. > > Signed-off-by: Jesse Taube Could you please test it on imx8mn_beacon_fspi_defconfig ?
Re: [PATCH v3] board: phytec: phycore-imx93: Add phyBOARD-Segin-i.MX93 support
On Thu, Jan 25, 2024 at 1:45 PM Mathieu Othacehe wrote: > +ipaddr=192.168.3.11 > +serverip=192.168.3.10 > +netmask=255.255.255.0 Please remove these hardcoded IP addresses.
[OE-core] [PATCH] piglit: Update to latest revision
From: Fabio Estevam Update to the latest piglit revision. Signed-off-by: Fabio Estevam --- meta/recipes-graphics/piglit/piglit_git.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-graphics/piglit/piglit_git.bb b/meta/recipes-graphics/piglit/piglit_git.bb index 69294c6c9468..1bc3b784c77e 100644 --- a/meta/recipes-graphics/piglit/piglit_git.bb +++ b/meta/recipes-graphics/piglit/piglit_git.bb @@ -13,7 +13,7 @@ SRC_URI = "git://gitlab.freedesktop.org/mesa/piglit.git;protocol=https;branch=ma " UPSTREAM_CHECK_COMMITS = "1" -SRCREV = "71c21b1157c4f9a96453bdfcb9f4dda091360afd" +SRCREV = "f3f1b3f960611a88cb1a037114ba4724f1bf330e" # (when PV goes above 1.0 remove the trailing r) PV = "1.0+gitr" -- 2.34.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#194329): https://lists.openembedded.org/g/openembedded-core/message/194329 Mute This Topic: https://lists.openembedded.org/mt/103955076/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[QGIS-it-user] R: Etichette in DWG da qgis
In QGIS, dovrebbe essere sufficiente abilitare le “etichette” assegnando il valore del campo da visualizzare, nel tuo caso, la posizione Z. Prova a vederei 3.2. Lesson: Etichette — QGIS Documentation documentazione<https://docs.qgis.org/3.28/it/docs/training_manual/vector_classification/label_tool.html> Fabio Da: QGIS-it-user Per conto di Giada Biraghi via QGIS-it-user Inviato: mercoledì, 24 gennaio 2024 16:51 A: qgis-it-user@lists.osgeo.org Oggetto: [QGIS-it-user] Etichette in DWG da qgis Buona sera, avrei bisogno di una consulenza in merito ad una procedura da QGIS a PROGECAD. In QGIS ho creato dei punti con associato nella tabella degli attributi una quota altimetrica (con etichetta visibile direttamente in QGIS con ciascun punto la relativa quota). Ho poi esportato in PROGECAD i punti che si posizionano correttamente nello spazio e a cui è correttamente associata la quota Z visibile nella geometria del punto (Z posizione). Avrei la necessità di visualizzare un’etichetta con la quota per ciascuno dei punti (più di 1000). È possibile in qualche maniera? Grazie Giada ___ QGIS-it-user mailing list QGIS-it-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/qgis-it-user
[OE-core] [PATCH v2] pulseaudio: Update to 17.0
From: Fabio Estevam
Update to pulseaudio 17.0 version.
Since pulseaudio commit e96d278bfc51 ("daemon/meson.build: Install
dbus policy in /usr, not /etc"), pulseaudio-system.conf needs to be passed
in FILES, otherwise the following QA error is seen:
ERROR: pulseaudio-17.0-r0 do_package: QA Issue: pulseaudio: Files/directories
were installed but not shipped in any package:
/usr/share/dbus-1
/usr/share/dbus-1/system.d
/usr/share/dbus-1/system.d/pulseaudio-system.conf
Signed-off-by: Fabio Estevam
---
Changes since v1:
- Onley add the specific pulseaudio-system.conf" instead of
whole ${datadir} (Ross).
meta/recipes-multimedia/pulseaudio/pulseaudio.inc | 1 +
.../pulseaudio/{pulseaudio_16.1.bb => pulseaudio_17.0.bb} | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
rename meta/recipes-multimedia/pulseaudio/{pulseaudio_16.1.bb =>
pulseaudio_17.0.bb} (84%)
diff --git a/meta/recipes-multimedia/pulseaudio/pulseaudio.inc
b/meta/recipes-multimedia/pulseaudio/pulseaudio.inc
index 2245a73392..ae16056d24 100644
--- a/meta/recipes-multimedia/pulseaudio/pulseaudio.inc
+++ b/meta/recipes-multimedia/pulseaudio/pulseaudio.inc
@@ -187,6 +187,7 @@ FILES:${PN}-dev += "${libdir}/pulse-${PV}/modules/*.la
${datadir}/vala"
FILES:${PN}-bin += "${sysconfdir}/default/volatiles/04_pulse"
FILES:${PN}-pa-info = "${bindir}/pa-info"
FILES:${PN}-server = "${bindir}/pulseaudio ${bindir}/start-* ${sysconfdir}
${bindir}/pactl */udev/rules.d/*.rules */*/udev/rules.d/*.rules
${systemd_user_unitdir}/*"
+FILES:${PN}-server += "${datadir}/dbus-1/system.d/pulseaudio-system.conf"
#SYSTEMD_PACKAGES = "${PN}-server"
SYSTEMD_SERVICE:${PN}-server = "pulseaudio.service"
diff --git a/meta/recipes-multimedia/pulseaudio/pulseaudio_16.1.bb
b/meta/recipes-multimedia/pulseaudio/pulseaudio_17.0.bb
similarity index 84%
rename from meta/recipes-multimedia/pulseaudio/pulseaudio_16.1.bb
rename to meta/recipes-multimedia/pulseaudio/pulseaudio_17.0.bb
index 64002cd1cc..54c79b4097 100644
--- a/meta/recipes-multimedia/pulseaudio/pulseaudio_16.1.bb
+++ b/meta/recipes-multimedia/pulseaudio/pulseaudio_17.0.bb
@@ -6,5 +6,5 @@ SRC_URI =
"http://freedesktop.org/software/pulseaudio/releases/${BP}.tar.xz \
file://volatiles.04_pulse \
file://0001-doxygen-meson.build-remove-dependency-on-doxygen-bin.patch \
"
-SRC_URI[sha256sum] =
"8eef32ce91d47979f95fd9a935e738cd7eb7463430dabc72863251751e504ae4"
+SRC_URI[sha256sum] =
"053794d6671a3e397d849e478a80b82a63cb9d8ca296bd35b73317bb5ceb87b5"
UPSTREAM_CHECK_REGEX = "pulseaudio-(?P\d+(\.(?!99)\d+)+)\.tar"
--
2.37.3
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#194275):
https://lists.openembedded.org/g/openembedded-core/message/194275
Mute This Topic: https://lists.openembedded.org/mt/103931861/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[Numpy-discussion] Enhancement: Chebyshev power using DCT
Hi,
In the `numpy.polynomial.chebyshev` module, the function for raising a
Chebyshev polynomial to a power, `chebpow` [1], is essentially implemented in
the following way:
{{{#!highlight python
def chebpow(c, pow):
"""Raise a Chebyshev series to a power."""
zs = _cseries_to_zseries(c)
prd = zs
for i in range(2, pow + 1):
prd = np.convolve(prd, zs)
return _zseries_to_cseries(prd)
}}}
For large coefficient arrays `c` and big exponents `pow`, this procedure is not
efficient. In fact, the complexity of this function is `O(pow*len(c)^2)`, since
the numpy convolution does not make use of a Fast Fourier Transform (FFT).
It is known that Chebyshev polynomials can be multiplied with Discrete Cosine
Transforms (DCT) [2]. What results is the following
algorithm`O(pow*len(c)*log(pow*len(c)))` algorithm for raising a Chebyshev
polynomial with coefficients `c` to an integer power:
{{{#!highlight python
def chebpow_dct(c, pow):
"""Raise a Chebyshev series to a power."""
pad_length = (pow - 1) * (len(c) - 1)
c = np.pad(c, (0, pad_length))
c[1:-1] /= 2
c_pow = idct(dct(c) ** pow)
c_pow[1:-1] *= 2
return c_pow
}}}
The only issue I am having is that as far as I know, `numpy` (unlike `scipy`)
does not have a specialized implementation for the DCT. So the only way of
getting the code to work is "emulating" a DCT with two calls to
`numpy.fft.rfft`, which is slightly slower than using the `scipy.fft.dct`.
I have created a Google colab notebook which compares the error and runtime of
the different implementations (current implementation, implementation using
`scipy.fft.dct`, and pure numpy implementation) [3]. Especially for larger
degree polynomials and higher powers this enhancement would make a huge
difference in terms of runtime.
Similarly, `chebmul` and `chebinterpolate` can also be implemented more
efficiently by using a DCT.
Do you think this enhancement is worth pursuing, and should I create a
pull-request for it?
Best,
Fabio
[1] https://github.com/numpy/numpy/blob/main/numpy/polynomial/chebyshev.py#L817
[2] https://www.sciencedirect.com/science/article/pii/0024379595006966
[3]
https://colab.research.google.com/drive/1JtDDeWC1CEQHDidZ9f5_Ma_ifoBv4Tuz?usp=sharing
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com
Re: [OE-core] [PATCH] pulseaudio: Update to 17.0
Hi Ross,
On Wed, Jan 24, 2024 at 9:48 AM Ross Burton wrote:
>
> On 23 Jan 2024, at 14:08, Fabio Estevam via lists.openembedded.org
> wrote:
> > +FILES:${PN}-server = "${bindir}/pulseaudio ${bindir}/start-* ${datadir}
> > ${sysconfdir} ${bindir}/pactl */udev/rules.d/*.rules
> > */*/udev/rules.d/*.rules ${systemd_user_unitdir}/*”
>
> It’s best not to add entire trees like ${datadir} to files, as there may be
> unexpected consequences.
Thanks for the feedback.
I will send v2 that only adds the specific file instead:
FILES:${PN}-server += "${datadir}/dbus-1/system.d/pulseaudio-system.conf"
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#194270):
https://lists.openembedded.org/g/openembedded-core/message/194270
Mute This Topic: https://lists.openembedded.org/mt/103909681/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: Could you please help me in resolving the " /reset.c:42:(.text.do_reset+0x20): undefined reference to `reset_cpu'?"
On Tue, Jan 23, 2024 at 4:20 PM Liu Wang wrote: > > Hi Fabio, > > Thank you for your help. > > Attached is the 'git status' and 'git log' in my porting u-boot to my > cse_ptjob_cb3_r102 control board by following README in u-boot and being > blocked with the hurdle of "undefined reference to `reset_cpu'" in hope you > spot something familiar and shed a light in my building effort. I don't have any insight into the problem, unfortunately. Also, v2020.10 is too old. You should use mainline U-Boot and upstream your board (or hire someone to do it for you).
[OE-core] [PATCH] pulseaudio: Update to 17.0
From: Fabio Estevam
Update to pulseaudio 17.0 version.
Since pulseaudio commit e96d278bfc51 ("daemon/meson.build: Install
dbus policy in /usr, not /etc"), ${datadir} needs to be passed
in FILES, otherwise the following QA error is seen:
ERROR: pulseaudio-17.0-r0 do_package: QA Issue: pulseaudio: Files/directories
were installed but not shipped in any package:
/usr/share/dbus-1
/usr/share/dbus-1/system.d
/usr/share/dbus-1/system.d/pulseaudio-system.conf
Signed-off-by: Fabio Estevam
---
meta/recipes-multimedia/pulseaudio/pulseaudio.inc | 2 +-
.../pulseaudio/{pulseaudio_16.1.bb => pulseaudio_17.0.bb} | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-multimedia/pulseaudio/{pulseaudio_16.1.bb =>
pulseaudio_17.0.bb} (84%)
diff --git a/meta/recipes-multimedia/pulseaudio/pulseaudio.inc
b/meta/recipes-multimedia/pulseaudio/pulseaudio.inc
index 2245a73392..a55b5d12eb 100644
--- a/meta/recipes-multimedia/pulseaudio/pulseaudio.inc
+++ b/meta/recipes-multimedia/pulseaudio/pulseaudio.inc
@@ -186,7 +186,7 @@ FILES:libpulse-mainloop-glib =
"${libdir}/libpulse-mainloop-glib.so.*"
FILES:${PN}-dev += "${libdir}/pulse-${PV}/modules/*.la ${datadir}/vala"
FILES:${PN}-bin += "${sysconfdir}/default/volatiles/04_pulse"
FILES:${PN}-pa-info = "${bindir}/pa-info"
-FILES:${PN}-server = "${bindir}/pulseaudio ${bindir}/start-* ${sysconfdir}
${bindir}/pactl */udev/rules.d/*.rules */*/udev/rules.d/*.rules
${systemd_user_unitdir}/*"
+FILES:${PN}-server = "${bindir}/pulseaudio ${bindir}/start-* ${datadir}
${sysconfdir} ${bindir}/pactl */udev/rules.d/*.rules */*/udev/rules.d/*.rules
${systemd_user_unitdir}/*"
#SYSTEMD_PACKAGES = "${PN}-server"
SYSTEMD_SERVICE:${PN}-server = "pulseaudio.service"
diff --git a/meta/recipes-multimedia/pulseaudio/pulseaudio_16.1.bb
b/meta/recipes-multimedia/pulseaudio/pulseaudio_17.0.bb
similarity index 84%
rename from meta/recipes-multimedia/pulseaudio/pulseaudio_16.1.bb
rename to meta/recipes-multimedia/pulseaudio/pulseaudio_17.0.bb
index 64002cd1cc..54c79b4097 100644
--- a/meta/recipes-multimedia/pulseaudio/pulseaudio_16.1.bb
+++ b/meta/recipes-multimedia/pulseaudio/pulseaudio_17.0.bb
@@ -6,5 +6,5 @@ SRC_URI =
"http://freedesktop.org/software/pulseaudio/releases/${BP}.tar.xz \
file://volatiles.04_pulse \
file://0001-doxygen-meson.build-remove-dependency-on-doxygen-bin.patch \
"
-SRC_URI[sha256sum] =
"8eef32ce91d47979f95fd9a935e738cd7eb7463430dabc72863251751e504ae4"
+SRC_URI[sha256sum] =
"053794d6671a3e397d849e478a80b82a63cb9d8ca296bd35b73317bb5ceb87b5"
UPSTREAM_CHECK_REGEX = "pulseaudio-(?P\d+(\.(?!99)\d+)+)\.tar"
--
2.37.3
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#194241):
https://lists.openembedded.org/g/openembedded-core/message/194241
Mute This Topic: https://lists.openembedded.org/mt/103909681/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Bug#1056906: debuild: cannot disable lintian
Please close this issue. Thanks.
Re: Could you please help me in resolving the " /reset.c:42:(.text.do_reset+0x20): undefined reference to `reset_cpu'?"
Hi Liu Wang, On Mon, Jan 22, 2024 at 10:55 PM Liu Wang wrote: > > Hi Fabio, > > Could you please help me in resolving the " > /reset.c:42:(.text.do_reset+0x20): undefined reference to `reset_cpu'?" from: > u-boot$make all: Looking at the errors below, there are several errors besides the reset_cpu one. As you are using an out-of-tree U-Boot, there is not much the U-Boot community can do to help you, sorry. You need to get assistance from the U-Boot provider that you are using.
[neon] [Bug 480179] KDE Connect Daemon crashes after update to Frameworks 5.114.0
https://bugs.kde.org/show_bug.cgi?id=480179 Fabio C. Barrionuevo changed: What|Removed |Added CC||bna...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
Pull request: Please pull u-boot-imx-20240115
Hi Tom, Please pull from u-boot-imx, thanks. The following changes since commit 3c04fcf3137d5f694d52b8f355373e4baabe5f78: Merge patch series "k3-j721e: beagleboneai: Fix USB" (2024-01-20 11:39:13 -0500) are available in the Git repository at: https://gitlab.denx.de/u-boot/custodians/u-boot-imx.git tags/u-boot-imx-master-20240122 for you to fetch changes up to a80e0e7711a2b2890a583d88dcd9af978ddada32: ARM: imx: Enable kaslrseed command on DH i.MX8M Plus DHCOM (2024-01-22 08:40:02 -0300) u-boot-imx-master-20240122 -- CI: https://source.denx.de/u-boot/custodians/u-boot-imx/-/pipelines/19406 - Allow i.MX8M Plus DHCOM to operate in overdrive mode. - Allow i.MX8M Plus eDM SBC to operate in overdrive mode. - Enable the 'kaslrseed' command on DH i.MX8M Plus DHCOM. - Select LTO by default on i.MX8M. - Convert pico-dwarf/hobbit-imx6ul to CONFIG_DM_SERIAL. - Fix 'reset' command on wandboard. ---- Fabio Estevam (3): imx8m: Enable LTO by default wandboard: Convert to watchdog driver model pico-dwarf/hobbit-imx6ul: Convert to CONFIG_DM_SERIAL Marek Vasut (3): ARM: imx: Enable SPL_BOARD_INIT on DH i.MX8M Plus DHCOM ARM: imx: Configure GIC clock parent on Data Modul i.MX8M Plus eDM SBC ARM: imx: Enable kaslrseed command on DH i.MX8M Plus DHCOM arch/arm/dts/imx6qdl-wandboard-u-boot.dtsi | 10 ++ arch/arm/mach-imx/imx8m/Kconfig | 1 + board/data_modul/imx8mp_edm_sbc/spl.c | 13 + configs/imx8mp_data_modul_edm_sbc_defconfig | 1 + configs/imx8mp_dhcom_pdk2_defconfig | 3 +++ configs/imx8mp_dhcom_pdk3_defconfig | 3 +++ configs/pico-dwarf-imx6ul_defconfig | 1 + configs/pico-hobbit-imx6ul_defconfig| 1 + configs/wandboard_defconfig | 3 +++ 9 files changed, 36 insertions(+)
Re: [PATCH] ARM: imx: Enable kaslrseed command on DH i.MX8M Plus DHCOM
On Fri, Jan 19, 2024 at 9:36 PM Marek Vasut wrote: > > Linux 6.6.y with KASLR enabled would print the following message on boot: > " > KASLR disabled due to lack of seed > " > Enable the 'kaslrseed' command so a random number seed can be pulled > from CAAM and inserted into the /chosen node 'kaslr-seed' property of > Linux kernel DT before boot, thus letting KASLR work properly. > > Signed-off-by: Marek Vasut Applied, thanks.
Re: [PATCH] pico-dwarf/hobbit-imx6ul: Convert to CONFIG_DM_SERIAL
On Fri, Jan 19, 2024 at 4:41 PM Fabio Estevam wrote: > > The conversion to CONFIG_DM_SERIAL is mandatory, so select > this option. > > Signed-off-by: Fabio Estevam Applied, thanks.
Re: [PATCH] wandboard: Convert to watchdog driver model
On Fri, Jan 19, 2024 at 2:25 PM Fabio Estevam wrote:
>
> Commit 68dcbdd594d4 ("ARM: imx: Add weak default reset_cpu()") caused
> the 'reset' command in U-Boot to not cause a board reset.
>
> Fix it by switching to the watchdog driver model via sysreset, which
> is the preferred method for implementing the watchdog reset.
>
> Signed-off-by: Fabio Estevam
Applied, thanks.
Re: [PATCH v2] ARM: imx: Configure GIC clock parent on Data Modul i.MX8M Plus eDM SBC
On Fri, Jan 19, 2024 at 1:09 PM Marek Vasut wrote: > > The CONFIG_SPL_BOARD_INIT lets SPL common code call spl_board_init() > during the SPL start up. On this particular system, spl_board_init() > is used to reconfigure GIC clock parent to PLL2 500M, which is the > configuration expected by the Linux kernel. Enable SPL_BOARD_INIT > and fill in the GIC clock configuration code. > > Set GIC clock to 500 MHz for OD VDD_SOC. Kernel driver does not > allow to change it. Should set the clock after PMIC setting done. > Default is 400 MHz (system_pll1_800m with div = 2) set by ROM for > ND VDD_SOC. > > Signed-off-by: Marek Vasut Applied, thanks.
Re: [PATCH 1/2] imx8m: Enable LTO by default
On Thu, Jan 18, 2024 at 12:06 PM Fabio Estevam wrote: > > From: Fabio Estevam > > In an attempt to select ARMV8_SPL_EXCEPTION_VECTORS, the SPL size > could not fit into the internal SRAM of some imx8m targets: > >aarch64: + imx8mm_phg > +aarch64-linux-ld.bfd: u-boot-spl section `__u_boot_list' will not fit in > region `.sram' > +aarch64-linux-ld.bfd: region `.sram' overflowed by 1824 bytes > > Select LTO to prevent that. > > Signed-off-by: Fabio Estevam Applied only this one, thanks.
Re: [PATCH] ARM: imx: Enable kaslrseed command on DH i.MX8M Plus DHCOM
On Fri, Jan 19, 2024 at 9:36 PM Marek Vasut wrote: > > Linux 6.6.y with KASLR enabled would print the following message on boot: > " > KASLR disabled due to lack of seed > " > Enable the 'kaslrseed' command so a random number seed can be pulled > from CAAM and inserted into the /chosen node 'kaslr-seed' property of > Linux kernel DT before boot, thus letting KASLR work properly. > > Signed-off-by: Marek Vasut Applied, thanks.
Re: AusweisApp2 build failed on rawhide/x86_64 (unsupported reloc 43)
On Sat, Jan 20, 2024 at 2:41 PM Jakub Jelinek wrote: > > On Sat, Jan 20, 2024 at 02:27:58PM +0100, Julian Sikorski wrote: > > AusweisApp2-2.0.3 build failed on rawhide/x86_64 with unsupported reloc 43 > > errors [1]. Other architectures have built fine, similarly to released > > branches. Is this a problem with rawhide ld.gold? > > I thought reloc 43 (aka R_X86_64_CODE_4_GOTPCRELX) is a relocation for APX > code (i.e. when an instruction uses %r16-%r31 registers and needs GOTPCREL), > it surprises me a package in the distro would use it so quickly. > > In any case, ld.gold is an unmaintained linker for years, just use ld.bfd > instead. It looks like this is a problem in the latest binutils build actually: https://bugzilla.redhat.com/show_bug.cgi?id=2259333 Fabio -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [PATCH] ARM: imx: Enable kaslrseed command on DH i.MX8M Plus DHCOM
On Fri, Jan 19, 2024 at 9:36 PM Marek Vasut wrote: > > Linux 6.6.y with KASLR enabled would print the following message on boot: > " > KASLR disabled due to lack of seed > " > Enable the 'kaslrseed' command so a random number seed can be pulled > from CAAM and inserted into the /chosen node 'kaslr-seed' property of > Linux kernel DT before boot, thus letting KASLR work properly. > > Signed-off-by: Marek Vasut Reviewed-by: Fabio Estevam
Re: [PATCH v2] ARM: imx: Configure GIC clock parent on Data Modul i.MX8M Plus eDM SBC
On Fri, Jan 19, 2024 at 1:09 PM Marek Vasut wrote: > > The CONFIG_SPL_BOARD_INIT lets SPL common code call spl_board_init() > during the SPL start up. On this particular system, spl_board_init() > is used to reconfigure GIC clock parent to PLL2 500M, which is the > configuration expected by the Linux kernel. Enable SPL_BOARD_INIT > and fill in the GIC clock configuration code. > > Set GIC clock to 500 MHz for OD VDD_SOC. Kernel driver does not > allow to change it. Should set the clock after PMIC setting done. > Default is 400 MHz (system_pll1_800m with div = 2) set by ROM for > ND VDD_SOC. > > Signed-off-by: Marek Vasut Reviewed-by: Fabio Estevam
Re: [PATCH v2] ARM: imx: Enable SPL_BOARD_INIT on DH i.MX8M Plus DHCOM
On Fri, Jan 19, 2024 at 1:08 PM Marek Vasut wrote: > > The CONFIG_SPL_BOARD_INIT lets SPL common code call spl_board_init() > during the SPL start up. On this particular system, spl_board_init() > is used to reconfigure GIC clock parent to PLL2 500M, which is the > configuration expected by the Linux kernel. Enable SPL_BOARD_INIT . > > Set GIC clock to 500 MHz for OD VDD_SOC. Kernel driver does not > allow to change it. Should set the clock after PMIC setting done. > Default is 400 MHz (system_pll1_800m with div = 2) set by ROM for > ND VDD_SOC. > > Signed-off-by: Marek Vasut Reviewed-by: Fabio Estevam
Re: SSH key management for Guix cloud machines
On 2024-01-19, 11:09 -0800, Felix Lechner wrote: > I publish my server-side keys via SSHFP records in a domain secured by > DNSSEC. Hi Felix, Thanks. How does the publishing happen exactly, if I may ask? Is it `ssh-keygen -r ...' + a web API call to the DNS provider? My problem with this is that I wouldn't want to include my API credentials in the Guix image. Unless there's a simpler alternative that doesn't require credentials and that I'm not seeing? For instance if the DNS functionality is provided by the hosting provider itself, then credentials might not be needed? Thanks, best wishes, Fabio. -- Fabio Natali https://fabionatali.com
[PATCH] pico-dwarf/hobbit-imx6ul: Convert to CONFIG_DM_SERIAL
The conversion to CONFIG_DM_SERIAL is mandatory, so select this option. Signed-off-by: Fabio Estevam --- configs/pico-dwarf-imx6ul_defconfig | 1 + configs/pico-hobbit-imx6ul_defconfig | 1 + 2 files changed, 2 insertions(+) diff --git a/configs/pico-dwarf-imx6ul_defconfig b/configs/pico-dwarf-imx6ul_defconfig index 7ae37264612c..8b90285980f4 100644 --- a/configs/pico-dwarf-imx6ul_defconfig +++ b/configs/pico-dwarf-imx6ul_defconfig @@ -67,6 +67,7 @@ CONFIG_DM_REGULATOR=y CONFIG_DM_REGULATOR_PFUZE100=y CONFIG_DM_REGULATOR_FIXED=y CONFIG_DM_REGULATOR_GPIO=y +CONFIG_DM_SERIAL=y CONFIG_MXC_UART=y CONFIG_USB=y CONFIG_SPL_USB_HOST=y diff --git a/configs/pico-hobbit-imx6ul_defconfig b/configs/pico-hobbit-imx6ul_defconfig index fc5a54b4e5ed..e3aca6e82e16 100644 --- a/configs/pico-hobbit-imx6ul_defconfig +++ b/configs/pico-hobbit-imx6ul_defconfig @@ -70,6 +70,7 @@ CONFIG_DM_REGULATOR=y CONFIG_DM_REGULATOR_PFUZE100=y CONFIG_DM_REGULATOR_FIXED=y CONFIG_DM_REGULATOR_GPIO=y +CONFIG_DM_SERIAL=y CONFIG_MXC_UART=y CONFIG_USB=y CONFIG_SPL_USB_HOST=y -- 2.34.1
[PATCH] wandboard: Convert to watchdog driver model
Commit 68dcbdd594d4 ("ARM: imx: Add weak default reset_cpu()") caused
the 'reset' command in U-Boot to not cause a board reset.
Fix it by switching to the watchdog driver model via sysreset, which
is the preferred method for implementing the watchdog reset.
Signed-off-by: Fabio Estevam
---
arch/arm/dts/imx6qdl-wandboard-u-boot.dtsi | 10 ++
configs/wandboard_defconfig| 3 +++
2 files changed, 13 insertions(+)
diff --git a/arch/arm/dts/imx6qdl-wandboard-u-boot.dtsi
b/arch/arm/dts/imx6qdl-wandboard-u-boot.dtsi
index 46c4b3b31f4a..80921e80123f 100644
--- a/arch/arm/dts/imx6qdl-wandboard-u-boot.dtsi
+++ b/arch/arm/dts/imx6qdl-wandboard-u-boot.dtsi
@@ -6,4 +6,14 @@
aliases {
mmc0 =
};
+
+ wdt-reboot {
+ compatible = "wdt-reboot";
+ wdt = <>;
+ bootph-pre-ram;
+ };
+};
+
+ {
+ bootph-pre-ram;
};
diff --git a/configs/wandboard_defconfig b/configs/wandboard_defconfig
index 168e2f086008..e9deab38038f 100644
--- a/configs/wandboard_defconfig
+++ b/configs/wandboard_defconfig
@@ -75,6 +75,8 @@ CONFIG_DM_PMIC_PFUZE100=y
CONFIG_SCSI=y
CONFIG_DM_SERIAL=y
CONFIG_MXC_UART=y
+CONFIG_SYSRESET=y
+CONFIG_SYSRESET_WATCHDOG=y
CONFIG_DM_THERMAL=y
CONFIG_USB=y
CONFIG_VIDEO=y
@@ -88,3 +90,4 @@ CONFIG_IMX_HDMI=y
CONFIG_SPLASH_SCREEN=y
CONFIG_SPLASH_SCREEN_ALIGN=y
CONFIG_BMP_16BPP=y
+CONFIG_IMX_WATCHDOG=y
--
2.34.1
SSH key management for Guix cloud machines
Hi All, I wanted to ask what the best practice is (or what people usually do) when it comes to SSH key management for Guix systems deployed in the cloud. In a nutshell, consider a cloud server that's been instantiated out of a Guix system image. Suppose that the image comes with a predefinded (passwordless) user and an authorised SSH key for remote access. On first access, the user is asked to verify and accept the server's SSH fingerprint, and rightfully so to protect against MITM attacks. Is there any mechanism that would allow to access the server without having to trust-on-first-use the server's fingerprint? In other words, once the server SSH key has been generated, is there any standard/common way to have the fingerprint published (or somehow "phoned home")? In the context of cloud-init, I think this is achieved via the Phone Home module⁰. I believe Terraform and other orchestration tools also provide their own solution to this. Am I missing anything macroscopic here? Is there any similar SSH phone-home service under Guix? If not, would there be interest around such a service or potentially to have this functionality as part of the SSH service? A cheap (but convoluted) option would be to have the SSH fingerprint saved in /etc/issue. Some cloud providers allow the possibility to connect to the machine via a web console. A user would be able to use the web console to retrieve the key. A bit of a hack, to be honest. Any idea or comment welcome. Thanks, cheers, Fabio. - 0 https://cloudinit.readthedocs.io/en/latest/reference/modules.html#phone-home -- Fabio Natali https://fabionatali.com
Re: [PATCH] ARM: imx: Enable SPL_BOARD_INIT on DH i.MX8M Plus DHCOM
On Thu, Jan 18, 2024 at 9:38 PM Marek Vasut wrote: > > The CONFIG_SPL_BOARD_INIT lets SPL common code call spl_board_init() > during the SPL start up. On this particular system, spl_board_init() > is used to reconfigure GIC clock parent to PLL2 500M, which is the > configuration expected by the Linux kernel. Enable SPL_BOARD_INIT . Same as the other patch, please explain why setting the PLL2 to 500MHz is needed.
Re: [PATCH] ARM: imx: Configure GIC clock parent on Data Modul i.MX8M Plus eDM SBC
Hi Marek, On Thu, Jan 18, 2024 at 9:47 PM Marek Vasut wrote: > > The CONFIG_SPL_BOARD_INIT lets SPL common code call spl_board_init() > during the SPL start up. On this particular system, spl_board_init() > is used to reconfigure GIC clock parent to PLL2 500M, which is the > configuration expected by the Linux kernel. Enable SPL_BOARD_INIT > and fill in the GIC clock configuration code. Please add an explanation about the "configuration expected by the Linux kernel". In the comments below, you explain that this is needed for overdrive mode. It would be great to have such a comment in the commit log as well. Thanks
Re: F40 Change Proposal: Optimized Binaries for the AMD64 Architecture (System-Wide)
On Tue, Jan 16, 2024 at 2:43 PM Dridi Boukelmoune wrote: > > > This is also a valid approach. This is the first alternative proposal > > which makes me say "hmm, this would also work". It is possibly even > > simpler than setting the $PATH. A very small disadvantage is that the > > wrapper would need to do its work every time the binary is called. > > But the wrapper could be trivially implemented in shell or it could be > > a compiled binary, making the wrapper very cheap. > > > > Hmm, what do other people think? > > With my computer user hat on, I would much prefer this approach. If > the supposed "dozen" of relevant packages can be built with several > binaries variants, then let's pack them all in the same RPM and use > this mechanism. I'm sure that if successful it would extend to more > packages, including packages on the critical path. I'm fine with that > eventual outcome with this scheme. > > This way, if I ever need to take my drive out of a fried laptop and > USB-boot from it on my spare laptop from 2013, then I'm not painting > myself into a corner with binaries too recent for that hardware. I was > happy to be able to do that last summer, and hope to still be able to > in the future (but also hope not to ever need it again). And yes, > Fedora (Xfce) works just fine on that decade-old laptop. But ... you would be able to do this if the proposal was implemented as-is, as well? The "non-optimized" variant would still be installed, and PATH would be set appropriately to fall back to it if you stick the hard drive into an old machine (unless I misunderstand the proposal, or your argument here). Just to give my 2¢ here as well, I was skeptical about the "systemd sets the $PATH appropriately for the hardware it's booting on", but I actually like that approach now. Using symbolic links smells too much like using alternatives, and those have always been a bit brittle. Fabio -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [PATCH 2/2] arm: imx: imx8m: Enable the SError exception
On Thu, Jan 18, 2024 at 4:08 PM Marek Vasut wrote:
>
> On 1/18/24 16:06, Fabio Estevam wrote:
> > From: Ye Li
> >
> > To work with commit 2f3c92060dcd ("imx8m: workaround ROM serror")
> > we need to enable the SError exception and install vector in SPL.
>
> This really does need better commit message, sorry.
>
> Details, please.
>
> What does trigger the SError ?
Ye Li, please improve the commit message and send a v2.
Thanks
[wacomtablet] [Bug 467457] Screen Cursor dont follow the Tablet Cursor
https://bugs.kde.org/show_bug.cgi?id=467457 --- Comment #5 from Fabio Ortolan --- Created attachment 165021 --> https://bugs.kde.org/attachment.cgi?id=165021=edit Spectacle screenshot showing the cursor with the option off. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 467457] Screen Cursor dont follow the Tablet Cursor
https://bugs.kde.org/show_bug.cgi?id=467457 Fabio Ortolan changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #4 from Fabio Ortolan --- Well the bug is back on when I upgrade to Fedora 39. Something that I noted is the Spectacle (screenshot utility) is showing the cursor even if the option is not enabled. Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Kernel Version: 6.6.11-200.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i3-7100 CPU @ 3.90GHz Memory: 11.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 Manufacturer: Dell Inc. Product Name: Inspiron 3268 -- You are receiving this mail because: You are watching all bug changes.
Re: Guix at 37C3 Chaos Communication Congress in late Dec?
On 2024-01-18, 14:25 +0100, Andreas Enge wrote: > thanks for your report! Hey Andreas, thank you for getting back to me. > This is quite amazing. One of the most depressing experiences at a CCC > was when I went to a Lisp assembly, and there were at most a dozen > people around a table, none of whom used the same Lisp dialect. Haha, yes, I can see how this can very well be a risk! The advantage of a Lisp assembly is the economy of scale. That'd combine together various projects that were all massively under-represented at 37c3 - I'm primarily thinking of Guix, Guile, and Emacs as those are the projects I care about, but there are others too. If we build enough momentum, we should be able to have decently sized assembly subgroups - in other words, we should be able to avoid the twelve-people-that-speak-twelve-different-lisps scenario. :) What's not ideal with a Lisp assembly is that Guix and Emacs are not programming languages and, despite related to Lisp, their scope and ideas transcend - or are partly orthogonal to - Lisp itself. An other option would be to go the "FOSDEM way" and have a "declarative and minimalist computing" assembly instead - what do you think? I still have a slight preference for the Lisp assembly idea, but let's see what the general feeling/preference is here in the ML. 38c3 won't be happening any time soon anyway. :) Thanks, best, F. -- Fabio Natali https://fabionatali.com
[PATCH 2/2] arm: imx: imx8m: Enable the SError exception
From: Ye Li
To work with commit 2f3c92060dcd ("imx8m: workaround ROM serror")
we need to enable the SError exception and install vector in SPL.
Signed-off-by: Ye Li
Reviewed-by: Peng Fan
Reported-by: Thomas Schaefer
Reviewed-by: Fabio Estevam
Signed-off-by: Fabio Estevam
---
arch/arm/mach-imx/imx8m/Kconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/mach-imx/imx8m/Kconfig b/arch/arm/mach-imx/imx8m/Kconfig
index 328c3e388051..eb0488a9e8bf 100644
--- a/arch/arm/mach-imx/imx8m/Kconfig
+++ b/arch/arm/mach-imx/imx8m/Kconfig
@@ -13,14 +13,17 @@ config IMX8MQ
bool
select IMX8M
select CLK_IMX8MQ
+ select ARMV8_SPL_EXCEPTION_VECTORS
config IMX8MM
bool
select IMX8M
+ select ARMV8_SPL_EXCEPTION_VECTORS
config IMX8MN
bool
select IMX8M
+ select ARMV8_SPL_EXCEPTION_VECTORS
config IMX8MP
bool
--
2.34.1
[PATCH 1/2] imx8m: Enable LTO by default
From: Fabio Estevam In an attempt to select ARMV8_SPL_EXCEPTION_VECTORS, the SPL size could not fit into the internal SRAM of some imx8m targets: aarch64: + imx8mm_phg +aarch64-linux-ld.bfd: u-boot-spl section `__u_boot_list' will not fit in region `.sram' +aarch64-linux-ld.bfd: region `.sram' overflowed by 1824 bytes Select LTO to prevent that. Signed-off-by: Fabio Estevam --- arch/arm/mach-imx/imx8m/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/mach-imx/imx8m/Kconfig b/arch/arm/mach-imx/imx8m/Kconfig index b1937198402f..328c3e388051 100644 --- a/arch/arm/mach-imx/imx8m/Kconfig +++ b/arch/arm/mach-imx/imx8m/Kconfig @@ -5,6 +5,7 @@ config IMX8M select BINMAN select GICV3 if ARMV8_PSCI select HAS_CAAM + select LTO select ROM_UNIFIED_SECTIONS select ARMV8_CRYPTO -- 2.34.1
Re: [PATCH] arm: imx: imx8m: Enable the SError exception
On Fri, Jan 12, 2024 at 3:00 PM Fabio Estevam wrote: > > Hi Ye Li, > > On Fri, Jan 12, 2024 at 4:07 AM Ye Li wrote: > > > > To work with commit 2f3c920(imx8m: workaround ROM serror), > > we need to enable the SError exception and install vector in SPL. > > > > Signed-off-by: Ye Li > > Reviewed-by: Peng Fan > > This causes an image increase that makes SPL to not fit into the > internal SRAM on some boards: > > https://source.denx.de/u-boot/custodians/u-boot-imx/-/jobs/769422 To fix this problem, what if we enable LTO for all imx8m platforms? diff --git a/arch/arm/mach-imx/imx8m/Kconfig b/arch/arm/mach-imx/imx8m/Kconfig index b1937198402f..6617a631b4d6 100644 --- a/arch/arm/mach-imx/imx8m/Kconfig +++ b/arch/arm/mach-imx/imx8m/Kconfig @@ -7,19 +7,23 @@ config IMX8M select HAS_CAAM select ROM_UNIFIED_SECTIONS select ARMV8_CRYPTO + select LTO config IMX8MQ What do you think?
Re: Could you please help me in resolving the "arch/arm/lib/vectors.S:87: Error: no such instruction: `b reset' ?"
On Wed, Jan 17, 2024 at 10:26 PM Liu Wang wrote: > > Hi Fabio, > > Thank you for your help. > > Switching to "arm-gnu-toolchain-13.2.Rel1-x86-64-arm-none-eabi" seems a fix > for : > ...gnueabihf-gcc: cannot execute binary file: Exec format error... I would suggest installing the default arm toolchain from Ubuntu. As for the build error, you would need to ask to whoever provided you with the code. Since this is not a mainline U-Boot, we cannot help.
[OE-core] [PATCH] iputils: Update to 20240117
From: Fabio Estevam
Update to the 20240117 release.
Signed-off-by: Fabio Estevam
---
.../iputils/{iputils_20231222.bb => iputils_20240117.bb}| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-extended/iputils/{iputils_20231222.bb =>
iputils_20240117.bb} (97%)
diff --git a/meta/recipes-extended/iputils/iputils_20231222.bb
b/meta/recipes-extended/iputils/iputils_20240117.bb
similarity index 97%
rename from meta/recipes-extended/iputils/iputils_20231222.bb
rename to meta/recipes-extended/iputils/iputils_20240117.bb
index e919febd12..5a5e15528e 100644
--- a/meta/recipes-extended/iputils/iputils_20231222.bb
+++ b/meta/recipes-extended/iputils/iputils_20240117.bb
@@ -11,7 +11,7 @@ LIC_FILES_CHKSUM =
"file://LICENSE;md5=627cc07ec86a45951d43e30658bbd819"
DEPENDS = "gnutls"
SRC_URI = "git://github.com/iputils/iputils;branch=master;protocol=https"
-SRCREV = "84cdf26908b4a03b917a5429a6339b7374fcc38b"
+SRCREV = "8372f355bdf7a9b0c79338dd8ef8464c00a5c4e2"
S = "${WORKDIR}/git"
--
2.37.3
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193951):
https://lists.openembedded.org/g/openembedded-core/message/193951
Mute This Topic: https://lists.openembedded.org/mt/103799183/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: Could you please help me in resolving the "arch/arm/lib/vectors.S:87: Error: no such instruction: `b reset' ?"
On Wed, Jan 17, 2024 at 3:25 PM Liu Wang wrote: > 2. You are right. I have not exported the tool chain. > Could you please share me a link to a readme in setting up the tool chain for > Ubuntu cross build environment ? You can do like this: export ARCH=arm export CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- make cse_ptjob_cb3_r102_defconfig make
Re: Could you please help me in resolving the "arch/arm/lib/vectors.S:87: Error: no such instruction: `b reset' ?"
On Wed, Jan 17, 2024 at 9:27 AM Liu Wang wrote: > > Sir/Madam, > > Could you please help me in resolving the "arch/arm/lib/vectors.S:87: Error: > no such instruction: `b reset' ?" > > Sincerely, > Liu Wang > liuw@liuw-SYS-E100-12T-H:~/Downloads/u-boot$ make cse_ptjob_cb3_r102_defconfig This is not a configuration supported by U-Boot mainline. > # > # configuration written to .config > # > liuw@liuw-SYS-E100-12T-H:~/Downloads/u-boot$ make all > scripts/kconfig/conf --syncconfig Kconfig > CFG u-boot.cfg > GEN include/autoconf.mk > GEN include/autoconf.mk.dep > UPD include/generated/timestamp_autogenerated.h > HOSTCC tools/mkenvimage.o > HOSTLD tools/mkenvimage > HOSTCC tools/dumpimage.o > HOSTLD tools/dumpimage > HOSTCC tools/mkimage.o > HOSTLD tools/mkimage > LD arch/arm/cpu/built-in.o > LD arch/arm/cpu//built-in.o > AS arch/arm/lib/vectors.o > arch/arm/lib/vectors.S: Assembler messages: > arch/arm/lib/vectors.S:87: Error: no such instruction: `b reset' Have you exported the toolchain?
Re: [PATCH] Add Phytec i.MX93 support
Hi Mathieu,
Thanks for the patch.
I have added more Phytec folks in case they could help review/test.
On Wed, Jan 17, 2024 at 4:53 AM Mathieu Othacehe wrote:
>
> Add support for the Phytec i.MX93 Segin evaluation kit. The SoM consists
> of an NXP i.MX93 dual A55 CPU. The SoM is mounted on a Phytec Segin SBC.
>
> Signed-off-by: Mathieu Othacehe
> ---
> arch/arm/dts/Makefile |3 +-
> arch/arm/dts/imx93-phycore-segin-u-boot.dtsi | 274 +++
> arch/arm/dts/imx93-phycore-segin.dts | 95 +
> arch/arm/dts/imx93-phycore-som.dtsi | 64 +
> arch/arm/mach-imx/imx9/Kconfig|6 +
> board/phytec/common/mmc.c | 49 +
> board/phytec/imx93_phycore/Kconfig| 21 +
> board/phytec/imx93_phycore/MAINTAINERS| 10 +
> board/phytec/imx93_phycore/Makefile | 16 +
> board/phytec/imx93_phycore/imx93_phycore.c| 89 +
> board/phytec/imx93_phycore/imx93_phycore.env | 96 +
> .../phytec/imx93_phycore/lpddr4_timing_1GB.c | 1546 +
> board/phytec/imx93_phycore/spl.c | 181 ++
> configs/imx93_phycore_defconfig | 147 ++
> doc/board/phytec/imx93_phycore.rst| 68 +
> doc/board/phytec/index.rst|1 +
> include/configs/imx93_phycore.h | 47 +
> 17 files changed, 2712 insertions(+), 1 deletion(-)
> create mode 100644 arch/arm/dts/imx93-phycore-segin-u-boot.dtsi
> create mode 100644 arch/arm/dts/imx93-phycore-segin.dts
> create mode 100644 arch/arm/dts/imx93-phycore-som.dtsi
> create mode 100644 board/phytec/common/mmc.c
> create mode 100644 board/phytec/imx93_phycore/Kconfig
> create mode 100644 board/phytec/imx93_phycore/MAINTAINERS
> create mode 100644 board/phytec/imx93_phycore/Makefile
> create mode 100644 board/phytec/imx93_phycore/imx93_phycore.c
> create mode 100644 board/phytec/imx93_phycore/imx93_phycore.env
> create mode 100644 board/phytec/imx93_phycore/lpddr4_timing_1GB.c
> create mode 100644 board/phytec/imx93_phycore/spl.c
> create mode 100644 configs/imx93_phycore_defconfig
> create mode 100644 doc/board/phytec/imx93_phycore.rst
> create mode 100644 include/configs/imx93_phycore.h
>
> diff --git a/arch/arm/dts/Makefile b/arch/arm/dts/Makefile
> index d456a524b36..4a23e2a2f49 100644
> --- a/arch/arm/dts/Makefile
> +++ b/arch/arm/dts/Makefile
> @@ -1127,7 +1127,8 @@ dtb-$(CONFIG_ARCH_IMX8M) += \
>
> dtb-$(CONFIG_ARCH_IMX9) += \
> imx93-11x11-evk.dtb \
> - imx93-var-som-symphony.dtb
> + imx93-var-som-symphony.dtb \
> + imx93-phycore-segin.dtb
>
> dtb-$(CONFIG_ARCH_IMXRT) += imxrt1050-evk.dtb \
> imxrt1020-evk.dtb \
> diff --git a/arch/arm/dts/imx93-phycore-segin-u-boot.dtsi
> b/arch/arm/dts/imx93-phycore-segin-u-boot.dtsi
> new file mode 100644
> index 000..6d75f1985aa
> --- /dev/null
> +++ b/arch/arm/dts/imx93-phycore-segin-u-boot.dtsi
> @@ -0,0 +1,274 @@
> +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
> +/*
> + * Copyright (C) 2023 PHYTEC Messtechnik GmbH
> + * Christoph Stoidner
> + *
> + * Product homepage:
> + * phyBOARD-Segin carrier board is reused for the i.MX93 design.
> + *
> https://www.phytec.de/produkte/single-board-computer/phyboard-segin-imx6ul/
> + */
> +
> +#include "imx93-u-boot.dtsi"
> +
> +/ {
> + wdt-reboot {
> + compatible = "wdt-reboot";
> + wdt = <>;
> + bootph-pre-ram;
> + bootph-some-ram;
> + };
> +
> + aliases {
> + ethernet0 =
> + ethernet1 =
> + };
> +
> + firmware {
> + optee {
> + compatible = "linaro,optee-tz";
> + method = "smc";
> + };
> + };
> +};
> +
> +&{/soc@0} {
> + bootph-all;
> + bootph-pre-ram;
> +};
> +
> + {
> + bootph-pre-ram;
> + bootph-all;
> +};
> +
> + {
> + bootph-pre-ram;
> + bootph-some-ram;
> +};
> +
> + {
> + bootph-pre-ram;
> + bootph-some-ram;
> +};
> +
> + {
> + bootph-pre-ram;
> + bootph-some-ram;
> +};
> +
> +_usdhc2_vmmc {
> + u-boot,off-on-delay-us = <2>;
> + bootph-pre-ram;
> + bootph-some-ram;
> +};
> +
> +_reg_usdhc2_vmmc {
> + bootph-pre-ram;
> +};
> +
> +_uart1 {
> + bootph-pre-ram;
> + bootph-some-ram;
> +};
> +
> +_usdhc2 {
> + bootph-pre-ram;
> + bootph-some-ram;
> +};
> +
> + {
> + bootph-pre-ram;
> + bootph-some-ram;
> +};
> +
> + {
> + bootph-pre-ram;
> + bootph-some-ram;
> +};
> +
> + {
> + bootph-pre-ram;
> + bootph-some-ram;
> +};
> +
> + {
> + bootph-pre-ram;
> + bootph-some-ram;
> +};
> +
> + {
> + bootph-pre-ram;
> + bootph-some-ram;
> +};
> +
> + {
> + bootph-pre-ram;
> + bootph-some-ram;
> +};
> +
> + {
> + bootph-pre-ram;
> + bootph-some-ram;
> +
Bug#1061021: cinnamon-control-center: FTBFS: Package 'libevdev', required by 'libwacom', not found
Il 16/01/2024 20:29, Lucas Nussbaum ha scritto: CMake binary for host machine is not cached CMake binary missing from cross or native file, or env var undefined. Trying a default CMake fallback at cmake Did not find CMake 'cmake' Found CMake: NO Dependency lookup for libwacom with method 'cmake' failed: CMake binary for machine host machine not found. Giving up. Run-time dependency libwacom found: NO ../meson.build:86:14: ERROR: Dependency lookup for libwacom with method 'pkgconfig' failed: Could not generate cflags for libwacom: Package libevdev was not found in the pkg-config search path. Perhaps you should add the directory containing `libevdev.pc' to the PKG_CONFIG_PATH environment variable Package 'libevdev', required by 'libwacom', not found dh_auto_configure: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1 returned exit code 1 make: *** [debian/rules:10: binary] Error 25 Thanks for your work about FTBFS reports. libevdev seems don't required by cinnamon-control-center but by wacom, from a fast look I saw require it but don't have libevdev-dev dep. anyway is already reported by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060687 I don't think is a good thing add libevdev-dev build-dep. in cinnamon-control-center as temporary workaround and should wait fix in libwacom instead, or I'm wrong? OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1061021: cinnamon-control-center: FTBFS: Package 'libevdev', required by 'libwacom', not found
Il 16/01/2024 20:29, Lucas Nussbaum ha scritto: CMake binary for host machine is not cached CMake binary missing from cross or native file, or env var undefined. Trying a default CMake fallback at cmake Did not find CMake 'cmake' Found CMake: NO Dependency lookup for libwacom with method 'cmake' failed: CMake binary for machine host machine not found. Giving up. Run-time dependency libwacom found: NO ../meson.build:86:14: ERROR: Dependency lookup for libwacom with method 'pkgconfig' failed: Could not generate cflags for libwacom: Package libevdev was not found in the pkg-config search path. Perhaps you should add the directory containing `libevdev.pc' to the PKG_CONFIG_PATH environment variable Package 'libevdev', required by 'libwacom', not found dh_auto_configure: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1 returned exit code 1 make: *** [debian/rules:10: binary] Error 25 Thanks for your work about FTBFS reports. libevdev seems don't required by cinnamon-control-center but by wacom, from a fast look I saw require it but don't have libevdev-dev dep. anyway is already reported by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060687 I don't think is a good thing add libevdev-dev build-dep. in cinnamon-control-center as temporary workaround and should wait fix in libwacom instead, or I'm wrong? OpenPGP_signature.asc Description: OpenPGP digital signature
