From: "Ling Su" <lingsu@palmmicro.com>
To: "Jonathan Larmour" <jlarmour@redhat.com>
Cc: <ecos-discuss@sources.redhat.com>, "Nick Garnett" <nickg@redhat.com>
Subject: Re: [ECOS] Re: eCos PCI problem and NEC vrc4373 build option.
Date: Thu, 31 Aug 2000 10:57:00 -0000 [thread overview]
Message-ID: <005101c01375$5496bc40$1201a8c0@crusoe> (raw)
In-Reply-To: <39ADBB98.28EC1E09@redhat.com>
> > Thanks, Jifl, the patch works well in PCI1. The left things puzzled me,
> >
> > <1>. It didn't detect out the another PCI Network card on PCI slot 1,
how
> > you every try to plug one card on the board to test?
>
> Sorry I haven't. Nick, any ideas?
>
Today I found two old PCI graphic card, one from S3, and another from
Trident, after I plugged them in, they are both successfully detected by
pci1. The previous card was from PCtel (a winmodem actally), I guess it
might be a legacy device, not fully support PCI spec. Anyway, this question
is solved.
Thanks, Jifl and Nick.
Regards,
-Ling
prev parent reply other threads:[~2000-08-31 10:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-29 11:37 [ECOS] eCos tools binary installation under Cygwin Grant Edwards
2000-08-29 11:57 ` Jonathan Larmour
2000-08-29 12:28 ` Ling Su
2000-08-29 12:43 ` Jonathan Larmour
[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 [this message]
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='005101c01375$5496bc40$1201a8c0@crusoe' \
--to=lingsu@palmmicro.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=jlarmour@redhat.com \
--cc=nickg@redhat.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).