From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 6C1F31A1E06 for ; Mon, 26 Sep 2016 05:52:22 -0700 (PDT) Received: by mail-wm0-x22c.google.com with SMTP id b130so147623329wmc.0 for ; Mon, 26 Sep 2016 05:52:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/2KzKyEwyQoElcmK5vwMHbKKRwIQojrOuotTeP08wRw=; b=nseHN3+9Ap5dzm3Zy2N2wBdGu0ggOCEFJyNyvQO2HNmIkBB7SC6uj0K7YgdDUYISaF jejNO2Zc+R6YO0dRGsmeu0TabxZ4fr06otv8mhJMlSmzuVX57URLtSbqbKnXUFoyPbPC qTLeee7Ha8CJCwd1tOJTaB7UCtWIjatI3Xw0SfC7dwofrPc3RjGYn8KKc+VSlfmVvc1N Yhu7UAW4JK/b9RfLVLRhmfYufy2LgZxDCVZxkM0ZLYiUfhlxpWW+GaKJXjYQRU5moXxX NaGm+iw0j8oV0cO7BZx6PfRvekaRnAnGc8hra954lwNGUJ9HNCmxFVYSJJRYvUG75yoV hDDA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=/2KzKyEwyQoElcmK5vwMHbKKRwIQojrOuotTeP08wRw=; b=h88J2R0P9HJSQjB/k2lavF4Kl2dbS67MbdLyGnW5MCl0uNkXDVr7Xw7Br61ligIh9F r7SUtFp6mNLLhSJtuLCKlyPEWTlukSvt21h0zk8NxcO0hvmiNg7D/P02uF5GAAM8i7wM WQnyoaA4y937qLmeeMHGF7b/326njac8tYsvq32bQRs2YYTP2y0N7LMI9QkYC62ixEkm YfYrCm0+qsX6C9TsNIpyPeZGDFwDlhcpVME1lxRj/wMpmPbrrPZUguhUKCnpXG6CvYrm L/qcgDwss9pSywFZ2yZ2zXA/MZK7WXLSIBq/7XS+enJbD81PP+IQ8LI0KGtemL2xSEOr 3OMQ== X-Gm-Message-State: AA6/9Rl2/R/4HG3zsVPzG5GMg1ky6r3JZkHOBm+SRC7/Z1f4+JnQ6iINltf45Jm7Y2ApqYX2jQFbot9R8slUvw== X-Received: by 10.194.84.67 with SMTP id w3mr17428118wjy.148.1474894340983; Mon, 26 Sep 2016 05:52:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.36.212 with HTTP; Mon, 26 Sep 2016 05:52:20 -0700 (PDT) In-Reply-To: References: From: Michael Zimmermann Date: Mon, 26 Sep 2016 14:52:20 +0200 Message-ID: To: Ard Biesheuvel Cc: "edk2-devel@lists.01.org" , Leif Lindholm X-Content-Filtered-By: Mailman/MimeDel 2.1.21 Subject: Re: System hang when using SetMemoryAttributes X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Sep 2016 12:52:22 -0000 Content-Type: text/plain; charset=UTF-8 > Are you saying your framebuffer does work with cached attributes? That > would mean the graphics device is DMA coherent, which is actually a > good thing. What hardware are we talking about here? yes it does but ofc, it causes glitches since the writes aren't always synced correctly. My edk2 port is cross platorm by using PrePi and a function table provided by another bootloader for hardware communication. The device that's broken is 'Asus Zenfone 2 Laser ZE550KL' which uses a 'Qualcomm MSM8939 Snapdragon 615' chipset. On Mon, Sep 26, 2016 at 2:47 PM, Ard Biesheuvel wrote: > On 26 September 2016 at 05:44, Michael Zimmermann > wrote: > > I'm thankful for the hint about _WC because it drastically improves the > > speed on my other devices. > > Glad I could be of help. > > > Unfortunately, it doesn't fix the device I have problems with. I tested > all > > possible attributes and only EFI_MEMORY_WB seems to be working(even > > EFI_MEMORY_WT is broken). > > > > The weird thing is that even if I disable accesses to the framebuffer by > > disabling all code in the Blt function, it hangs during boot. > > I really can't explain this behavior. > > > > Are you saying your framebuffer does work with cached attributes? That > would mean the graphics device is DMA coherent, which is actually a > good thing. What hardware are we talking about here? >