This is the mail archive of the
mailing list for the eCos project.
Re: [Bug 1000096] new AT91 platform: JTST
- From: "Andrea Michelotti" <amichelotti at atmel dot com>
- To: "Andrew Lunn" <andrew dot lunn at ascom dot ch>
- Cc: "Andrew Lunn" <andrew dot lunn at ascom dot ch>, <ecos-maintainers at ecos dot sourceware dot org>
- Date: Fri, 17 Sep 2004 20:59:27 +0200
- Subject: Re: [Bug 1000096] new AT91 platform: JTST
- References: <20040917115657.246B365C110@smtp.ecoscentric.com> <firstname.lastname@example.org> <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.
> 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
> 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
> 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
> > (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?