public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: Andrea Michelotti <amichelotti@atmel.com>
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 17:23:00 -0000	[thread overview]
Message-ID: <414B1D8D.3000303@eCosCentric.com> (raw)
In-Reply-To: <06c801c49cd6$948bc9a0$0b0110ac@ipitec.it>

Andrea Michelotti wrote:
> Hi Andrew,
> JTST has the same AIC controller as the other AT91 platforms, but jtst uses
> both line 0 (FIQ, connected with dsp halt signal) and line 1 (IRQ).
> In general atmel AIC has 1 FIQ +31 IRQs always available, depends on the
> board/SOC if they are used.
> In this simple at91 port I included the minimum to run eCos on diopsis and
> to lunch dsp applications.
> It exists supplemental DSP APIs for debbuging, user support and for system
> service routines. The problem is
> that I have to undestand the best way to plug them into eCos.
> At the moment I have a package that is situated in my local tree in
> package/devs/dsp/arm/magic.
> I thought magic as a device. It works, but I'm absolutely not sure that is
> the right thing to do.
> 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..
> At the moment all JTST in the world have Redboot installed in flash and run
> obviously eCos applications.
> 
> Here two links to jtst datasheets:
> http://www.atmel.com/dyn/general/tech_doc.asp?doc_id=9586
> http://www.atmel.com/dyn/general/tech_doc.asp?doc_id=9889

This is useful info, could you consider adding appropriate info containing 
useful info like this and some of the other things you've written as a 
README in the doc/ subdirectory of the platform HAL? SGML Docbook would be 
even better as it would mean it could be integrated into the full proper 
eCos documentation set (as at 
<http://ecos.sourceware.org/docs-latest/ref/ecos-ref.html>).

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine

  reply	other threads:[~2004-09-17 17:23 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 [this message]
2004-09-17 18:07   ` Andrew Lunn
2004-09-17 19:03     ` Andrea Michelotti
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=414B1D8D.3000303@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=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).