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]
Date: Tue, 18 Jun 2024 07:58:49 +0100
From: Conor Dooley <conor.dooley@...rochip.com>
To: Yangyu Chen <cyy@...self.name>
CC: Conor Dooley <conor@...nel.org>, Jisheng Zhang <jszhang@...nel.org>, Yixun
 Lan <dlan@...too.org>, <linux-riscv@...ts.infradead.org>, Conor Dooley
	<conor+dt@...nel.org>, Palmer Dabbelt <palmer@...belt.com>, Paul Walmsley
	<paul.walmsley@...ive.com>, Samuel Holland <samuel.holland@...ive.com>, Anup
 Patel <anup.patel@....com>, Rob Herring <robh@...nel.org>, Krzysztof
 Kozlowski <krzk+dt@...nel.org>, <devicetree@...r.kernel.org>, Linux Kernel
 Mailing List <linux-kernel@...r.kernel.org>, Jesse Taube <jesse@...osinc.com>
Subject: Re: [PATCH v1 0/9] riscv: add initial support for SpacemiT K1

On Tue, Jun 18, 2024 at 01:42:34AM +0800, Yangyu Chen wrote:
> 
> 
> > On Jun 18, 2024, at 01:14, Conor Dooley <conor@...nel.org> wrote:
> > 
> > On Tue, Jun 18, 2024 at 12:39:30AM +0800, Yangyu Chen wrote:
> >> 
> >> The vendor uses a special intel pxa uart driver, marked deprecated
> >> in the kernel and incompatible with ns16550. If we use ns16550 in
> >> the dt, the behavior of uart is like the uart has no interrupt and
> >> stops working permanently when fifo overruns, making many developers
> >> not know how to start unless they use the SBI HVC console, which
> >> needs to turn on CONFIG_NONPORTABLE.
> > 
> > This I just do not understand. Why did they use this IP? Is it free?
> > Did they use it before for something else? It's a rather strange design
> > choice to me.
> 
> I don't know either. However, PXA is a subfamily of XScale. The
> kernel also probed the UART as an XScale. So, using XScale compatible
> string is OK.

Using a fallback to an Xscale compatible is okay, FTFY ;)

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ