public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Fabrice Gautier <Fabrice_Gautier@sdesigns.com>
To: 'Jonathan Larmour' <jifl@eCosCentric.com>,
	"Gary D. Thomas" <gary.thomas@mind.be>
Cc: "Ecos-List (E-mail)" <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] memory maps
Date: Thu, 30 Jan 2003 06:05:00 -0000	[thread overview]
Message-ID: <9F77D654ED40B74CA79E5A60B97A087B0423F2@sd-exchange.sdesigns.com> (raw)

Yep,

I was thinking of making a simple perl script to do it. Thats quite simple
for the .h file but not so simple for the .ldi file.

Also i noticed there are some things impossible to do with the configuration
tool.
In particular one cannot place a not relocated section just after the
initial place of  a relocated section.  If you try to do it, it will always
place itself after the final place of the relocated section. (That can be
usefull if you want to add a file at the end of your rom image and access
the file using a user defined section name...)

-- 
Fabrice Gautier, 
Fabrice_Gautier@sdesigns.com


> -----Original Message-----
> From: Jonathan Larmour [mailto:jifl@eCosCentric.com]
> Sent: Wednesday, January 29, 2003 4:53 PM
> To: Gary D. Thomas
> Cc: Fabrice Gautier; Ecos-List (E-mail)
> Subject: Re: [ECOS] memory maps
> 
> 
> Gary D. Thomas wrote:
> > On Wed, 2003-01-29 at 16:36, Fabrice Gautier wrote:
> > 
> >>Hi,
> >>
> >>Is there any other tool than the config tool v1.3 than can 
> generate the
> >>mlt_xxx.ldi and mlt_xxx.h files from a .mlt files?  I know 
> its not yet in
> >>CT2, but is there a command line tool for that ? I think 
> not, but just want
> >>to make sure.
> > 
> > 
> > Sadly, no.  I just edit them by hand - it's not too hard.
> 
> But unfortunately error-prone (whoever does it). I'm dreading 
> the breakage 
> when we eventually get a new MLT and regenerate the .ldi/.h files!
> 
> The MLT is AFAIK the only missing feature of the config tool 
> v2 and we'd 
> really like it to be there (or especially someone to pay for it!).
> 
> Ideally we could move to a more user-readable format and make 
> it work with 
> the CLUI tools too at the same time.
> 
> Jifl
> -- 
> eCosCentric       http://www.eCosCentric.com/       
> <info@eCosCentric.com>
> --[ "You can complain because roses have thorns, or you ]--
> --[  can rejoice because thorns have roses." -Lincoln   ]-- 
> Opinions==mine
> 

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

             reply	other threads:[~2003-01-30  3:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-30  6:05 Fabrice Gautier [this message]
2003-01-30  6:10 ` Jonathan Larmour
  -- strict thread matches above, loose matches on Subject: below --
2007-12-07 17:11 hong zhang
2007-12-07 17:29 ` Gary Thomas
2007-12-07 18:18   ` hong zhang
2003-01-30 19:55 Fabrice Gautier
2003-01-30 21:38 ` Jonathan Larmour
2003-01-29 23:37 Fabrice Gautier
2003-01-30  0:53 ` Gary D. Thomas
2003-01-30  3:49   ` 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=9F77D654ED40B74CA79E5A60B97A087B0423F2@sd-exchange.sdesigns.com \
    --to=fabrice_gautier@sdesigns.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=gary.thomas@mind.be \
    --cc=jifl@eCosCentric.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).