| 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
| ||
|
Message-ID: <541C4DE8.3010307@nexus-software.ie> Date: Fri, 19 Sep 2014 16:38:16 +0100 From: Bryan O'Donoghue <pure.logic@...us-software.ie> To: "Chew, Kean Ho" <kean.ho.chew@...el.com>, "heikki.krogerus@...ux.intel.com" <heikki.krogerus@...ux.intel.com> CC: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>, "jslaby@...e.cz" <jslaby@...e.cz>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org> Subject: Re: [PATCHv2] serial: 8250: Add Quark X1000 to 8250 PCI driver On 19/09/14 15:31, Chew, Kean Ho wrote: >> Hi Ho. >> >> Do you have an idea when ? >> >> I guess if we're saying the simple patch which works right now - should be >> rejected in favour of alternative code coming - then at a minimum could you >> please give an indication of when that alternative code will be available ? >> >> Otherwise I think it makes sense to enable the hardware now - using the >> bog-standard means of doing that - just like BYT and others :) > > Make sense. I go with Hekki's direction. > Great. So Hekki, are OK with the suggested path here then ? I think myself and Ho are pretty much in agreement. Apply the patch I've submitted to 8250_pci.c - and then do whatever mods are appropriate later to enable whatever you're doing quark_8250.c. I think, it'd be a win from a Galileo enabling point of view. Best, Bryan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists