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] [day] [month] [year] [list]
Date:   Wed, 21 Jul 2021 11:24:57 +0200
From:   Christian König <christian.koenig@....com>
To:     Christoph Hellwig <hch@...radead.org>
Cc:     Anson Jacob <Anson.Jacob@....com>, mpe@...erman.id.au,
        benh@...nel.crashing.org, paulus@...ba.org,
        christophe.leroy@...roup.eu, linuxppc-dev@...ts.ozlabs.org,
        amd-gfx@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
        Sunpeng.Li@....com, Harry.Wentland@....com, qingqing.zhuo@....com,
        Rodrigo.Siqueira@....com, roman.li@....com,
        Aurabindo.Pillai@....com, Bhawanpreet.Lakha@....com,
        bindu.r@....com
Subject: Re: [RFC v2 2/2] drm/amd/display: Use PPC FPU functions

Am 21.07.21 um 08:51 schrieb Christoph Hellwig:
> On Wed, Jul 21, 2021 at 08:29:43AM +0200, Christian K??nig wrote:
>> Looks good in general, but question is what about other architectures like
>> ARM?
> DRM_AMD_DC_DCN currently requires X86 || PPC64.

And exactly that's the problem I'm noting here. At least officially AMD 
claims that we support ARM and some very brave still use the hardware 
together with MIPS as well.

> Maybe a good think would be to add a new KERNEL_FPU_API Kconfig symbol,
> selected by x86 and powerpc (I think ppc32 should be fine too now) so
> that we get these arch dependencies out of the driver.

Good idea.

Christian.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ