public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS]  Re: Building redboot with eCos Kernel
Date: Wed, 31 May 2006 03:09:00 -0000	[thread overview]
Message-ID: <e5j1c7$b14$1@sea.gmane.org> (raw)
In-Reply-To: <20060531001355.CGIS2009.tomts10-srv.bellnexxia.net@smtp1.sympatico.ca>

On 2006-05-31, Andre-John Mas <ajmas@sympatico.ca> wrote:

> Is it accepted to include the ecos kernel in a redboot image?

No, I don't think so.  At least I've never heard of that being
done, and based on what I know of things I don't think it can
work.  Redboot is purely a "mainloop" type polling application,
and the the eCos kernel requires interrupts be enabled.

> I am working on some existing code for my company and when the
> kernel is included in the boot we have trouble debugging. What
> happens, is when we connect using gdm the application gets
> sent, but stalls. The serial connection then stalls and then
> timesout.
>
> Any idea?

What are you trying to accomplish by including the eCos Kernel
in RedBoot?

-- 
Grant Edwards                   grante             Yow!  Is something VIOLENT
                                  at               going to happen to a
                               visi.com            GARBAGE CAN?


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

  reply	other threads:[~2006-05-31  3:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-31  0:14 [ECOS] " Andre-John Mas
2006-05-31  3:09 ` Grant Edwards [this message]
2006-06-01  1:51   ` [ECOS] " André-John Mas
  -- strict thread matches above, loose matches on Subject: below --
2004-05-21 15:03 [ECOS] Re: building redboot with eCos kernel Savin Zlobec
2004-05-21 16:18 ` Nick Garnett

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='e5j1c7$b14$1@sea.gmane.org' \
    --to=grante@visi.com \
    --cc=ecos-discuss@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).