public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.co.uk>
To: Ling Su <lingsu@palmmicro.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] eCos tools binary installation under Cygwin
Date: Tue, 29 Aug 2000 12:43:00 -0000	[thread overview]
Message-ID: <39AC1265.947D9697@redhat.co.uk> (raw)
In-Reply-To: <000901c011ef$b8839160$1201a8c0@crusoe>

Ling Su wrote:
> 
> Hi, Jifl,
> 
> Do you ever meet following errors when you run pci1.exe test, following is
> what I met even I use the most updated cvs release, it is the same as
> before. The PCI bus scan failed for a SIGBUS bus error...Could you please
> take a look? Thanks!

I built pci1 from the latest sources (should be no different in any
relevant way to yours) and ran pci1. I got:

(gdb) c
Continuing.
Found device on bus 0, devfn 0x00:
 Note that board is active. Probed sizes and CPU addresses invalid!
 Device configuration failed - device already enabled
 Vendor    0x1033 [NEC][NEC Corporation]
 Device    0x001A [UNKNOWN]
 Command   0x0146, Status 0x0280
 Class/Rev 0x06800001 [Bridge Device][Other][]
 Header 0x11FF0E
 SubVendor 0x1111, Sub ID 0xFF19
 BAR[0]    0x1C000000 / probed size 0x00000000 / CPU addr 0x1111FF15
 BAR[1]    0x80000000 / probed size 0x00000000 / CPU addr 0x00000000
 BAR[2]    0x00000000 / probed size 0x00000000 / CPU addr 0x1111FF16
 BAR[3]    0x00000000 / probed size 0x00000000 / CPU addr 0x00000000
 BAR[4]    0x00000000 / probed size 0x00000000 / CPU addr 0x1111FF17
 BAR[5]    0x00000000 / probed size 0x00000000 / CPU addr 0x00000000
 Wired to HAL vector 11
Found device on bus 0, devfn 0x18:
 Device configuration succeeded
 Vendor    0x1011 [DEC][Digital Equipment Corporation]
 Device    0x0009 [DC21140][Fast Ethernet Ctrlr]
 Command   0x0000, Status 0x0280
 Class/Rev 0x02000022 [Network Controller][Ethernet][]
 Header 0x11FF0E
 SubVendor 0x1111, Sub ID 0xFF19
 BAR[0]    0x00000001 / probed size 0xFFFFFF81 / CPU addr 0xAC000000
 BAR[1]    0x00000000 / probed size 0xFFFFFF80 / CPU addr 0xC0000000
 BAR[2]    0x00000000 / probed size 0x00000000 / CPU addr 0xFFFFFFFF
 BAR[3]    0x00000000 / probed size 0x00000000 / CPU addr 0xFFFFFFFF
 BAR[4]    0x00000000 / probed size 0x00000000 / CPU addr 0xFFFFFFFF
 BAR[5]    0x00000000 / probed size 0x00000000 / CPU addr 0xFFFFFFFF
 Wired to HAL vector 14
 
Strings in [] are from the PCI Code List at http://www.yourvote.com/pci
It seems that some of the device information has not been registered in
the PCI Code List. Please consider improving the database by registering
the [UNKNOWN] information for your devices. Thanks.
PASS:<pci1 test OK>
EXIT:<done>

I will send you the executable by private mail to see if it works on your
board.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

  reply	other threads:[~2000-08-29 12:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-29 11:37 Grant Edwards
2000-08-29 11:57 ` Jonathan Larmour
2000-08-29 12:28   ` Ling Su
2000-08-29 12:43     ` Jonathan Larmour [this message]
     [not found]       ` <39AC12F4.9C2F7678@redhat.co.uk>
2000-08-29 17:18         ` [ECOS] eCos PCI problem and NEC vrc4373 build option Ling Su
2000-08-30 15:25           ` [ECOS] " Jonathan Larmour
2000-08-30 15:51             ` Ling Su
2000-08-30 15:58               ` Jonathan Larmour
2000-08-30 16:38                 ` Alfredo Knecht
2000-08-30 17:20                   ` Jonathan Larmour
2000-08-30 18:10                     ` Alfredo Knecht
2000-08-30 18:22                       ` Jonathan Larmour
2000-08-30 17:42                   ` Ling Su
2000-08-30 18:02                     ` Jonathan Larmour
2000-08-30 18:28                       ` Ling Su
2000-08-30 18:57                         ` Jonathan Larmour
2000-08-31  3:34                           ` Nick Garnett
2000-08-31 10:57                           ` Ling Su

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=39AC1265.947D9697@redhat.co.uk \
    --to=jlarmour@redhat.co.uk \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=lingsu@palmmicro.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).