public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: miguelon@tiscali.it
Cc: ecos-discuss@ecos.sourceware.org, andrew@lunn.ch
Subject: Re: [ECOS] AT91RM9200 chip select
Date: Tue, 15 Aug 2006 10:04:00 -0000	[thread overview]
Message-ID: <20060815100407.GA20506@lunn.ch> (raw)
In-Reply-To: <19869077.1155633747089.JavaMail.root@ps7>

> I finally found a package on the CVS repository 
> (packages/hal/arm/arm9/aaed2000/) which is similar to mine, at least as 
> for the MMU setup. As I understood from other threads the file which 
> has to be modified is /include/hal_platform_setup.h but in this case 
> the code calls a function (hal_mmu_init) to create MMU tables. I've 
> found the code for this function in /src/aaed2000_misc.c and actually 
> it defines a MMU table using the macro X_ARM_MMU_SECTION. The first 
> thing that comes into my head is to modify directly the source file 
> adding the mapping for my device but maybe there's a more elegant way 
> to do it. I hope to have provided all the information you need to help 
> me, I'm at the beginning with eCos. Thanks a lot.

It might be possible to call the X_ARM_MMU_SECTION macro in
"application" space. I've done with with the EBSA285 target when i
needed to map an external bus into memory. Doing it this way you have
less trouble in the future if eCosCentric gives you an update. No need
to move your patches between trees.

   Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2006-08-15 10:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-15  9:22 miguelon
2006-08-15 10:04 ` Andrew Lunn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-14 12:12 miguelon
2006-08-14 12:25 ` Andrew Lunn
2006-08-22  7:41 ` Daniel Morris
2006-08-14 11:53 pippo
2006-08-14 11:58 ` Gary Thomas

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=20060815100407.GA20506@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=miguelon@tiscali.it \
    /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).