public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Marcin Wojtas" <mw@semihalf.com>
To: edk2-devel-groups-io <devel@edk2.groups.io>
Cc: Leif Lindholm <leif@nuviainc.com>,
	Ard Biesheuvel <ard.biesheuvel@arm.com>,
	 Greg V <greg@unrelenting.technology>
Subject: Additional configuration options on Armada/Cn913x
Date: Fri, 5 Jun 2020 17:19:53 +0200	[thread overview]
Message-ID: <CAPv3WKfnhQE3v4TAkQXh+PcUpxAgAuq7SsDfejVQjP1PZSmD9w@mail.gmail.com> (raw)

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

Hi,

I'd like to ask for comments before I develop the actual code - currently
we have 2 workarounds done specifically for Linux:
a. ECAM shift in PCIE
b. SPCR address space definition

Both above are not needed e.g. in FreeBSD and I was requested to add their
optional disabling. The idea is to add dedicated variables that would
optionally allow to disable the quirks, accessible via BootManager.
Questions:

- Would above be acceptable or is there a better way to handle such cases?
- In case it's fine, is there a dedicated place in the BootManager menu to
add custom switches?
- Are you aware of good examples for adding custom options?

Best regards,
Marcin

[-- Attachment #2: Type: text/html, Size: 841 bytes --]

             reply	other threads:[~2020-06-05 15:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-05 15:19 Marcin Wojtas [this message]
2020-06-11 13:19 ` [edk2-devel] Additional configuration options on Armada/Cn913x Ard Biesheuvel
2020-06-11 14:07 ` greg
2020-06-11 14:17   ` Ard Biesheuvel
2020-06-11 22:43     ` Mark Kettenis
2020-06-12  8:45       ` Ard Biesheuvel
2020-06-12 15:07         ` Marcin Wojtas
2020-06-12 16:32           ` greg
2020-06-12 17:09             ` Marcin Wojtas
2020-06-20 15:44               ` Marcin Wojtas
2020-06-11 14:33   ` greg
2020-06-11 14:38     ` Ard Biesheuvel
2020-06-11 14:46     ` greg

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=CAPv3WKfnhQE3v4TAkQXh+PcUpxAgAuq7SsDfejVQjP1PZSmD9w@mail.gmail.com \
    --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