From: Rutger Hofman <rutger@cs.vu.nl>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Legacy Flash implementation (was: Re: [ECOS] Build fails after CVS update)
Date: Fri, 06 Jul 2007 10:37:00 -0000 [thread overview]
Message-ID: <468E1AE7.6050605@cs.vu.nl> (raw)
In-Reply-To: <46852457.5080601@cs.vu.nl>
Rutger Hofman wrote:
>> Rutger Hofman wrote:
>>> I updated to the most recent version of the CVS list; the previous
>>> checkout was from last february, not too long ago; but I ran into some
>>> problems:
>>>
>>> = the Legacy Flash stuff has disappeared, but I use it (I think I might
>>> be the only user, but still!).
> The ... problem is with the flash stuff. The "Legacy API" flash
> ... won't compile.
>
> What is the best way to tackle this? What is the quickest way to tackle
> this? I don't really want to port our vendor's flash implementation to the
> newer flash implementation. Is there a way that I can easily restore the
> legacy API stuff?
A week ago, I asked this. I think it has escaped the attention of the
list. Right now, to keep things alive I had to revert to my previous
eCos checkout. I would really like to upgrade to bleeding-edge CVS (e.g.
I want to add my external RTC chip, DS1339, which is driven via I2C, but
the I2C interface has changed/improved meanwhile).
How would I go about upgrading? Our vendor has provided Flash drivers
but they speak the old Legacy API. Would it be a breeze to convert them
to the newer Flash API? Or would it be easier to try to reinstate a
Legacy portability layer, with maybe symbol name changes in our vendor's
code to avoid name conflicts?
Rutger Hofman
VU Amsterdam
--
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:[~2007-07-06 10:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 8:04 [ECOS] Build fails after CVS update Rutger Hofman
2007-06-30 15:00 ` Gary Thomas
2007-06-30 16:12 ` Rutger Hofman
2007-07-06 10:37 ` Rutger Hofman [this message]
2007-07-08 18:57 ` [ECOS] Legacy Flash implementation (was: Re: [ECOS] Build fails after CVS update) Andrew Lunn
2007-07-08 20:15 ` [ECOS] Legacy Flash implementation Rutger Hofman
2007-07-09 11:08 ` Rutger Hofman
2007-07-09 13:48 ` Andrew Lunn
2007-06-30 17:14 ` [ECOS] Build fails after CVS update Gary Thomas
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=468E1AE7.6050605@cs.vu.nl \
--to=rutger@cs.vu.nl \
--cc=ecos-discuss@ecos.sourceware.org \
/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).