From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: BALATON Zoltan <balaton@eik.bme.hu>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [PATCH] mv64361: Add dummy gigabit ethernet PHY access registers
Date: Fri, 30 Jun 2023 13:44:41 -0300 [thread overview]
Message-ID: <8168ffc8-a20d-b6ad-581e-b0f4a1887468@gmail.com> (raw)
In-Reply-To: <a56d91b8-696f-a56e-904d-cda8a2ec3a16@eik.bme.hu>
On 6/14/23 16:21, BALATON Zoltan wrote:
> On Mon, 5 Jun 2023, BALATON Zoltan wrote:
>> We don't emulate the gigabit ethernet part of the chip but the MorphOS
>> driver accesses these and expects to get some valid looking result
>> otherwise it hangs. Add some minimal dummy implementation to avoid rhis.
>>
>> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
>> ---
>> This is only used by MorphOS on pegasos2 so most likely could go via
>> the ppc queue.
And it will.
Queued in gitlab.com/danielhb/qemu/tree/ppc-next. Thanks,
Daniel
>
> Ping?
>
> Regards,
> BALATON Zoltan
>
>> hw/pci-host/mv64361.c | 6 ++++++
>> hw/pci-host/mv643xx.h | 3 +++
>> 2 files changed, 9 insertions(+)
>>
>> diff --git a/hw/pci-host/mv64361.c b/hw/pci-host/mv64361.c
>> index 19e8031a3f..01bd8c887f 100644
>> --- a/hw/pci-host/mv64361.c
>> +++ b/hw/pci-host/mv64361.c
>> @@ -541,6 +541,12 @@ static uint64_t mv64361_read(void *opaque, hwaddr addr, unsigned int size)
>> }
>> }
>> break;
>> + case MV64340_ETH_PHY_ADDR:
>> + ret = 0x98;
>> + break;
>> + case MV64340_ETH_SMI:
>> + ret = BIT(27);
>> + break;
>> case MV64340_CUNIT_ARBITER_CONTROL_REG:
>> ret = 0x11ff0000 | (s->gpp_int_level << 10);
>> break;
>> diff --git a/hw/pci-host/mv643xx.h b/hw/pci-host/mv643xx.h
>> index cd26a43f18..f2e1baea88 100644
>> --- a/hw/pci-host/mv643xx.h
>> +++ b/hw/pci-host/mv643xx.h
>> @@ -656,6 +656,9 @@
>> /* Ethernet Unit Registers */
>> /****************************************/
>>
>> +#define MV64340_ETH_PHY_ADDR 0x2000
>> +#define MV64340_ETH_SMI 0x2004
>> +
>> /*******************************************/
>> /* CUNIT Registers */
>> /*******************************************/
>>
prev parent reply other threads:[~2023-06-30 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 21:51 [PATCH] mv64361: Add dummy gigabit ethernet PHY access registers BALATON Zoltan
2023-06-14 19:21 ` BALATON Zoltan
2023-06-21 12:34 ` BALATON Zoltan
2023-06-29 8:36 ` BALATON Zoltan
2023-06-29 11:04 ` Cédric Le Goater
2023-06-30 14:22 ` Daniel Henrique Barboza
2023-06-30 16:44 ` Daniel Henrique Barboza [this message]
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=8168ffc8-a20d-b6ad-581e-b0f4a1887468@gmail.com \
--to=danielhb413@gmail.com \
--cc=balaton@eik.bme.hu \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).