public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Doyle, Patrick" <WPD@dtccom.com>
To: "'David Marqvar (DAM)'" <DAM@tt.dk>, Andrew Lunn <andrew@lunn.ch>
Cc: ecos-discuss@ecos.sourceware.org
Subject: RE: [ECOS] Flash infrastructure rework
Date: Mon, 09 Aug 2004 12:58:00 -0000	[thread overview]
Message-ID: <F18ED44D2778844592DFB732956B66510225C624@DTCNT40S4> (raw)

Not having thought about it too much (at all), I have been planning on
writnig a CFI driver as well, based on the hacks I made to the strata driver
that I published several months ago.  I hadn't thought about making it
support both Intel and AMD algorithms, since I only have Intel-algorithm
based parts to play with.  We should coordinate, however, so we don't
duplicate work.

--wpd


> -----Original Message-----
> From: David Marqvar (DAM) [mailto:DAM@tt.dk] 
> Sent: Friday, August 06, 2004 9:45 AM
> To: Andrew Lunn
> Cc: ecos-discuss@ecos.sourceware.org
> Subject: RE: [ECOS] Flash infrastructure rework
> 
> 
> Sounds great.
> 
> I've been wanting to make a general flash driver based on CFI which
> would support the two main programming algorithm's around: Intel
> (Strata) and AMD (don't know if it's really these companies that
> invented the algorithm, anyway I think you know what I mean). 
> Is SST yet
> another programming algorithm or == ADM?
> 
> Though CFI I can read the physical layout of the flash and the
> programming algorithm to use.
> This way the flash-driver could be generel, not limited to one or more
> certian devices.
> 
> Do you see any show-stoppers for creating such driver?
> 
> /David
> 
> -----Original Message-----
> From: ecos-discuss-owner@ecos.sourceware.org
> [mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of 
> Andrew Lunn
> Sent: 6. august 2004 15:23
> To: eCos Disuss
> Subject: Re: [ECOS] Flash infrastructure rework
> 
> > I put the code on a branch so that a few people can test it 
> and so we 
> > get a better idea how stable the code is with hardware i don't have 
> > access to.
> 
> This is what i decided to do. In cvs there is now a branch called
> flash_v2. If you checkout/update to that branch you will get my new
> flash code. There is also new generic drivers for SST and 
> Strata. Since
> so many targets use strata i did not want to modify them all 
> to use the
> new driver. So the strata driver is a new packets along side the old
> one. For the SST driver i have modified all targets that use it. That
> was easier since only the e7t and the aim711 use this driver.
> 
> I've attached a hardware dependent driver for our platform which makes
> use of the sst and strata device. This could be used as an 
> example as to
> how to modify the hardware dependent part of a flash driver to use the
> new code.
> 
> One thing to watch out for is that the hardware dependent 
> driver has to
> go into libextras.a. If you forget this the driver will be thrown away
> at link time...
> 
> And lastly a warning to testers.... There could be bugs which destroy
> your boot loader etc. Make sure you can restore the device with jtag
> before playing with this code.
> 
>         Thanks
>                 Andrew
> 
> -- 
> Before posting, please read the FAQ: 
> http://ecos.sourceware.org/fom/ecos
> and search the list 
> archive: http://ecos.sourceware.org/ml/ecos-discuss
> 

Patrick Doyle
DSP Design Engineer
(603) 546-2179

 

This communication is from DTC Communications, Inc. and is intended to be
confidential and solely for the use of the persons or entities addressed
above.  If you are not an intended recipient, be aware that the information
contained herein may be protected from unauthorized use by privilege or law,
and any copying, distribution, disclosure, or other use of this information
is prohibited.  If you have received this communication in error, please
contact the sender by return e-mail or telephone the above number
immediately and delete or destroy all copies.  Thank you for your
cooperation.

 



-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2004-08-09 12:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09 12:58 Doyle, Patrick [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-09-08 12:25 Savin Zlobec
2004-08-09  8:47 David Marqvar (DAM)
2004-08-10  2:33 ` Vivek Kumar
     [not found] <0175EEA85416D811893E009027D0F5D79389D4@MAILHOST>
2004-08-06 17:19 ` Vivek Kumar
     [not found] <0175EEA85416D811893E009027D0F5D79389D3@MAILHOST>
2004-08-06 16:40 ` Vivek Kumar
2004-08-06 18:06   ` Gary Thomas
2004-08-06 13:43 David Marqvar (DAM)
2004-08-06 14:08 ` Andrew Lunn
2004-08-04 20:23 Doyle, Patrick
2004-08-04 20:17 Doyle, Patrick
2004-08-04 20:06 Doyle, Patrick
2004-08-04 20:12 ` Andrew Lunn
2004-08-04 19:49 Doyle, Patrick
2004-08-04 19:55 ` Andrew Lunn
2004-07-16 13:39 Andrew Lunn
2004-07-19 14:18 ` Ian Campbell
2004-07-30 10:43   ` Andrew Lunn
2004-08-04 12:54 ` Jani Monoses
2004-08-04 19:06   ` Andrew Lunn
2004-08-04 19:13 ` Andrew Lunn
2004-08-06 13:22   ` Andrew Lunn
2004-08-19 15:21 ` Bart Veer
2004-08-19 16:38   ` Andrew Lunn
2004-08-20 14:44     ` Bart Veer
2004-08-20 16:37       ` Andrew Lunn
2004-08-22 13:02         ` 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=F18ED44D2778844592DFB732956B66510225C624@DTCNT40S4 \
    --to=wpd@dtccom.com \
    --cc=DAM@tt.dk \
    --cc=andrew@lunn.ch \
    --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).