public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: "Andrea Michelotti" <amichelotti@atmel.com>
To: "Andrew Lunn" <andrew.lunn@ascom.ch>
Cc: "Andrew Lunn" <andrew.lunn@ascom.ch>,
	<ecos-maintainers@ecos.sourceware.org>
Subject: Re: [Bug 1000096] new AT91 platform: JTST
Date: Fri, 17 Sep 2004 19:03:00 -0000	[thread overview]
Message-ID: <002c01c49ce8$77376000$330110ac@pitagora> (raw)
In-Reply-To: <20040917180643.GB26968@biferten.ma.tech.ascom.ch>

The splitting you propose sounds good.
I agree with you to found the final good solution we need some discussion.
The copyright agreement I sent to you covers all the code written by me in
Atmel Rome (jtst port, patches... it was signed by our Atmel Rome CEO).
Diopsis (and all boards) is an Atmel Rome project that's responsible for all
the hardware and the software product.
For the usb driver (separate package from atmel Asia), at the moment I can't
include sources. The authors, have to ask permission to their local CEO.

thanks again

best regards.

Andrea.



> Humm. As a starting point that is reasonable.
>
> However we might want to think a bit about the long term. I can see
> more silicon with a CPU and a DSP together comming along. eg there is
> TI OMAP and im sure there are others. You should also think about your
> own internal plans. Maybe you will release another chipset which has
> the same DSP but a different processor. Or maybe you keep the same
> processor but have a different DSP. You want to keep the API the same
> to make it easy to port software between the different systems.
>
> So you might want to split it up into multiple packages. Maybe one
> package that implements the API. Another which implements the things
> which are specific to the DSP and a third which is specific to the
> processor?
>
> Now is the API generic enough that it could say be used for the OMAP
> or some other manufactures CP+DSP chipset? Im guessing not, it would
> be very difficult to have such a generic API.
>
> So maybe you need something like the following structure
>
> packages/devs/dsp/atmel/magic
> packages/devs/dsp/atmel/jtst
> packages/devs/dsp/atmel/api
>
> Since there is nothing like this at the moment we have much more
> freedom for discussion, so if you have other ideas or requirements
> please let us know.
>
> > We have developed (work done by atmel China) an ecos driver also for the
USB
> > (philips isp1181) included in the JTST; but I must check if we can
> > distribute the sources..
>
> We would also need to look at the copyright assignment. Is it specifc
> to you, Atmel Italy, or Atmel world wide?
>
>    Andrew
>

  reply	other threads:[~2004-09-17 19:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040917115657.246B365C110@smtp.ecoscentric.com>
2004-09-17 16:47 ` Andrea Michelotti
2004-09-17 17:23   ` Jonathan Larmour
2004-09-17 18:07   ` Andrew Lunn
2004-09-17 19:03     ` Andrea Michelotti [this message]
2004-09-17 21:43     ` Jonathan Larmour

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='002c01c49ce8$77376000$330110ac@pitagora' \
    --to=amichelotti@atmel.com \
    --cc=andrew.lunn@ascom.ch \
    --cc=ecos-maintainers@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).