All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Eric Piel <Eric.Piel@lifl.fr>
Cc: "Màrius Montón" <Marius.Monton@uab.es>,
	linux-kernel@vger.kernel.org, mulix@mulix.org
Subject: Re: 'virtual HW' into kernel (SystemC)
Date: Wed, 07 Sep 2005 08:07:14 -0400	[thread overview]
Message-ID: <431ED7F2.5030200@pobox.com> (raw)
In-Reply-To: <431ED6DC.9040503@lifl.fr>

Eric Piel wrote:
> 09/07/2005 01:40 PM, Jeff Garzik wrote/a écrit:
>> No need for a set of tools.  As long as your SystemC simulator 
>> simulates an entire platform -- CPU, DRAM, etc. -- then you can boot 
>> Linux on the simulated platform.
>>
>> If you can boot Linux on the simulated platform, then you can easily 
>> develop a Linux driver long before real HW is available.
> 
> 
> No, this approach is not feasible because it would be require to 
> describe the entire computer in SystemC:

Correct.


> it's extremly complex to do

Not if you can reuse pre-existing parts from http://www.opencores.org/ 
and similar places.


> the simulation will be very slow.

Depends on your simulator ;-)


>  From what I understand Màrius tries to only simulate one component 
> (like a PCI card). As suggested Muli, a plugin to something like quemu 
> sounds like a good idea?

A plugin to qemu or Bochs should work, in theory.  In practice, neither 
are great for PCI MMIO or PCI DMA.

	Jeff



  reply	other threads:[~2005-09-07 12:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-07 10:31 'virtual HW' into kernel (SystemC) Màrius Montón
2005-09-07 11:40 ` Jeff Garzik
2005-09-07 11:54   ` Muli Ben-Yehuda
2005-09-07 12:02   ` Eric Piel
2005-09-07 12:07     ` Jeff Garzik [this message]
2005-09-07 13:26       ` Màrius Montón
2005-09-07 14:16 ` Benjamin LaHaise
2005-09-07 14:59   ` linux-os (Dick Johnson)
2005-09-07 15:12   ` Màrius Montón
2005-09-07 17:01 ` Alan Cox
     [not found] <BFECAF9E178F144FAEF2BF4CE739C66801B76517@exmail1.se.axis.com>
2005-09-07 16:38 ` Màrius Montón

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=431ED7F2.5030200@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=Eric.Piel@lifl.fr \
    --cc=Marius.Monton@uab.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mulix@mulix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.