public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Tim Drury <tdrury@siliconmotorsports.com>
To: Jani Monoses <jani@iv.ro>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] source code credits
Date: Mon, 01 Jul 2002 05:40:00 -0000	[thread overview]
Message-ID: <200207010838.32670.tdrury@siliconmotorsports.com> (raw)
In-Reply-To: <20020701115919.33ffa74e.jani@iv.ro>


Jani,

I'd love to see it.  Funny, I was going to leave off the smaller plane also
since its sectors are a different size from the larger plane.  Maybe I can
model the flash as two flash chips of different sizes.

-tim


On Monday 01 July 2002 07:59 am, Jani Monoses wrote:
> We have an at49 driver here for at49V8011.
> I suppose this is not the same as you are using but if you're interested
> I can mail it to you.The reason I didn't submit it is that it only supports
> one of the two areas of the flash the one with fixed size erase sectors...
> The other is the boot part and is 128K (vs the rest until 1M) and quite
> small but still....
> Jani.
>
> > I'm going to copy the devs/flash code for the Atmel at29C flash and
> > create one for Atmel 49bv flash.  Trivial (but important) question:
> > Do I just add myself as a contributor in the comment block, or do I
> > make myself the author?
> >
> > -tim
> >
> >
> > --
> > Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> > and search the list archive: http://sources.redhat.com/ml/ecos-discuss


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

      reply	other threads:[~2002-07-01 12:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-28 12:12 Tim Drury
2002-06-28 13:13 ` Pete Barrie
2002-06-28 17:08   ` Tim Drury
2002-07-01  1:20 ` Jani Monoses
2002-07-01  5:40   ` Tim Drury [this message]

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=200207010838.32670.tdrury@siliconmotorsports.com \
    --to=tdrury@siliconmotorsports.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=jani@iv.ro \
    /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).