From: Nick Garnett <nickg@cygnus.co.uk>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: Ling Su <lingsu@palmmicro.com>, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Re: eCos PCI problem and NEC vrc4373 build option.
Date: Thu, 31 Aug 2000 03:34:00 -0000 [thread overview]
Message-ID: <por975en6a.fsf@balti.cygnus.co.uk> (raw)
In-Reply-To: <39ADBB98.28EC1E09@redhat.com>
Jonathan Larmour <jlarmour@redhat.com> writes:
> Ling Su wrote:
> >
> > 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?
>
Sorry, no.
Thinking about it, I suspect we never tried plugging a card into the
PCI slots on the board. This was never something we needed to do, we
only ever used the on-board PCI devices. However, there should be no
additional software issues, it should just work. So maybe there are
problems with the PCI slots on the board. Are all the power pins
working? Are there any jumpers to change to enable them?
--
Nick Garnett, eCos Kernel Architect
Red Hat, Cambridge, UK
next prev parent reply other threads:[~2000-08-31 3:34 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 [this message]
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=por975en6a.fsf@balti.cygnus.co.uk \
--to=nickg@cygnus.co.uk \
--cc=ecos-discuss@sources.redhat.com \
--cc=jlarmour@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).