From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753189AbcDXSL4 (ORCPT ); Sun, 24 Apr 2016 14:11:56 -0400 Received: from bh-25.webhostbox.net ([208.91.199.152]:46261 "EHLO bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752009AbcDXSLy (ORCPT ); Sun, 24 Apr 2016 14:11:54 -0400 Subject: Re: qemu:beagle no longer booting with omap2plus_defconfig in -next To: Boris Brezillon References: <571BB682.1010806@roeck-us.net> <20160423214617.4d0905d2@bbrezillon> <571CF780.1080308@roeck-us.net> <20160424193414.2bc82d47@bbrezillon> Cc: "linux-next@vger.kernel.org" , Stephen Rothwell , "linux-kernel@vger.kernel.org" , Roger Quadros , Brian Norris , Tony Lindgren , "linux-mtd@lists.infradead.org" , "linux-omap@vger.kernel.org" From: Guenter Roeck Message-ID: <571D0C65.1020500@roeck-us.net> Date: Sun, 24 Apr 2016 11:11:49 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <20160424193414.2bc82d47@bbrezillon> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated_sender: linux@roeck-us.net X-OutGoing-Spam-Status: No, score=-1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bh-25.webhostbox.net X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - roeck-us.net X-Get-Message-Sender-Via: bh-25.webhostbox.net: authenticated_id: linux@roeck-us.net X-Authenticated-Sender: bh-25.webhostbox.net: linux@roeck-us.net X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/24/2016 10:34 AM, Boris Brezillon wrote: > On Sun, 24 Apr 2016 09:42:40 -0700 > Guenter Roeck 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 > Yep, I figured out that one a minute ago :-) Thanks again! Guenter