From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-iw0-f179.google.com (mail-iw0-f179.google.com [209.85.214.179]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id 5E005B70A9 for ; Sat, 12 Feb 2011 06:16:17 +1100 (EST) Received: by iwb12 with SMTP id 12so2897982iwb.38 for ; Fri, 11 Feb 2011 11:16:14 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <1296682842.2349.730.camel@pasglop> Date: Fri, 11 Feb 2011 13:16:14 -0600 Message-ID: Subject: Re: BootX From: kevin diggs To: Benjamin Herrenschmidt Content-Type: text/plain; charset=ISO-8859-1 Cc: linuxppc-dev@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi, I have looked at the -S output for mesh.c from both 4.1.2 and 4.3.5. The generated code is quite different but I can not see any difference that is causing the problem? If I read and print the bus status register 0, it does appear to have the busy bit set? I'm in way over my head here. It appears to complete a pair of inquiries (one with a small data buffer and a second with a larger one) to each target. It then tries a test unit ready but discovers the bus busy? ANY suggestions welcome and appreciated! Thanks!