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]
Message-ID: <1420eb9f-c5d9-c9c3-b71f-37f4f3475c67@gmail.com>
Date:   Tue, 30 Nov 2021 22:49:18 +0300
From:   Dmitry Osipenko <digetx@...il.com>
To:     Rob Herring <robh@...nel.org>
Cc:     Thierry Reding <thierry.reding@...il.com>,
        Sam Ravnborg <sam@...nborg.org>,
        David Airlie <airlied@...ux.ie>,
        Daniel Vetter <daniel@...ll.ch>,
        Anton Bambura <jenneron@...tonmail.com>,
        dri-devel@...ts.freedesktop.org, devicetree@...r.kernel.org,
        linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 1/2] dt-bindings: sharp,lq101r1sx01: Add compatible for
 LQ101R1SX03

30.11.2021 18:54, Dmitry Osipenko пишет:
> 30.11.2021 00:32, Rob Herring пишет:
>> On Sun, Nov 14, 2021 at 11:07:16PM +0300, Dmitry Osipenko wrote:
>>> From: Anton Bambura <jenneron@...tonmail.com>
>>>
>>> LQ101R1SX03 is compatible with LQ101R1SX01, document it.
>>
>> Then sounds like '"sharp,lq101r1sx03", "sharp,lq101r1sx01"' would be the 
>> appropriate compatible value. Do that, and you don't need a driver 
>> change.
> 
> Apparently you're right. The "sharp,lq101r1sx03" should be a slightly
> improved revision of "sharp,lq101r1sx01". I see now that LQ101R1SX03 is
> sold as a spare part panel for ASUS TF701T, hence these panels should be
> entirely compatible with each other.
> 

I mixed up the panel model which TF701T uses.

I compared datasheets of both panel variants. These panel have
differences in the pins configuration. Hence panels seems aren't
compatible in terms of hardware integration, although the difference is
small. They should be compatible from software perspective.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ