From: "Dmitry Ponamorev" <dponamorev@gmail.com>
To: "Marcello Sylvester Bauer" <marcello.bauer@9elements.com>,
devel@edk2.groups.io
Subject: Re: [edk2-devel] [PATCH v2 0/2] Add support for scanning Option ROMs
Date: Wed, 09 Oct 2024 02:11:04 -0700 [thread overview]
Message-ID: <10004.1728465064233625774@groups.io> (raw)
In-Reply-To: <CAB1kMnf31aEaw5tO6z5UFP2iRFf2jm58b85XrSP9ML0qef1aLg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 757 bytes --]
Hi.
Thank you for this solution. This is a very useful feature for me. Some devices work - they detect and load optional ROM firmware, but some do not.
The presence of optional ROM is confirmed, but 0xFFFF is read instead of signature AA55 and other rom header fields.
Apparently the base address of the optional firmware is incorrect?
How can I debug this problem?
Thanks,
Dmitry
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120612): https://edk2.groups.io/g/devel/message/120612
Mute This Topic: https://groups.io/mt/76863515/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 2847 bytes --]
next prev parent reply other threads:[~2024-10-09 9:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 12:26 [PATCH v2 0/2] Add support for scanning Option ROMs Marcello Sylvester Bauer
2020-09-15 12:26 ` [PATCH v2 1/2] MdeModulePkg: Fix OptionROM scanning Marcello Sylvester Bauer
2020-09-15 12:34 ` [edk2-devel] " Laszlo Ersek
2020-09-15 12:26 ` [PATCH v2 2/2] UefiPayloadPkg: Scan for Option ROMs Marcello Sylvester Bauer
2020-09-16 8:28 ` [edk2-devel] [PATCH v2 0/2] Add support for scanning " Ni, Ray
2020-09-21 13:25 ` Marcello Sylvester Bauer
2020-09-22 23:58 ` Michael D Kinney
2020-11-10 15:01 ` Marcello Sylvester Bauer
2024-10-09 9:11 ` Dmitry Ponamorev [this message]
[not found] ` <16353648FD0ACD96.16285@groups.io>
2020-09-17 1:41 ` Ni, Ray
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-list 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=10004.1728465064233625774@groups.io \
--to=devel@edk2.groups.io \
/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