From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Programmingkid <programmingkidx@gmail.com>
Cc: jasowang@redhat.com, qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] Make rtl8139 network interface card compatible with Mac OS 10.4
Date: Wed, 30 Dec 2015 16:58:19 +0000 [thread overview]
Message-ID: <56840D2B.7020908@ilande.co.uk> (raw)
In-Reply-To: <96B9267A-2429-4C38-B187-0A8F68B5A991@gmail.com>
On 30/12/15 16:47, Programmingkid wrote:
> I did disable the change I made to the pci_dma_read() function and applied this
> patch to OpenBIOS. It makes Mac OS X stop booting. This is the message it is
> stuck at when Zoltan's patch is applied:
> mig_table_max_displ = 70
>
> I even removed the rtl8139 from QEMU's options and Mac OS X still stopped booting
> at the same exact spot.
Okay. I've just posted a revised patchset to the OpenBIOS list which may
(or may not) help, so please test with that aswell to see if it makes a
difference.
>> It looks like we have to face up to the reality that Apple's OF
>> implementation likes to enable bus mastering for some cards and emulate
>> this behaviour in OpenBIOS, since because of this some drivers don't
>> explicitly enable bus mastering and so fail under emulation.
>>
>> I'll go back and revisit Zoltan's patches to see if we can come up with
>> something that works better for OpenBIOS upstream. In the meantime I
>> still can't quite work out why you still need to swap the BARs around as
>> AFAICT both the mmio and io BARs are mapped onto the chip registers -
>> any chance you could add some debugging to QEMU in order to figure out
>> what is going wrong without your patch?
>
> I have done a lot of debugging. With only the pci_dma_read() change applied to QEMU, nothing the Mac OS X driver does ever accesses any of the functions from the rtl8139.c file (as far as I can tell). I will add that when this code "if ( csrRead8( RTL_CM ) & R_CM_RST )" is executed by the driver, the value is 16. It appeared to be pretty consistent. The value returned by just "csrRead8( RTL_CM )" is 24.
Right, so then the question to ask is what is the difference in
behaviours both before and after the BAR swap? It seems that you're
getting a value back but presumably it must be a different value with
your patch applied.
ATB,
Mark.
next prev parent reply other threads:[~2015-12-30 16:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-29 17:59 [Qemu-devel] [PATCH] Make rtl8139 network interface card compatible with Mac OS 10.4 Programmingkid
2015-12-29 21:04 ` Mark Cave-Ayland
2015-12-30 0:05 ` Programmingkid
2015-12-30 0:35 ` Programmingkid
2015-12-30 14:03 ` Mark Cave-Ayland
2015-12-30 16:47 ` Programmingkid
2015-12-30 16:58 ` Mark Cave-Ayland [this message]
2015-12-30 17:50 ` Programmingkid
2015-12-31 13:23 ` Mark Cave-Ayland
2015-12-31 18:26 ` Programmingkid
2015-12-31 18:56 ` Mark Cave-Ayland
2015-12-31 19:47 ` Programmingkid
2016-01-02 4:00 ` Programmingkid
2016-01-02 9:39 ` Mark Cave-Ayland
2016-01-02 17:08 ` Programmingkid
2016-01-02 20:46 ` Mark Cave-Ayland
2016-01-01 21:36 ` Paolo Bonzini
2016-01-01 21:49 ` Programmingkid
2016-01-01 20:32 ` Paolo Bonzini
2016-01-01 20:42 ` Programmingkid
2016-01-01 22:36 ` Paolo Bonzini
2016-01-01 22:42 ` Programmingkid
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=56840D2B.7020908@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=jasowang@redhat.com \
--cc=programmingkidx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.