public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: Peter Huszar <phuszar@freemail.hu>
Cc: eCos Patches List <ecos-patches@ecos.sourceware.org>
Subject: Re: LPC2XXX ADC modification
Date: Mon, 28 Jun 2010 09:54:00 -0000	[thread overview]
Message-ID: <4C287151.8090609@dallaway.org.uk> (raw)
In-Reply-To: <002a01cb1639$e93a4c50$bbaee4f0$@hu>

Hi Peter

Peter Huszar wrote:

> I have noticed that the Olimex H2294 board support includes an ADC that is
> specific to some versios of LPC2XXX processors.
> It only covers models that have individual conversion registers (LPC24XX
> and  LPC21XX/LPC22XX with 01 suffix).
> 
> I have modified the ADC driver to support all LPC ADC configurations.
> 
> Please let me know if this is of any interest to the eCOS maintainers and/or
> the eCOS community.
> 
> If interested, please let me know how to go about contributing the modified
> ADC code and package information.
> I have tested the configurations that I am using, but would only do more
> generic test if there is interest from the community.

Thank you for your interest in contributing your ADC driver changes.

Extended hardware support is always of interest. If the patch is just a
few lines we may be able to accept it without a copyright assignment,
otherwise you will need to complete copyright paperwork as described at:

  http://ecos.sourceware.org/assign.html

Could you post your patch to ecos-patches@ecos.sourceware.org so we can
advise further?

John Dallaway
eCos maintainer

  reply	other threads:[~2010-06-28  9:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-27 20:47 Peter Huszar
2010-06-28  9:54 ` John Dallaway [this message]
     [not found]   ` <000301cb16eb$744e8660$5ceb9320$@hu>
2010-06-30  8:26     ` John Dallaway

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=4C287151.8090609@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --cc=ecos-patches@ecos.sourceware.org \
    --cc=phuszar@freemail.hu \
    /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).