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: <Z8AcFq9bDuW0oiD5@nchen-desktop>
Date: Thu, 27 Feb 2025 16:02:30 +0800
From: Peter Chen <peter.chen@...tech.com>
To: Jianfeng Liu <liujianfeng1994@...il.com>
Cc: arnd@...db.de, catalin.marinas@....com, cix-kernel-upstream@...tech.com,
	conor+dt@...nel.org, devicetree@...r.kernel.org, krzk+dt@...nel.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	marcin@...zkiewicz.com.pl, robh@...nel.org, will@...nel.org
Subject: Re: [PATCH v2 0/6] arm64: Introduce CIX P1 (SKY1) SoC

On 25-02-27 12:52:36, Jianfeng Liu wrote:
> Hi Peter,
> 
> I'm really happy to see the linux mainline upstream work sent. And I have
> also reveived radxa orion o6 before the Chinese new year. I have heard
> that CIX is testing vendor kernel with ACPI. And now the mainline upstream
> work is based on devicetree. I want to know what the upstream work of CIX
> would go in the future, are we going to toggle to ACPI instead of
> devicetree?
> 
> And it would be good to let outsiders know the plan/roadmap of upstream.
> For example collaboara is doing good job on upstreaming rockchip[1][2] and
> mediatek[3] socs.
> 
> [1] https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md
> [2] https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3576/-/blob/main/mainline-status.md?ref_type=heads
> [3] https://gitlab.collabora.com/mediatek/aiot/wiki/-/blob/main/mainline-status.md
> 

Hi Jianfeng,

Thanks for your interesting of our hardware. Radxa will open our
v6.1 device tree vendor kernel source code at the beginning of next month.
For ACPI vendor kernel source code based on v6.6, it has planned to open
at Q2 of this year.

For upstream, we will submit support based on device tree first, since
some common code changes are needed for supporting ACPI well at Arm,
it may involve lots of discussion. After most of IP drivers are
supported by upstream kernel, we will start ACPI upstream work.

For upstream status record for CIX SoC, we will find some public place
for it.

-- 

Best regards,
Peter

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ