public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>, Jon Masters <jcm@redhat.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	Marc Zyngier <marc.zyngier@arm.com>,
	Drew Jones <drjones@redhat.com>
Subject: Re: [PATCH] ArmVirtPkg/PlatformHasAcpiDtDxe: allow manual override for DT installation
Date: Wed, 29 Mar 2017 18:55:26 +0200	[thread overview]
Message-ID: <52dc0685-ae37-63db-d7b5-feb49490a12d@redhat.com> (raw)
In-Reply-To: <CAKv+Gu-7ozsJmdW91G7Va4JxFzLkrwhyPkFTBvo6Tqd+r77P8g@mail.gmail.com>

On 03/29/17 18:17, Ard Biesheuvel wrote:
> On 29 March 2017 at 17:09, Jon Masters <jcm@redhat.com> wrote:
>> Thanks Laszlo. A quick note from me that regardless of this discussion I will be pushing to ensure the version Red Hat ships makes ACPI the default with it being extremely painful to use DT. It is time the ecosystem got with the program we all agreed upon and there will be no more excuses.
>>
> 
> This has *nothing* to do with the ecosystem. This has to do with
> existing users of ArmVirtQemu (admittedly, a small fraction) that will
> be forced to compile their UEFI images from source because we made a
> backwards incompatible change.
> 
> I am 100% on board with making ACPI and DT mutually exclusive. But I
> don't believe for a second that 'everybody just exposes ACPI and DT at
> the same time' if this gets merged.

That's where we disagree, 100%.

> That happens because people are
> clueless, not because they are deliberately spending time and effort
> on producing two hardware descriptions.

If this were true, then the kernel's preference would have been changed
to ACPI aeons ago (assuming both DT and ACPI were present). ACPI is
superior to DT (cue again Grant Likely's blog post), yet kernel people
resist it. That's not cluelessness. If the kernel's DT camp has any
influence on platform vendors (and that's rather more a "given that"
than an "if"), when they find out about this loophole, I expect them to
actively recommend it as a way to perpetuate the status quo.

IMO, with this patch you are eviscerating the work we've been doing in
the last few weeks. Well, politics is nasty.

Laszlo


  reply	other threads:[~2017-03-29 16:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 15:19 [PATCH] ArmVirtPkg/PlatformHasAcpiDtDxe: allow manual override for DT installation Ard Biesheuvel
2017-03-29 16:00 ` Laszlo Ersek
2017-03-29 16:02   ` Ard Biesheuvel
2017-03-29 16:03     ` Laszlo Ersek
2017-03-29 16:07       ` Ard Biesheuvel
2017-03-29 16:40         ` Laszlo Ersek
     [not found]           ` <2fb8acda-2786-e3de-e035-32d13e3f5868@arm.com>
2017-03-29 17:07             ` Ard Biesheuvel
2017-03-29 17:23               ` Laszlo Ersek
2017-03-29 17:30                 ` Ard Biesheuvel
2017-03-29 17:50                   ` Laszlo Ersek
2017-03-29 17:15             ` Laszlo Ersek
     [not found]               ` <010325b6-1c23-5da7-9df5-337619c519bb@arm.com>
2017-03-29 18:04                 ` Laszlo Ersek
2017-03-29 17:16           ` Ard Biesheuvel
     [not found]       ` <e78f315f-1e84-cc6c-ab41-fe98b842af21@arm.com>
2017-03-29 17:03         ` Laszlo Ersek
     [not found]   ` <7F72156F-3814-4CF1-8847-A7272409A85E@redhat.com>
2017-03-29 16:17     ` Ard Biesheuvel
2017-03-29 16:55       ` Laszlo Ersek [this message]
2017-03-29 17:44         ` Mark Rutland
2017-03-29 17:58           ` Laszlo Ersek

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=52dc0685-ae37-63db-d7b5-feb49490a12d@redhat.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