public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Rainer Adlich <rainer.adlich@x2e.de>
Cc: ecos-patches@sources.redhat.com
Subject: Re: Xilinx UART and TEMAC driver
Date: Tue, 04 Nov 2008 20:35:00 -0000	[thread overview]
Message-ID: <20081104203428.GO20110@lunn.ch> (raw)
In-Reply-To: <48F46693.6040906@x2e.de>

On Tue, Oct 14, 2008 at 11:29:55AM +0200, Rainer Adlich wrote:
> Hi eCos maintainers,
> 
> although I've been working with eCos for more than a year I am new to
> this mailing-list. I like eCos very much and had very good experience
> with it - thanks to all the people maintaining and contributing to it.
> 
> During the work on our "Spyder IV" board (based on Xilinx Virtex-4 with
> PowerPC), drivers for Xilinx' opb_uartlite UART- and plb_temac
> Ethernet-IP cores (the latter with DMA support) arose.
> 
> If these drivers could be of use for someone, I would like to contribute
> them. As this would be my first contribution, I would be glad to obtain
> some help. Please let me know how to proceed.

We are always interested in contributions.

I can help with the Software aspects. However the hardware parts is
out of my knowledge. So i guess i need to ask some dumb questions
first...

What are the licenses for these cores? Is there anything which would
restrict the distribution of the software? Is all the documentation
publicly available or did you need to sign an NDA for them?

From what i understand of cores, they are normally parameters you can
tune for the hardware, to add or remove features etc. How generic are
your drivers? Are there similar tunable settings so that the driver
can be made to match the core? Or is the driver set for just one
specific configuration and is this well documented?

         Thanks
                Andrew

      reply	other threads:[~2008-11-04 20:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14  9:30 Rainer Adlich
2008-11-04 20:35 ` Andrew Lunn [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=20081104203428.GO20110@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-patches@sources.redhat.com \
    --cc=rainer.adlich@x2e.de \
    /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).