From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Michael Zimmermann <sigmaepsilon92@gmail.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>,
Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: System hang when using SetMemoryAttributes
Date: Mon, 26 Sep 2016 03:23:52 -0700 [thread overview]
Message-ID: <CAKv+Gu9L1BEidOW29xBRYnXUQ5-tFnUnovUWwVB-y2wTan-Ntw@mail.gmail.com> (raw)
In-Reply-To: <CAN9vWDKzdjRPWYV=_MbRS82mchOyG-2ip7fHdCZe--boNN-p8w@mail.gmail.com>
On 26 September 2016 at 00:44, Michael Zimmermann
<sigmaepsilon92@gmail.com> wrote:
> oh and in case it makes a difference: it's a 64bit ARM device running 32bit
> code.
>
That shouldn't matter.
> On Mon, Sep 26, 2016 at 9:13 AM, Michael Zimmermann
> <sigmaepsilon92@gmail.com> wrote:
>>
>> Ard,
>>
>> I have to mark the framebuffer as uncached, because if writes to it are
>> cached, they don't instantly reach the underlying hardware. I'd have to
>> manually flush the cache for that region every time otherwise.
>>
>> Isn't that the normal way? I don't think that any device would work with a
>> write-cache framebuffer - I actually copied the code from the ArmVirt LCD
>> drivers which do the same.
>>
_WC means write-combining, and so these accesses are not cacheable,
but they do allow unaligned accesses, unlike _UC
next prev parent reply other threads:[~2016-09-26 10:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-25 19:01 System hang when using SetMemoryAttributes Michael Zimmermann
2016-09-26 6:35 ` Ard Biesheuvel
2016-09-26 7:13 ` Michael Zimmermann
2016-09-26 7:44 ` Michael Zimmermann
2016-09-26 10:23 ` Ard Biesheuvel [this message]
2016-09-26 12:44 ` Michael Zimmermann
2016-09-26 12:47 ` Ard Biesheuvel
2016-09-26 12:52 ` Michael Zimmermann
2016-09-26 17:00 ` Ard Biesheuvel
2016-09-26 20:25 ` Michael Zimmermann
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=CAKv+Gu9L1BEidOW29xBRYnXUQ5-tFnUnovUWwVB-y2wTan-Ntw@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