> 2026年1月5日 00:42,Simon Richter <[email protected]> 写道:
> 
> Hi,
> 
> On 1/5/26 01:05, Miao Wang wrote:
> 
>>   Description     : DKMS package for YT6801 network driver
> 
> Is there a name a user would recognize this under?
> 
>> The YT6801 is a high-performance Ethernet controller designed by
>> Motor-comm Corporation, offering advanced networking features and
>> reliable connectivity for various applications.
> 
> This sentence provides no information to users beyond "Ethernet". The 
> "Ethernet" should probably go into the short description.
> 
> Please think from the point of view of an user trying to decide if they want 
> to install this package, not that of a mainboard manufacturer deciding on an 
> Ethernet chipset to use. The user will have heard the name of the OEM selling 
> the box, but not of the manufacturers of individual ICs.
> 
> The first paragraph should probably be something like
> 
>    The Motor-comm YT6801 Ethernet controller is often found in X or Y
>    brand mini PCs and laptops built in or after 2025.
> 
> so users can see at a glance if this is even interesting to them, and 
> full-text search can still match on the manufacturer name.
> 
> You can add a paragraph like
> 
>    This package automatically builds and installs the kernel module.
> 
> if you feel like the description is too short otherwise.

Thanks for your suggestion. I'd like to rephrase the description as follows:

Description: DKMS Driver for Motorcomm YT6801 ethernet controller
This package provides the DKMS source for the YT6801 network driver.
.
The YT6801 is a high-performance Ethernet controller designed by
Motor-comm Corporation, offering advanced networking features and
reliable connectivity for various applications, which can be found
in several Mini PCs and laptops, such as SOYO M2 Mini PC, MLLSE Mini
PC series, and Tuxedo laptops.
.
This package automatically builds and installs the kernel module, if
appropriate kernel headers are installed.


Users can see "Motorcomm YT6801 ethernet controller" from the output
of lspci and can then find and discover this package.

> 
>> I plan to maintain this package, regularly synchronize with the
>> driver source code from its official website and fix possible
>> compilation issues with different versions of linux kernel.
> 
> Is there a timeline on integration with the mainline kernel?

Frank Sae from Motorcomm, the manufacturer of the chip, has tried to
include this driver in the mainline kernel since 2024[1]. The attempt
lasted for 4 versions until Frank Sae gave up for unknown reason in
2025[2]. Yao Zi, who is independent from Motorcomm, is now proposing
another way to implement this driver and the series is now under
review[3].

> If it looks like there will be a stable Debian release without this driver in 
> mainline, it may also be necessary to build an udeb to make it available in 
> the installer, and a mechanism to add the dkms package to the installed 
> system.

If everything goes smoothly, I believe the driver will be merged
before 2027. If not, there should be coordination with the installer
team to see if there can be a mechanism to make a udeb which is
tracking the kernel version and pull in the dkms package to the
installed system.

> 
> Also, you might need a plan for what happens when the driver is added to 
> mainline kernels. DKMS modules go into a separate directory below 
> /lib/modules/, but may still conflict with modules from the mainline kernel. 
> Most DKMS packages do not have this problem because they remain out-of-tree 
> for some good reason (e.g. "five users worldwide" or "must match userspace"), 
> so few of them handle this case, but yours might need to.

If a driver for the hardware get merged into the kernel, and the
kernel is compiled with it, the kernel package can Provides:
this package and Replaces: this package to ensure a smooth transition
from the DKMS driver to the in-tree driver.

Cheers,

Miao Wang


[1]: 
https://lore.kernel.org/lkml/[email protected]/
[2]: 
https://lore.kernel.org/lkml/[email protected]/
[3]: https://lore.kernel.org/lkml/[email protected]/

Reply via email to