From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] efifb: avoid reconfiguration of BAR that covers the framebuffer
Date: Thu, 30 Mar 2017 11:05:32 +0100 [thread overview]
Message-ID: <20170330100524.GA22801@red-moon> (raw)
In-Reply-To: <CAKv+Gu-qRg8-YRCairppKrEfeLcW+OwVF8qZHp7vxXJA_AwPOw@mail.gmail.com>
On Thu, Mar 30, 2017 at 09:46:39AM +0100, Ard Biesheuvel wrote:
[...]
> > I'm asking why we don't fix the actual problem in PCIe ARM64 adaptation instead
> > of working around it by quirks.
> >
> > I don't see any reason why ACPI ARM64 should carry the burden of legacy systems.
> >
> > Legacy only applies to DT based systems.
> >
>
> I fully agree with this point: ACPI implies firmware, and so we should
> be able to rely on firmware to have initialized the PCIe subsystem by
> the time the kernel gets to access it.
https://lkml.org/lkml/2016/3/3/458
Lorenzo
next prev parent reply other threads:[~2017-03-30 10:05 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 15:30 [PATCH v3] efifb: avoid reconfiguration of BAR that covers the framebuffer Ard Biesheuvel
2017-03-22 19:31 ` Lukas Wunner
2017-03-22 19:32 ` Ard Biesheuvel
2017-03-23 8:48 ` Lukas Wunner
2017-03-23 9:04 ` Ard Biesheuvel
2017-03-23 10:57 ` Lorenzo Pieralisi
2017-03-23 12:25 ` Ard Biesheuvel
2017-03-23 14:31 ` Lorenzo Pieralisi
2017-03-23 15:15 ` Ard Biesheuvel
2017-03-27 15:37 ` Ard Biesheuvel
2017-03-28 21:27 ` Sinan Kaya
2017-03-28 21:39 ` Ard Biesheuvel
2017-03-28 21:49 ` Sinan Kaya
2017-03-30 8:46 ` Ard Biesheuvel
2017-03-30 10:05 ` Lorenzo Pieralisi [this message]
2017-03-30 10:09 ` Ard Biesheuvel
2017-03-30 11:42 ` okaya at codeaurora.org
2017-03-30 13:38 ` Ard Biesheuvel
2017-03-30 13:50 ` Sinan Kaya
2017-04-02 15:16 ` Ard Biesheuvel
2017-04-10 15:28 ` Ard Biesheuvel
2017-04-10 16:53 ` Lorenzo Pieralisi
2017-04-10 17:06 ` Sinan Kaya
2017-04-10 17:13 ` Ard Biesheuvel
2017-04-10 17:29 ` Ard Biesheuvel
2017-04-11 13:16 ` Lorenzo Pieralisi
2017-04-11 16:06 ` Ard Biesheuvel
2017-04-23 1:45 ` Yinghai Lu
2017-04-27 13:55 ` Ard Biesheuvel
2017-04-28 20:51 ` Yinghai Lu
2017-03-22 19:36 ` Sinan Kaya
2017-03-22 19:41 ` Ard Biesheuvel
2017-03-22 19:49 ` Sinan Kaya
2017-03-22 19:52 ` Ard Biesheuvel
2017-03-22 19:57 ` Sinan Kaya
2017-03-22 20:00 ` Ard Biesheuvel
2017-05-03 3:09 ` Heyi Guo
2017-05-18 14:01 ` Bjorn Helgaas
2017-05-20 8:19 ` Heyi Guo
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=20170330100524.GA22801@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).