public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: Ling Su <lingsu@palmmicro.com>
Cc: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: eCos PCI problem and NEC vrc4373 build option.
Date: Wed, 30 Aug 2000 15:58:00 -0000	[thread overview]
Message-ID: <39AD917B.EDBF58F4@redhat.com> (raw)
In-Reply-To: <001901c012d5$3cf3f990$1201a8c0@crusoe>

Ling Su wrote:
> 
> Could you please tell me what snapshot you exactly use for free, or I need
> to pay some money for the answer? :-)

We have our own commerically supported and verified versions of gcc/gdb
etc.
 
> Another question I have is, is there any documents on what improvement has
> been done on a specific platform (like NECvrc4373)? I checked the NEWS in
> the new cvs release, it doesn't give me a clear idea on what exact will
> appear on the vrc4373 platform. For example, the Redboot can not be applied
> now on vrc4373. How about the network support for vrc4373 then? It does have
> a DEC ethernet chip on PCI bus.

Not on the roadmap yet - no-one is paying us to work on it, and as far as I
know, no-one on the net is doing anything.

So the only things in the NEWS file of relevance to the vrc4373 are the
generic items. But there's still quite a lot of those!
 
> BTW, I remeber I asked you another question last time,  if I plug a PCI card
> in one of the PCI slots, why the pci1.exe test program can not find it and
> display some Vendor information, I tried the code you send to me, it doesn't
> work, either. Any clue?

Ah, I sent you a reply but the list wasn't CC'd. Whatever.
 
> I do want to pay something for a technical support, but I just wonder if the
> support quality can compare with the experts as you on the list. :)

Hah. Well, for a start I would answer all your mails rather than sometimes
not having time and leaving them. And we'd give you tools certified to work
with eCos so these problems would have been behind you ages ago!

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-30 15:58 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 [this message]
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=39AD917B.EDBF58F4@redhat.com \
    --to=jlarmour@redhat.com \
    --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).