From: "Meiring, H, Mnr <meiring@sun.ac.za>" <meiring@sun.ac.za>
To: <ecos-devel@ecos.sourceware.org>
Subject: Guidance porting AT91sam7
Date: Mon, 09 Apr 2007 12:11:00 -0000 [thread overview]
Message-ID: <FC829C66C7DA824A96A893C28F1B7AD969E88A@STBEVS01.stb.sun.ac.za> (raw)
Hi, I am attempting a port of an ATMEL AT91SAM7A2 uP.
The sam7s and sam7x ports seems the closest to what I need (but still = with quite a few differences).=20 With starting this port I would like some guidance in the format that = the port must be according to =93your=94 standards with regards to = directory structure and which layers to implement. The current structure = is as follows with my recommendations next to them: =20
ARM arch layer - great keep as is
AT91 var layer =96 this layer contains a lot of platform specific info = specifically for AT91SAM7 series (for instance in var_io.h ) =96 why = here, can=92t it be moved to the platform specific source (plf_io.h)? Or = shall I rather=20 say how must I approach this to get the anonymous sources changed? I = think it will make things more structured and when I want to port the =
AT91SAM7A2 series I only need to do platform changes and not variant = changes as well.
AT91SAM7S - How do you want the directory structure and why call the =
directory at91sam7s (and not at91sam7) when the x series is implemented = in it as well and the variant name it resides under is at91sam7=20 (CYGPKG_HAL_ARM_AT91SAM7). Now must the new port be made alongside the = at91sam7s platform or completely independent from the existing port? How = must this be done so that they will add the new port to the anonymous = cvs format wise etc?
Can anyone give me some guidance on how to attempt this specific port? =20
Regards
Hendrik Meiring
MScEng student at the University of Stellenbosch South Africa
next reply other threads:[~2007-04-09 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 12:11 Meiring, H, Mnr <meiring@sun.ac.za> [this message]
2007-04-09 12:40 ` Andrew Lunn
2007-04-09 15:10 ` Meiring, H, Mnr <meiring@sun.ac.za>
2007-04-10 10:18 ` Nick Garnett
2007-04-09 12:18 Meiring, H, Mnr <meiring@sun.ac.za>
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=FC829C66C7DA824A96A893C28F1B7AD969E88A@STBEVS01.stb.sun.ac.za \
--to=meiring@sun.ac.za \
--cc=ecos-devel@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).