public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Aaron Passey <aaronp@ngwee.ugcs.caltech.edu>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] SH1 port of eCos
Date: Thu, 11 Jan 2001 13:02:00 -0000	[thread overview]
Message-ID: <20010111210214.EC92CCC001@ngwee.ugcs.caltech.edu> (raw)

Hi,

I just thought I would let everybody know that I have started working on an
SH1 port of eCos.  If anybody else is working on such a port, please let me
know and we can hopefully work together.  Assuming my port works, I have no
problem contributing it back.

Now to the meat of the issue.  hal/sh/arch/current/src/vector.S seems to
contain a lot of SH3 specific assembly which does not apply to the SH1 (or
SH2).  It has code in there dealing with the SH3's banked registers which
the SH1 and SH2 don't have, for example.  What's the best way to deal with
this?  Should all this code get moved to sh[34]/current/src/variant.S?

For the curious, my project is entirely for fun.  I am building "Laser
Tetris".  The plan is to play Tetris (or astroids or anything else that can
be reasonably done with vector graphics) on the wall using a couple of
galvos and a laser.  It's based around a board I designed that has a
Hitachi SH7032 SH1 processor, the usual RAM and ROM, and a couple of 16bit
DACs that drive the galvos (through a couple driver boards, of course).
All the hardware is built and tested (including drawing basic shapes on the
wall with the laser) and now I need to write the software.  Actually, all
my original software got wiped out in a harddrive crash so I thought I
would do it right this time and put a real OS on it (and maybe backup my
work by contributing it back to eCos!).

Oh, I'm not currently subscribed to eCos-discuss so I would appreciate
being cc'd on any replies.

Thanks,

Aaron

             reply	other threads:[~2001-01-11 13:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-11 13:02 Aaron Passey [this message]
2001-01-12  0:42 ` Jesper Skov
2001-01-15 15:49   ` Aaron Passey
2001-01-15 18:40     ` Jonathan Larmour
2001-01-15 20:10       ` Aaron Passey
2001-01-15 23:55     ` Jesper Skov

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=20010111210214.EC92CCC001@ngwee.ugcs.caltech.edu \
    --to=aaronp@ngwee.ugcs.caltech.edu \
    --cc=ecos-discuss@sources.redhat.com \
    /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).