From: SEBASTIEN ANDRE <sebastien.andre@sxb.bsf.alcatel.fr>
To: egcs@cygnus.com
Cc: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] MLT structure files
Date: Wed, 11 Jul 2001 00:17:00 -0000 [thread overview]
Message-ID: <3B4BFD6A.E867CB9A@sxb.bsf.alcatel.fr> (raw)
In-Reply-To: <2253171AF143D21185A60000F8FA748B02DA4E33@pluto.combitech.se>
I need to adjust the memoty layout of the reference board PID for our custom
board !!
Si i try to edit mlt files and h files in pkgconf !! but
i don't have exactly structure of it and i don't know sense of all values !!
I'm under linux host developpement and if someone can give me the scheme of
theses
files i appreciate it !! or a tool under linux that can generate easily these
files.
I find on redhat home site structure of CDL files but not for MLT :-(
Thx a lot
best regards.
Sebastien.
next prev parent reply other threads:[~2001-07-11 0:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 0:01 [ECOS] Serial problem on EB40 Daniel.Andersson
2001-07-11 0:17 ` SEBASTIEN ANDRE [this message]
2001-07-11 10:57 ` [ECOS] MLT structure files Jonathan Larmour
2001-07-11 0:21 ` [ECOS] Serial problem on EB40 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=3B4BFD6A.E867CB9A@sxb.bsf.alcatel.fr \
--to=sebastien.andre@sxb.bsf.alcatel.fr \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=egcs@cygnus.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).