linux-8086.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Marc-F. LUCCA-DANIAU" <mfld.fr@gmail.com>
To: ELKS <Linux-8086@Vger.Kernel.Org>
Subject: Starting ELKS in EMU86
Date: Fri, 27 May 2016 16:19:42 +0200	[thread overview]
Message-ID: <5748577E.4010909@gmail.com> (raw)

A kind of POC... and much work remaining :-)

MFLD


/home/mfld/advantech/dev86/emu86 $ ./emu86 -w 0xe0000 -f 
../../elks/elks/arch/i86/Image -x 0xe000:0x42 -i
info: load address E0000h
info: load file ../../elks/elks/arch/i86/Image
info: file size=10000h
success: file loaded
info: execute address E000h:0042h
info: PTS for serial emulation: /dev/pts/2

AX 0000  BX 0000  CX 0000  DX 0000  FL 0000
SI 0000  DI 0000  SP 0000  BP 0000
DS 0000  ES 0000  SS 0000  CS E000  IP 0042

CF 0  PF 0  AF ?  ZF 0  SF 0  TF ?  IF 0  DF 0  OF 0

E000:0042  B8 60 00           MOV     AX,0060h

 >g
warning: INT3


/home/mfld/advantech/dev86/emu86 $ ./pcat `cat emu86.pts`
Loading kernel image...
C
onsole: BIOS 80x25 emulating ANSI (3 virtual consoles)
PC/XT class machine, NEC V20 CPU
512K base RAM.
ELKS kernel (39008 text + 4168 data + 48648 bss)
Kernel text at e062:0000, data at 90:0000
458 K of memory for user processes.
ELKS network sockets
TCP/IP stack by Harry Kalogirou
ELKS version 0.2.0

panic: VFS: Unable to mount root fs on FFFF

apparent call stack:
Line: Addr    Parameters
~~~~: ~~~~    ~~~~~~~~~~
    0: 1D59 => 0000 7102 0000 0000 0000 0000 0000
    1: 00B7 => 0000 0000 0000 0000 0000 0000 0000
    2: 0000 => CE50 0000 0000 0001 0000 6166 6C69
    3: 1048 => 0000 0000 0000 0000 0000 0000 0000
    4: 0000 => CE50 0000 0000 0001 0000 6166 6C69
    5: 1048 => 0000 0000 0000 0000 0000 0000 0000
    6: 0000 => CE50 0000 0000 0001 0000 6166 6C69
    7: 1048 => 0000 0000 0000 0000 0000 0000 0000
    8: 0000 => CE50 0000 0000 0001 0000 6166 6C69

SYSTEM LOCKED - Press CTRL-ALT-DEL to reboot:




                 reply	other threads:[~2016-05-27 14:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5748577E.4010909@gmail.com \
    --to=mfld.fr@gmail.com \
    --cc=Linux-8086@Vger.Kernel.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).