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
| ||
|
Date: Sat, 6 Feb 2016 22:22:06 -0800 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: Sergei Ianovich <ynvich@...il.com> Cc: linux-kernel@...r.kernel.org, Heikki Krogerus <heikki.krogerus@...ux.intel.com>, James Cameron <quozl@...top.org>, Robert Jarzmik <robert.jarzmik@...e.fr>, Russell King <linux@....linux.org.uk>, Jiri Slaby <jslaby@...e.com>, Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, Arnd Bergmann <arnd@...db.de>, Joachim Eastwood <manabian@...il.com>, Sebastian Andrzej Siewior <bigeasy@...utronix.de>, Scott Wood <scottwood@...escale.com>, Paul Gortmaker <paul.gortmaker@...driver.com>, Paul Burton <paul.burton@...tec.com>, Mans Rullgard <mans@...sr.com>, Ralf Baechle <ralf@...ux-mips.org>, Masahiro Yamada <yamada.masahiro@...ionext.com>, Peter Hurley <peter@...leysoftware.com>, "open list:SERIAL DRIVERS" <linux-serial@...r.kernel.org> Subject: Re: [PATCH v6] serial: rewrite pxa2xx-uart to use 8250_core On Thu, Dec 24, 2015 at 06:15:14PM +0300, Sergei Ianovich wrote: > pxa2xx-uart was a separate uart platform driver. It was declaring > the same device names and numbers as 8250 driver. As a result, > it was impossible to use 8250 driver on PXA SoCs. > > Upon closer examination pxa2xx-uart turned out to be a clone of > 8250_core driver. > > Workaround for Erratum #19 according to Marvel(R) PXA270M Processor > Specification Update (April 19, 2010) is dropped. 8250_core reads > from FIFO immediately after checking DR bit in LSR. > > The patch leaves the original SERIAL_PXA driver around. The original > driver is just marked DEPRECATED in Kconfig and C source. When > the original driver is considered safe to remove, no changes > to SERIAL_8250 will be necessary. But, you just broke existing configurations, right? The serial port is a different name now, are you willing to handle the angry users? If so, great, get the platform maintainer to sign off on this please and then resend it. thanks, greg k-h
Powered by blists - more mailing lists