From: "Frank Ch. Eigler" <fche@redhat.com>
To: Mathieu Lacage <mathieu_lacage@realmagic.fr>
Cc: sid@sources.redhat.com
Subject: Re: running eCos under sid
Date: Wed, 14 Nov 2001 04:00:00 -0000 [thread overview]
Message-ID: <20011123080204.B9819@redhat.com> (raw)
In-Reply-To: <1006520035.9233.48.camel@mathieu>; from mathieu_lacage@realmagic.fr on Fri, Nov 23, 2001 at 01:53:55PM +0100
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
Hi -
On Fri, Nov 23, 2001 at 01:53:55PM +0100, Mathieu Lacage wrote:
: [...]
: If I understood how sid works, this means writing the components not
: available for the new board and writing a configuration file for the
: board connecting the relevant pieces together ?
That's right.
: [...]
: I'll try this later. As a side note, I do not even own an Integrator
: board
(Then you might find eCos' "pid" platform a more comfortable fit for
sid's provided components & configurations.)
: and my target system has nothing to do with traditional boards so
: I'll have to hack together a simulation environment myself anyway...
Good - you may find the sid manuals of use.
: [...]
: I'll keep you updated if I can manage to release some GPL code of our
: (not-yet-written) modules.
Even if you simply end up using some peculiar configurations of
existing models, it would be good to hear of them.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
WARNING: multiple messages have this Message-ID
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Mathieu Lacage <mathieu_lacage@realmagic.fr>
Cc: sid@sources.redhat.com
Subject: Re: running eCos under sid
Date: Fri, 23 Nov 2001 05:02:00 -0000 [thread overview]
Message-ID: <20011123080204.B9819@redhat.com> (raw)
Message-ID: <20011123050200.FzgAcRiX012CKPt-z5tRYdaRAht9O1BvChqhQgyVAq4@z> (raw)
In-Reply-To: <1006520035.9233.48.camel@mathieu>
Hi -
On Fri, Nov 23, 2001 at 01:53:55PM +0100, Mathieu Lacage wrote:
: [...]
: If I understood how sid works, this means writing the components not
: available for the new board and writing a configuration file for the
: board connecting the relevant pieces together ?
That's right.
: [...]
: I'll try this later. As a side note, I do not even own an Integrator
: board
(Then you might find eCos' "pid" platform a more comfortable fit for
sid's provided components & configurations.)
: and my target system has nothing to do with traditional boards so
: I'll have to hack together a simulation environment myself anyway...
Good - you may find the sid manuals of use.
: [...]
: I'll keep you updated if I can manage to release some GPL code of our
: (not-yet-written) modules.
Even if you simply end up using some peculiar configurations of
existing models, it would be good to hear of them.
- FChE
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7/kjMVZbdDOm/ZT0RAlkgAJ0dgykI1mdBarsGsqDBX0wjoVgGrACff+6n
Gi+hZcdzLmXl00ZagRuhaSc=
=xek7
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2001-11-23 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 14:00 Mathieu Lacage
2001-11-14 0:14 ` Frank Ch. Eigler
2001-11-14 3:43 ` Mathieu Lacage
2001-11-14 4:00 ` Frank Ch. Eigler [this message]
2001-11-23 5:02 ` Frank Ch. Eigler
2001-11-23 4:53 ` Mathieu Lacage
2001-11-23 4:30 ` Frank Ch. Eigler
2001-11-23 1:31 ` Mathieu Lacage
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=20011123080204.B9819@redhat.com \
--to=fche@redhat.com \
--cc=mathieu_lacage@realmagic.fr \
--cc=sid@sources.redhat.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).