From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27216 invoked by alias); 6 Jul 2007 10:37:39 -0000 Received: (qmail 27206 invoked by uid 22791); 6 Jul 2007 10:37:38 -0000 X-Spam-Check-By: sourceware.org Received: from top.few.vu.nl (HELO top.few.vu.nl) (130.37.20.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 06 Jul 2007 10:37:33 +0000 Received: from [130.37.193.14] (mercury.cs.vu.nl [130.37.193.14]) by top.few.vu.nl with esmtp (Smail #115) id m1I6lBq-0001O1C; Fri, 6 Jul 2007 12:37 +0200 Message-ID: <468E1AE7.6050605@cs.vu.nl> Date: Fri, 06 Jul 2007 10:37:00 -0000 From: Rutger Hofman User-Agent: Thunderbird 1.5.0.5 (X11/20060719) MIME-Version: 1.0 To: ecos-discuss@ecos.sourceware.org References: <46851C3D.5000400@cs.vu.nl> <46851F7A.8010709@mlbassoc.com> <46852457.5080601@cs.vu.nl> In-Reply-To: <46852457.5080601@cs.vu.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: [ECOS] Legacy Flash implementation (was: Re: [ECOS] Build fails after CVS update) X-SW-Source: 2007-07/txt/msg00060.txt.bz2 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