qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: Laurent Vivier <Laurent.Vivier@bull.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2][UPDATE] Add arg -drive to define new drive with more features
Date: Mon, 12 Nov 2007 18:44:37 +0200	[thread overview]
Message-ID: <f43fc5580711120844t6b574c08j847a99e0193598be@mail.gmail.com> (raw)
In-Reply-To: <11948799213737@bull.net>

On 11/12/07, Laurent Vivier <Laurent.Vivier@bull.net> wrote:
> It also defines the default interface type to "scsi" for targets
> "realview", "SS-5", "SS-10", "versatilepb", "versatileab"
> to keep old behavior, where "-hda" is a SCSI disk.

For maximal compatibility, I'd like the following mappings for SS-5,
SS-10, and SS-600MP:
-hda = SCSI ID 0
-hdb = SCSI ID 1
-hdc = -cdrom = SCSI ID 2
-hdd = SCSI ID 3
There is no bus 1, only 0. Maybe a warning should be issued for bus=1.

I didn't find where this was implemented, so is the above in line with
the patch?

> Index: qemu/hw/sun4m.c

> -    if (hwdef->fd_base != (target_phys_addr_t)-1)
> -        sun4m_fdctrl_init(slavio_irq[hwdef->fd_irq], hwdef->fd_base, fd_table);
> +    if (hwdef->fd_base != (target_phys_addr_t)-1) {
> +        for(i = 0; i < MAX_FD; i++) {
> +            index = drive_get_index(IF_FLOPPY, 0, i);
> +            if (index != -1)
> +                fd[i] = drives_table[index].bdrv;
> +            else
> +                fd[i] = NULL;
> +        }
> +
> +        sun4m_fdctrl_init(slavio_irq[hwdef->fd_irq], hwdef->fd_base, fd);
> +    }

This is broken, there are zero or one floppy drives, never more.

> Index: qemu/hw/sun4u.c

> -    floppy_controller = fdctrl_init(NULL/*6*/, 2, 0, 0x3f0, fd_table);
> +    for(i = 0; i < MAX_FD; i++) {
> +        index = drive_get_index(IF_FLOPPY, 0, i);
> +       if (index != -1)
> +           fd[i] = drives_table[index].bdrv;
> +       else
> +           fd[i] = NULL;
> +    }
> +    floppy_controller = fdctrl_init(NULL/*6*/, 2, 0, 0x3f0, fd);

I think same applies here (0 to 1 drives), but as the hardware is
PC-like, technically it may be possible that someone could replace the
cables and insert additional floppy drives.

  reply	other threads:[~2007-11-12 16:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-12 15:05 [Qemu-devel] [PATCH 0/2][UPDATE] Add "-drive" parameter Laurent Vivier
2007-11-12 15:05 ` [Qemu-devel] [PATCH 1/2][UPDATE] remove unused parameters from QEMUMachineInitFunc Laurent Vivier
2007-11-12 15:05   ` [Qemu-devel] [PATCH 2/2][UPDATE] Add arg -drive to define new drive with more features Laurent Vivier
2007-11-12 16:44     ` Blue Swirl [this message]
2007-11-12 16:53       ` Laurent Vivier
2007-11-13 16:02       ` Laurent Vivier
2007-11-13 20:50         ` Blue Swirl
2007-11-13 21:22           ` Laurent Vivier
2007-11-12 16:23   ` [Qemu-devel] [PATCH 1/2][UPDATE] remove unused parameters from QEMUMachineInitFunc Blue Swirl
2007-11-12 16:36     ` Laurent Vivier
2007-11-12 17:14       ` Laurent Vivier

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=f43fc5580711120844t6b574c08j847a99e0193598be@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=Laurent.Vivier@bull.net \
    --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).