From: "Lewin A.R.W. Edwards" <larwe@larwe.com>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] More information on crash with CVS sources
Date: Thu, 15 Feb 2001 06:31:00 -0000 [thread overview]
Message-ID: <4.3.2.7.2.20010215092653.00bf16e0@larwe.com> (raw)
In-Reply-To: <3A8AFDB3.BDF179C7@redhat.com>
Hi Jonathan (and Gary),
>There is stuff in the CYGPKG_LIBC_STARTUP package to do this for you - it
>provides a default cyg_user_start() that will create (and resume) a thread
>that will call main(). This differs from v1.3.1 because this used to happen
Once I upgraded to redboot on the host, then main() started getting called
again, so that is OK. I need to do some more reading. I don't fully
understand yet how to compile the current version to work with stubs (as I
think I don't want to use redboot). I'm also getting close to the point
where I will have real hardware, so I'll need to port it.
The reason I've been working on several things at once is to get a feel of
how large the app will wind up, so that I could get my ROM and RAM budgets.
The networking layer takes up a vast amount of RAM, I'd like to try
decreasing that if I can.
I also need to read more on the network layer to better understand how it
all fits together (networking internals are not my forte).
Thanks for all the help; at the moment the ball is in my court and I have a
lot I can do without bothering you guys on the list :)
=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/
"Und setzet ihr nicht das Leben ein,
Nie wird euch das Leben gewonnen sein."
prev parent reply other threads:[~2001-02-15 6:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 12:42 Lewin A.R.W. Edwards
2001-02-13 17:34 ` Jonathan Larmour
2001-02-13 20:38 ` Lewin A.R.W. Edwards
2001-02-14 13:50 ` Jonathan Larmour
2001-02-15 6:31 ` Lewin A.R.W. Edwards [this message]
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=4.3.2.7.2.20010215092653.00bf16e0@larwe.com \
--to=larwe@larwe.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=jlarmour@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).