From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7680 invoked by alias); 16 Mar 2006 15:49:16 -0000 Received: (qmail 7660 invoked by uid 22791); 16 Mar 2006 15:49:15 -0000 X-Spam-Status: No, hits=0.0 required=5.0 tests=BAYES_50 X-Spam-Check-By: sourceware.org Received: from mail.suremessenger.com (HELO mail.suremessenger.com) (12.5.48.16) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 16 Mar 2006 15:49:12 +0000 Received: from [65.40.127.178] (account stepheng@adiengineering.com HELO Mercury) by mail.suremessenger.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 87300394; Thu, 16 Mar 2006 10:49:10 -0500 From: "Stephen Goadhouse" To: , , Subject: RE: [ECOS] Redboot causes PCI abort in Linux Ixp425 Date: Thu, 16 Mar 2006 15:49:00 -0000 Organization: ADI Engineering, Inc. MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Thread-Index: AcZIv3/+srSSv8qWRT6T62EHJW5VUgAUOhsg In-Reply-To: <20060316060422.33764.qmail@web33213.mail.mud.yahoo.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-ID: X-IsSubscribed: yes Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2006-03/txt/msg00020.txt.bz2 Xscale processors, and perhaps other ARM-based processors, will get a data abort exception while scanning the PCI bus. This is normal. To scan the bus, the system should be trying to read every available PCI configuration slot address to see if a device is there. If no device is there, you'll get a data abort exception because technically the PCI transaction did not complete (no target to handle the PCI configuration read). Typically, this is handled by installing a data abort exception handler prior to scanning the bus that gracefully handles these exceptions during PCI bus scan. Another alternative with the IXP425 may be to setup its internal PCI bridge so that it returns 0xFFFFFFFF instead of doing a data abort. I have not looked at the ixp425 manual in a while, but I am fairly certain that it has this ability. I would expect that's what your old RedBoot did to handle this so that Linux would not have to. Receiving 0xFFFFFFFF when reading non-existent PCI slots is what happens in a PC environment and I'm fairly certain that is what Linux typically expects. _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ _/ Stephen Goadhouse Work: (434) 978-2888 x254 _/ _/ Senior Staff Engineer stephen.goadhouse@adiengineering.com _/ _/ ADI Engineering http://www.adiengineering.com _/ _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ > -----Original Message----- > From: ecos-discuss-owner@ecos.sourceware.org > [mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of > Ravi modgekar > Sent: Thursday, March 16, 2006 1:04 AM > To: ecos-devel@sourceware.org; ecos-discuss@sourceware.org > Subject: [ECOS] Redboot causes PCI abort in Linux Ixp425 > > Hi, > I have an IXP425 based board based on Gateworks > GW2345 board.This > board already had a redboot image programmed through which > we could easily load linux and work on it. > Now I have compiled the redboot for our IXP based board > from the Avila redboot sources.With this newly compiled > redboot I am able to > boot linux, but unfortunately the PCI cribs and the > linux crashes > with PCI abort. The error message being "!!! > abort_handler addr = > 0x40015000 ,isr = 0x0 , status = 0x22a0". > Interestingly the same Linux > image works fine with the old redboot ,for which we don't > have the source code. > Has anybody in this list faced this problem.Am I missing > configuring something in the Redboot which is causing the > PCI abort.I have tried with completely disabling PCI > interface , but I still see this problem. > > any pointers !!! > > Regds > Ravi > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection > around http://mail.yahoo.com > > -- > Before posting, please read the FAQ: > http://ecos.sourceware.org/fom/ecos > and search the list archive: > http://ecos.sourceware.org/ml/ecos-discuss > > > __________ NOD32 1.1445 (20060315) Information __________ > > This message was checked by NOD32 antivirus system. > http://www.eset.com > >