From: "Ramgopal Kota" <rkota@broadcom.com>
To: "ecos-discuss@ecos.sourceware.org" <ecos-discuss@ecos.sourceware.org>
Cc: "Raju (Narasimha Raju) Chinta" <narasimha.chinta@broadcom.com>,
"Sindhu Bharathi Chintakrindi" <chsindhu@broadcom.com>
Subject: [ECOS] Does eCOS 2.0/3.0 support CFI ?
Date: Fri, 11 Dec 2009 10:28:00 -0000 [thread overview]
Message-ID: <6C370B347C3FE8438C9692873287D2E1108131098B@SJEXCHCCR01.corp.ad.broadcom.com> (raw)
In-Reply-To: <4B1F7216.60104@ecoscentric.com>
Hi,
Does eCOS support CFI Flash interface ?
We have desgined a board based on spansion flash with 8MBytes.Due to procument issues, the team wants to use non-uniform sectors parts also.
Thanks & Regards,
Ramgopal Kota
-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Ross Younger
Sent: Wednesday, December 09, 2009 3:17 PM
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Re: Can not compile API file
m mariga wrote:
>> PPOUT.C
It looks to me like this file has not been selected for compilation
because the build system is case sensitive: I suspect that if you rename
it to PPOUT.c it should compile.
Ross
--
eCosCentric Ltd, Barnwell House, Barnwell Drive, Cambridge CB5 8UU, UK
Registered in England no. 4422071. www.ecoscentric.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2009-12-11 10:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 9:32 [ECOS] Re: Can not compile API file m mariga
2009-12-09 9:47 ` Ross Younger
2009-12-11 10:28 ` Ramgopal Kota [this message]
2009-12-11 22:51 ` m mariga
2009-12-14 12:38 ` m mariga
2009-12-14 12:49 ` Edgar Grimberg
2009-12-15 12:47 ` m mariga
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=6C370B347C3FE8438C9692873287D2E1108131098B@SJEXCHCCR01.corp.ad.broadcom.com \
--to=rkota@broadcom.com \
--cc=chsindhu@broadcom.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=narasimha.chinta@broadcom.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).