[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240418.222237.2262785113908798789.fujita.tomonori@gmail.com>
Date: Thu, 18 Apr 2024 22:22:37 +0900 (JST)
From: FUJITA Tomonori <fujita.tomonori@...il.com>
To: gregkh@...uxfoundation.org
Cc: fujita.tomonori@...il.com, netdev@...r.kernel.org, andrew@...n.ch,
rust-for-linux@...r.kernel.org, tmgross@...ch.edu
Subject: Re: [PATCH net-next v1 4/4] net: phy: add Applied Micro QT2025 PHY
driver
Hi,
On Thu, 18 Apr 2024 15:10:36 +0200
Greg KH <gregkh@...uxfoundation.org> wrote:
> On Thu, Apr 18, 2024 at 10:00:47PM +0900, FUJITA Tomonori wrote:
>> >> + if i == 0x4000 {
>> >
>> > What does 0x4000 mean here?
>> >
>> >> + a = MDIO_MMD_PHYXS;
>> >> + j = 0x8000;
>> >
>> > What does 0x8000 mean here?
>> >
>> >> + }
>> >> + dev.c45_write(a, j, (*val).into())?;
>> >> +
>> >> + j += 1;
>> >> + }
>> >> + dev.c45_write(MDIO_MMD_PCS, 0xe854, 0x0040)?;
>> >
>> > Lots of magic values in this driver, is that intentional?
>>
>> The original driver uses lots of magic values. I simply use them. As
>> Andrew wrote, we could infer some. I'll try to comment these.
>
> Wait, this is a rewrite of an existing driver in the tree into Rust?
No. As I exampled in the cover-letter of the patchset, the vendor
released drivers but they haven't merged into the tree. The vendor
went out of bushiness and the drivers have been abandoned.
Powered by blists - more mailing lists