Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757927Ab3CNPD4 (ORCPT ); Thu, 14 Mar 2013 11:03:56 -0400 Received: from mail-oa0-f41.google.com ([209.85.219.41]:64049 "EHLO mail-oa0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755834Ab3CNPDy (ORCPT ); Thu, 14 Mar 2013 11:03:54 -0400 MIME-Version: 1.0 In-Reply-To: References: <1362666556-10036-1-git-send-email-yxlraid@gmail.com> Date: Thu, 14 Mar 2013 09:03:53 -0600 Message-ID: Subject: Re: [PATCH 2/2] PCI: fix system hang issue of Marvell SATA host controller From: Myron Stowe To: Xiangliang Yu Cc: Bjorn Helgaas , yxlraid , "linux-pci@vger.kernel.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1017 Lines: 27 On Wed, Mar 13, 2013 at 3:40 AM, Xiangliang Yu wrote: > Hi, Bjorn > >> >> > Now, the situation is like this: >> >> > I captured the PCIE trace with analyzer and found that 1st BE is 0x1111 >> >> > when >> >> > accessing IO port space. But 9125 spec has some limitation, and the BE >> >> > must >> >> > be >> >> > 0x0100, to access the 2nd byte only. So, the chip will go to bad. >> >> >> >> Great, this is new, interesting, data. Is the 9125 spec publicly >> >> accessible and/or could you elaborate on the "some limitation" >> >> comment? >> > 9125 spec is publicly accessible. > If you can't see the pic, please open the attachment. Thanks! Neither Bjorn nor myself could see the pic (from the previous thread or this thread's attachment). > > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/