iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Jörg Rödel" <joro@8bytes.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: David Coe <david.coe@live.co.uk>,
	Robert Richter <rrichter@amd.com>,
	Alexander Monakov <amonakov@ispras.ru>,
	iommu@lists.linux-foundation.org,
	Mario Limonciello <mario.limonciello@amd.com>,
	Dell.Client.Kernel@dell.com
Subject: Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).
Date: Wed, 15 Sep 2021 10:47:17 +0200	[thread overview]
Message-ID: <2DF5BF35-DF81-41B1-825D-E36AF83242DF@8bytes.org> (raw)
In-Reply-To: <bb53516e-6d48-cff8-d14e-32bc76754a26@molgen.mpg.de>

Possible, but still DELL is the first point of contact here. If they find out that the problem is actually in Agesa, then DELL can escalate this to AMD.

> Am 15.09.2021 um 10:42 schrieb Paul Menzel <pmenzel@molgen.mpg.de>:
> 
> Dear Jörg,
> 
> 
> Am 15.09.21 um 10:30 schrieb Jörg Rödel:
>> Mainly DELL should look at this, because it is their BIOS which is
>> responsible for this inconsistency.
> 
> I am not so sure about that, as today’s (x86) firmware often consists of platform initialization (PI) code (or firmware support package (FSP), provided by the chipset/SoC vendors, like AGESA for AMD, which the ODM just integrate.
> 
> If only Dell systems are affected, that would of course point to a bug in the Dell firmware.
> 
> 
> Kind regards,
> 
> Paul

_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2021-09-15  8:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 18:07 AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada) Paul Menzel
2021-09-14  9:10 ` Paul Menzel
2021-09-14 12:09   ` Jörg Rödel
2021-09-14 22:15     ` Paul Menzel
2021-09-14 22:17       ` Paul Menzel
2021-09-15  8:30         ` Jörg Rödel
2021-09-15  8:42           ` Paul Menzel
2021-09-15  8:47             ` Jörg Rödel [this message]
2021-09-15 14:39         ` Paul Menzel

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=2DF5BF35-DF81-41B1-825D-E36AF83242DF@8bytes.org \
    --to=joro@8bytes.org \
    --cc=Dell.Client.Kernel@dell.com \
    --cc=amonakov@ispras.ru \
    --cc=david.coe@live.co.uk \
    --cc=iommu@lists.linux-foundation.org \
    --cc=mario.limonciello@amd.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=rrichter@amd.com \
    /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;
as well as URLs for NNTP newsgroup(s).