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: Fab
Peng,
On Wed, Mar 27, 2024 at 11:07 AM Sumit Garg wrote:
> That's the real reason why we should try to migrate to OF_UPSTREAM at
> SoC level rather than at board level. If a particular board isn't
> supported upstream then they can opt out for the time being.
All the imx93 boards in U-Boot are
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: Fab
Hi Christian,
On Wed, Mar 27, 2024 at 3:54 AM Christian Gmeiner
wrote:
> It does help \o/
Ok, great!
> When you send out a proper patch feel free to add Tested-by: Christian
> Gmeiner
I have sent a more complete fix, so I have not included your Tested-by.
Please test the formal version and
in board_type() to read the
board revision pins in SPL.
Reported-by: Christian Gmeiner
Signed-off-by: Fabio Estevam
---
board/solidrun/mx6cuboxi/mx6cuboxi.c | 13 +
1 file changed, 5 insertions(+), 8 deletions(-)
diff --git a/board/solidrun/mx6cuboxi/mx6cuboxi.c
b/board/solidrun
On Tue, 26 Mar 2024 19:48:13 +0100 Carsten Schoenert
wrote:
> Hello Mikhail,
>
> Am 26.03.24 um 08:37 schrieb Kosolapov Ivan:
> > Hello, Carsten!
> > I have built a new version of IMSProg (v1.3.3).
> > Can you please tell me how I can get this version to you? Do I have to
> > upload the new
On Tue, 26 Mar 2024 19:48:13 +0100 Carsten Schoenert
wrote:
> Hello Mikhail,
>
> Am 26.03.24 um 08:37 schrieb Kosolapov Ivan:
> > Hello, Carsten!
> > I have built a new version of IMSProg (v1.3.3).
> > Can you please tell me how I can get this version to you? Do I have to
> > upload the new
Hi Javier,
On Tue, Mar 26, 2024 at 8:07 AM Javier Viguera wrote:
>
> According to the documentation (for example AN13994), for AHAB-enabled
> devices the format of the signature block is:
>
> +--+--+--+-+
> | Tag | Length - msb |
Hi Adam,
On Tue, Mar 26, 2024 at 5:25 PM Adam Ford wrote:
>
> The imx8mm-beacon boards can migrate to OF_UPSTREAM which also
> allows for the removal the device tree files.
>
> Signed-off-by: Adam Ford
Please split the series by SoC family, thanks.
On Tue, Mar 26, 2024 at 12:30 AM Joy Zou wrote:
> + {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + clock-frequency = <40>;
> + pinctrl-names = "default", "sleep";
> + pinctrl-0 = <_lpi2c3>;
> + pinctrl-1 = <_lpi2c3>;
> + status = "okay";
> +
On Tue, Mar 26, 2024 at 12:30 AM Joy Zou wrote:
>
> Enable CONFIG_RTC_PCF2127 configs to support pcf2131.
Subject should be imx93_11x11_evk specific:
imx93_11x11_evk: Add PCF2131 RTC support
On Tue, Mar 26, 2024 at 12:30 AM Joy Zou wrote:
> +bool is_pcf2131_type(struct udevice *dev)
static bool
> static int pcf2127_rtc_read(struct udevice *dev, uint offset, u8 *buffer,
> uint len)
> {
> struct dm_i2c_chip *chip = dev_get_parent_plat(dev);
> @@ -43,10 +75,64 @@ static
On Tue, Mar 26, 2024 at 1:11 PM Christian Gmeiner
wrote:
> It got better but the model is (still) wrong:
>
> U-Boot 2024.04-rc5-dirty (Mar 26 2024 - 17:03:41 +0100)
>
> CPU: Freescale i.MX6Q rev1.3 996 MHz (running at 792 MHz)
> CPU: Extended Commercial temperature grade (-20C to 105C) at
Hi Christian,
On Tue, Mar 26, 2024 at 12:17 PM Christian Gmeiner
wrote:
>
> I am seeing model detection problems with the current git master.
>
> U-Boot 2024.04-rc5 (Mar 26 2024 - 15:59:22 +0100)
>
> CPU: Freescale i.MX6Q rev1.3 996 MHz (running at 792 MHz)
> CPU: Extended Commercial
Hi Vivek,
[Please don't top-post and do not post HTML]
On Mon, Mar 25, 2024 at 1:37 PM Vivek Jaiswal wrote:
>
> Hello Fabio,
> I tried using the this github repository.
> https://github.com/u-boot/u-boot.git
>
> And the configuration used was following
>
> rockchip-r
From: Fabio Estevam
Add a weak default reset_cpu() implementation just like
it is done on arch/arm/mach-imx/cpu.c.
This allows the removal of the empty reset_cpu() in several
board files.
Signed-off-by: Fabio Estevam
---
arch/arm/mach-imx/imx8/cpu.c | 4
board
Linux DTS).
I did not understand this part, do you mean that Linux will also do the
imx28-xea.dts => imx28-xea.dtsi rename and will also have the new
imx28-xea-1.dts and imx28-xea-2.dts?
Regards,
Fabio Estevam
> Version 1.8.10 fixed this bug (see "udp" and "tcp" in "prot") in
> https://git.netfilter.org/iptables/commit/?id=34f085b1607364f4eaded1140060dcaf965a2649
iptables 1.8.10 was released on 2023-10-10, but this commit was merged
in 2024-02-07, so it is not fixed in 1.8.10, but it will be in the
Control: tag -1 pending
Hello,
Bug #1066711 in freeipmi reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
was able to make it work by
dropping the IPv6 gateway altogether, as suggested by Felix.
Thanks for sharing your settings/experience with this.
Cheers, Fabio.
--
Fabio Natali
https://fabionatali.com
Version: 24.0.3-1+b1
Great, they belong to the same source package and should be both upgraded.
Closing.
> With mesa-va-drivers:amd64 24.0.3-1+b1 and libgl1-mesa-dri:amd64
> 23.3.3-3, the result is the same.
>
> But with also updating libgl1-mesa-dri:amd64 to 24.0.3-1+b1, the issue
> is fixed.
Version: 24.0.3-1+b1
Great, they belong to the same source package and should be both upgraded.
Closing.
> With mesa-va-drivers:amd64 24.0.3-1+b1 and libgl1-mesa-dri:amd64
> 23.3.3-3, the result is the same.
>
> But with also updating libgl1-mesa-dri:amd64 to 24.0.3-1+b1, the issue
> is fixed.
On 2024-03-25, 11:52 +, Fabio Natali wrote:
> Once the reconfiguration has taken place and when restarting the
> networking service, I get this error:
>
> ,
> | herd: error: exception caught while executing 'start' on service
> 'networking':
> | Throw to key `
t; worked for me at the time. [1]
I think I tried that (commenting out the default gateway part, which
might be picked up automatically by means of Router Advertisement
RA?). I'll definitely try again once in front of the machine and update
the bug report with my findings.
Thanks for now!
Cheers, Fabio.
happens on an up-to-date Guix system.
Thanks, best wishes, Fabio.
⁰
https://guix.gnu.org/manual/devel/en/html_node/Networking-Setup.html#index-static_002dnetworking
--
Fabio Natali
https://fabionatali.com
CONFIG_USB_GADGET_VENDOR_NUM is a 16-bit number, so remove
the leading zero.
Reported-by: Marek Vasut
Signed-off-by: Fabio Estevam
---
configs/phycore_pcl063_defconfig | 2 +-
configs/phycore_pcl063_ull_defconfig | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
' on service 'networking':
| Throw to key `%exception' with args `("#< errno:
17>")'.
`
It'd seem to be relevant to bug report 64653¹?
Do you know what this might be related to and what I can do to solve it?
This happens on an up-to-date Guix system.
Thanks, best wishes, F
Hi Emanuele,
On Mon, Mar 25, 2024 at 8:47 AM Emanuele Ghidoli
wrote:
> +config FSL_CAAM_JR_NTZ_ACCESS
> + bool "Give caam Job Ring access to non-secure world"
Please spell CAAM instead.
> + default n
'default n' is already the default, please drop this line.
On Fri, Mar 22, 2024 at 9:55 AM Yannic Moog wrote:
>
> The "run netargs" command should come later in the "netboot" command
> order when using dhcp since it sets the server and client ip addresses.
> The previous order led to misconfigured kernel boot params and thus
> kernel panic when serverip
On Thu, Mar 21, 2024 at 4:17 PM Marek Vasut wrote:
> $ git grep -i usb.*phytec configs
> configs/phycore_pcl063_defconfig:CONFIG_USB_GADGET_MANUFACTURER="Phytec"
> configs/phycore_pcl063_ull_defconfig:CONFIG_USB_GADGET_MANUFACTURER="Phytec"
>
> It would be good to be consistent.
>
> Also, what
On Thu, Mar 21, 2024 at 4:17 PM Marek Vasut wrote:
>
> On 3/21/24 3:45 PM, Mathieu Othacehe wrote:
> > Enable both usbotg1 and usbotg2 ports. Disable over-current as OC pins are
> > not connected to the SoC.
> >
> > This
>
> "This addition to ...-u-boot.dtsi is temporary, ..." would be clearer.
On Thu, Mar 21, 2024 at 4:20 AM Mathieu Othacehe wrote:
>
> This message is used to commit into the fuses any new SRK revocation and
> FW version information that have been found into the NXP (ELE FW) and
> OEM containers.
>
> Signed-off-by: Mathieu Othacehe
Applied to u-boot-imx/next, thanks.
On Fri, Mar 22, 2024 at 10:51 AM Fabio Estevam wrote:
>
> Hi Sumit,
>
> On Thu, Mar 21, 2024 at 11:55 AM Sumit Garg wrote:
>
> > Changes in v4:
> > - Incorporated misc comments from Marek and added his review tag.
> > - Dropped patch #4 (imx8mp: power-domain: Do
Hi Tom,
Please pull this material for next from u-boot-imx, thanks.
The following changes since commit fb49d6c289d942ff7de309a5c5eaa37a7f4235db:
remoteproc: uclass: Add methods to load firmware to rproc and boot rproc
(2024-03-22 15:50:28 -0400)
are available in the Git repository at:
On Fri, Mar 22, 2024 at 4:31 PM Fabio Estevam wrote:
> As Pierre's explanation addresses Marc's concern,
> do you think this can go to 2024.01 to fix the boot regression on imx8qxp/8qm?
I meant 2024.04, sorry.
Hi Tom,
On Tue, Mar 19, 2024 at 9:39 AM Pierre-Clément Tosi wrote:
> For most AArch64 U-Boot ports (including the i.MX family), the answer is
> trivial
> because they use the arch code i.e. setup_all_pgtables(). However, as
> fsl-layerscape re-implements mmu_setup(), it had to be looked at
Hi Paul,
On Sun, Feb 11, 2024 at 4:42 PM Paul Liu wrote:
>
> Hi Fabio,
>
> I'm on vacation now (Chinese new year). I hope I'll find some time to revive
> my imx8 board.
> I've tried sandbox and qemu. Both of them are not reproducible. I'm wondering
> if it could be some pa
re how to
> deal with this issue?
Yes, these error messages represent all the crate dependencies that
cannot be resolved from Fedora repositories.
They will need to be packaged separately if you want to submit this as
an official package for Fedora.
Or if you want a &quo
it is also here:
www.sundialatlas.eu/atlas.php?sun=ES877
Fabio Savian
Il 22/03/2024 15:40, Douglas Bateman via sundial ha scritto:
Diese Nachricht wurde eingewickelt um DMARC-kompatibel zu sein. Die
eigentliche Nachricht steht dadurch in einem Anhang.
This message was wrapped to be DMARC
Hi Sumit,
On Thu, Mar 21, 2024 at 11:55 AM Sumit Garg wrote:
> Changes in v4:
> - Incorporated misc comments from Marek and added his review tag.
> - Dropped patch #4 (imx8mp: power-domain: Don't power off pd_bus)
> since power domain off path is never excercised for DT based devices.
> -
Hi Lukasz,
On Fri, Mar 22, 2024 at 8:43 AM Lukasz Majewski wrote:
> arch/arm/dts/Makefile | 3 +-
> arch/arm/dts/imx28-xea-1-u-boot.dtsi | 11
> arch/arm/dts/imx28-xea-1.dts | 8 +++
> arch/arm/dts/imx28-xea-2-u-boot.dtsi | 11
Il 22/03/2024 03:31, Matthias Klose ha scritto:
Control: reopen -1
Control: tags -1 + ftbfs patch
some library names in the symbols file were omitted.
patch attached.
http://launchpadlibrarian.net/720580389/muffin_6.0.1-1build1_6.0.1-1ubuntu1.diff.gz
thanks, I didn't notice that, I just
; Signed-off-by: Mathieu Othacehe
Thanks, this looks better:
Reviewed-by: Fabio Estevam
Hi Mathieu,
On Thu, Mar 21, 2024 at 3:57 AM Mathieu Othacehe wrote:
> Mathieu Othacehe (3):
> arm: dts: imx93-phyboard-segin: Add USB support
> configs: imx93-phyboard-segin: Add USB support
> configs: imx93-phyboard-segin: Add fastboot support
>
> arch/arm/dts/imx93-phyboard-segin.dts
packaging guidelines for this case:
https://docs.fedoraproject.org/en-US/packaging-guidelines/Rust/#_rust_crates
You should get a working spec file by just running "rust2rpm -s rublk".
Fabio
--
___
devel mailing list -- devel@lists.fedoraprojec
DX identifiers is only
the "easy" part of the transition.
Re-reviewing package contents and re-classifying licenses is the
non-trivial part, and that definitely can't be scripted.
Fabio
--
___
devel mailing list -- devel@lists.fedoraproject.org
To
in Fedora 41
anyway?
Or is this just about OpenSSL maintainers not wanting to have to keep
maintaining Engine support in Fedora while it will be phased out in
RHEL sooner?
Fabio
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an
Maybe it's better to file an issue or send a MR upstream:
https://gitlab.freedesktop.org/mesa/mesa/-/issues
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests
It looks like m68k was considered in the past:
https://cgit.freedesktop.org/mesa/mesa/log/?qt=grep=m68k
Maybe it's better to file an issue or send a MR upstream:
https://gitlab.freedesktop.org/mesa/mesa/-/issues
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests
It looks like m68k was considered in the past:
https://cgit.freedesktop.org/mesa/mesa/log/?qt=grep=m68k
ic section sizes: No such file or directory
>
> I have no idea what is up here.
>
Isn't this what this change was about?
https://fedoraproject.org/wiki/Changes/Linker_Error_On_Security_Issues
Fabio
> Seems to have started with:
>
> gcc 14.0.1-0.7.fc41
> glibc 2.39.9000
e; urgency=medium
.
* Return to Debian Python Team and add myself to uploaders (Closes:
#1065808)
* Remove libgtk-3-0 from depends (Closes: #1067171)
Regards,
--
Fabio Fantoni
e; urgency=medium
.
* Return to Debian Python Team and add myself to uploaders (Closes:
#1065808)
* Remove libgtk-3-0 from depends (Closes: #1067171)
Regards,
--
Fabio Fantoni
Control: tag -1 pending
Hello,
Bug #1067171 in bleachbit reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Hi, I'd like to request the backports of xtables-addons as follow.
bullseye-backports: backport 3.23-1 from bookworm.
Note that linux 6.1 is already available in bullseye-backports and
it's not compatible with the default bullseye xtables-addons (3.13-1).
Backporting xtables-addons 3.23-1 from
indeed
El lunes, 18 de marzo de 2024 a la(s) 9:53:11 p.m. UTC-5, ji-podhead
escribió:
> theres no channel on discord. gitter and git-discussion are dead.
> i dont have any slack invites.
> k8s groups have no grpc sub.
> maybe we should start a server on our own?
> love from germany:
> ji
>
--
INDEED!
Sent from Mailspring
(https://link.getmailspring.com/link/9bb5a3ec-703b-421a-b623-f557c0992...@getmailspring.com/0?redirect=https%3A%2F%2Fgetmailspring.com%2F=Z3JwYy1pb0Bnb29nbGVncm91cHMuY29t),
the best free email app for work
On Mar 15 2024, at 1:22 pm, ji-podhead wrote:
> theres no
1088A, LS2080A, LX2162A and LX2160A
I saw the original boot problem with the i.MX8QX.
The i.MX8QX is part of the i.MX family, not the Layerscape family.
> I suppose Fabio and Stefano can answer this and/or help with ensuring that
> setup_pgtables() is never called on live PTs.
Let me know if you need any clarification.
Thanks,
Fabio Estevam
Il giorno mar 19 mar 2024 alle ore 11:48 Diego Giorio
ha scritto:
>
> Questa è decisamente carina.
>
> E non ditemi che sono out of topic, perché riguarda l'affidabilità dei
> sistemi di traduzione automatica.
>
> Il paese in questione è naturalmente la cittadina di BRA, opportunamente
>
Hi Tom and Sean,
On Fri, Mar 8, 2024 at 5:13 PM Fabio Estevam wrote:
>
> Since commit cc7df0b9e8bc ("serial: lpuart: Enable IPG clock")
> the colibri-imx8qxp board no longer boots.
>
> The reason is that the imx8qxp clock driver does not handle the
> LPUART IPG clocks
the
> issue?
Your patch fixed the boot regression. Thanks for your fix, appreciated it!
I have replied with my Tested-by tag.
Cheers,
Fabio Estevam
ensures that it actually was a block mapping (calls panic() otherwise)
> before splitting it.
>
> Fixes: 41e2787f5ec4 ("arm64: Reduce add_map() complexity")
> Signed-off-by: Pierre-Clément Tosi
This fixes the boot regression on colibri-imx8x.
Thanks a lot for your fix!
Tested-by: Fabio Estevam
On Mon, Mar 18, 2024 at 5:22 PM Dan Horák wrote:
>
> On Mon, 18 Mar 2024 17:07:08 +0100
> Fabio Valentini wrote:
> > I wonder why these packages rely in pkg-config and don't just install
> > to `%{bash_completions_dir}`?
>
> because it hasn't always exist? Or it's m
lly it installs completion file
> into the wrong
> directory).
I wonder why these packages rely in pkg-config and don't just install
to `%{bash_completions_dir}`?
This macro is defined in the default buildroot, regardless of
BuildRequires, and always expands to the correct location for
installing bash
On Mon, Mar 18, 2024 at 10:31 AM Fabio Estevam wrote:
> I tried dumping the page table entries, but could not notice anything
> that looked suspicious.
This looks suspicious:
With 41e2787f5ec4 reverted:
Checking if pte fits for virt=1c00 size=6400 blocksize=4000
Checking
Hi Pierre,
On Fri, Mar 15, 2024 at 12:13 PM Pierre-Clément Tosi wrote:
> I had a quick look through your logs and notice that U-Boot master attempts to
> map addresses in the high VA range e.g.
>
> Checking if pte fits for virt=e400 [...]
>
> while the logs that boot successfully
in needs to happen on
src.fedoraproject.org, not with any other Fedora service.
For me, sometimes opening "src.fedoraproject.org" in an incognito
browser window and logging in there has helped.
Fabio
--
___
devel mailing list -- devel@lis
Version: 8.0-1
mga driver was removed from mesa since 8.0 in 2012:
https://docs.mesa3d.org/relnotes/8.0.html
Version: 8.0-1
mga driver was removed from mesa since 8.0 in 2012:
https://docs.mesa3d.org/relnotes/8.0.html
Version: 8.0-1
It looks like this was addressed in mesa years ago with this commit:
https://cgit.freedesktop.org/mesa/mesa/commit/?id=4833104718677caad0027d5e7539ca9bba389392
Version: 8.0-1
It looks like this was addressed in mesa years ago with this commit:
https://cgit.freedesktop.org/mesa/mesa/commit/?id=4833104718677caad0027d5e7539ca9bba389392
It looks like the src/gallium/auxiliary/gallivm/lp_bld_misc.cpp file
in mesa was heavily updated for managing newer llvm versions, even if
mesa is still using getHostCPUName and still not getCPUTargetFeatures.
Michael, do you think there is still something to do in mesa?
Steve and Bernhard, are
It looks like the src/gallium/auxiliary/gallivm/lp_bld_misc.cpp file
in mesa was heavily updated for managing newer llvm versions, even if
mesa is still using getHostCPUName and still not getCPUTargetFeatures.
Michael, do you think there is still something to do in mesa?
Steve and Bernhard, are
On Fri, Mar 15, 2024 at 11:45 AM Vitor Soares wrote:
>
> From: Vitor Soares
>
> On imx8m[m|p|q].dtsi, upstream Linux uses different names for NPU/VPU
> IP block nodes. It leads variants without such HW block having it
> enabled by default.
>
> This patch adds the upstream Linux node's paths to
On Tue, Mar 12, 2024 at 9:59 PM Fabio Estevam wrote:
>
> Commit bfb3409d676f ("imx: toradex/apalis-imx8: correct SCU API usage")
> made an incorrect logic change in the error code check of
> sc_misc_otp_fuse_read():
>
> - if (scierr == SC_ERR_
On Tue, Mar 12, 2024 at 9:36 PM Fabio Estevam wrote:
>
> Commit aa6e698a7acd ("imx: toradex/colibri-imx8x: correct SCU API usage")
> made an incorrect logic change in the error code check of
> sc_misc_otp_fuse_read():
>
> - if (sc_err == SC_ERR_
On Tue, Mar 12, 2024 at 10:16 PM Fabio Estevam wrote:
>
> Hi Tim,
>
> On Tue, Mar 12, 2024 at 4:05 PM Tim Harvey wrote:
> >
> > Move to imx8m{m,n,p}-venice to OF_UPSTREAM:
> > - replace the non-upstream generic imx8m{m,n,p}-venice dt with one of the
> >
On Tue, Mar 12, 2024 at 6:00 AM Leonard Anderweit wrote:
>
> This series adds RAUC boot logic for the phycore_imx8mp.
> The first patch converts the environment from a CFG_EXTRA_ENV_SETTINGS #define
> to a text environment for better readability and maintainability.
> The second patch moves the
On Tue, Mar 12, 2024 at 6:39 AM Benjamin Hahn wrote:
>
> define the phytec_get_som_type function also when the SoM detection is
> disabled.
>
> Fixes:
> commit 110d321a56c3 ("board: phytec: common: phytec_som_detection: Add
> phytec_get_som_type")
>
> Signed-off-by: Benjamin Hahn
Applied for
On Thu, Mar 7, 2024 at 12:23 PM Parth Pancholi wrote:
>
> From: Parth Pancholi
>
> Enable watchdog functionality for Toradex's Colibri iMX7 (NAND/EMMC)
> modules.
>
> Signed-off-by: Parth Pancholi
Applied for u-boot-imx/next, thanks.
On Mon, Mar 4, 2024 at 8:49 AM Benjamin Hahn wrote:
>
> The polling rate is already specified in some devicetrees, like
> imx8mp.dtsi for example, but was not selected so far. For the
> trippoints, the cpu-thermal node is used. Also get the polling rate from
> this node. Use the default of 5000ms
Hi Tom,
Please pull this material for next from u-boot-imx, thank
The following changes since commit 099c94b7613bb10d97936447f5136f3a36694325:
Merge tag 'u-boot-rockchip-20240315' of
https://source.denx.de/u-boot/custodians/u-boot-rockchip into next (2024-03-15
09:15:31 -0400)
are
.
Benjamin Hahn (1):
board: phytec: define get_som_type also when SoM detection is disabled
Fabio Estevam (2):
colibri-imx8x: Fix sc_misc_otp_fuse_read() error check
apalis-imx8: Fix sc_misc_otp_fuse_read() error check
Vitor Soares (1):
arm: imx: imx8m: soc: Fix NPU
There is a MR here, but needs to be updated:
https://salsa.debian.org/xorg-team/lib/mesa/-/merge_requests/26
There is a MR here, but needs to be updated:
https://salsa.debian.org/xorg-team/lib/mesa/-/merge_requests/26
https://bugs.kde.org/show_bug.cgi?id=483824
Bug ID: 483824
Summary: Timer does not play sound when finished
Classification: Applications
Product: KClock
Version: 24.02.0
Platform: Mint (Ubuntu based)
OS: Linux
Version: 22.2.0-1
"svga" gallium driver was added in 22.2.0-1.
Version: 22.2.0-1
"svga" gallium driver was added in 22.2.0-1.
This was fixed in mutter 43.8 and 44.4 as per mutter report
https://gitlab.gnome.org/GNOME/mutter/-/issues/2602
This was fixed in mutter 43.8 and 44.4 as per mutter report
https://gitlab.gnome.org/GNOME/mutter/-/issues/2602
Closing as per previous comment.
Closing as per previous comment.
Can you try again with 24.0.3-1 ?
Thanks.
Il giorno ven 1 mar 2024 alle ore 00:12 Alexis Murzeau
ha scritto:
>
> Package: mesa-va-drivers
> Version: 24.0.1-1
> Severity: important
>
> * What led up to the situation?
> Upgrading mesa-va-drivers to version 24.0.1-1 cause GPU process craches
>
Can you try again with 24.0.3-1 ?
Thanks.
Il giorno ven 1 mar 2024 alle ore 00:12 Alexis Murzeau
ha scritto:
>
> Package: mesa-va-drivers
> Version: 24.0.1-1
> Severity: important
>
> * What led up to the situation?
> Upgrading mesa-va-drivers to version 24.0.1-1 cause GPU process craches
>
Current Debian stable (12, bookworm) has the fix.
Current Debian stable (12, bookworm) has the fix.
Version: 21.0.3-1
Fixed since 21.0.3-1, as per upstream bug report.
Version: 21.0.3-1
Fixed since 21.0.3-1, as per upstream bug report.
altermetax [1] filed a request to merge eclipse-cpp-bin [2] into
eclipse-cpp [3]:
- The eclipse-cpp-bin package seems unmaintained
- Both eclipse-cpp and eclipse-cpp-bin create the package from pre-
built artifacts, however as per the AUR submission guidelines Java
software shouldn't have the
paulgureghian [1] filed a deletion request for libpamac-aur [2]:
Are you going to update this soon?
[1] https://aur.archlinux.org/account/paulgureghian/
[2] https://aur.archlinux.org/pkgbase/libpamac-aur/
Deletion requests are not made for prompting updates
You already commented today with:
Hi Hiago,
On Fri, Mar 15, 2024 at 11:39 AM Hiago De Franco wrote:
>
> From: Hiago De Franco
>
> Update and improve the building documentation of Colibri iMX8X.
> The following changes were made:
> - imx-atf repository changed to nxp-imx GitHub.
> - imx-atf branch updated to 'lf_v2.6'.
> -
301 - 400 of 90918 matches
Mail list logo
