linux-kernel - Re: [PATCH 2/2] ARC: [axs10x] Specify reserved memory for frame buffer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <57221693.50401@synopsys.com>
Date:	Thu, 28 Apr 2016 19:26:35 +0530
From:	Vineet Gupta <vgupta@...opsys.com>
To:	Alexey Brodkin 
	<Alexey.Brodkin-HKixBCOQz3hWk0Htik3J/w@...lic.gmane.org>
Cc:	"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
	lkml <linux-kernel@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	arcml <linux-snps-arc@...ts.infradead.org>
Subject: Re: [PATCH 2/2] ARC: [axs10x] Specify reserved memory for frame
 buffer

On Thursday 28 April 2016 07:16 PM, Alexey Brodkin wrote:
>> > Note that the IOC start alignment needs to follow
>> > max(4k, size). What will be maximum size of frame buffer - 16M always !
> What do you mean by that?

For HS38, we intend to bypass the frame buffer traffic from IOC port. So the frame
buffer start needs to be inside the IOC aperture base address. That value can't be
arbitrary - it is atleast 4K aligned value and further also needs to be aligned to
the size of aperture. So if the size is 16M it needs to be 16M aligned etc...

-Vineet