qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jordan Justen <jljusten@gmail.com>
To: Cristi Magherusan <Cristi.Magherusan@net.utcluj.ro>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Intel 440bx hardware emulation correctness
Date: Mon, 27 Jul 2009 10:43:48 -0700	[thread overview]
Message-ID: <2a50f7880907271043h621ebb8dif547e3966b503296@mail.gmail.com> (raw)
In-Reply-To: <1248626273.28944.3.camel@ufo>

Cristi,

My impression is that QEMU does not focus on strict hardware
emulation.  I think it would be counter-productive to (what I see as)
QEMU's main goals ... to emulate a functional system with good
performance.

It seems that the level of hardware compatibility is driven by
software dependencies.  Essentially, if an OS driver expects the
hardware to behave a certain way, then QEMU will emulate it to achieve
compatibility.

But, since the OS's do not generally know about SPD & configuring the
chipset memory, it is easier to ignore this completely in QEMU.

-Jordan

On Sun, Jul 26, 2009 at 9:37 AM, Cristi
Magherusan<Cristi.Magherusan@net.utcluj.ro> wrote:
> On Sun, 2009-07-26 at 14:35 +0300, Cristi Magherusan wrote:
>> Hello,
>>
>>
>> Does qemu aim to completely emulate the Intel 440bx northbridge hardware
>> (and maybe other) to detail, or instead does it on purpose skip some
>> parts for the sake of simplicity?
>>
>> As an example, I've seen that the RAM parameters are written in CMOS
>> instead of doing it using SPD and some RAM control registers, as
>> documented in the 440 datasheet.
>>
>> This only affects the BIOS code that does RAM detection, so the Bochs
>> BIOS code would also need to be changed accordingly.
>
> Actually, in fact I'm interested to find out wether there are other
> differences between qemu and a real 440bx-based motherboard, besides RAM
> detection.
>
> I'm asking because I'm willing to rewrite the coreboot qemu support code
> based on the generic northbridge/southbridge code.
>
> Thanks,
> Cristi
>
> --
> Ing. Cristi Măgherușan, System/Network Engineer
> Technical University of Cluj-Napoca, Romania
> http://cc.utcluj.ro  +40264 401247
>

      reply	other threads:[~2009-07-27 17:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-26 11:35 [Qemu-devel] Intel 440bx hardware emulation correctness Cristi Magherusan
2009-07-26 16:37 ` Cristi Magherusan
2009-07-27 17:43   ` Jordan Justen [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=2a50f7880907271043h621ebb8dif547e3966b503296@mail.gmail.com \
    --to=jljusten@gmail.com \
    --cc=Cristi.Magherusan@net.utcluj.ro \
    --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).