public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Ben Wu <bwu@changind.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] editing  MLT files?
Date: Tue, 22 May 2007 23:30:00 -0000	[thread overview]
Message-ID: <46536D59.8000502@changind.com> (raw)
In-Reply-To: <46536A2A.6000407@mlbassoc.com>

Great, thank you.

On another note, in the course of migrating our ECOS 1.3.1 based Redboot 
to the newest ECOS sources, there is a configuration bit missing in 
SDRAM register definitions located the hal_ixp425.h chip header file.

#define SDRAM_CONFIG_64MB          (1 << 5)

That line exists in the 1.3.1 based hal_ixp425.h file that we have - I 
don't know if it was put in by one of our previous developers, but it is 
a valid configuration bit listed in the datasheet (that we require) and 
should logically located there. Who do I refer the fix request to?

Thanks.

-Ben




---------------------------
Ben Wu
Design Engineer
email: bwu@changind.com
phone: (909) 596-7888
CHANG Industry, Inc.
1925 McKinley Ave. Suite F
La Verne, CA 91750


Gary Thomas wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Ben Wu wrote:
>> I'm creating a new board based of one of the XScale dev boards. I need
>> to modify the ECOS memory layout files, but there are nice big comments
>> saying :
>>
>> // This is a generated file - do not edit
>>
>> Can I safely ignore that comment if I'm only using using command line
>> tools? Is there a command line tool I should be using to generate the
>> files?
> 
> Yes, you can safely ignore this comment as the tools which manipulate
> the MLT files no longer exist.
> 
> n.b. the eCos sources and build system only use the .h and .ldi files
> 
> - --
> - ------------------------------------------------------------
> Gary Thomas                 |  Consulting for the
> MLB Associates              |    Embedded world
> - ------------------------------------------------------------
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
> 
> iD8DBQFGU2oqmaKbSsQGV8ARApSeAJ0cvbw3kqWF+4hL7OzQWx79t4h9JACdHQZP
> 54LdD+mk6gEh0nLsgps2WJk=
> =K/c9
> -----END PGP SIGNATURE-----
> 

-- 
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:[~2007-05-22 22:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-22 22:09 Ben Wu
2007-05-22 22:23 ` Gary Thomas
2007-05-22 23:30   ` Ben Wu [this message]
2007-05-22 23:51     ` 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=46536D59.8000502@changind.com \
    --to=bwu@changind.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=gary@mlbassoc.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).