qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Natalia Portillo" <claunia@claunia.com>
To: blp@cs.stanford.edu, qemu-devel@nongnu.org
Subject: RE: [Qemu-devel] Re: BIOS behaves different as real BIOS
Date: Sat, 17 Jul 2004 08:04:30 +0100	[thread overview]
Message-ID: <E1BljGw-0003aM-0e@lists.gnu.org> (raw)
In-Reply-To: <87u0w7ktx1.fsf@benpfaff.org>

Thanks it works.

Boots the floppy but seems that Xenix isn't supported xD.

Does this value in CMOS do anything in a real BIOS?
Where is it documented?

Regards 

> -----Mensaje original-----
> De: qemu-devel-bounces+iosglpgc=teleline.es@nongnu.org 
> [mailto:qemu-devel-bounces+iosglpgc=teleline.es@nongnu.org] 
> En nombre de Ben Pfaff
> Enviado el: sábado, 17 de julio de 2004 7:52
> Para: qemu-devel@nongnu.org
> Asunto: [Qemu-devel] Re: BIOS behaves different as real BIOS
> 
> "Natalia Portillo" <claunia@claunia.com> writes:
> 
> > Excuse me, where are the CMOS RAM values in qemu :? 
> 
> In hw/pc.c.  Add a line like
>         rtc_set_memory(s, 0x38, 1);
> to the end of cmos_init().
> 
> As far as I know there is currently no way to customize CMOS 
> without modifying source code.
> --
> "In this world that Hugh Heffner had made,  he alone seemed 
> forever bunnyless."
> --John D. MacDonald
> 
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel

  reply	other threads:[~2004-07-17  7:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-17  6:01 [Qemu-devel] BIOS behaves different as real BIOS Natalia Portillo
2004-07-17  6:40 ` [Qemu-devel] " Ben Pfaff
2004-07-17  6:45   ` Natalia Portillo
2004-07-17  6:51     ` Ben Pfaff
2004-07-17  7:04       ` Natalia Portillo [this message]
2004-07-17 15:47         ` Ben Pfaff
2004-07-17  7:12 ` [Qemu-devel] " Antony T Curtis
2004-07-17  8:20   ` Natalia Portillo

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=E1BljGw-0003aM-0e@lists.gnu.org \
    --to=claunia@claunia.com \
    --cc=blp@cs.stanford.edu \
    --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).