public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Rob Brewer <ipfire-devel@grantura.co.uk>
To: development@lists.ipfire.org
Subject: Re: Last call for Core Update 167 (was: Re: Core Updates 166 and 167)
Date: Mon, 11 Apr 2022 20:14:47 +0100	[thread overview]
Message-ID: <t31un7$3ju$1@tuscan3.grantura.co.uk> (raw)
In-Reply-To: <68cf898c-4861-6e7e-276c-9bb596861508@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 685 bytes --]

On Monday 11 April 2022 07:21 Bernhard Bitsch wrote:

> Hello,
> 
> Hope I'm not too late with this.
> Since a week I have running the latest APU firmware ( v4.16.02 ) on my
> system.
> Found no problems until now, but an enhancement. The AMD PSP CCP is now
> found as entropy source. So the boot process is faster.
> 
> This may be useful for many IPFire users. Is it possible to include in
> CU 167?
> 
> Regards,
> Bernhard

Poor entropy on my APU2 E4 has been a serious problem so much so that I will 
do anything not to re-boot IPFire. I wasn't aware that this was a firmware 
problem so this is really good news.

I hope the new firmware will soon be available via pakfire.

Rob

      parent reply	other threads:[~2022-04-11 19:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a19176a0-e95e-b58b-aa0e-35ce80ffa056@ipfire.org>
2022-04-02  7:42 ` Peter Müller
2022-04-02 11:00   ` Michael Tremer
2022-04-02 11:30     ` Peter Müller
2022-04-02 14:16       ` Michael Tremer
2022-04-04  9:21     ` Bernhard Bitsch
2022-04-02 14:54   ` Stefan Schantl
2022-04-11  6:21   ` Bernhard Bitsch
2022-04-11  7:49     ` Michael Tremer
2022-04-11 19:14     ` Rob Brewer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='t31un7$3ju$1@tuscan3.grantura.co.uk' \
    --to=ipfire-devel@grantura.co.uk \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox