public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Jean-Francois Argentino <jf.argentino@osean.fr>
Cc: ecos-patches@sources.redhat.com
Subject: Re: bsp for Olimex LPC-L2294-8M
Date: Fri, 05 Nov 2010 17:57:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.00.1011051734540.23460@sg-laptop> (raw)
In-Reply-To: <4CD3EB1B.3000709@osean.fr>

On Fri, 5 Nov 2010, Jean-Francois Argentino wrote:
> Hello,
>
> Following is a patch to support the OLIMEX LPC-L2294-8M development
> board: same as LPC-L2294-1M with 8Mbytes of RAM (2 x SAMSUNG
> K1S321611C) and 4M of FLASH (INTEL TE28F320C3BD70).
> I don't have a LPC-L2294-1M, so I'm not sure if it has broken
> something.  Be aware that this is my 1st contact with eCos, maybe
> there's a better way to do this.

Salut,

Thank you for your contribution to eCos. Sure, you can send the patches
on this list, however, today's preferred method is to submit the patches
through an eCos Bugzilla Engine: http://bugs.ecos.sourceware.org/

Jean-Francois, although your patch(es) is/are small enough, it exceeds
that "ten lines limit" to incorporate the patch(es) without a Copyright
assignment (CA). Read, please, more about eCos CA needs and points here:
http://ecos.sourceware.org/contrib.html

I think that to start a process to get CA from FSF is good idea as your
both patches (the second is a fix for one FLASH device driver) have TODO
lines :-)

One thought according the selected name for CDL to manage a hardware
variant for the target (CYGPKG_HAL_ARM_LPC2XXX_OLPCL2294_RAMSIZE), for
my taste CDL name to distinguish hardware would be something like
CYGHWR_HAL_ARM_LPC2XXX_OLPCL2294_VARIANT and using such an option you
could enter the changes in HAL startup code and in the target's flash
device driver.

So, could you, please, re-submit the patch(es) for eCos Bugzilla system
and start the process of obtaining CA (if you can)? At the least, I will
be able to test your changes for 8M variant on OLPCL2294-1M target then.

Je vous remercie,

Sergei

  reply	other threads:[~2010-11-05 17:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-05 11:31 Jean-Francois Argentino
2010-11-05 17:57 ` Sergei Gavrikov [this message]
2010-11-08  8:35   ` Jean-Francois Argentino
2010-11-08 11:30     ` Jean-Francois Argentino
2010-11-08 12:01       ` Sergei Gavrikov

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=alpine.DEB.2.00.1011051734540.23460@sg-laptop \
    --to=sergei.gavrikov@gmail.com \
    --cc=ecos-patches@sources.redhat.com \
    --cc=jf.argentino@osean.fr \
    /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).