| 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: Sun, 24 Apr 2016 19:34:14 +0200 From: Boris Brezillon <boris.brezillon@...e-electrons.com> To: Guenter Roeck <linux@...ck-us.net> Cc: "linux-next@...r.kernel.org" <linux-next@...r.kernel.org>, Stephen Rothwell <sfr@...b.auug.org.au>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Roger Quadros <rogerq@...com>, Brian Norris <computersforpeace@...il.com>, Tony Lindgren <tony@...mide.com>, "linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>, "linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org> Subject: Re: qemu:beagle no longer booting with omap2plus_defconfig in -next On Sun, 24 Apr 2016 09:42:40 -0700 Guenter Roeck <linux@...ck-us.net> wrote: > In qemu, it looks like gpmc bit 0 is considered to be the NAND chip select, > which is distinctly different to a chip ready pin. Guess I would have to try > finding a chip datasheet to figure out what this pin is supposed to do, and > what is wrong. Since it is somewhat unlikely that I'll find the time to do that, > I just disabled MTD_NAND_OMAP2 in my qemu tests instead. Not an ideal solution, > of course, but the alternative would be to drop the beagle qemu tests entirely. Here is a patch [1] which should fix your problem. It's obviously not enough to handle the different use cases we have in in the wild, but should fix your problem on the beagle board. Regards, Boris [1]http://code.bulix.org/i5c4yc-97598 -- Boris Brezillon, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
Powered by blists - more mailing lists