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-next>] [day] [month] [year] [list]
Date:   Sat, 18 Feb 2023 21:56:39 +0200
From:   Ramon Fried <rfried.dev@...il.com>
To:     linux@...linux.org.uk, Greg KH <gregkh@...uxfoundation.org>,
        jirislaby@...nel.org, linux-serial@...r.kernel.org
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Baruch Siach <baruch@...s.co.il>
Subject: amba pl011 non amba/sbsa driver

Hi.
Our upcoming SOC is using pl011 ip, but we have a different NOC than
AMBA and we don't want to use the SBSA, as it provides limited
functionality in the UART.

My question is should we develop a new driver or add more
functionality to the current driver.
The pl011 driver is a bit messy, and the functionality we actually
need is actually supported in the current driver, but I can't
differentiate my HW using AMBA id.

If a change will be more suitable in the driver, my plan is to add
support for an oe_device_id table  along with an amba_device_id table
for generic amba pl011 drivers.
Does this make sense ?

Thanks,
Ramon.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ