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: <m2qzs6l8ms.fsf@free.fr>
Date: Sat, 03 Jan 2026 21:54:35 +0100
From: Robert Jarzmik <robert.jarzmik@...e.fr>
To: "Arnd Bergmann" <arnd@...db.de>
Cc: "Rob Herring" <robh@...nel.org>,  "Geert Uytterhoeven"
 <geert+renesas@...der.be>,  "Magnus Damm" <magnus.damm@...il.com>,
  "Krzysztof Kozlowski" <krzk+dt@...nel.org>,  "Conor Dooley"
 <conor+dt@...nel.org>,  "Daniel Mack" <daniel@...que.org>,  "Haojian
 Zhuang" <haojian.zhuang@...il.com>,  "Andrew Lunn" <andrew@...n.ch>,
  "Gregory Clement" <gregory.clement@...tlin.com>,  "Sebastian Hesselbarth"
 <sebastian.hesselbarth@...il.com>,  Linux-Renesas
 <linux-renesas-soc@...r.kernel.org>,  devicetree@...r.kernel.org,
  linux-kernel@...r.kernel.org,  linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] ARM: dts: intel: Drop pxa2xx

"Arnd Bergmann" <arnd@...db.de> writes:

> If you or anyone else is still using PXA27x, we can always
> bring it back later, but I'd then put the burden on them to
> submit the dts file for inclusion without introducing DT
> warnings.
Well not anymore, for RAM constraints as I said.
I can still fallback to an older kernel though if I feel like 
hacking.

>> +	docg3: flash@0 {
>> +		compatible = "m-systems,diskonchip-g3";
>> +		reg = <0x0 0x2000>;
>> +	};
>
> This currently has no upstream users I can see, so
> removing pxa27x would probably mean we should remove
> that as well.
Yep, this driver was only used on the Mitac MIO A701 (my main 
board,
pxa27x based).

>> +	panel {
>> +		compatible = "toshiba,ltm0305a776";
>> +		lcd-type = "color-tft";
>
> I don't see a driver that matches the compatible string,
> does this one actually work?
Yes it does. The compatible string doesn't really matter. What is
relevant in that part is the "timings" node, which is used by 
pxafb
driver to setup its registers to control the LCD panel.

More generally, each and every part of this DT was working 3 years 
ago.

Cheers.

--
Robert

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ