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: What device for ROMFS ?
Date: Mon, 23 May 2016 19:09:07 +0200	[thread overview]
Message-ID: <57433933.9070907@gmail.com> (raw)

Hello,

In a few words: what is the device to be used for a ROMFS root ?

More: I configured ELKS as a ROM image for an embedded system, and I run 
it under EMU86, but I cannot figure out:

1- how to tell ELKS to read the ROMFS superblock from ROM address space?
2- how to build a ROMFS image to put in the ROM address space?

All my tries end up with the well known:

$ ./emu86 -w 0xe0000 -f ../../elks/elks/arch/i86/Image -x 0xe000:0x42 -i

$ ./pcat `cat emu86.pts`
Loading kernel image...
Console: BIOS 10x115 emulating ANSI (3 virtual consoles)
PC/AT class machine, inode! CPU8308K base RAM, CPUID `nd socket for in'.
ELKS kernel (39008 text + 4168 data + 48648 bss)
Kernel text at e062:0000, data at 90:0000 62 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 206D
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:

Any suggestion ?

Thanks,

MFLD


             reply	other threads:[~2016-05-23 17:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-23 17:09 Marc-F. LUCCA-DANIAU [this message]
2016-05-23 23:07 ` What device for ROMFS ? Juan Perez-Sanchez
     [not found]   ` <5746A3A6.7010002@gmail.com>
2016-05-26  7:22     ` Marc-François LUCCA-DANIAU
     [not found]       ` <CAMKR1yu1nyCysPrwTubBF8VBBOJ_4u6vSQnD7R7h_nMmJeOfWg@mail.gmail.com>
2016-05-26 12:11         ` Marc-François LUCCA-DANIAU
2016-05-26 12:33           ` One Thousand Gnomes
2016-05-26 22:36     ` Juan Perez-Sanchez
2017-01-22 10:48       ` Marc-F. LUCCA-DANIAU
2017-01-22 13:23         ` Marc-François LUCCA-DANIAU
     [not found] <CACpuWUnkJ01bXDfTCSPS5_VfWHL+gca9=pixfM-YGG+_Mnob5A@mail.gmail.com>
2017-01-23 19:48 ` Marc-F. LUCCA-DANIAU

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=57433933.9070907@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).