qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Hrdina <phrdina@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: kwolf@redhat.com, pbonzini@redhat.com,
	Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 1/3] fdc: floppy drive should be visible after start without media
Date: Tue, 05 Jun 2012 14:32:53 +0200	[thread overview]
Message-ID: <4FCDFC75.4010906@redhat.com> (raw)
In-Reply-To: <m3hauq7ylh.fsf@blackfin.pond.sub.org>

On 06/05/2012 02:05 PM, Markus Armbruster wrote:
> Marcelo Tosatti<mtosatti@redhat.com>  writes:
>
>> On Tue, Jun 05, 2012 at 08:23:53AM +0200, Markus Armbruster wrote:
>>> Marcelo Tosatti<mtosatti@redhat.com>  writes:
>>>
>>>> On Thu, May 24, 2012 at 11:02:28AM +0200, Pavel Hrdina wrote:
>>>>> If you start guest with floppy drive but without media inserted, guest
>>>>> still should see floppy drive pressent.
>>>>>
>>>>> Signed-off-by: Pavel Hrdina<phrdina@redhat.com>
>>>>> ---
>>>>>   hw/pc.c |    2 +-
>>>>>   1 files changed, 1 insertions(+), 1 deletions(-)
>>>>>
>>>>> diff --git a/hw/pc.c b/hw/pc.c
>>>>> index 4d34a33..967c17a 100644
>>>>> --- a/hw/pc.c
>>>>> +++ b/hw/pc.c
>>>>> @@ -382,7 +382,7 @@ void pc_cmos_init(ram_addr_t ram_size, ram_addr_t above_4g_mem_size,
>>>>>       if (floppy) {
>>>>>           fdc_get_bs(fd, floppy);
>>>>>           for (i = 0; i<  2; i++) {
>>>>> -            if (fd[i]&&  bdrv_is_inserted(fd[i])) {
>>>>> +            if (fd[i]) {
>>>>>                   bdrv_get_floppy_geometry_hint(fd[i],&nb_heads,&max_track,
>>>>>                                                 &last_sect, FDRIVE_DRV_NONE,
>>>>>                                                 &fd_type[i],&rate);
>>>>> -- 
>>>> This commit breaks WinXP.32 installation. It crashes during early setup
>>>> stage, without a floppy disk specified.
>>>>
>>>> Specifying a floppy disk with -fda fixes the problem.
>>> Backtrace?
>> None, WinXP is spinning (presumably the floppy driver).
> Bummer.  Pavel, can you look into this?
Hi, I have just read this issue. Sure, I will look into.

  reply	other threads:[~2012-06-05 12:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24  9:02 [Qemu-devel] [PATCH v4 0/3] fdc: fix media handling Pavel Hrdina
2012-05-24  9:02 ` [Qemu-devel] [PATCH v4 1/3] fdc: floppy drive should be visible after start without media Pavel Hrdina
2012-06-05  2:54   ` Marcelo Tosatti
2012-06-05  6:23     ` Markus Armbruster
2012-06-05 10:05       ` Marcelo Tosatti
2012-06-05 12:05         ` Markus Armbruster
2012-06-05 12:32           ` Pavel Hrdina [this message]
2012-05-24  9:02 ` [Qemu-devel] [PATCH v4 2/3] fdc: fix media detection Pavel Hrdina
2012-05-24  9:02 ` [Qemu-devel] [PATCH v4 3/3] fdc-test: introduced qtest no_media_on_start and cmos qtest for floppy Pavel Hrdina
2012-05-25 16:24 ` [Qemu-devel] [PATCH v4 0/3] fdc: fix media handling Kevin Wolf

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=4FCDFC75.4010906@redhat.com \
    --to=phrdina@redhat.com \
    --cc=armbru@redhat.com \
    --cc=avi@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.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).