From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Finn Thain <fthain@linux-m68k.org>
Cc: "Laurent Vivier" <laurent@vivier.eu>,
"Jason Wang" <jasowang@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-devel@nongnu.org
Subject: Re: [RFC PATCH 6/6] dp8393x: Rewrite dp8393x_get() / dp8393x_put()
Date: Mon, 5 Jul 2021 07:34:57 +0100 [thread overview]
Message-ID: <d44ae2a3-112a-a84e-5900-bdfa7594cd1c@ilande.co.uk> (raw)
In-Reply-To: <b2cbdfbf-398-3530-b37b-5416aa612af9@linux-m68k.org>
On 05/07/2021 02:36, Finn Thain wrote:
>> Unfortunately I don't have a test mips64el image available to see if this
>> combination works for Linux. Phil, do you have a suitable test kernel and
>> rootfs image available to allow this to be tested?
>>
>
> You can build and boot a mipsel vmlinux by following the steps I described
> previously. In the kernel messages you'll see the jazzsonic driver attempt
> to probe the device. When it succeeds, you'll see the MAC address
> reported. You can also observe the regression I reported with regards to
> patch 2/6, "dp8393x: don't force 32-bit register access".
Those instructions are useful, but since I am not a MIPS developer I don't have an
existing toolchain/kernel tree and rootfs available to test this.
If you can provide me with a link to your vmlinux and rootfs with busybox or similar
in it, I can take a look to see what is happening here. Otherwise it's almost
impossible for me to understand and debug the problem you are seeing on your setup.
ATB,
Mark.
next prev parent reply other threads:[~2021-07-05 6:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 14:19 [RFC PATCH 0/6] dp8393x: Housekeeping Philippe Mathieu-Daudé
2021-07-03 14:19 ` [PATCH 1/6] dp8393x: fix CAM descriptor entry index Philippe Mathieu-Daudé
2021-07-03 14:19 ` [PATCH 2/6] dp8393x: don't force 32-bit register access Philippe Mathieu-Daudé
2021-07-03 14:39 ` Mark Cave-Ayland
2021-07-03 16:29 ` Philippe Mathieu-Daudé
2021-07-04 15:34 ` Mark Cave-Ayland
2021-07-04 2:06 ` Finn Thain
2021-07-03 14:19 ` [RFC PATCH 3/6] dp8393x: Restrict bus access to 16/32-bit operations Philippe Mathieu-Daudé
2021-07-03 14:52 ` Mark Cave-Ayland
2021-07-04 14:45 ` Mark Cave-Ayland
2021-07-03 14:19 ` [RFC PATCH 4/6] dp8393x: Store CAM registers as 16-bit Philippe Mathieu-Daudé
2021-07-03 14:56 ` Mark Cave-Ayland
2021-07-04 14:48 ` Mark Cave-Ayland
2021-07-06 17:29 ` Philippe Mathieu-Daudé
2021-07-06 19:27 ` Mark Cave-Ayland
2021-07-03 14:19 ` [PATCH 5/6] dp8393x: Replace address_space_rw(is_write=1) by address_space_write() Philippe Mathieu-Daudé
2021-07-03 14:57 ` Mark Cave-Ayland
2021-07-04 14:49 ` Mark Cave-Ayland
2021-07-03 14:19 ` [RFC PATCH 6/6] dp8393x: Rewrite dp8393x_get() / dp8393x_put() Philippe Mathieu-Daudé
2021-07-03 15:00 ` Mark Cave-Ayland
2021-07-03 15:04 ` Philippe Mathieu-Daudé
2021-07-04 1:46 ` Finn Thain
2021-07-04 15:07 ` Mark Cave-Ayland
2021-07-05 1:36 ` Finn Thain
2021-07-05 6:34 ` Mark Cave-Ayland [this message]
2021-07-07 1:30 ` Finn Thain
2021-07-07 10:12 ` Mark Cave-Ayland
2021-07-09 9:13 ` Finn Thain
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=d44ae2a3-112a-a84e-5900-bdfa7594cd1c@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=f4bug@amsat.org \
--cc=fthain@linux-m68k.org \
--cc=jasowang@redhat.com \
--cc=laurent@vivier.eu \
--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.