MIME-Version: 1.0
References: <997b2c1f-d580-484e-820a-ebb1a78a1531@riseup.net>
 <em469a0a35-1ffc-4053-a8de-221227172576@79518054.com> <c2a503d1-4679-4da3-8969-79517fbe123c@riseup.net>
In-Reply-To: <c2a503d1-4679-4da3-8969-79517fbe123c@riseup.net>
From: Will Sinatra <wpsinatra@gmail.com>
Date: Fri, 5 Dec 2025 18:22:44 -0500
Message-ID: <CAJH62qkkb_4q1ottXe0sUFvWhdzOq_B-DrnvkjP47835xqL5=g@mail.gmail.com>
Subject: Re: The chosen driver for ethernet being incorrect in Alpine ISO on
 Amlogic A311D
To: Farooq Karimi Zadeh <hapu@riseup.net>
Cc: ~alpine/devel@lists.alpinelinux.org
Content-Type: multipart/alternative; boundary="000000000000c672d006453cb9b6"

--000000000000c672d006453cb9b6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

We're working to revamp the official documentation, it's part of our 3.24
release milestone.

The wiki is currently a good resource for this, it's entirely community
driven, so if you see something is missing and are actively figuring it out
contributing an article is a huge help! You can access that here:
https://wiki.alpinelinux.org/wiki/Main_Page

Of course there's absolutely nothing wrong with asking for help here or on
IRC! IRC tends to be the fastest way to get help in my experience.

On Fri, Dec 5, 2025, 2:35=E2=80=AFPM Farooq Karimi Zadeh <hapu@riseup.net> =
wrote:

> On 12/5/25 22:53, Laurent Bercot wrote:
> >> It seems that `mdev` is responsible for choosing drivers. Am I right?
> >> I needed some hints to write and send a patch.
> >>
> >> Please don't give me fish, instead teach me how to fish. The first
> >> step is that how should I realize who is responsible for managing
> >> device drivers in Linux/Alpine.
> >
> >  By default, it is mdev, yes. You can select what device manager you
> > use by running /usr/sbin/setup-devd. You can keep using eudev with
> > Alpine if it works for you.
> >
> >  If you use mdev or mdevd, the file that configures their behaviour
> > is /etc/mdev.conf, but that's not what explains that they would choose
> > another driver than what eudev would. For that, some investigation into
> > the uevent itself, and the udev rules, would be necessary. It's possibl=
e
> > that eudev has an exception coded that chooses a different driver than
> > what the uevent would naturally say.
> >
> > --
> >  Laurent
> >
> Thanks. I got good clues!
>
> Where can I read about overall architecture of Alpine?
>
> There is https://docs.alpinelinux.org but I can't find much in it.
>
> In general, when I have a question about Alpine internals, how do
>
> I find me answer instead of asking directly from people?
>
>
> Best Regards,
>
> Farooq.
>
>

--000000000000c672d006453cb9b6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">We&#39;re working to revamp the official documentation, i=
t&#39;s part of our 3.24 release milestone.<div dir=3D"auto"><br></div><div=
 dir=3D"auto">The wiki is currently a good resource for this, it&#39;s enti=
rely community driven, so if you see something is missing and are actively =
figuring it out contributing an article is a huge help! You can access that=
 here:=C2=A0<a href=3D"https://wiki.alpinelinux.org/wiki/Main_Page" target=
=3D"_blank" rel=3D"noreferrer">https://wiki.alpinelinux.org/wiki/Main_Page<=
/a></div><div dir=3D"auto"><br>Of course there&#39;s absolutely nothing wro=
ng with asking for help here or on IRC! IRC tends to be the fastest way to =
get help in my experience.</div></div><br><div class=3D"gmail_quote"><div d=
ir=3D"ltr" class=3D"gmail_attr">On Fri, Dec 5, 2025, 2:35=E2=80=AFPM Farooq=
 Karimi Zadeh &lt;<a href=3D"mailto:hapu@riseup.net" target=3D"_blank" rel=
=3D"noreferrer">hapu@riseup.net</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">On 12/5/25 22:53, Laurent Bercot wrote:<br>
&gt;&gt; It seems that `mdev` is responsible for choosing drivers. Am I rig=
ht? <br>
&gt;&gt; I needed some hints to write and send a patch.<br>
&gt;&gt;<br>
&gt;&gt; Please don&#39;t give me fish, instead teach me how to fish. The f=
irst <br>
&gt;&gt; step is that how should I realize who is responsible for managing =
<br>
&gt;&gt; device drivers in Linux/Alpine.<br>
&gt;<br>
&gt; =C2=A0By default, it is mdev, yes. You can select what device manager =
you<br>
&gt; use by running /usr/sbin/setup-devd. You can keep using eudev with<br>
&gt; Alpine if it works for you.<br>
&gt;<br>
&gt; =C2=A0If you use mdev or mdevd, the file that configures their behavio=
ur<br>
&gt; is /etc/mdev.conf, but that&#39;s not what explains that they would ch=
oose<br>
&gt; another driver than what eudev would. For that, some investigation int=
o<br>
&gt; the uevent itself, and the udev rules, would be necessary. It&#39;s po=
ssible<br>
&gt; that eudev has an exception coded that chooses a different driver than=
<br>
&gt; what the uevent would naturally say.<br>
&gt;<br>
&gt; -- <br>
&gt; =C2=A0Laurent<br>
&gt;<br>
Thanks. I got good clues!<br>
<br>
Where can I read about overall architecture of Alpine?<br>
<br>
There is <a href=3D"https://docs.alpinelinux.org" rel=3D"noreferrer norefer=
rer noreferrer" target=3D"_blank">https://docs.alpinelinux.org</a> but I ca=
n&#39;t find much in it.<br>
<br>
In general, when I have a question about Alpine internals, how do<br>
<br>
I find me answer instead of asking directly from people?<br>
<br>
<br>
Best Regards,<br>
<br>
Farooq.<br>
<br>
</blockquote></div>

--000000000000c672d006453cb9b6--