qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Jordan Justen <jljusten@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ISA BIOS mapping for system flash emulation
Date: Thu, 01 Nov 2012 07:57:39 +0100	[thread overview]
Message-ID: <50921D63.9@web.de> (raw)
In-Reply-To: <CAFe8ug8+cNg413VUa3yiiWM=-K5qqbMQ=HK21B5jtREd8Pk7XA@mail.gmail.com>

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

On 2012-11-01 03:55, Jordan Justen wrote:
> On Tue, Oct 30, 2012 at 11:14 PM, Jan Kiszka <jan.kiszka@web.de> wrote:
>> Hi Jordan,
>>
>> I was starring at pc_isa_bios_init and wondering why you are creating a
>> copy of the system flash for the low ISA range instead of using an alias
>> here as well, just like old_pc_system_rom_init does. That means the ISA
>> BIOS range can run out of sync when the system flash is updated during
>> runtime and requires a restart of QEMU then. Switching to an alias would
>> also allow some code consolidation. Can you explain the idea behind the
>> current version?
> 
> I'm pretty sure I tried this and found that it did not work on the flash device.
> 
> I wrote an email to the list on Oct 17, 2011 about this, but I didn't
> get a response. (Re: [Qemu-devel] [PATCH 2/4] pc: Support system flash
> memory with pflash)

Can you be more specific how/when it failed? A trivial test cannot
confirm this so far.

Jan



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

  reply	other threads:[~2012-11-01  6:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31  6:14 [Qemu-devel] ISA BIOS mapping for system flash emulation Jan Kiszka
2012-11-01  2:55 ` Jordan Justen
2012-11-01  6:57   ` Jan Kiszka [this message]
2012-11-01 16:13     ` Jordan Justen
2012-11-01 16:28       ` Jan Kiszka

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=50921D63.9@web.de \
    --to=jan.kiszka@web.de \
    --cc=jljusten@gmail.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).