qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cristi Magherusan <Cristi.Magherusan@net.utcluj.ro>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Intel 440bx hardware emulation correctness
Date: Sun, 26 Jul 2009 19:37:53 +0300	[thread overview]
Message-ID: <1248626273.28944.3.camel@ufo> (raw)
In-Reply-To: <1248608109.15752.40.camel@ufo>

[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]

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

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-07-26 16:38 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 [this message]
2009-07-27 17:43   ` Jordan Justen

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=1248626273.28944.3.camel@ufo \
    --to=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).