Received: from mx0.riseup.net (mx0.riseup.net [198.252.153.6]) by gbr-app-1.alpinelinux.org (Postfix) with ESMTPS id AD54722587F for <~alpine/devel@lists.alpinelinux.org>; Fri, 5 Dec 2025 19:35:27 +0000 (UTC) Received: from fews03-sea.riseup.net (fews03-sea-pn.riseup.net [10.0.1.153]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx0.riseup.net (Postfix) with ESMTPS id 4dNM6P3t2cz9x0m for <~alpine/devel@lists.alpinelinux.org>; Fri, 5 Dec 2025 19:35:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=riseup.net; s=squak; t=1764963325; bh=f81I5cEDw/jJQzGkfi1VvewhRBjagE+8aHC8YaVb7ws=; h=Date:Subject:To:References:From:In-Reply-To:From; b=bpuPQ1pVkRhGl19O3Iaz2y4Iy/D5gAdVfk+2/FS4Y2pdpZe2SL8Jshl6ph5gTu0VB QQwl9XxeRNPqplH4r3pUQKij8eRuDgOSKeXfMhBkF/Wtq1Kv/qf0/fb59FYUz0G2F9 vtuh0wg5xcnV1x4taYaO6VjG0LF5GKShhEJChAnM= X-Riseup-User-ID: 2D90BAB0FC03097E6E15000F0E65D4F48FF7177F3A1461FB5AA00E3E0D875D37 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews03-sea.riseup.net (Postfix) with ESMTPSA id 4dNM6N5G1Nz1xrd for <~alpine/devel@lists.alpinelinux.org>; Fri, 5 Dec 2025 19:35:24 +0000 (UTC) Message-ID: Date: Fri, 5 Dec 2025 23:05:18 +0330 MIME-Version: 1.0 Subject: Re: The chosen driver for ethernet being incorrect in Alpine ISO on Amlogic A311D To: ~alpine/devel@lists.alpinelinux.org References: <997b2c1f-d580-484e-820a-ebb1a78a1531@riseup.net> Content-Language: en-US From: Farooq Karimi Zadeh In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 possible > 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.