From: "jiang jet" <jetjiang@hotmail.com>
To: deerxiaolu@gmail.com
Cc: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] RE: how to check my modifications to the kernel without a board? size=100 maxlength=80 style=
Date: Fri, 15 Jun 2007 08:59:00 -0000 [thread overview]
Message-ID: <BAY137-F32249290DE090097933CDDDF1F0@phx.gbl> (raw)
In-Reply-To: <b48951870706140804w102664ffx6bc692e5403fb4c2@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb2312; format=flowed, Size: 1373 bytes --]
>From: "xiaolu zhao" <deerxiaolu@gmail.com>
>To: "jiang jet" <jetjiang@hotmail.com>, ecos-discuss@ecos.sourceware.org
>Subject: how to check my modifications to the kernel without a
board?>Date: Thu, 14 Jun 2007 17:04:05 +0200
>
>Hi, I met a big problem, would you like to give me some advices?
>
>I did some modifications to the ecos Kernel code(like in sched.cxx,
>thread.hxx etc.). But I have no a real hardware board. So I want to
>use VMware as a virtual machine to see the results.Is it possible?
>
Redboot just uses the same hal layer as ecos, so it is sure possible
>I tried the redbbot on the Vmware and the "hello.c" example works.
>But
>after I modified the kernel code and rebuild the ecos using the
>configtool, it did not give any compilation complaints. I know it is
>impossible, there should be a lot of errors in the code. Does
>Redbbot
>have nothing to do with the ecos kernel files?
>
>If the redboot has nothing to do with the kernels, how can I check
>my
>modificaiton to the kernel files with VMare?
using test cases in ecos
>
>Thank you so much in advance!!!
_________________________________________________________________
Ãâ·ÑÏÂÔØ MSN Explorer: http://explorer.msn.com/lccn/
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
parent reply other threads:[~2007-06-14 23:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <b48951870706140804w102664ffx6bc692e5403fb4c2@mail.gmail.com>]
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=BAY137-F32249290DE090097933CDDDF1F0@phx.gbl \
--to=jetjiang@hotmail.com \
--cc=deerxiaolu@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).