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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20240329232528.79332-1-shimmyshai00@gmail.com>
Date: Fri, 29 Mar 2024 18:25:28 -0500
From: Shimrra Shai <shimmyshai00@...il.com>
To: jonathan.cameron@...wei.com
Cc: heiko@...ech.de,
	linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org,
	linux-rockchip@...ts.infradead.org,
	max.schwarz@...ine.de,
	niyas.sait@...wei.com,
	shimmyshai00@...il.com
Subject: Re: Re: [PATCH 0/0] (proposed?) Add ACPI binding to Rockchip RK3xxx I2C bus

Hey Jonathan,

I just heard back from the firmware team. Apparently, there is rationale
behind including the clock bindings as part of the _DSD_ - it is because
apparently MS Windows can also run on this platform and it expects those
bindings to be there to configure the clocks on this platform. If they are
changed, it will break that capability, rendering it kind of moot to use
the ACPI boot which is intended to be universal across OSes. (I also wonder
if NetBSD uses the same bindings as well; that OS can boot via ACPI boot
without much issue on this platform.)

Shimrra


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ