public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Manfred Gruber <m.gruber@tirol.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Ecos FLash V2 chips Spansion
Date: Fri, 07 Jul 2006 13:13:00 -0000	[thread overview]
Message-ID: <200607071513.14013.m.gruber@tirol.com> (raw)

Hi !

I am using ecos-redboot flash_v2 branche for a long time now, works wonderfull 
with Spansion Flash Chips S29GLXXXM. S29GLXXXM have a erase size of 64k. Now 
I want to change to S29GLXXXN, which have a erases sizes of 2x64k.

I have seen that this chips(S29GLXXX) are now in the standard AMD driver. But 
what is with flash_v2 do I get in troubles when I want to use them on 
flash_v2 branche, would it be hard to use this chips or do you think it would 
be easy to implement, hack and use them ? 

Hopefully someone has some pre information about that for me...

thanks regards manfred

-- 
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:[~2006-07-07 13:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200607071513.14013.m.gruber@tirol.com \
    --to=m.gruber@tirol.com \
    --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).