From: Mark Cave-Ayland <email@example.com> To: Finn Thain <firstname.lastname@example.org> Cc: email@example.com, "Jason Wang" <firstname.lastname@example.org>, "Laurent Vivier" <email@example.com>, "Philippe Mathieu-Daudé" <firstname.lastname@example.org> Subject: Re: [RFC PATCH 6/6] dp8393x: Rewrite dp8393x_get() / dp8393x_put() Date: Wed, 7 Jul 2021 11:12:20 +0100 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On 07/07/2021 02:30, Finn Thain wrote: > On Mon, 5 Jul 2021, Mark Cave-Ayland wrote: > >> 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. >> > > You don't need a rootfs to see the jazzsonic driver messages. But if you > still want one, you could try the mipsel builds from these distros (not > the 64-bit ones): > > https://ftp.jaist.ac.jp/pub/Linux/Gentoo/experimental/mips/stages/ > https://landley.net/aboriginal/downloads/binaries/ That's true, but then this wouldn't enable testing of Phil's proposed CRC changes. Having a simple shell with ping and wget/curl is a real help here. >> 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. >> > > Uploading kernels is a hassle (for me) as it brings a trust question and > requires a file hosting service. I really should use PGP and organise a > web of trust but that's very difficult given my rural location. Given that these are only running in a VM I'm not too worried about trust. I also have a VPS with scp access that I could temporarily grant you access via an SSH public key if that helps? ATB, Mark.
next prev parent reply other threads:[~2021-07-07 10:13 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 2021-07-07 1:30 ` Finn Thain 2021-07-07 10:12 ` Mark Cave-Ayland [this message] 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [RFC PATCH 6/6] dp8393x: Rewrite dp8393x_get() / dp8393x_put()' \ /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
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.