linux-kernel - Re: [PATCH v6 1/3] drm/lsdc: add drm driver for loongson display controller

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: <3133a629-eebf-928e-d6b0-72867d96d2b5@flygoat.com>
Date:   Wed, 9 Feb 2022 14:14:18 +0000
From:   Jiaxun Yang <jiaxun.yang@...goat.com>
To:     Maxime Ripard <maxime@...no.tech>
Cc:     Sui Jingfeng <15330273260@....cn>,
        Dan Carpenter <dan.carpenter@...cle.com>,
        Lucas Stach <l.stach@...gutronix.de>,
        Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
        Roland Scheidegger <sroland@...are.com>,
        Zack Rusin <zackr@...are.com>,
        Christian Gmeiner <christian.gmeiner@...il.com>,
        David Airlie <airlied@...ux.ie>,
        Daniel Vetter <daniel@...ll.ch>,
        Rob Herring <robh+dt@...nel.org>,
        Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
        Krzysztof Kozlowski <krzk@...nel.org>,
        Andrey Zhizhikin <andrey.zhizhikin@...ca-geosystems.com>,
        Sam Ravnborg <sam@...nborg.org>,
        suijingfeng <suijingfeng@...ngson.cn>,
        linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org,
        dri-devel@...ts.freedesktop.org,
        Randy Dunlap <rdunlap@...radead.org>
Subject: Re: [PATCH v6 1/3] drm/lsdc: add drm driver for loongson display
 controller



在 2022/2/9 14:04, Maxime Ripard 写道:
> On Wed, Feb 09, 2022 at 11:56:48AM +0000, Jiaxun Yang wrote:
>>
>> 在 2022/2/9 8:52, Maxime Ripard 写道:
>>> On Thu, Feb 03, 2022 at 11:47:16PM +0800, Sui Jingfeng wrote:
>> [...]
>>> DT isn't really a solution either. Let's take the distribution
>>> perspective there. Suppose you're a Fedora or Debian developer, and want
>>> to make a single kernel image, and ship a DT to the user for their board
>>> without any modification. How is either the Kconfig solution or DT flags
>>> solution any good there? It doesn't help them at all.
>> We are working in another way. As we can tell model of the board by strings
>> passed from the firmware, we just built-in all poosible DTs into the kernel
>> and then tell which DT to load at boot time. So we can ensure users has
>> smmoth experience.
> It's not really for you to say though. Once your driver is in a release,
> distros are going to use it. That's the whole point of you asking us to
> merge it.

Ah I was meant to say we can determine which type of memory is best for a
type of board and then hardcode it into ST accroading to the model.

Though personally I want a knob in cmdline to override it at runtime.

Thanks.
- Jiaxun

>
> Maxime