On Sun, Sep 27, 2020, at 18:27, Ben Hutchings wrote:
> On Sun, 2020-09-27 at 13:43 -0300, Henrique de Moraes Holschuh wrote:
> > Answering from my phone, please excuse brevity and other netiquete
> > issues such as poor quoting cleanup.
This is still true :(
> However, we normally take all change
On Sun, 2020-09-27 at 13:43 -0300, Henrique de Moraes Holschuh wrote:
> Answering from my phone, please excuse brevity and other netiquete
> issues such as poor quoting cleanup.
>
> On Fri, Sep 25, 2020, at 09:14, maximilian attems wrote:
> > Dear Henrique,
> >
> > It be great to get your input,
Answering from my phone, please excuse brevity and other netiquete issues such
as poor quoting cleanup.
On Fri, Sep 25, 2020, at 09:14, maximilian attems wrote:
> Dear Henrique,
>
> It be great to get your input, hence repinging (;
>
> Especially as linux-firmware is the common upstream source,
Dear Henrique,
It be great to get your input, hence repinging (;
Especially as linux-firmware is the common upstream source, it be ideal to ship
the amd64 mircrocode out of our firmware packages.
Thanks for letting us know.
kind regards,
maximilian
On Sun, Sep 20, 2020 at 10:36:12AM +0200, max
Dear Henrique, dear debian kernel maintainers, Cc: Michael,
Would you agree to generate the amd64-firmware packages directly out of the
debian
linux-firmware source package?
This way the microcode would be updated on every linux-firmware non-free upload?
I am asking as it keeps nugging me to hav
Source: firmware-nonfree
Severity: important
Dear maintainer,
first of all thanks for maintaining and packaging the linux-firmware files
repository as debian packages.
We currently need to manually obtain the
linux-firmware.git:amd/amd_sev_fam17h_model3xh.sbin [1] file on
our AMD EPYC servers.
6 matches
Mail list logo