qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Insert module into kernel
Date: Wed, 12 Jul 2006 14:36:25 +0100	[thread overview]
Message-ID: <200607121436.26998.paul@codesourcery.com> (raw)
In-Reply-To: <20060712131515.966.qmail@web38102.mail.mud.yahoo.com>

On Wednesday 12 July 2006 14:15, Tieu Ma Dau wrote:
> Hi all,
>  I want to simulate the ARM system and add a simple simulated device with
> its corresponding module device driver. So: 
> 1. I must run the command "insmod" to insert this module into kernel. 
> But there is not this command in the ARM Linux shell
> 2. I must run the command "mknod" to make a file 
> (exp: /dev/my_simulated_device) corresponding to the simulated device. But
> this command is not run because the "read only" property of file system.
> 3. I must make a small program in which I open the file by the command
> "fopen("/dev/my_simulated_device","w")" but I think that I have the problem
> as in the question 2 Do you have any idea?

None of these problems have anything to do with qemu.  They are problems with 
your root FS. Qemu works exactly the same way as a real Arm machine.

The arm_test image on the qemu website is a minimal cut-down test/demo system. 
It is not not intended to be a full general purpose linux system. Sounds like 
you need to get yourself a proper linux install. The Debian installers work 
pretty much out the box.

If you already are using a different linux distro, you need to contact whoever 
supplied it.

Paul

  reply	other threads:[~2006-07-12 13:36 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 18:11 [Qemu-devel] QEMU GUI Fabrice Bellard
2006-06-21 19:42 ` Mike Kronenberg
2006-06-22 19:32   ` gbeauchesne
2006-06-22 19:32   ` gbeauchesne
2006-06-28 23:03     ` Joe Lee
2006-06-29 13:19       ` Daniel P. Berrange
2006-06-29 21:05         ` Joe Lee
2006-06-29 21:47           ` Daniel P. Berrange
2006-06-22 15:06 ` Luca Barbato
2006-07-01 22:47   ` Chris Wilson
2006-07-05 20:51     ` Luca Barbato
2006-07-08  2:14       ` Chris Wilson
2006-07-08  2:46         ` Johannes Schindelin
2006-07-08  6:34           ` M. Warner Losh
2006-07-08 14:34             ` wxWidgets and C: was " Jim C. Brown
2006-07-08 15:02               ` Joe Lee
2006-07-08 15:13                 ` Jim C. Brown
2006-07-08 16:34                   ` Kevin F. Quinn
2006-07-08 21:26               ` Oliver Gerlich
2006-07-10  0:03                 ` John R.
2006-07-10  0:10                   ` Jim C. Brown
2006-07-11  7:44                   ` David Fraser
2006-07-11 12:40                     ` Jason Gress
2006-07-11 13:17                       ` Linas Žvirblis
2006-07-11 14:52                         ` Oliver Gerlich
2006-07-11 15:29                           ` Linas Žvirblis
2006-07-12  8:17         ` Luca Barbato
2006-07-12 13:15           ` [Qemu-devel] Insert module into kernel Tieu Ma Dau
2006-07-12 13:36             ` Paul Brook [this message]
2006-07-13  8:11               ` Tieu Ma Dau
2006-06-22 15:18 ` [Qemu-devel] QEMU GUI Christian MICHON
2006-06-30 10:28   ` Dan Sandberg
2006-06-22 21:50 ` Anthony Liguori
2006-06-23  0:18   ` Kevin F. Quinn
2006-06-23  1:53     ` Anthony Liguori
2006-06-23  7:17       ` Kevin F. Quinn

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=200607121436.26998.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.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 NNTP newsgroup(s).