public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "Robert Cragie" <rcc@jennic.com>
To: "Evgeny Belyanco" <esp1@kbkcc.ru>,
		"pintu mehta" <pintumehta@gmail.com>,
		<ecos-discuss@ecos.sourceware.org>
Cc: <sid@sources.redhat.com>
Subject: RE: Re[2]: kernel massage through sid simulator
Date: Fri, 14 Jul 2006 14:00:00 -0000	[thread overview]
Message-ID: <NMEDLDELHPEFHOMFIJBHOEHDELAA.rcc@jennic.com> (raw)
In-Reply-To: <1319782642.20060714174222@kbkcc.ru>

I think Pintu Mehta has the wrong idea about SID. SID is a hardware platform
emulator on which you run whatever executables will run on the target. This
may be eCos, which in turn may be running a multi-tasking application. Or it
may be uClinux, or just a simple embedded application which does not use an
operating system at all.

Therefore SID itself does not produce 'kernel messages'. If it were running
Linux, and there was a clearly assigned terminal on the platform to which
kernal messages are emitted, it is there you would see the kernel messages.
Any 'drives' would also have to be emulated in the SID environment.

I'm not sure what Pintu Mehta is trying to achieve but it might also be
worth looking at Bochs (http://bochs.sourceforge.net/) or if he is wanting a
platform for eCos, the synthetic linux target or even the straight i386
target for eCos.

Robert Cragie, Design Engineer
_______________________________________________________________
Jennic Ltd, Furnival Street, Sheffield, S1 4QT,  UK
http://www.jennic.com  Tel: +44 (0) 114 281 2655
_______________________________________________________________


> -----Original Message-----
> From: sid-owner@sourceware.org [mailto:sid-owner@sourceware.org]On
> Behalf Of Evgeny Belyanco
> Sent: 14 July 2006 14:42
> To: pintu mehta; ecos-discuss@ecos.sourceware.org
> Cc: sid@sources.redhat.com
> Subject: Re[2]: kernel massage through sid simulator
>
>
> Friday, July 14, 2006, 4:09:41 PM, you wrote:
>
> pm>   thanks for that. i got all useful information . ..about kernel
> pm> massages??...i mean to say massages that a typical Boot Up sequence
> pm> involves so i can able to see
> pm>   display a message on the screen for each drive/memory they detect
> pm> and configure. .. i m linux programmer but new in this field.
> pm> ..one more things ..i used following command for my hello.c program &
> pm> i find out hello.c.config file ...what is this inside config file.
>
> pm> arm-elf-sid --no-run --sidrtc=0xe0000000 hello.c
>
> I think, you need
>
> eCos doc
> http://ecos.sourceware.org/docs.html
>
> eCos list
> http://ecos.sourceware.org/intouch.html
>
> SID list
> http://sourceware.org/sid/
> http://sourceware.org/ml/sid/
>
> Evgeny Belyanko
> **********************************
> * E-mail: ea@kbkcc.ru
> **********************************
>

      reply	other threads:[~2006-07-14 14:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b186d0580607132202r140117f2uc7564d7b9bfd54e4@mail.gmail.com>
2006-07-14 10:06 ` Evgeny Belyanco
     [not found]   ` <b186d0580607140509t7a5d7defmb72c53022392a963@mail.gmail.com>
2006-07-14 13:45     ` Re[2]: " Evgeny Belyanco
2006-07-14 14:00       ` Robert Cragie [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=NMEDLDELHPEFHOMFIJBHOEHDELAA.rcc@jennic.com \
    --to=rcc@jennic.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=esp1@kbkcc.ru \
    --cc=pintumehta@gmail.com \
    --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).