From: Blue Swirl <blauwirbel@gmail.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kevin@koconnor.net, qemu-devel@nongnu.org, kvm@vger.kernel.org,
The OpenBIOS Mailinglist <openbios@openbios.org>
Subject: [Qemu-devel] Re: [PATCHv8 00/16] boot order specification
Date: Sat, 11 Dec 2010 18:59:18 +0000 [thread overview]
Message-ID: <AANLkTinBMWdLrtBOevq7Jc-1UNB834mDQ941ceqGKcy3@mail.gmail.com> (raw)
In-Reply-To: <20101211180223.GA7994@redhat.com>
2010/12/11 Gleb Natapov <gleb@redhat.com>:
> On Sat, Dec 11, 2010 at 05:19:01PM +0000, Blue Swirl wrote:
>> >> What should we do with
>> >> ata-2@600 vs drive@1?
>> > There is no available IDE OF binding spec, so I when with the way
>> > OpenBIOS reports ata on qemu-x86. I have no idea what 600 in ata-2@600
>> > may mean, but looking at g3_beige_300.html there is no such node there
>> > and looking at any other device tree in http://penguinppc.org/historical/dev-trees-html/
>> > I haven't found one that use this kind of addressing for pci-ata.
>> > http://penguinppc.org/historical/dev-trees-html/g3bw_400.html for
>> > instance has pci@80000000/pci-bridge@d/pci-ata@1/ata-4. ata-2@600 kind of
>> > addressing is used by devices on mac-io bus which I do not think we
>> > emulate in qemu. So it looks like OpneBIOS is wrong here.
>>
>> We have PMAC IDE, but this device is CMD646, so mac-io bus addressing
>> rules should not be used.
>>
> So you agree that OpenBIOS is wrong here?
I think so.
next prev parent reply other threads:[~2010-12-11 19:02 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 11:34 [Qemu-devel] [PATCHv8 00/16] boot order specification Gleb Natapov
2010-12-08 11:34 ` [Qemu-devel] [PATCHv8 01/16] Introduce fw_name field to DeviceInfo structure Gleb Natapov
2010-12-08 11:34 ` [Qemu-devel] [PATCHv8 02/16] Introduce new BusInfo callback get_fw_dev_path Gleb Natapov
2010-12-08 11:34 ` [Qemu-devel] [PATCHv8 03/16] Keep track of ISA ports ISA device is using in qdev Gleb Natapov
2010-12-08 11:34 ` [Qemu-devel] [PATCHv8 04/16] Add get_fw_dev_path callback to ISA bus " Gleb Natapov
2010-12-08 11:34 ` [Qemu-devel] [PATCHv8 05/16] Store IDE bus id in IDEBus structure for easy access Gleb Natapov
2010-12-08 11:34 ` [Qemu-devel] [PATCHv8 06/16] Add get_fw_dev_path callback to IDE bus Gleb Natapov
2010-12-08 11:35 ` [Qemu-devel] [PATCHv8 07/16] Add get_fw_dev_path callback for system bus Gleb Natapov
2010-12-08 11:35 ` [Qemu-devel] [PATCHv8 08/16] Add get_fw_dev_path callback for pci bus Gleb Natapov
2010-12-08 11:35 ` [Qemu-devel] [PATCHv8 09/16] Record which USBDevice USBPort belongs too Gleb Natapov
2010-12-08 11:35 ` [Qemu-devel] [PATCHv8 10/16] Add get_fw_dev_path callback for usb bus Gleb Natapov
2010-12-08 11:35 ` [Qemu-devel] [PATCHv8 11/16] Add get_fw_dev_path callback to scsi bus Gleb Natapov
2010-12-08 11:35 ` [Qemu-devel] [PATCHv8 12/16] Add bootindex parameter to net/block/fd device Gleb Natapov
2011-01-28 13:29 ` Markus Armbruster
2011-01-28 15:53 ` Gleb Natapov
2011-01-28 17:19 ` Markus Armbruster
2011-02-02 15:08 ` Markus Armbruster
2011-02-02 15:10 ` Gleb Natapov
2011-02-02 15:12 ` Gleb Natapov
2010-12-08 11:35 ` [Qemu-devel] [PATCHv8 13/16] Change fw_cfg_add_file() to get full file path as a parameter Gleb Natapov
2010-12-08 11:35 ` [Qemu-devel] [PATCHv8 14/16] Add bootindex for option roms Gleb Natapov
2010-12-08 11:35 ` [Qemu-devel] [PATCHv8 15/16] Add notifier that will be called when machine is fully created Gleb Natapov
2010-12-08 11:35 ` [Qemu-devel] [PATCHv8 16/16] Pass boot device list to firmware Gleb Natapov
2010-12-11 15:13 ` [Qemu-devel] Re: [PATCHv8 00/16] boot order specification Blue Swirl
2010-12-11 16:06 ` Gleb Natapov
2010-12-11 17:19 ` Blue Swirl
2010-12-11 18:02 ` Gleb Natapov
2010-12-11 18:27 ` Gleb Natapov
2010-12-11 19:06 ` Blue Swirl
2010-12-11 19:11 ` Gleb Natapov
2010-12-11 23:27 ` Benjamin Herrenschmidt
2010-12-11 18:59 ` Blue Swirl [this message]
2010-12-11 23:22 ` Benjamin Herrenschmidt
2010-12-14 19:59 ` Andreas Färber
2010-12-14 20:31 ` Benjamin Herrenschmidt
2010-12-14 23:02 ` Alexander Graf
2010-12-17 14:05 ` Andreas Färber
2010-12-11 22:10 ` Blue Swirl
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=AANLkTinBMWdLrtBOevq7Jc-1UNB834mDQ941ceqGKcy3@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=gleb@redhat.com \
--cc=kevin@koconnor.net \
--cc=kvm@vger.kernel.org \
--cc=openbios@openbios.org \
--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).