[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC PATCH 6/6] dp8393x: Rewrite dp8393x_get() / dp8393x_put()
From: |
Finn Thain |
Subject: |
Re: [RFC PATCH 6/6] dp8393x: Rewrite dp8393x_get() / dp8393x_put() |
Date: |
Wed, 7 Jul 2021 11:30:38 +1000 (AEST) |
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/
> 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.
- [PATCH 5/6] dp8393x: Replace address_space_rw(is_write=1) by address_space_write(), (continued)