linux-kernel - RE: fsl-dcu not works on latest "drm-next"

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]

Date:	Mon, 06 Jun 2016 19:46:38 -0700
From:	Stefan Agner <stefan@...er.ch>
To:	Meng Yi <meng.yi@....com>
Cc:	Alexander Stein <alexander.stein@...tec-electronic.com>,
	linux-kernel@...r.kernel.org, Mark Brown <broonie@...nel.org>,
	dri-devel@...ts.freedesktop.org, David Airlie <airlied@...ux.ie>,
	airlied@...hat.com
Subject: RE: fsl-dcu not works on latest "drm-next"

On 2016-06-06 19:16, Meng Yi wrote:
> Hi Stefan,
> 
> Sorry for reply late, I was on PTO. And another PTO on  June 9~11, 2016.UTC+8
> 
>> >> static const struct regmap_config fsl_dcu_regmap_config = {
>> >>     .reg_bits = 32,
>> >>     .reg_stride = 4,
>> >>     .val_bits = 32,
>> >>     .cache_type = REGCACHE_RBTREE,
>> >
>> > This needs to be a flat cache. See
>> > https://lists.freedesktop.org/archives/dri-devel/2016-January/099121.h
>> > tml or https://lkml.org/lkml/2016/3/24/281
>> > max_register also needs an appropriate value.
>>
>> Ok, since the complete set which switches to the atomic helper is not stable
>> material (and also won't make it into 4.7 anymore), I created a seperate bugfix
>> now:
>> https://lists.freedesktop.org/archives/dri-devel/2016-June/109625.html
>>
> 
> What is bug?
> 

The bug is that we should not use REGCACHE_RBTREE for MMIO registers...

--
Stefan