This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: redboot info threads problem
- Subject: Re: [ECOS] redboot info threads problem
- From: Hugo Tyson <hmt at redhat dot com>
- Date: 07 Dec 2000 12:32:53 +0000
- Cc: Andrew Lunn <andrew dot lunn at ascom dot ch>, eCos Disuss <ecos-discuss at sourceware dot cygnus dot com>
- Newsgroups: cygnus.project.ecc.redboot
- Posted-To: cygnus.project.ecc.redboot
- References: <20001207123451.I7689@biferten.ma.tech.ascom.ch> <20001207125137.A7817.cygnus.project.ecc.redboot@biferten.ma.tech.ascom.ch>
The following message is a courtesy copy of an article
that has been posted to cygnus.project.ecc.redboot as well.
andrew.lunn@ascom.ch (Andrew Lunn) writes:
> > I can send you [privately] a RedBoot to try which I built here, just to
> > verify that the thread stuff works as expected.
>
> Thats not so interesting for me. What i want to do is extend redboot to
> include the kernel so i can give it much more functionality.
I have to interject: Andrew, if this is related to the issues with using
code that has mutexes &c in, in RedBoot, without starting the kernel, that
we've discussed elsewhere and that I suspect may be contributing to
problems with the thread debugging, I'd like to restate this recommendation
for the list:
Don't put the kernel in RedBoot. Use the device driver kernel API for
doing synchronization. That's what it's for (OK, maybe it's misnamed.)
That way you'll be able to use the same sources with safe no-ops for
synchronization primitives, compiled for running in both a single-context
boot ROM sans kernel, or in a threaded application.
OTOH, what functionality is it you want in RedBoot that needs the kernel?
- Huge