From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4424 invoked by alias); 22 Mar 2006 14:42:18 -0000 Received: (qmail 4415 invoked by uid 22791); 22 Mar 2006 14:42:17 -0000 X-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_20 X-Spam-Check-By: sourceware.org Received: from mga02.intel.com (HELO orsmga101-1.jf.intel.com) (134.134.136.20) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 22 Mar 2006 14:42:14 +0000 Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101-1.jf.intel.com with ESMTP; 22 Mar 2006 06:42:12 -0800 Received: from fmsmsx332.fm.intel.com (HELO fmsmsx332.amr.corp.intel.com) ([132.233.42.148]) by orsmga001.jf.intel.com with ESMTP; 22 Mar 2006 06:42:11 -0800 X-IronPort-AV: i="4.03,117,1141632000"; d="scan'208"; a="14639405:sNHT317672460" Received: from fmsmsx311.amr.corp.intel.com ([132.233.42.214]) by fmsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 22 Mar 2006 06:42:11 -0800 Received: from hdsmsx401.amr.corp.intel.com ([10.127.2.60]) by fmsmsx311.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 22 Mar 2006 06:42:11 -0800 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [ECOS] Redboot causes PCI abort in Linux Ixp425 Date: Wed, 22 Mar 2006 14:42:00 -0000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ECOS] Redboot causes PCI abort in Linux Ixp425 Thread-Index: AcZNu92/XX0bA8K2SIyZbO76miB8GgAAiMTw From: "Daly, Jeffrey" To: X-OriginalArrivalTime: 22 Mar 2006 14:42:11.0147 (UTC) FILETIME=[CD6151B0:01C64DBE] 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/msg00024.txt.bz2 The situation isn't quite clear to me from your original email. Are you saying you've got 2 boards, one GW2345 and one custom? The GW2345 works fine. The custom one works fine with the GW2345 redboot and linux, but doesn't work whith the custom redboot and linux? Pls clarify. Sounds to me like your PCI configuration during redboot is wrong (or at least is different that what the original does). You should dump the PCI config of the GW2345 (from redboot, before booting linux) and dump the PCi config of the custom board (again redboot, not linux) and post that. -----Original Message----- From: ecos-devel-owner@ecos.sourceware.org [mailto:ecos-devel-owner@ecos.sourceware.org] On Behalf Of Ravi modgekar Sent: Wednesday, March 22, 2006 9:21 AM To: Stephen Goadhouse; ecos-devel@sourceware.org; ecos-discuss@sourceware.org Subject: RE: [ECOS] Redboot causes PCI abort in Linux Ixp425 Hi Stephen, Data abort exception during PCI scan is ok.But in my case, the abort does not happen while scanning the bus , but it happens while accessing the device!!!! Basically Linux does the PCI enumeration at the boot time and sets up the device properly.There is absolutely no problem while scanning.The abort happens only when you try to access the PCI device.Now when you are trying to access the device , there is no question of scanning the bus again. I am wondering , if I am missing something else in the redboot .I also don't see any need to scan the PCI bus in the redboot, since linux is re doing it for me.what could be wrong. By the way, I think even the ADI coyote board does not scan the PCI bus in Redboot. Regds Ravi =20=20=20 --- Stephen Goadhouse wrote: >=20 > Xscale processors, and perhaps other ARM-based > processors, will get a > data abort exception while scanning the PCI bus.=20 > 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.=20=20=20 >=20 >=20 > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ >=20=20 > _/ Stephen Goadhouse Work: (434) > 978-2888 x254 _/ > _/ Senior Staff Engineer=20 > stephen.goadhouse@adiengineering.com _/ > _/ ADI Engineering=20=20=20=20=20=20=20=20=20=20=20=20=20=20 > http://www.adiengineering.com _/ > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ >=20 >=20 >=20 > > -----Original Message----- > > From: ecos-discuss-owner@ecos.sourceware.org=20 > > [mailto:ecos-discuss-owner@ecos.sourceware.org] On > Behalf Of=20 > > 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 > >=20 > > Hi, > > I have an IXP425 based board based on > Gateworks > > GW2345 board.This > > board already had a redboot image programmed=20 > through which=20 > > we could easily load linux and work on it. > > Now I have compiled the redboot for our IXP > based board=20 > > from the Avila redboot sources.With this newly > compiled=20 > > 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 =3D > > 0x40015000 ,isr =3D 0x0 , status =3D 0x22a0". > > Interestingly the same Linux > > image works fine with the old redboot ,for which > we don't=20 > > have the source code. > > Has anybody in this list faced this problem.Am I > missing=20 > > configuring something in the Redboot which is > causing the=20 > > PCI abort.I have tried with completely disabling > PCI=20 > > interface , but I still see this problem. > >=20 > > any pointers !!! > >=20 > > Regds > > Ravi > >=20 > > __________________________________________________ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam > protection=20 > > around http://mail.yahoo.com=20 > >=20 > > -- > > Before posting, please read the FAQ:=20 > > http://ecos.sourceware.org/fom/ecos > > and search the list archive:=20 > > http://ecos.sourceware.org/ml/ecos-discuss > >=20 > >=20 > > __________ NOD32 1.1445 (20060315) Information > __________ > >=20 > > This message was checked by NOD32 antivirus > system. > > http://www.eset.com > >=20 > >=20 >=20 >=20 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around=20 http://mail.yahoo.com=20