From nobody Tue Mar 24 22:50:13 2026 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4fgQGs0v4bz6WJqT for ; Tue, 24 Mar 2026 22:50:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R12" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4fgQGs0LsGz4QjS for ; Tue, 24 Mar 2026 22:50:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1774392613; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=S52Lcbkjthrsi3nGwZg561pLcU9w3O3zSZsWOjaXmqc=; b=mo1pr5RrqbjvFqIlYpMAFfZ2sCavfGI/hXDZYiCXsR6c0y9zXeqwx2BrqodUxjRE389/E1 QAfwbSwL5uSnaupeuQRECrG0QsZNsVBrS2TxUEjC+wz0wPSS+KP7KcgiZf21HBYWu8pHAH guVTw8/4fpcCPiNTjpoWECS6IU+Trb3lBfzsWWeU86vhlefe/s3wQv/L5U+MH47werqe9+ VvefhVTSQKHkzbYFGmiGhgFIeynOh2QCs/S3J/+t19X8okEO6t5X6iveA/RRhlpk2ziITv jJ3xOeZLdNx/1HLwrs/tqOTY5RMrVADUBX4FGukGpOc5iMHbCwEtPWbb/30wUQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1774392613; a=rsa-sha256; cv=none; b=py88mal6IXtiTUBo9FYF48b3bt6mUvPPTOUyZUjX1n+xvwjFthUKXMzznke0jYiHfblvyp 2FMlLi6cur4wL6zGWT7KeSWwu1qkPJc0M7jyS0Bkv78xttmUR7fnAC4CtEoSxYkjxl4Ck4 1IJ3MH4htdnt/ffCjir1p7MeYcsblXO5CQAIwABYPOAJZE/jvolOqgkbiKG7vKvppvkWEJ AAPIX/me2V3PmktJKgBprrJdENWuTG6MPLvQKndlZExBKqDcA+e/iafNAi4Z6bMJXku1y7 Of9HFbtF4wtbqUlEenSKPJklJovWWUHmfUzMZkvzifaprE39oVUG7J1ToJCPBg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1774392613; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=S52Lcbkjthrsi3nGwZg561pLcU9w3O3zSZsWOjaXmqc=; b=vcELCkrGjbVwsS6xs9pxhrvx8JDbKm9Uxfnkv8meggwzY1uCmdvug/GZQxXAbXDXF2qgf6 ULdQE8KAhuccfgVxDl597cFrysCe5KflblFV7+unRRnnNRs7jRsHJQ4ga6GsCe83hratgd QJscX5J9SvBUQLLpeFhMQP1eLx+A7jKhJC6cHYuVTiGF0c1qNDMFfDyEUcpfnLIZ7otmPj kBx4OKdwsAd4DsHzZE1kAavMdLH/IDVrd4WtI8Q3uVTdcEoi+EmswrzMfaqAHLURiUT5Vu gyt7QvRpKGDNfEatcDBnpLpybkFimRDzPSKu+/EbDmd1UvuGk5yS7GJLrJvwhA== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4fgQGr6WQMzfXh for ; Tue, 24 Mar 2026 22:50:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 62OMoCGT049237 for ; Tue, 24 Mar 2026 22:50:12 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 62OMoCoJ049236 for wireless@FreeBSD.org; Tue, 24 Mar 2026 22:50:12 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 203827] hostapd getting stuck with net.bpf.zerocopy_enable=1 Date: Tue, 24 Mar 2026 22:50:13 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ndenev@gmail.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Feedback Timeout X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-wireless@freebsd.org Sender: owner-freebsd-wireless@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203827 Nikolay Denev changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |Feedback Timeout Status|New |Closed --- Comment #4 from Nikolay Denev --- This was very long time ago, I no longer have this system running. This can probably be closed. --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Wed Mar 25 22:43:26 2026 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4fh24k4B6kz6WtLF for ; Wed, 25 Mar 2026 22:43:34 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R13" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4fh24k3cBdz4CgF; Wed, 25 Mar 2026 22:43:34 +0000 (UTC) (envelope-from bz@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1774478614; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=zU2OzzMh7BJIDy0j03GHPoUbBba/4bIFH+10VptUrtM=; b=FOT6kWnhYkz3BD9ZkzoZfBeaNNosK07xMVmZCzsHHz+ESrpKMGqFkMl5ieqkd0BVs46Cx8 Wc4fl64+WqAYWi94GuUWtLzqABIEO7r4l1R5pGaslODaNM8I6OHu0qVakJ1kz2trkNWKv/ x7bWDgBdpv5Evld+ozoT1+cWflZ6gDNJ+goALKEn+t+HeI7NBVcERhDsB1TcTb4hUayPbe 9TWKNqwMigdqG+zjlfgxD/JbI86yHLY6PMrRiugF8+VYm8Xch+SiUrweY9LqAaDqxo2+Vs IepHJswOK078n2ULPR7Tyi3+lqXHtivRNFs+5fcMRlH+S0/AsgWLUA6nL1wGoQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1774478614; a=rsa-sha256; cv=none; b=sAnX2wjenLH9/lzZLxo1wCSoUv5+r7nYPPfzwwUT5EgtGDxcnq+6Lh29c2h5DIFN4UpCpu 42B7tKXBEZ9vDDh+TS+fK/q1pXXg/+MHvlM29cJIjd+Q8vhuf9jACOyKoEjO5nMN6CA8/w f+JFPdqdJ9NW5QwBs5Dng3gfdty+RgNWCJJVy2nQv6xBYoFJ1K1IOS+6gNdWeXTT/Tn7nR UYOQxjdI1KQaGllCugN7rWUnwH2B78Fn1YdKPAnxvDz5iVeFD5cBQxsC67OpVkH3BDDrJY wEYmc5flLpi70yALQsm35s0xbsLwJ+bQf/0WNzV+P+PSoeB1X4rotVte8Y2Nyg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1774478614; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=zU2OzzMh7BJIDy0j03GHPoUbBba/4bIFH+10VptUrtM=; b=QYmZuJ4cMW9M9IDCkDvO+YYAgHU0tAJYjDXS8ow472eXBEMvAgVzcKleP/Crq9r+taUD2w /kXzzK8nGL3xBFv0jG72aMbiVf0kpC6KSu8Y3TrHQevDsezvpcxG3qq0URH7dfzPtIUf+f OgXHuDqEowCIv5DwtoQK2YhxTe71aSP0iUgFbUw3wG3MucPv6wbLNWLRwE4gOkPCYUHcs1 gYL8rnFnqeWXFXNbdoF7X1ydaXXCj7HY74q0EqYdIicjeqZBKu1rKMkgDbwGu8NobmdqeJ 7N0iNaHG8Ziw/PqDLVymLRnrgFtfowT3EhIo61onotXnWoSkKb0z0rHb0t7r6A== Received: from mx-01.divo.sbone.de (mx-01.divo.sbone.de [IPv6:2003:a:140a:2200:6:594:fffe:19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (prime256v1) client-digest SHA256) (Client CN "mx-01.divo.sbone.de", Issuer "E7" (not verified)) (Authenticated sender: bz/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4fh24k26z4z12lM; Wed, 25 Mar 2026 22:43:34 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx-01.divo.sbone.de (Postfix) with ESMTPS id 0C9DFA64805; Wed, 25 Mar 2026 22:43:12 +0000 (UTC) Received: from content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 851102D029E9; Wed, 25 Mar 2026 22:43:32 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) by content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (amavisd-new, port 10024) with ESMTP id 8jnLCMSDk1N8; Wed, 25 Mar 2026 22:43:31 +0000 (UTC) Received: from nv.t4-02.sbone.de (nv.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 829E72D029D8; Wed, 25 Mar 2026 22:43:29 +0000 (UTC) Date: Wed, 25 Mar 2026 22:43:26 +0000 (UTC) From: "Bjoern A. Zeeb" To: Volodymyr Kostyrko cc: FreeBSD wireless mailing list Subject: Re: How is testing going? In-Reply-To: <9ee20d9b-313a-4d91-a86b-e39054821abd@b1t.name> Message-ID: <3rqsqoo-ro22-r062-1256-qr9q89pnp4q4@mnoonqbm.arg> References: <6p4r5o3-4218-sn14-o712-7944359sqno6@mnoonqbm.arg> <9ee20d9b-313a-4d91-a86b-e39054821abd@b1t.name> X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-wireless@freebsd.org Sender: owner-freebsd-wireless@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed On Sat, 21 Mar 2026, Volodymyr Kostyrko wrote: Hi, > Well, I tried it, and I'm still reverting back to iwm. I'm just using iwlwifi > to upload newer firmware on boot. Need to say I have some weird issues, when > whole pcie lane is going off and Wi-Fi adapter is gone completely (happened > before iwlwifi, happened on windows, yet doesn't happen recently), so this > might be just a noise. > > Last problem I got was: > > Mar 14 11:46:33 stick kernel: iwlwifi0: Error sending SCAN_CFG_CMD: time out > after 2000ms. > Mar 14 11:46:33 stick kernel: iwlwifi0: Current CMD queue read_ptr 69 > write_ptr 70 I've hit this and can reproduce it. The SCAN_CFG_CMD is a red herring though as they currently send some details to the firmware regularly from a work job; I disabled it locally and now I see the less regular statistics command, which I can confirm logging hardware comands. > Mar 14 11:46:43 stick kernel: iwlwifi0: Queue 4 is active on fifo 1 and stuck > for 10000 ms. SW [208, 222] HW [222, 222] FH TRB=0x0c01040dd This is the other interesting information; though for me it's an AX210 and slightly different. THere I see things like: iwlwifi0: Queue 2 is stuck 27854 28080 before the firmware dump. The numbers are the read and write indexes. I need to go and see if we have a PR for this somewhere open as well still. We clearly had a lot omre reports years ago (see e674ddec0b41). It'll likely be a few days but keep an eye on the commits mentioning something like this. /bz -- Bjoern A. Zeeb r15:7 From nobody Sat Mar 28 00:25:43 2026 X-Original-To: freebsd-wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4fjJG24pBYz6X74k for ; Sat, 28 Mar 2026 00:26:02 +0000 (UTC) (envelope-from bounce.1x22bho7z8ku0d4=jrxa692um2hl=68i0f06mvmp314@em653246.varank.in) Received: from e3i456.smtp2go.com (e3i456.smtp2go.com [158.120.85.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4fjJG12Dy6z3JR8 for ; Sat, 28 Mar 2026 00:26:01 +0000 (UTC) (envelope-from bounce.1x22bho7z8ku0d4=jrxa692um2hl=68i0f06mvmp314@em653246.varank.in) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=varank.in header.s=s653246 header.b=lL9pUjFJ; dmarc=pass (policy=none) header.from=varank.in; spf=pass (mx1.freebsd.org: domain of "bounce.1x22bho7z8ku0d4=jrxa692um2hl=68i0f06mvmp314@em653246.varank.in" designates 158.120.85.200 as permitted sender) smtp.mailfrom="bounce.1x22bho7z8ku0d4=jrxa692um2hl=68i0f06mvmp314@em653246.varank.in" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=varank.in; i=@varank.in; q=dns/txt; s=s653246; t=1774657554; h=from : subject : to : message-id : date; bh=/w+Xw1P6rJ4/1YJnAtd0img2HXpt1P94fj4wdSG0Tyw=; b=lL9pUjFJKz+60gEWfUSbOebcYL2h30Uv0FIwYcAI6jpLbnPc4zm3Pozpgxc4abXvsC6t8 nAZm8Fq5kMrzw5gQiwH/B6w07Nd290HAItL9zqtLu6kAiHYtHJfy+BpYGjuHzsSKzGY+LYX 0wvyKcHwkx7j8vwb5+Rt2YD4ypPrCt0RSHq5HUSSl8l0mE38Tge47egUVoaLL5dJe47PBZw mKqkx3e/mL/wzp3ZHLj9/U3Zgmyv6vTT4MPT31e+rkCCYqGCOeDeox38k9mrhPylvY7VUEk ZH62V/C4VvV6n4v3QvOIooZfQdl6LbAnameyQ1fixvCUICreQDCt+MpKAMKw== Received: from [10.66.241.78] (helo=mail-pf1-f169.google.com) by smtpcorp.com with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_128_GCM:128) (Exim 4.99.1-S2G) (envelope-from ) id 1w6HUw-4o5NDgrfmvS-fE5o for freebsd-wireless@freebsd.org; Sat, 28 Mar 2026 00:25:54 +0000 Received: by mail-pf1-f169.google.com with SMTP id d2e1a72fcca58-82985f42664so1608305b3a.0 for ; Fri, 27 Mar 2026 17:25:54 -0700 (PDT) X-Gm-Message-State: AOJu0YwSKlGGhH7XC6hwzwAxRqfnplNWEG9zPTAzE3bj/TwW+GZAUfXZ BZD6PIQVasCChtUHuNQUrdr+/hkAQibRovpPOUExs1OG5GmwIpJL8PoGSws2BSlP2jgIWt73ibY rD6ZFT6el9bXtmeUGvkXYRnAU5FDT9qI= X-Received: by 2002:a05:6a00:c82:b0:82a:ea3:c16f with SMTP id d2e1a72fcca58-82c960341d1mr4283529b3a.53.1774657554389; Fri, 27 Mar 2026 17:25:54 -0700 (PDT) List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-wireless@freebsd.org Sender: owner-freebsd-wireless@FreeBSD.org MIME-Version: 1.0 References: <75f56507-49e8-4f43-987f-7025d62b0bd9@gmail.com> In-Reply-To: From: Vladimir Varankin Date: Sat, 28 Mar 2026 01:25:43 +0100 X-Gmail-Original-Message-ID: X-Gm-Features: AQROBzDCw2eApPQRcgjEbXUbASxsiSdgyQvxXfN672EoLb7iqic9F5PmZy4x8yo Message-ID: Subject: Re: Rebuilding brcmfmac Wi-Fi driver with the help of AI To: Bugs Beastie Cc: freebsd-wireless@freebsd.org Content-Type: multipart/alternative; boundary="00000000000020a270064e0aa981" X-Report-Abuse: Please forward a copy of this message, including all headers, to Feedback-ID: 653246m:653246a4bqTde:653246soHGFQkrE5 X-smtpcorp-track: UK6A71r3DYu6.C8IQlIrf86Io.YLh3zQAj5AU X-Spamd-Result: default: False [-4.09 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.995]; DMARC_POLICY_ALLOW(-0.50)[varank.in,none]; RWL_MAILSPIKE_EXCELLENT(-0.40)[158.120.85.200:from]; FORGED_SENDER(0.30)[vladimir@varank.in,bounce.1x22bho7z8ku0d4=jrxa692um2hl=68i0f06mvmp314@em653246.varank.in]; R_SPF_ALLOW(-0.20)[+ip4:158.120.80.0/21]; R_DKIM_ALLOW(-0.20)[varank.in:s=s653246]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:23352, ipnet:158.120.84.0/22, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MISSING_XM_UA(0.00)[]; TO_DN_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_NEQ_ENVFROM(0.00)[vladimir@varank.in,bounce.1x22bho7z8ku0d4=jrxa692um2hl=68i0f06mvmp314@em653246.varank.in]; FROM_HAS_DN(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-wireless@freebsd.org]; MLMMJ_DEST(0.00)[freebsd-wireless@freebsd.org]; DKIM_TRACE(0.00)[varank.in:+] X-Rspamd-Queue-Id: 4fjJG12Dy6z3JR8 X-Spamd-Bar: ---- --00000000000020a270064e0aa981 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hey-hey, >> Given the workflow, prompts, AI models to use, etc. are in place AND you have >> a physical Raspberry Pi 4, how long would it take to vibe-port brcmfmac43455-sdio >> wifi driver? The complication it is attached via SDIO interface, not PCI= ! > > That'd be fun thing to try. I've forgotten that RPi4 comes with a broadcom chip. > Will find some time to spin up a testing stand, and will see how that goes. This's been keeping me busy, and it hasn't been a smooth ride so far. But I finally saw some exciting progress today. Currently, the codebase is a mess [1]. But we (mainly agents, of course) go= t Raspberry Pi 4b to connect to my home Wi-Fi AP (5GHz, WPA2), and sent traffic to the Internet. One problem was that the stock kernel, that came with the RPI image (FreeBSD-15.0-RELEASE-arm64-aarch64-RPI.img) needed patching and a fixed device tree overlay. The RPI4-HOWTO.md [2] in the driver's repo has more details. *Again, to be 100% clear and hones: these are experimental "vibes" to see how far the AI tooling can push. I'm welcoming productive feedback about the results.* The repo's docs/00-progress.md [3] has a list of next steps to fix, before I'll ask the agents to do a deep code-review and refactoring. Details of the tests: freebsd@rpi4-freebsd-1:~ % uname -v FreeBSD 15.0-STABLE #2 9c49c393a81b-dirty: Fri Mar 27 22:59:19 CET 2026 v@freebsd-test-0:/usr/obj/usr/src/arm64.aarch64/sys/SDIO % dmesg | grep -i 'raspberry pi' gpio1: on bcm2835_firmware0 % sysctl hw.model hw.model: ARM Cortex-A72 r0p3 % ls /boot/firmware/ | grep brcm brcmfmac43455-sdio.bin brcmfmac43455-sdio.clm_blob brcmfmac43455-sdio.txt % kldstat Id Refs Address Size Name 1 8 0xffff000000000000 1446958 kernel 2 1 0xffff0000b2c00000 33000 if_brcmfmac.ko % ifconfig wlan0 wlan0: flags=3D8843 metric 0 mtu 15= 00 options=3D0 ether dc:a6:32:29:7b:1b inet 192.168.188.182 netmask 0xffffff00 broadcast 192.168.188.255 groups: wlan ssid =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 channel 116 (55= 80 MHz 11a ht/20) bssid 1c=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2= =96=88:3c country 511 authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit AES-CCM 3:128-bit AES-CCM ucast:128-bit txpower 0 bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 60 -ht -htcompat -ampdu ampdulimit 8k -amsdu -stbc -ldpc -uapsd wme roaming MANUAL parent interface: brcmfmac0 media: IEEE 802.11 Wireless Ethernet MCS mode 11na status: associated nd6 options=3D29 % traceroute -i wlan0 1.1.1.1 traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 40 byte packets 1 192.168.188.114 (192.168.188.114) 185.541 ms 34.019 ms 53.549 ms 2 192.168.188.1 (192.168.188.1) 49.716 ms 47.651 ms 49.251 ms 3 10.103.18.1 (10.103.18.1) 55.914 ms 44.769 ms 57.156 ms 4 89.246.252.169 (89.246.252.169) 46.803 ms 13.387 ms 48.198 ms 5 i689729BA.versanet.de (104.151.41.186) 52.102 ms 51.937 ms 50.030 ms 6 62.214.73.216 (62.214.73.216) 53.640 ms 43.454 ms 58.782 ms 7 62.214.73.217 (62.214.73.217) 49.132 ms 49.143 ms 46.480 ms 8 one.one.one.one (1.1.1.1) 51.158 ms 49.501 ms 56.651 ms P.S. Zig has gone from the driver's codebase. Making it work in a kernel driver on aarch64 turned out even more challenging today. I'll park the idea into a backlog of future playground projects. [1]: https://github.com/narqo/freebsd-brcmfmac [2]: https://github.com/narqo/freebsd-brcmfmac/blob/629b801123966bbbea71d5ff8ccb= 7a789f43e792/RPI4-HOWTO.md [3]: https://github.com/narqo/freebsd-brcmfmac/blob/629b801123966bbbea71d5ff8ccb= 7a789f43e792/docs/00-progress.md Cheers, V. On Thu, 12 Mar 2026 at 09:56, Vladimir Varankin wrote: > > Given the workflow, prompts, AI models to use, etc. are in place AND yo= u > have > > a physical Raspberry Pi 4, how long would it take to vibe-port > brcmfmac43455-sdio > > wifi driver? The complication it is attached via SDIO interface, not PC= I! > > That'd be fun thing to try. I've forgotten that RPi4 comes with > a broadcom chip. > Will find some time to spin up a testing stand, and will see how that goe= s. > > > C/Zig split rationale - at the end 94.7% of code is in C, 4.7% in Zig. > Would you still > > go for anything in Zig again? > > Initially I was sold by Zig's promise of interoperability with C [1]. > > Given that I'm more comfortable with Zig compiler's promises, the thinkin= g > was that > understanding the details will be simpler for me, when the majority of > code is generated > by AIs. In practice this didn't work out: the interoperability has number > of corner cases, > that, as an example, doesn't "just work" with kernel's linker. > > So it's not Zig the language was the issue. But the extra supporting > layers needed > to make it work required more involvement than I (naively) hoped it will > be. > > Although, it works, I'm willing to rewrite Zig's chunk back to C, just to > avoid it to be an easy > target to latch on in the critics of the approach. > > [1]: > https://ziglang.org/learn/overview/#integration-with-c-libraries-without-= ffibindings > > On Wed, 11 Mar 2026 at 16:16, Bugs Beastie wrote: > >> Mar 10, 2026 20:33:53 Vladimir Varankin : >> >> > I recently wrote a blog post [1] sharing my experience of rebuilding >> > a Wi-Fi driver for BCM4350 for FreeBSD with the help of agenting AI >> > tooling. >> > >> Omitting any comments about AI usege,...cool and impressive! :) >> >> Very practical question: >> Given the workflow, prompts, AI models to use, etc. are in place AND you >> have a physical Raspberry Pi 4, how long would it take to vibe-port >> brcmfmac43455-sdio wifi driver? The complication it is attached via SDIO >> interface, not PCI! >> >> Question out of curiosity: >> C/Zig split rationale - at the end 94.7% of code is in C, 4.7% in Zig. >> Would you still go for anything in Zig again? >> >> > I'm aware that different groups of people have different opinions abou= t >> > the topic of using AI in software development. Still I think this was >> > a fairly interesting experiment, and I'm curious to hear the opinion >> > on the approach and the results, from people close to in-tree drivers >> > development. >> > >> > The GitHub repository [2] includes documentation about the testing >> > approach, recorded decisions and know issues (which I'm =E2=80=94 stil= l with >> > the help of AI agents =E2=80=94 addressing in my spare time). >> > >> > P.S. Just to be absolute clear: I'm not proposing or suggesting to >> > upstream the code of this driver. Neither do I think that in the curre= nt >> > state the AIs can vibe-code something reliable in one go. But I do >> think, >> > the tooling can be a huge multiplier for building, testing, explaining= , >> > reviewing, etc large bodies of complex code. >> > >> > Cheers, >> > V. >> > >> > [1]: https://vladimir.varank.in/notes/2026/02/freebsd-brcmfmac/ >> > [2]: https://github.com/narqo/freebsd-brcmfmac >> > >> > -- >> > Vladimir Varankin >> > vladimir@varank.in >> >> >> > > -- > Vladimir Varankin > vladimir@varank.in > --=20 Vladimir Varankin vladimir@varank.in --00000000000020a270064e0aa981 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hey-hey,

>> Given the workflow, prompts, AI m= odels to use, etc. are in place AND you have
>> a physical Raspber= ry Pi 4, how long would it take to vibe-port brcmfmac43455-sdio
>>= wifi driver? The complication it is attached via SDIO interface, not PCI!<= br>>
> That'd be fun thing to try. I've forgotten that RPi= 4 comes with a broadcom chip.
> Will find some time to spin up a test= ing stand, and will see how that goes.

This's been keeping me bu= sy, and it hasn't been a smooth ride so far. But I finally
saw some = exciting progress today.

Currently, the codebase is a mess [1]. But = we (mainly agents, of course) got
Raspberry Pi 4b to connect to my home = Wi-Fi AP (5GHz, WPA2), and sent traffic
to the Internet.

One prob= lem was that the stock kernel, that came with the RPI image
(FreeBSD-15.= 0-RELEASE-arm64-aarch64-RPI.img) needed patching and a fixed device
tree= overlay. The RPI4-HOWTO.md [2] in the driver's repo has more details.<= br>
*Again, to be 100% clear and hones: these are experimental "vib= es" to see how far
the AI tooling can push. I'm welcoming produ= ctive feedback about the results.*

The repo's docs/00-progr= ess.md [3] has a list of next steps to fix, before I'll ask the agents<= /div>
to do a deep code-review and refactoring.

Details of the= tests:

freebsd@rpi4-freebsd-1:~ % uname -v
FreeBSD 15.0-STABLE #= 2 9c49c393a81b-dirty: Fri Mar 27 22:59:19 CET 2026 v@freebsd-test-0:/usr/ob= j/usr/src/arm64.aarch64/sys/SDIO

% dmesg | grep -i 'raspberry pi= '
gpio1: <Raspberry Pi Firmware GPIO controller> on bcm2835_fi= rmware0

% sysctl hw.model
hw.model: ARM Cortex-A72 r0p3

% = ls /boot/firmware/ | grep brcm
brcmfmac43455-sdio.bin
brcmfmac43455-s= dio.clm_blob
brcmfmac43455-sdio.txt

% kldstat
Id Refs Address = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Size Name
=C2=A01= =C2=A0 =C2=A08 0xffff000000000000 =C2=A01446958 kernel
=C2=A02 =C2=A0 = =C2=A01 0xffff0000b2c00000 =C2=A0 =C2=A033000 if_brcmfmac.ko

% ifcon= fig wlan0
wlan0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&= gt; metric 0 mtu 1500
options=3D0
ether dc:a6:32:29:7b:1b
inet = 192.168.188.182 netmask 0xffffff00 broadcast 192.168.188.255
groups: wl= an
ssid =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 channel = 116 (5580 MHz 11a ht/20) bssid 1c=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96= =88=E2=96=88:3c
country 511 authmode WPA2/802.11i privacy ON deftxkey U= NDEF
AES-CCM 2:128-bit AES-CCM 3:128-bit AES-CCM ucast:128-bit txpower = 0
bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 60 -ht -htcompat -ampdu
= ampdulimit 8k -amsdu -stbc -ldpc -uapsd wme roaming MANUAL
parent inter= face: brcmfmac0
media: IEEE 802.11 Wireless Ethernet MCS mode 11na
= status: associated
nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKL= OCAL>

% traceroute -i wlan0 1.1.1.1
traceroute to 1.1.1.1 (1.= 1.1.1), 64 hops max, 40 byte packets
=C2=A01 =C2=A0192.168.188.114 (192.= 168.188.114) =C2=A0185.541 ms =C2=A034.019 ms =C2=A053.549 ms
=C2=A02 = =C2=A0192.168.188.1 (192.168.188.1) =C2=A049.716 ms =C2=A047.651 ms =C2=A04= 9.251 ms
=C2=A03 =C2=A010.103.18.1 (10.103.18.1) =C2=A055.914 ms =C2=A04= 4.769 ms =C2=A057.156 ms
=C2=A04 =C2=A089.246.252.169 (89.246.252.169) = =C2=A046.803 ms =C2=A013.387 ms =C2=A048.198 ms
=C2=A05 =C2=A0i689729BA.versanet.de (104.151.41.186) = =C2=A052.102 ms =C2=A051.937 ms =C2=A050.030 ms
=C2=A06 =C2=A062.214.73.= 216 (62.214.73.216) =C2=A053.640 ms =C2=A043.454 ms =C2=A058.782 ms
=C2= =A07 =C2=A062.214.73.217 (62.214.73.217) =C2=A049.132 ms =C2=A049.143 ms = =C2=A046.480 ms
=C2=A08 =C2=A0one.one.one.one (1.1.1.1) =C2=A051.158 ms = =C2=A049.501 ms =C2=A056.651 ms

P.S. Zig has gone from the driver= 9;s codebase. Making it work in a kernel driver
on aarch64 turned out ev= en more challenging today. I'll park the idea into a backlog
of= future playground projects.

[1]: https://github.com/narqo/freebsd-brcmfmac
[2]:= https://github.com/narqo/freebsd-br= cmfmac/blob/629b801123966bbbea71d5ff8ccb7a789f43e792/RPI4-HOWTO.md
[= 3]: https://github.com/narqo/f= reebsd-brcmfmac/blob/629b801123966bbbea71d5ff8ccb7a789f43e792/docs/00-progr= ess.md

Cheers,
V.

<= /div>

On Thu, 12 Mar 2026 at 09:56, Vladimir Var= ankin <vladimir@varank.in> = wrote:
> Given the workflow, prompts, AI models to us= e, etc. are in place AND you have
> a physical Raspberry Pi 4, how long would = it take to vibe-port=20 brcmfmac43455-sdio
> wifi driver? The complication= it is attached via SDIO interface, not PCI!

That'd be fun= thing to try. I've forgotten that RPi4 comes with a=C2=A0broadcom=C2= =A0chip.
Will find some time to spin up a testing stand, and will= see how that goes.

>= =C2=A0 C/Zig split rationale - at the end 94.7% of code is in C, 4.7% in Zig. Woul= d you still
> go for anything in Zig again?
<= div dir=3D"ltr">
Initially I was sold by Zig's promise of= =C2=A0interoperability with C [1].

Given that I= 9;m more comfortable with Zig compiler's promises, the thinking was tha= t
understanding the details will be simpler for me, when the majo= rity of code is generated
by AIs. In practice this didn't wor= k out: the=C2=A0interoperability has number of corner cases,
that= , as an example, doesn't "just work" with kernel's linker= .

So it's not Zig the language was the issue. = But the extra supporting layers needed
to make it work required m= ore involvement than I (naively) hoped it will be.

Although, it works, I'm willing to rewrite Zig's chunk back to C, = just to avoid it to be an easy
target to latch on in the critics = of the approach.


On Wed, 11 Mar 2026 at 16:16, Bugs Beastie &l= t;bugsbeastie@gm= ail.com> wrote:
Mar 10, 2026 20:33:53 Vladimir Varankin <vladimir@varank.in>:

> I recently wrote a blog post [1] sharing my experience of rebuilding > a Wi-Fi driver for BCM4350 for FreeBSD with the help of agenting AI > tooling.
>
Omitting any comments about AI usege,...cool and impressive! :)

Very practical question:
Given the workflow, prompts, AI models to use, etc. are in place AND you ha= ve a physical Raspberry Pi 4, how long would it take to vibe-port brcmfmac4= 3455-sdio wifi driver? The complication it is attached via SDIO interface, = not PCI!

Question out of curiosity:
C/Zig split rationale - at the end 94.7% of code is in C, 4.7% in Zig. Woul= d you still go for anything in Zig again?

> I'm aware that different groups of people have different opinions = about
> the topic of using AI in software development. Still I think this was<= br> > a fairly interesting experiment, and I'm curious to hear the opini= on
> on the approach and the results, from people close to in-tree drivers<= br> > development.
>
> The GitHub repository [2] includes documentation about the testing
> approach, recorded decisions and know issues (which I'm =E2=80=94 = still with
> the help of AI agents =E2=80=94 addressing in my spare time).
>
> P.S. Just to be absolute clear: I'm not proposing or suggesting to=
> upstream the code of this driver. Neither do I think that in the curre= nt
> state the AIs can vibe-code something reliable in one go. But I do thi= nk,
> the tooling can be a huge multiplier for building, testing, explaining= ,
> reviewing, etc large bodies of complex code.
>
> Cheers,
> V.
>
> [1]: https://vladimir.varank.in/notes= /2026/02/freebsd-brcmfmac/
> [2]: https://github.com/narqo/freebsd-brcmfmac
>
> --
> Vladimir Varankin
> vladimir@varan= k.in




--
Vladimir Varankin


--
Vladimir Varankin
--00000000000020a270064e0aa981-- From nobody Sun Mar 29 07:49:30 2026 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4fk63W6RQBz6WGr8 for ; Sun, 29 Mar 2026 07:49:43 +0000 (UTC) (envelope-from ben@benhutton.com.au) Received: from mail.myuniquemail.com (mail.myuniquemail.com [115.70.107.139]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4fk63V26Pxz3M7J for ; Sun, 29 Mar 2026 07:49:41 +0000 (UTC) (envelope-from ben@benhutton.com.au) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=reject) header.from=benhutton.com.au; spf=pass (mx1.freebsd.org: domain of ben@benhutton.com.au designates 115.70.107.139 as permitted sender) smtp.mailfrom=ben@benhutton.com.au Received: from [10.128.2.109] (unknown [10.128.10.1]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mail.myuniquemail.com (Postfix) with ESMTPSA id 2126B1DB7C3 for ; Sun, 29 Mar 2026 15:49:31 +0800 (AWST) Message-ID: <2b031f6d-936d-4ec0-89ec-a12a5b6597aa@benhutton.com.au> Date: Sun, 29 Mar 2026 15:49:30 +0800 List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-wireless@freebsd.org Sender: owner-freebsd-wireless@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: How is testing going? To: wireless@freebsd.org References: <6p4r5o3-4218-sn14-o712-7944359sqno6@mnoonqbm.arg> Content-Language: en-AU From: Ben Hutton In-Reply-To: <6p4r5o3-4218-sn14-o712-7944359sqno6@mnoonqbm.arg> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-1.10 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_SPAM_SHORT(0.70)[0.699]; DMARC_POLICY_ALLOW(-0.50)[benhutton.com.au,reject]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; FREEFALL_USER(0.00)[ben]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:10143, ipnet:115.70.104.0/21, country:AU]; R_DKIM_NA(0.00)[]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[wireless@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[wireless@freebsd.org]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4fk63V26Pxz3M7J X-Spamd-Bar: - Working allot better for me than the last update. On 3/21/26 07:04, Bjoern A. Zeeb wrote: > Hi, > > to those who have updated.  Did you encounter further problems than > reported, > any instabilities, etc. now that it's been a few more days? > > /bz > From nobody Sun Mar 29 15:38:37 2026 X-Original-To: freebsd-wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4fkJSq00Pnz6WYJP for ; Sun, 29 Mar 2026 15:38:51 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R13" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4fkJSp4nlmz4JGb for ; Sun, 29 Mar 2026 15:38:50 +0000 (UTC) (envelope-from eduardo@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1774798730; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=sME5kKsksSGLXS91+LY9/sxVbaGat2CNnIENEZcCKCk=; b=hccwSYhE5HO5TnAx9DNo3UsDWyktGO08f8NasJMHb3V/q+j3rJGdbmzoe4dkhBXsP0yGM1 jDlAEG4aX3pjcehOx3gdkQ/v+q588vuKakJMFhGsHJwMzusiNl1XqDobcjVk5Ryp8zeYGO Q8BVXPR8xmXZpzqdsaklTZCR1BRO7CJQDa3x8odt95chcIMATBVAZ4dAe2ICBGXFEQkSrV huJR2GFCohR5cQtcMJ4Rfumwu3AN2PVlHxgkD3SVW7irs6GNEyAKn+G8aXl7kdSHmsjz+k 7IFTELvRqUfSuPc1+rFCZm+QESPLxuKW1y8gmTXC7wqGjhnS6RTsAYlzDG3PHA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1774798730; a=rsa-sha256; cv=none; b=dnjrqlY/6rgGHqNb217MJw9ULIJ0CBTUxaWP5gFPPhFeSWOF2UgAgfDL4mxq9/7d22t2JR C35nav1Nkzd1Pn0H6G6q0L92baHKr+XZ2y7CddGnaCrFWB5HsSnx3eCNOilqK+TjRjqihd NU3prOKa4zfncWE5sH/20iS6c0RSiHTWlUesyF2iElTMEe5kcJwsIPI/MqqJZqQHyDOMMz dRV1vH5ydPteDcAVxMHSEQRZVk4cNW3LZty3a2VWeumy/3nX5FOCMn3MtofagGFhqyu7Go ENNdiOFExLggvhoUHF3dneabyKqAV09ro3AebfZ+JzJHyd2jvmPpTfcht52Z0A== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1774798730; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=sME5kKsksSGLXS91+LY9/sxVbaGat2CNnIENEZcCKCk=; b=GVstb6nZtBQ57MXWNwtrcG5ZtAjWAkK9zmPFfJdHwZk1w8VUJzqLhi1xWHwSJ1b/Hgq0Uj 6GzuUnlNjq7UqqERwziBFatmy2xYBULZYncSa+2Xtp9y3mjbNYyOMnIJLZyrjichbzGfxN WGaut3Ro8RFGQWZccFdhTJQRusUrdVTxuhcSdTp5QUO31oNBVvouOl3IO4JNLlfWYhU3EL vDraOV05a89AngVwTidUB1WZnyIOzP6piCQm9FCYvzZsRFmHpCa/selsf9Que9oajq2U1n K75jjfnLxu+GWsdAxpE0ZueV76G/Gizyrz/DNDuuTVq3Rsu8wOwV3NxI9YPq9Q== Received: from mail-lj1-f179.google.com (mail-lj1-f179.google.com [209.85.208.179]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) (Authenticated sender: eduardo) by smtp.freebsd.org (Postfix) with ESMTPSA id 4fkJSp3nBKz1586 for ; Sun, 29 Mar 2026 15:38:50 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: by mail-lj1-f179.google.com with SMTP id 38308e7fff4ca-386c441ba1dso1796551fa.2 for ; Sun, 29 Mar 2026 08:38:50 -0700 (PDT) X-Forwarded-Encrypted: i=1; AJvYcCWse4SlEgCSc9Cj0FUAj+t24tKHF5ND66aiS32XLz+Vefh1SMEMjm+ljdNg5VP25GB29x6ZXVIeI5LJId8TOAre@freebsd.org X-Gm-Message-State: AOJu0Yw6Z5eo9QURcoQUwT92Nit7OqiQlOwsfO4zYcUM4pUXiqMo2dl0 mDLIbnLY5KWEU3ErZwFhEhRa0WtwVAV1i6MYXFlZYNxqBAIMSwR7HBlAGS/eteulOuZm36K4xVN RatOCb4Q6sIoLTRJRJ2EncAKrePuXvMQ= X-Received: by 2002:a05:651c:4cb:b0:38a:3473:526d with SMTP id 38308e7fff4ca-38c740675c0mr14719321fa.7.1774798728660; Sun, 29 Mar 2026 08:38:48 -0700 (PDT) List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-wireless@freebsd.org Sender: owner-freebsd-wireless@FreeBSD.org MIME-Version: 1.0 References: <75f56507-49e8-4f43-987f-7025d62b0bd9@gmail.com> In-Reply-To: From: Nuno Teixeira Date: Sun, 29 Mar 2026 16:38:37 +0100 X-Gmail-Original-Message-ID: X-Gm-Features: AQROBzC4MD6avcwv4Fxl35JhcxVka1hnyBj5AdfNo7xQLJ-eJzWqIiPVpwc4NdM Message-ID: Subject: Re: Rebuilding brcmfmac Wi-Fi driver with the help of AI To: Vladimir Varankin Cc: Bugs Beastie , freebsd-wireless@freebsd.org Content-Type: multipart/alternative; boundary="000000000000c50fc3064e2b87cb" --000000000000c50fc3064e2b87cb Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, It seems that OpenBSD and NetBSD have drivers for BCM43455. Could those drivers be imported fo FreeBSD? Thanks, Vladimir Varankin escreveu (s=C3=A1bado, 28/03/2026 = =C3=A0(s) 00:26): > Hey-hey, > > >> Given the workflow, prompts, AI models to use, etc. are in place AND > you have > >> a physical Raspberry Pi 4, how long would it take to vibe-port > brcmfmac43455-sdio > >> wifi driver? The complication it is attached via SDIO interface, not > PCI! > > > > That'd be fun thing to try. I've forgotten that RPi4 comes with a > broadcom chip. > > Will find some time to spin up a testing stand, and will see how that > goes. > > This's been keeping me busy, and it hasn't been a smooth ride so far. But > I finally > saw some exciting progress today. > > Currently, the codebase is a mess [1]. But we (mainly agents, of course) > got > Raspberry Pi 4b to connect to my home Wi-Fi AP (5GHz, WPA2), and sent > traffic > to the Internet. > > One problem was that the stock kernel, that came with the RPI image > (FreeBSD-15.0-RELEASE-arm64-aarch64-RPI.img) needed patching and a fixed > device > tree overlay. The RPI4-HOWTO.md [2] in the driver's repo has more details= . > > *Again, to be 100% clear and hones: these are experimental "vibes" to see > how far > the AI tooling can push. I'm welcoming productive feedback about the > results.* > > The repo's docs/00-progress.md [3] has a list of next steps to fix, befor= e > I'll ask the agents > to do a deep code-review and refactoring. > > Details of the tests: > > freebsd@rpi4-freebsd-1:~ % uname -v > FreeBSD 15.0-STABLE #2 9c49c393a81b-dirty: Fri Mar 27 22:59:19 CET 2026 > v@freebsd-test-0:/usr/obj/usr/src/arm64.aarch64/sys/SDIO > > % dmesg | grep -i 'raspberry pi' > gpio1: on bcm2835_firmware0 > > % sysctl hw.model > hw.model: ARM Cortex-A72 r0p3 > > % ls /boot/firmware/ | grep brcm > brcmfmac43455-sdio.bin > brcmfmac43455-sdio.clm_blob > brcmfmac43455-sdio.txt > > % kldstat > Id Refs Address Size Name > 1 8 0xffff000000000000 1446958 kernel > 2 1 0xffff0000b2c00000 33000 if_brcmfmac.ko > > % ifconfig wlan0 > wlan0: flags=3D8843 metric 0 mtu = 1500 > options=3D0 > ether dc:a6:32:29:7b:1b > inet 192.168.188.182 netmask 0xffffff00 broadcast 192.168.188.255 > groups: wlan > ssid =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 channel 116 (= 5580 MHz 11a ht/20) bssid 1c=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88= =E2=96=88:3c > country 511 authmode WPA2/802.11i privacy ON deftxkey UNDEF > AES-CCM 2:128-bit AES-CCM 3:128-bit AES-CCM ucast:128-bit txpower 0 > bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 60 -ht -htcompat -ampdu > ampdulimit 8k -amsdu -stbc -ldpc -uapsd wme roaming MANUAL > parent interface: brcmfmac0 > media: IEEE 802.11 Wireless Ethernet MCS mode 11na > status: associated > nd6 options=3D29 > > % traceroute -i wlan0 1.1.1.1 > traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 40 byte packets > 1 192.168.188.114 (192.168.188.114) 185.541 ms 34.019 ms 53.549 ms > 2 192.168.188.1 (192.168.188.1) 49.716 ms 47.651 ms 49.251 ms > 3 10.103.18.1 (10.103.18.1) 55.914 ms 44.769 ms 57.156 ms > 4 89.246.252.169 (89.246.252.169) 46.803 ms 13.387 ms 48.198 ms > 5 i689729BA.versanet.de (104.151.41.186) 52.102 ms 51.937 ms 50.030 > ms > 6 62.214.73.216 (62.214.73.216) 53.640 ms 43.454 ms 58.782 ms > 7 62.214.73.217 (62.214.73.217) 49.132 ms 49.143 ms 46.480 ms > 8 one.one.one.one (1.1.1.1) 51.158 ms 49.501 ms 56.651 ms > > P.S. Zig has gone from the driver's codebase. Making it work in a kernel > driver > on aarch64 turned out even more challenging today. I'll park the idea int= o > a backlog > of future playground projects. > > [1]: https://github.com/narqo/freebsd-brcmfmac > [2]: > https://github.com/narqo/freebsd-brcmfmac/blob/629b801123966bbbea71d5ff8c= cb7a789f43e792/RPI4-HOWTO.md > [3]: > https://github.com/narqo/freebsd-brcmfmac/blob/629b801123966bbbea71d5ff8c= cb7a789f43e792/docs/00-progress.md > > Cheers, > V. > > > On Thu, 12 Mar 2026 at 09:56, Vladimir Varankin > wrote: > >> > Given the workflow, prompts, AI models to use, etc. are in place AND >> you have >> > a physical Raspberry Pi 4, how long would it take to vibe-port >> brcmfmac43455-sdio >> > wifi driver? The complication it is attached via SDIO interface, not >> PCI! >> >> That'd be fun thing to try. I've forgotten that RPi4 comes with >> a broadcom chip. >> Will find some time to spin up a testing stand, and will see how that >> goes. >> >> > C/Zig split rationale - at the end 94.7% of code is in C, 4.7% in Zig= . >> Would you still >> > go for anything in Zig again? >> >> Initially I was sold by Zig's promise of interoperability with C [1]. >> >> Given that I'm more comfortable with Zig compiler's promises, the >> thinking was that >> understanding the details will be simpler for me, when the majority of >> code is generated >> by AIs. In practice this didn't work out: the interoperability has numbe= r >> of corner cases, >> that, as an example, doesn't "just work" with kernel's linker. >> >> So it's not Zig the language was the issue. But the extra supporting >> layers needed >> to make it work required more involvement than I (naively) hoped it will >> be. >> >> Although, it works, I'm willing to rewrite Zig's chunk back to C, just t= o >> avoid it to be an easy >> target to latch on in the critics of the approach. >> >> [1]: >> https://ziglang.org/learn/overview/#integration-with-c-libraries-without= -ffibindings >> >> On Wed, 11 Mar 2026 at 16:16, Bugs Beastie wrote= : >> >>> Mar 10, 2026 20:33:53 Vladimir Varankin : >>> >>> > I recently wrote a blog post [1] sharing my experience of rebuilding >>> > a Wi-Fi driver for BCM4350 for FreeBSD with the help of agenting AI >>> > tooling. >>> > >>> Omitting any comments about AI usege,...cool and impressive! :) >>> >>> Very practical question: >>> Given the workflow, prompts, AI models to use, etc. are in place AND yo= u >>> have a physical Raspberry Pi 4, how long would it take to vibe-port >>> brcmfmac43455-sdio wifi driver? The complication it is attached via SDI= O >>> interface, not PCI! >>> >>> Question out of curiosity: >>> C/Zig split rationale - at the end 94.7% of code is in C, 4.7% in Zig. >>> Would you still go for anything in Zig again? >>> >>> > I'm aware that different groups of people have different opinions abo= ut >>> > the topic of using AI in software development. Still I think this was >>> > a fairly interesting experiment, and I'm curious to hear the opinion >>> > on the approach and the results, from people close to in-tree drivers >>> > development. >>> > >>> > The GitHub repository [2] includes documentation about the testing >>> > approach, recorded decisions and know issues (which I'm =E2=80=94 sti= ll with >>> > the help of AI agents =E2=80=94 addressing in my spare time). >>> > >>> > P.S. Just to be absolute clear: I'm not proposing or suggesting to >>> > upstream the code of this driver. Neither do I think that in the >>> current >>> > state the AIs can vibe-code something reliable in one go. But I do >>> think, >>> > the tooling can be a huge multiplier for building, testing, explainin= g, >>> > reviewing, etc large bodies of complex code. >>> > >>> > Cheers, >>> > V. >>> > >>> > [1]: https://vladimir.varank.in/notes/2026/02/freebsd-brcmfmac/ >>> > [2]: https://github.com/narqo/freebsd-brcmfmac >>> > >>> > -- >>> > Vladimir Varankin >>> > vladimir@varank.in >>> >>> >>> >> >> -- >> Vladimir Varankin >> vladimir@varank.in >> > > > -- > Vladimir Varankin > vladimir@varank.in > --=20 Nuno Teixeira FreeBSD UNIX: Web: https://FreeBSD.org --000000000000c50fc3064e2b87cb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,

It seems that OpenBSD and NetBSD = have drivers for BCM43455. Could those drivers be imported fo FreeBSD?
<= div>
Thanks,

Vladimir Varankin <= ;vladimir@varank.in> escreveu = (s=C3=A1bado, 28/03/2026 =C3=A0(s) 00:26):
Hey-hey,

>> Given = the workflow, prompts, AI models to use, etc. are in place AND you have
= >> a physical Raspberry Pi 4, how long would it take to vibe-port brc= mfmac43455-sdio
>> wifi driver? The complication it is attached vi= a SDIO interface, not PCI!
>
> That'd be fun thing to try. = I've forgotten that RPi4 comes with a broadcom chip.
> Will find = some time to spin up a testing stand, and will see how that goes.

Th= is's been keeping me busy, and it hasn't been a smooth ride so far.= But I finally
saw some exciting progress today.

Currently, the c= odebase is a mess [1]. But we (mainly agents, of course) got
Raspberry P= i 4b to connect to my home Wi-Fi AP (5GHz, WPA2), and sent traffic
to th= e Internet.

One problem was that the stock kernel, that came with th= e RPI image
(FreeBSD-15.0-RELEASE-arm64-aarch64-RPI.img) needed patching= and a fixed device
tree overlay. The RPI4-HOWTO.md [2] in the driver= 9;s repo has more details.

*Again, to be 100% clear and hones: these= are experimental "vibes" to see how far
the AI tooling can pu= sh. I'm welcoming productive feedback about the results.*

T= he repo's docs/00-progress.md [3] has a list of next steps to fix, befo= re I'll ask the agents
to do a deep code-review and refactori= ng.

Details of the tests:

freebsd@rpi4-freebsd-1:~ % uname = -v
FreeBSD 15.0-STABLE #2 9c49c393a81b-dirty: Fri Mar 27 22:59:19 CET 20= 26 v@freebsd-test-0:/usr/obj/usr/src/arm64.aarch64/sys/SDIO

% dmesg = | grep -i 'raspberry pi'
gpio1: <Raspberry Pi Firmware GPIO c= ontroller> on bcm2835_firmware0

% sysctl hw.model
hw.model: AR= M Cortex-A72 r0p3

% ls /boot/firmware/ | grep brcm
brcmfmac43455-= sdio.bin
brcmfmac43455-sdio.clm_blob
brcmfmac43455-sdio.txt

% = kldstat
Id Refs Address =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0Size Name
=C2=A01 =C2=A0 =C2=A08 0xffff000000000000 =C2=A01446958= kernel
=C2=A02 =C2=A0 =C2=A01 0xffff0000b2c00000 =C2=A0 =C2=A033000 if_= brcmfmac.ko

% ifconfig wlan0
wlan0: flags=3D8843<UP,BROADCAST,= RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=3D0
ether d= c:a6:32:29:7b:1b
inet 192.168.188.182 netmask 0xffffff00 broadcast 192.= 168.188.255
groups: wlan
ssid =E2=96=88=E2=96=88=E2=96=88=E2=96=88= =E2=96=88=E2=96=88 channel 116 (5580 MHz 11a ht/20) bssid 1c=E2=96=88=E2=96= =88=E2=96=88=E2=96=88=E2=96=88=E2=96=88:3c
country 511 authmode WPA2/80= 2.11i privacy ON deftxkey UNDEF
AES-CCM 2:128-bit AES-CCM 3:128-bit AES= -CCM ucast:128-bit txpower 0
bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 6= 0 -ht -htcompat -ampdu
ampdulimit 8k -amsdu -stbc -ldpc -uapsd wme roam= ing MANUAL
parent interface: brcmfmac0
media: IEEE 802.11 Wireless = Ethernet MCS mode 11na
status: associated
nd6 options=3D29<PERFO= RMNUD,IFDISABLED,AUTO_LINKLOCAL>

% traceroute -i wlan0 1.1.1.1traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 40 byte packets
=C2=A01 = =C2=A0192.168.188.114 (192.168.188.114) =C2=A0185.541 ms =C2=A034.019 ms = =C2=A053.549 ms
=C2=A02 =C2=A0192.168.188.1 (192.168.188.1) =C2=A049.716= ms =C2=A047.651 ms =C2=A049.251 ms
=C2=A03 =C2=A010.103.18.1 (10.103.18= .1) =C2=A055.914 ms =C2=A044.769 ms =C2=A057.156 ms
=C2=A04 =C2=A089.246= .252.169 (89.246.252.169) =C2=A046.803 ms =C2=A013.387 ms =C2=A048.198 ms=C2=A05 =C2=A0= i689729BA.versanet.de (104.151.41.186) =C2=A052.102 ms =C2=A051.937 ms = =C2=A050.030 ms
=C2=A06 =C2=A062.214.73.216 (62.214.73.216) =C2=A053.640= ms =C2=A043.454 ms =C2=A058.782 ms
=C2=A07 =C2=A062.214.73.217 (62.214.= 73.217) =C2=A049.132 ms =C2=A049.143 ms =C2=A046.480 ms
=C2=A08 =C2=A0on= e.one.one.one (1.1.1.1) =C2=A051.158 ms =C2=A049.501 ms =C2=A056.651 ms
=
P.S. Zig has gone from the driver's codebase. Making it work in a k= ernel driver
on aarch64 turned out even more challenging today. I'll= park the idea into a backlog
of future playground projects.
<= br>[1]: https://github.com/narqo/freebsd-brcmfmac
[2]: https://github.com/narqo/freebsd-b= rcmfmac/blob/629b801123966bbbea71d5ff8ccb7a789f43e792/RPI4-HOWTO.md
= [3]: https:/= /github.com/narqo/freebsd-brcmfmac/blob/629b801123966bbbea71d5ff8ccb7a789f4= 3e792/docs/00-progress.md

Cheers,
V.


On Thu, 12 Mar 2026 at 09:56, Vladimir Varank= in <vladimir@var= ank.in> wrote:
> Given the workflow, prompts, A= I models to use, etc. are in place AND you have
> a physical Raspberry Pi 4, how long would = it take to vibe-port=20 brcmfmac43455-sdio
> wifi driver? The complication= it is attached via SDIO interface, not PCI!

That'd be fun= thing to try. I've forgotten that RPi4 comes with a=C2=A0broadcom=C2= =A0chip.
Will find some time to spin up a testing stand, and will= see how that goes.

>= =C2=A0 C/Zig split rationale - at the end 94.7% of code is in C, 4.7% in Zig. Woul= d you still
> go for anything in Zig again?
<= div dir=3D"ltr">
Initially I was sold by Zig's promise of= =C2=A0interoperability with C [1].

Given that I= 9;m more comfortable with Zig compiler's promises, the thinking was tha= t
understanding the details will be simpler for me, when the majo= rity of code is generated
by AIs. In practice this didn't wor= k out: the=C2=A0interoperability has number of corner cases,
that= , as an example, doesn't "just work" with kernel's linker= .

So it's not Zig the language was the issue. = But the extra supporting layers needed
to make it work required m= ore involvement than I (naively) hoped it will be.

Although, it works, I'm willing to rewrite Zig's chunk back to C, = just to avoid it to be an easy
target to latch on in the critics = of the approach.


On Wed, 11 Mar 2026 at 16:16, Bugs Beastie &l= t;bugsbeastie@gm= ail.com> wrote:
Mar 10, 2026 20:33:53 Vladimir Varankin <vladimir@varank.in>:

> I recently wrote a blog post [1] sharing my experience of rebuilding > a Wi-Fi driver for BCM4350 for FreeBSD with the help of agenting AI > tooling.
>
Omitting any comments about AI usege,...cool and impressive! :)

Very practical question:
Given the workflow, prompts, AI models to use, etc. are in place AND you ha= ve a physical Raspberry Pi 4, how long would it take to vibe-port brcmfmac4= 3455-sdio wifi driver? The complication it is attached via SDIO interface, = not PCI!

Question out of curiosity:
C/Zig split rationale - at the end 94.7% of code is in C, 4.7% in Zig. Woul= d you still go for anything in Zig again?

> I'm aware that different groups of people have different opinions = about
> the topic of using AI in software development. Still I think this was<= br> > a fairly interesting experiment, and I'm curious to hear the opini= on
> on the approach and the results, from people close to in-tree drivers<= br> > development.
>
> The GitHub repository [2] includes documentation about the testing
> approach, recorded decisions and know issues (which I'm =E2=80=94 = still with
> the help of AI agents =E2=80=94 addressing in my spare time).
>
> P.S. Just to be absolute clear: I'm not proposing or suggesting to=
> upstream the code of this driver. Neither do I think that in the curre= nt
> state the AIs can vibe-code something reliable in one go. But I do thi= nk,
> the tooling can be a huge multiplier for building, testing, explaining= ,
> reviewing, etc large bodies of complex code.
>
> Cheers,
> V.
>
> [1]: https://vladimir.varank.in/notes= /2026/02/freebsd-brcmfmac/
> [2]: https://github.com/narqo/freebsd-brcmfmac
>
> --
> Vladimir Varankin
> vladimir@varan= k.in




--
Vladimir Varankin


--
Vladimir Varankin


--
Nuno Teixeira
=
FreeBSD UNIX:=C2=A0 <eduardo@FreeBSD.org>=C2=A0 =C2=A0Web:=C2=A0 https://Fr= eeBSD.org
--000000000000c50fc3064e2b87cb-- From nobody Sun Mar 29 15:55:16 2026 X-Original-To: freebsd-wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4fkJqv4SMPz6WbDQ for ; Sun, 29 Mar 2026 15:55:23 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R13" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4fkJqv39Qnz4Kbx; Sun, 29 Mar 2026 15:55:23 +0000 (UTC) (envelope-from bz@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1774799723; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=x/N0yALM0BlQ5tj5QE6EDu0YCN23utnYRk5aWzuyzac=; b=CP83c5Oa/8sQKq4oMuZwx0s9gMzfOe8AJI4iOBymgS8W2aNXlFpFH+E3HlcXjxEezgYJpx W6yYtF8u1O4FUQ57rcSc16AJwMGV/ELuAxFkbDUuhuzHqy8q3yQ764iWhm6GNAUlTOZUK3 jB+T5VIWITsmTlegWLDfscwzXVRZB9fyQjF46cCaA4WiyzPF/W1LZzW1q8yZyBYaezXrXq yDyl3KnR7rdD0IFONDU0kOw169pLfAB7gc6zdyiU8eNd7b9ozEhUan8d/zeFyn5SPOTogO 3xVUDSU8hsoEELvtP6/s26byi9KLveE7OCi00qYVyvW/5a4F9zF03tqpLNHMeg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1774799723; a=rsa-sha256; cv=none; b=JmUNurA3rYItvxlOzIDYZbLaqcoqDzfAwJVg6tWCUzTFSS5WBM2/hue+iuczXkHC7/Ez1P 2OZy0/BPEDVBc6PI3BCFhkvdDapZl89evvZ3mnKEVaNEpImheYOBwjEM3JcNZLHITa5SHA HsXrVWpFmhhx1N+gxdz5Fl+0xvloki8iwb0lAdX0r4vIO8Q7gJodswfSrLCItlIhAZogFk DOMRwk0dy75nefrpzoFlW7Q3811zxvyvI1K7i49f+2Q8Ph+IuJHVVYQ2VK5m1c3yoH/CP4 KBWtehEsuF/ulRV5R7panNzFG6xp5b8fbzd5bb2RyDSw7oGVm/NsE/lvJVSaJg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1774799723; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=x/N0yALM0BlQ5tj5QE6EDu0YCN23utnYRk5aWzuyzac=; b=ZHM2gjs8E2IblzxDierdPWFMCquvrUHnmg/BfzWPMDSWCrPcSbqHwJxDGqwx8UebbRMrw9 lLb2klIEmnpfehkmHhbeqWGvnH1K7jOlmhcNWGR/czAT51nVqua6r5Y5Hzn9ubgAQSl9GB hiHFx/sld/rHVZaEBNlC5jbDG32Ia21rvqdP1qCD3xrrJiW8RYh1cU/zo2Hjxn/kipqZvu 2qg3Jr8rCa/3sqnx9r4tmIlc+Werdrr3/sErMDQzt5f7mBQBVU/ACKvfhT4VLlbTRtZ6wK Sck7eHA7YyLJ1s1r0tPm+KN82yQjo/sl+3kSlvHvQrVTyLB+aV1d7MjHKlWYGQ== Received: from mx-01.divo.sbone.de (mx-01.divo.sbone.de [IPv6:2003:a:140a:2200:6:594:fffe:19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (prime256v1) client-digest SHA256) (Client CN "mx-01.divo.sbone.de", Issuer "E7" (not verified)) (Authenticated sender: bz/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4fkJqv1fjLz14qY; Sun, 29 Mar 2026 15:55:23 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx-01.divo.sbone.de (Postfix) with ESMTPS id 26964A64805; Sun, 29 Mar 2026 15:54:58 +0000 (UTC) Received: from content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id E30DD2D029E9; Sun, 29 Mar 2026 15:55:18 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) by content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (amavisd-new, port 10024) with ESMTP id 91PWjWJk12T0; Sun, 29 Mar 2026 15:55:18 +0000 (UTC) Received: from nv.t4-02.sbone.de (nv.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id CCE6A2D029D8; Sun, 29 Mar 2026 15:55:17 +0000 (UTC) Date: Sun, 29 Mar 2026 15:55:16 +0000 (UTC) From: "Bjoern A. Zeeb" To: Nuno Teixeira cc: freebsd-wireless@freebsd.org Subject: porting bwfm from N/OBSD [was Re: Rebuilding brcmfmac Wi-Fi driver with the help of AI] In-Reply-To: Message-ID: References: <75f56507-49e8-4f43-987f-7025d62b0bd9@gmail.com> X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-wireless@freebsd.org Sender: owner-freebsd-wireless@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed On Sun, 29 Mar 2026, Nuno Teixeira wrote: Hi Nuno, > It seems that OpenBSD and NetBSD have drivers for BCM43455. Could those > drivers be imported fo FreeBSD? There's been like at least 3 or 4 people I know off, if not more, who started porting bwfm over the course of the last years; everyone went silent. That's the reason we now do have a compiling brcmfmac driver for LinuxKPI in the tree; it laods firmware on PCIe on X86 (and with a workaround on arm64) (and in theory on USB in my dev tree). In another dev tree sits a 85% finished SDIO implementation mostly tested on rtw88, where I already create wlan interfaces and have scanning results, etc. The one thing which is missing for brcmfmac really is a cfg80211/netdev compat shim to drive this, of which we porbably have half as well already in LinuxKPI. But that's kind-of disruptive to the other ongoing work for all the other mac80211-based drivers and so I have not really had a good look. It could boil down to three functions, it could boil down to a lot more. Preliminary LinuxKPI USB support is blocked on cleaning up some older compiler options in the tree, which we currently do not yet understand. Getting SDIO out as-is simply "need time to sit down", rebase and open reviews. In other words I need to finish the rtw8x (and mt76) work before I can find free time to look at it. rtw8x/LinuxKPI I really want in 15.1-R and the time for that is ticking. /bz -- Bjoern A. Zeeb r15:7 From nobody Sun Mar 29 15:56:35 2026 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4fkJsL25lmz6WbK9 for ; Sun, 29 Mar 2026 15:56:38 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R13" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4fkJsL1L9Sz4L5H; Sun, 29 Mar 2026 15:56:38 +0000 (UTC) (envelope-from bz@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1774799798; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=gTKJEzYf/fD//jbsmP7auhcmKCwBIVdu65sOZpmYUHc=; b=DPRXZ4OXYCghBQDKQm2vOjPx54kJhvI8cJb8YH3TpxZmeeKWd8bYJCKBj9BoIzaVtf7Vno +3TJIHmDPv1I/RpkhdKi+atF4k4yyM5Le0OY+rSKVoi1e7ws3y6iiRLhsMTBUcMwVFIim9 H/NKf59lwxD7IqyFudIcwP+RWBujK355YebNvh2HDA10bK34LR8UtFt0n1Km03ayAfpajb QzwtQFm62xcp/uFcNbWm1SIKCNvhs8gDyyT4ftzu46rJ5t3oOHEifTJzszZ+29SJMV1zFM GDeyuRPq2pvI2mY/nB2cyZChpf62Q5lBoyaHAV48F2N8WA2P1D+8JyQDhcRSog== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1774799798; a=rsa-sha256; cv=none; b=Gb5h/vmeDfSBpkvcsphjirG9xsplDHs8hGTRd1l46veQXdURuxVQACPrESQafYIZvqKBMb eHUu3Sn7bLb3e1vgH1Dxg9AyfqY8nT70X414u45QvYdaus5Er3KetB5mVZUYAEhCqV4n8k 59WImAj60UYXD24Ge+FwBzkW1MeuiuxzMvqa4M1zv9hC6DivChCCsaxjao5r/72JftwYha wqFAZk7dn4Zev/xyTQMty/wEVZcvqaCMG2mEUfGSguH67084CZzkgcR1N4dHG9pjrHUIgx idEyQXAxNA1iUwa3RdZZVm+gFJr0NxjrVsCarcB7gJQqhRXrVkXUk/RnQA7Srg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1774799798; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=gTKJEzYf/fD//jbsmP7auhcmKCwBIVdu65sOZpmYUHc=; b=eNe5IGqEC4HqXYf0nHwlbaoQPM7+BETcnCKXurf99sojnFy7H8EdgNBVI9OCTA5/YPAAEv eFm1AwVO5THvT0Uuc0+vbkJE6M2xOk5wOt1SiQcc7e1C1cSBNRVKgrt5bF68YOtRzLB89R 2eVefE+4U0O5WqS5IONN5YSVAen8DYdhgvFwH6SZr+3em2Aiy9v+8aYt5924/eEYax2dn6 extnzg1HKD4cd/bHlHZsJy1AZitxikJj+3yMmjMCcpT5vVsGGMx5EY/LvKZEzpz8++su8K Nh3xU6gQ6ckNIojMPAwwFC6/gHCm899R75/de/sSIQcCx4jlFSSYCykcRAi1Dg== Received: from mx-01.divo.sbone.de (mx-01.divo.sbone.de [IPv6:2003:a:140a:2200:6:594:fffe:19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (prime256v1) client-digest SHA256) (Client CN "mx-01.divo.sbone.de", Issuer "E7" (not verified)) (Authenticated sender: bz/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4fkJsL0762z15Zy; Sun, 29 Mar 2026 15:56:37 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx-01.divo.sbone.de (Postfix) with ESMTPS id 95B28A64808; Sun, 29 Mar 2026 15:56:15 +0000 (UTC) Received: from content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 7DDE32D029EA; Sun, 29 Mar 2026 15:56:36 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) by content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (amavisd-new, port 10024) with ESMTP id oXPNiPurniFS; Sun, 29 Mar 2026 15:56:35 +0000 (UTC) Received: from nv.t4-02.sbone.de (nv.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 7D4A22D029D8; Sun, 29 Mar 2026 15:56:35 +0000 (UTC) Date: Sun, 29 Mar 2026 15:56:35 +0000 (UTC) From: "Bjoern A. Zeeb" To: Ben Hutton cc: FreeBSD wireless mailing list Subject: Re: How is testing going? In-Reply-To: <2b031f6d-936d-4ec0-89ec-a12a5b6597aa@benhutton.com.au> Message-ID: References: <6p4r5o3-4218-sn14-o712-7944359sqno6@mnoonqbm.arg> <2b031f6d-936d-4ec0-89ec-a12a5b6597aa@benhutton.com.au> X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-wireless@freebsd.org Sender: owner-freebsd-wireless@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed On Sun, 29 Mar 2026, Ben Hutton wrote: Hi Ben, > Working allot better for me than the last update. Thanks for the feedback. Can you elaborate a bit more? >From which to which version did you go? What's currently troubling? Sorry for asking but I need the details in order to try to make it even better ;-) /bz -- Bjoern A. Zeeb r15:7 From nobody Sun Mar 29 16:17:12 2026 X-Original-To: freebsd-wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4fkKKK55yYz6Wctv for ; Sun, 29 Mar 2026 16:17:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qv1-f53.google.com (mail-qv1-f53.google.com [209.85.219.53]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4fkKKJ7259z4N0R for ; Sun, 29 Mar 2026 16:17:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; arc=pass ("google.com:s=arc-20240605:i=1"); dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none); spf=pass (mx1.freebsd.org: domain of adrian.chadd@gmail.com designates 209.85.219.53 as permitted sender) smtp.mailfrom=adrian.chadd@gmail.com Received: by mail-qv1-f53.google.com with SMTP id 6a1803df08f44-89a465bd7edso32046146d6.0 for ; Sun, 29 Mar 2026 09:17:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1774801044; cv=none; d=google.com; s=arc-20240605; b=gtSqGfEMVTgbdGuUfKq4A9aZy6swDtFv0S8ll+ZBt35EN2ZFirSIwc9SZfiSVqzEuA a494TOGsbCakl7KnAJP6X7LEHUWYvLr8X6RJOmXylKHo3EYq1bzdt6/lVMZcRVMA2aPu pYDOLEXvV5E5DrpoKbyO/m3COriDlh5eDMT32kG/fLOK1z7vwin9NLc0eM/UTOwRvnUq oUzIkgf+Tj04xBMnVu8UblnTbOFg2k5SrBA0qO8d+ZoCpItL2cMsYOBt34WKEKcAoLmS 1sSaSKF33KPrBTou4F7g3zhkTGTpuUG1neFa5bR4/rsM7gU/H/kVjvu4gFW4fw3pdKdl KBAw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version; bh=YkWZEN8h8kwkSnQZZCN3Vedn99RaZ5MERL1jPQAnVvM=; fh=lnER0QUGx/uVffA07JgpS21g8jzJn3fQwU7rb+bUxwM=; b=Jy0x2GP1k/vlN8y4LtsDWOLnsJXp8jwDBL8+hX2sys95Pyl3FVA6xrk8PpWNjN6Abl qb5mJSkpFN0gbOR5o5NiMSPdBZSAZlwYRBqV7CcBEoE0xLOLMl0ydbUkyfW3VHphyk4Q LXH8Gf+rO3FJpdP+Mcto0c6Niah3Zqb2HrSEpzzKHYQKn42dG6z6y0iPVtgm5LEuaxGP Khzak52DZIWEmYYFU5L2FwrhnR1ew7cD7Yk0W97AqtJ4vt66KO2M3XD71s+z68k28+/D JGAXJU327AtFC6sTdB0fyu83nAbebC2EdvFII+RTWYVy2XCTSE7SRuKnVdAyg1lbZ+HI fOuw==; darn=freebsd.org ARC-Authentication-Results: i=1; mx.google.com; arc=none X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1774801044; x=1775405844; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-gg:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=YkWZEN8h8kwkSnQZZCN3Vedn99RaZ5MERL1jPQAnVvM=; b=Z/kV+rUSRtOIpFNlw1f5LmOjQLu/7TevI/hlU49gJMYAAh71NVW4+OfvRDrXr6iX8s Ipt8zO3HwhjCds6Qb5MWFvZYU7Ez2Ej94HUDRbM+mMjzdjzcgx+/flk1xtXqBpltYAfA YTDwk35zj20ex3p8DZXQ62R3orYHh/s4OuTKs02yhNA31XMNaKPTnRGGfn/LmGHIYF1a tCkxxi3RQyAXKyWR914WSKIRnuwxiDdE7q2SzrYkcp35Gk4ZLL3YWujZjGoEYTdmtcF6 HdcvlZNTtteHbGgZqcDRjWIkCzC8eak8ttkn/nyaWEqTUbj3QWOr1CISe2/jR2ARJuz4 G/4A== X-Forwarded-Encrypted: i=1; AJvYcCX1fG1aExDxbuNC8T3baMVVTbUhSN6svfTIb3DiOG3XpmubyNHsptObxCmYHtCmPk3dYxWfQmYB/evQchtd5h0l@freebsd.org X-Gm-Message-State: AOJu0Yzc2frQz14R3EMSOVps0V4mwSRdot2w+HUTgwxBV+FGuyvMDTAu ynMxryPybbv2F4QCyiWhpYVjT3Fs+i+yHQZkid8pceAZI1mZI2IWzypvT3p3eft+dVA1bOWWlid +MYSN2bkzfRFgEpJ5FEpnLHOs4BIyFia0xA== X-Gm-Gg: ATEYQzzcBGTdwyxFjSeRtarFZlXjmKW7W+yu7tzPs7C+bXZcXlQvCBtsiHk69fXJ4A/ y28nbgx2Q8hsZa7LFa4dW4pLHtwznEh0tY+DwYBNkN1T+/QfMbg+PXYD21JaqyQaiy2kQucj5ix gWkWXLDmLPXLOC/zibAtlhbUWypOHd33SlEUfWoJSX7pf2BQRpWvecGkd/PdUH1S0/T5nZPv5qB lW2/CIwsdhVvFjUrRz5zHGKOtlBZ5TTwMpWKkM7CSuyKPRJqJspzhMkBoqhJXKqMVIggoqA/c/Z E6SgB9dKYJwxUYdGbZFbPFHvfkoxqVLcBfhm0LNV3yisU57Y4eyVoZ+Cy3eiCZ/OMJ4Pbq6T9Zj 8VkQ2e3ldyFXA3jzV0XHycO3gtP4= X-Received: by 2002:ad4:5c8b:0:b0:89c:55b1:c8dc with SMTP id 6a1803df08f44-89ce8d8a990mr132032186d6.21.1774801043721; Sun, 29 Mar 2026 09:17:23 -0700 (PDT) List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-wireless@freebsd.org Sender: owner-freebsd-wireless@FreeBSD.org MIME-Version: 1.0 References: <75f56507-49e8-4f43-987f-7025d62b0bd9@gmail.com> In-Reply-To: From: Adrian Chadd Date: Sun, 29 Mar 2026 09:17:12 -0700 X-Gm-Features: AQROBzAZ0OXf2BpQZp6zDkjoehv-Cke7qqdEg-0v0XpdAIyMq--ZWhLg2jnpTCo Message-ID: Subject: Re: Rebuilding brcmfmac Wi-Fi driver with the help of AI To: Vladimir Varankin Cc: Bugs Beastie , freebsd-wireless@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-3.81 / 15.00]; ARC_ALLOW(-1.00)[google.com:s=arc-20240605:i=1]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.992]; NEURAL_HAM_LONG(-0.91)[-0.914]; FORGED_SENDER(0.30)[adrian@freebsd.org,adrianchadd@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_THREE(0.00)[3]; FREEMAIL_CC(0.00)[gmail.com,freebsd.org]; FROM_HAS_DN(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; TAGGED_FROM(0.00)[]; TO_DN_SOME(0.00)[]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NEQ_ENVFROM(0.00)[adrian@freebsd.org,adrianchadd@gmail.com]; RCVD_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-wireless@freebsd.org]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-wireless@freebsd.org]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.219.53:from]; RCVD_IN_DNSWL_NONE(0.00)[209.85.219.53:from] X-Rspamd-Queue-Id: 4fkKKJ7259z4N0R X-Spamd-Bar: --- (top posting because i'm busy/tired, not because I like top posting) This is pretty neat. Please keep at cleaning it up and getting it to build/run on more stuff. The linux broadcom drivers support more things than the openbsd ones (notably having VAPs, AP/IBSS/etc modes working would be great.) It'll be good to look at the changes you and the agents made between linux and freebsd (ie, just a straight driver diff) to see what could be turned into mechanical conversion rules in the future. -adrian On Fri, 27 Mar 2026 at 17:26, Vladimir Varankin wrote: > > Hey-hey, > > >> Given the workflow, prompts, AI models to use, etc. are in place AND y= ou have > >> a physical Raspberry Pi 4, how long would it take to vibe-port brcmfma= c43455-sdio > >> wifi driver? The complication it is attached via SDIO interface, not P= CI! > > > > That'd be fun thing to try. I've forgotten that RPi4 comes with a broad= com chip. > > Will find some time to spin up a testing stand, and will see how that g= oes. > > This's been keeping me busy, and it hasn't been a smooth ride so far. But= I finally > saw some exciting progress today. > > Currently, the codebase is a mess [1]. But we (mainly agents, of course) = got > Raspberry Pi 4b to connect to my home Wi-Fi AP (5GHz, WPA2), and sent tra= ffic > to the Internet. > > One problem was that the stock kernel, that came with the RPI image > (FreeBSD-15.0-RELEASE-arm64-aarch64-RPI.img) needed patching and a fixed = device > tree overlay. The RPI4-HOWTO.md [2] in the driver's repo has more details= . > > *Again, to be 100% clear and hones: these are experimental "vibes" to see= how far > the AI tooling can push. I'm welcoming productive feedback about the resu= lts.* > > The repo's docs/00-progress.md [3] has a list of next steps to fix, befor= e I'll ask the agents > to do a deep code-review and refactoring. > > Details of the tests: > > freebsd@rpi4-freebsd-1:~ % uname -v > FreeBSD 15.0-STABLE #2 9c49c393a81b-dirty: Fri Mar 27 22:59:19 CET 2026 v= @freebsd-test-0:/usr/obj/usr/src/arm64.aarch64/sys/SDIO > > % dmesg | grep -i 'raspberry pi' > gpio1: on bcm2835_firmware0 > > % sysctl hw.model > hw.model: ARM Cortex-A72 r0p3 > > % ls /boot/firmware/ | grep brcm > brcmfmac43455-sdio.bin > brcmfmac43455-sdio.clm_blob > brcmfmac43455-sdio.txt > > % kldstat > Id Refs Address Size Name > 1 8 0xffff000000000000 1446958 kernel > 2 1 0xffff0000b2c00000 33000 if_brcmfmac.ko > > % ifconfig wlan0 > wlan0: flags=3D8843 metric 0 mtu = 1500 > options=3D0 > ether dc:a6:32:29:7b:1b > inet 192.168.188.182 netmask 0xffffff00 broadcast 192.168.188.255 > groups: wlan > ssid =E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88 channel 116 (= 5580 MHz 11a ht/20) bssid 1c=E2=96=88=E2=96=88=E2=96=88=E2=96=88=E2=96=88= =E2=96=88:3c > country 511 authmode WPA2/802.11i privacy ON deftxkey UNDEF > AES-CCM 2:128-bit AES-CCM 3:128-bit AES-CCM ucast:128-bit txpower 0 > bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 60 -ht -htcompat -ampdu > ampdulimit 8k -amsdu -stbc -ldpc -uapsd wme roaming MANUAL > parent interface: brcmfmac0 > media: IEEE 802.11 Wireless Ethernet MCS mode 11na > status: associated > nd6 options=3D29 > > % traceroute -i wlan0 1.1.1.1 > traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 40 byte packets > 1 192.168.188.114 (192.168.188.114) 185.541 ms 34.019 ms 53.549 ms > 2 192.168.188.1 (192.168.188.1) 49.716 ms 47.651 ms 49.251 ms > 3 10.103.18.1 (10.103.18.1) 55.914 ms 44.769 ms 57.156 ms > 4 89.246.252.169 (89.246.252.169) 46.803 ms 13.387 ms 48.198 ms > 5 i689729BA.versanet.de (104.151.41.186) 52.102 ms 51.937 ms 50.030 = ms > 6 62.214.73.216 (62.214.73.216) 53.640 ms 43.454 ms 58.782 ms > 7 62.214.73.217 (62.214.73.217) 49.132 ms 49.143 ms 46.480 ms > 8 one.one.one.one (1.1.1.1) 51.158 ms 49.501 ms 56.651 ms > > P.S. Zig has gone from the driver's codebase. Making it work in a kernel = driver > on aarch64 turned out even more challenging today. I'll park the idea int= o a backlog > of future playground projects. > > [1]: https://github.com/narqo/freebsd-brcmfmac > [2]: https://github.com/narqo/freebsd-brcmfmac/blob/629b801123966bbbea71d= 5ff8ccb7a789f43e792/RPI4-HOWTO.md > [3]: https://github.com/narqo/freebsd-brcmfmac/blob/629b801123966bbbea71d= 5ff8ccb7a789f43e792/docs/00-progress.md > > Cheers, > V. > > > On Thu, 12 Mar 2026 at 09:56, Vladimir Varankin wrot= e: >> >> > Given the workflow, prompts, AI models to use, etc. are in place AND y= ou have >> > a physical Raspberry Pi 4, how long would it take to vibe-port brcmfma= c43455-sdio >> > wifi driver? The complication it is attached via SDIO interface, not P= CI! >> >> That'd be fun thing to try. I've forgotten that RPi4 comes with a broadc= om chip. >> Will find some time to spin up a testing stand, and will see how that go= es. >> >> > C/Zig split rationale - at the end 94.7% of code is in C, 4.7% in Zig= . Would you still >> > go for anything in Zig again? >> >> Initially I was sold by Zig's promise of interoperability with C [1]. >> >> Given that I'm more comfortable with Zig compiler's promises, the thinki= ng was that >> understanding the details will be simpler for me, when the majority of c= ode is generated >> by AIs. In practice this didn't work out: the interoperability has numbe= r of corner cases, >> that, as an example, doesn't "just work" with kernel's linker. >> >> So it's not Zig the language was the issue. But the extra supporting lay= ers needed >> to make it work required more involvement than I (naively) hoped it will= be. >> >> Although, it works, I'm willing to rewrite Zig's chunk back to C, just t= o avoid it to be an easy >> target to latch on in the critics of the approach. >> >> [1]: https://ziglang.org/learn/overview/#integration-with-c-libraries-wi= thout-ffibindings >> >> On Wed, 11 Mar 2026 at 16:16, Bugs Beastie wrote= : >>> >>> Mar 10, 2026 20:33:53 Vladimir Varankin : >>> >>> > I recently wrote a blog post [1] sharing my experience of rebuilding >>> > a Wi-Fi driver for BCM4350 for FreeBSD with the help of agenting AI >>> > tooling. >>> > >>> Omitting any comments about AI usege,...cool and impressive! :) >>> >>> Very practical question: >>> Given the workflow, prompts, AI models to use, etc. are in place AND yo= u have a physical Raspberry Pi 4, how long would it take to vibe-port brcmf= mac43455-sdio wifi driver? The complication it is attached via SDIO interfa= ce, not PCI! >>> >>> Question out of curiosity: >>> C/Zig split rationale - at the end 94.7% of code is in C, 4.7% in Zig. = Would you still go for anything in Zig again? >>> >>> > I'm aware that different groups of people have different opinions abo= ut >>> > the topic of using AI in software development. Still I think this was >>> > a fairly interesting experiment, and I'm curious to hear the opinion >>> > on the approach and the results, from people close to in-tree drivers >>> > development. >>> > >>> > The GitHub repository [2] includes documentation about the testing >>> > approach, recorded decisions and know issues (which I'm =E2=80=94 sti= ll with >>> > the help of AI agents =E2=80=94 addressing in my spare time). >>> > >>> > P.S. Just to be absolute clear: I'm not proposing or suggesting to >>> > upstream the code of this driver. Neither do I think that in the curr= ent >>> > state the AIs can vibe-code something reliable in one go. But I do th= ink, >>> > the tooling can be a huge multiplier for building, testing, explainin= g, >>> > reviewing, etc large bodies of complex code. >>> > >>> > Cheers, >>> > V. >>> > >>> > [1]: https://vladimir.varank.in/notes/2026/02/freebsd-brcmfmac/ >>> > [2]: https://github.com/narqo/freebsd-brcmfmac >>> > >>> > -- >>> > Vladimir Varankin >>> > vladimir@varank.in >>> >>> >> >> >> -- >> Vladimir Varankin >> vladimir@varank.in > > > > -- > Vladimir Varankin > vladimir@varank.in From nobody Sun Mar 29 19:02:27 2026 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4fkNzr0LdVz6X9vB for ; Sun, 29 Mar 2026 19:02:32 +0000 (UTC) (envelope-from bz@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R13" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4fkNzq4PMjz3Z6d; Sun, 29 Mar 2026 19:02:31 +0000 (UTC) (envelope-from bz@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1774810951; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=SXcZSrtCEXpsfYJPg0wb1Oi7hKKinxOtEbArL56rpbg=; b=ZeGAKyFAIHMinanlbXAIw/XwzNBfrGTAqAKKIFGsNti7kluJ2M5U71tiqll7R//cPbbYmA fPl7H/NwVvI39qrOKKMtwjfRAQfuu87AbT5KJaFdN+wHrbuu2GYrH04omBG12bJhPRKDyT suSL0Ug+wOsxVJxAF0xMEqgq8ZTWVpAbaJ804eRs9KbQu0/JoEDhs24CrsRlhBDvCkKMIw lY+QLl+l5IV/UUsK0XMvaw+6abrEaIpBBl+/zXHy2hf+qcLovR/46M9bcRpNreOxTREcsv qled244pKG7hLKv6MDgIc9vziDa9+M4uoKAvR2Fw1LRlcKXVvUZNyfAcFv46og== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1774810951; a=rsa-sha256; cv=none; b=H1yU+TgaxUyXFl3YqwyLNBcYnylPSwQxxshdsifbyU4vvNeALFWuEdSMgdbDgie/hha9ob J/QRZVLCF0pZklcZtqwnNDeVi4JPMMMz7aodKiN6lAhOGyaXsMtqoJbPfJJLxCMTQuzZYE nsCgDwVFX9Lw7pfFfoUfNQ8JpQWALrzIOhSU+jBMZcpGUZErplIY6JCz7TIJUWo0emv+uF RcjGjeN2JyTv9+hMdgKvzfyKmLUdzqk7tUjvSZSHBzUHrBfS4qlHLFx/IJKbdC+Oskvbry PBS26EpTfJwCZLP8JC8RLwOEGa8AwbkIt6kPf2fj+AXGV6dpF+E4+jlm68iE4g== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1774810951; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=SXcZSrtCEXpsfYJPg0wb1Oi7hKKinxOtEbArL56rpbg=; b=QGBlc9PBy+D9Y57PUXtQ9r86paVvckX0otcTogJP35noUvNss87r2ECU4zFGyk+0f4U92m gxQMSL+MHHpuFJAdixEr5Ox9mNR39TqCkFq8W3p4prxJA0zRJntnD6eFxbG/dZneTxSw4F YrBu6XSAvHBsvLxcjOYuggIgLuoP43IJC9m1EiS9MmO9EK3JeHyPr19rlToGoFviC68k5Z 9S5VnzcUArmkL7ZQOBru7uYFHI9RJ9sVmeWACMdjrVjV1q5heaS0g9nd1VH9LOVme5Pl+F r8joHP7xmAE5GfgqIXuUFqr5HN80MCaZH/JLMggYvSEoA4mbI7AD/AAEO1WvNA== Received: from mx-01.divo.sbone.de (mx-01.divo.sbone.de [IPv6:2003:a:140a:2200:6:594:fffe:19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (prime256v1) client-digest SHA256) (Client CN "mx-01.divo.sbone.de", Issuer "E7" (not verified)) (Authenticated sender: bz/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4fkNzq28rbz17sn; Sun, 29 Mar 2026 19:02:31 +0000 (UTC) (envelope-from bz@freebsd.org) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx-01.divo.sbone.de (Postfix) with ESMTPS id CCC8AA64808; Sun, 29 Mar 2026 19:02:08 +0000 (UTC) Received: from content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id A49462D029E9; Sun, 29 Mar 2026 19:02:29 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) by content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (amavisd-new, port 10024) with ESMTP id DlxvFPJi3mco; Sun, 29 Mar 2026 19:02:27 +0000 (UTC) Received: from nv.t4-02.sbone.de (nv.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id AC42A2D029D8; Sun, 29 Mar 2026 19:02:27 +0000 (UTC) Date: Sun, 29 Mar 2026 19:02:27 +0000 (UTC) From: "Bjoern A. Zeeb" To: Oleg Nauman cc: FreeBSD wireless mailing list Subject: Re: rtw88 (8822be, 8821ce) - if you have one of these please join in [was: ..] In-Reply-To: Message-ID: References: <65165b44-b8c2-4762-b7fa-c21a70248848@benhutton.com.au> X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-wireless@freebsd.org Sender: owner-freebsd-wireless@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0-130366537-1774810947=:11296" This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-130366537-1774810947=:11296 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT On Fri, 6 Mar 2026, Oleg Nauman wrote: Hi Oleg, everyone else with one of the mentioned chipsets, > On Thu, Mar 5, 2026 at 3:59 PM Bjoern A. Zeeb wrote: >> >> In the last 48 hours I pushed the next round of LinuxKPI 802.11 >> changes which would be good to validate on a wide set of chipsets >> and supported drivers. One of them fixed a firmware crash, another >> one re-enabled some code again which was silently not doing its things >> due to Linux KPI changes (and surprisingly most of it worked anyway the >> last months). > > Unfortunately I am observing regression so my > > rtw880@pci0:2:0:0: class=0x028000 rev=0x00 hdr=0x00 vendor=0x10ec > device=0xc821 subvendor=0x1a3b subdevice=0x3040 > vendor = 'Realtek Semiconductor Co., Ltd.' > device = 'RTL8821CE 802.11ac PCIe Wireless Network Adapter' > class = network > > can't connect to 2.4 Ghz access point again So given rtw88 8822be abd 8821ce mostly are standing between me and pushing further changes I had a closer look this week. There are two problems: (a) switching from a (rejected) HW scan to a SW scan causes problems as it can race with the scan_to_auth state change due to the nature of the compat code and some extra locking assertions in net80211 which are hindering to at lest get half of it race free from the start. I tried to work around all this only to also observe the next item. (b) more so, rtw8821c_do_iqk() (for 8821ce) fails in a lot of times here, which leads to a *cough* 6s delay between starting the mgd_prepare_tx() and getting the actual frame out. There are moments when it works, in 20-40/120-150 ms but I have not yet looked into the differences (what leads to one failing and one working). If you turn rtw88 PHY debugging (0x8 on FreeBSD or Linux) on, you can see lines similar (slightly adjusted here currently) to these; where the counter is 300 the (300 * 20ms) timeout failures happened and the rf_reg=0xabcde (n_iqk_fail(mask)==0x00000) are the ones where things seem to have worked. [40558.969218] iqk counter=7 reload=0 do_iqk_cnt=154 n_iqk_fail(mask)=0x00000 rf_reg=0xabcde [40586.004212] iqk counter=300 reload=0 do_iqk_cnt=155 n_iqk_fail(mask)=0x000ea rf_reg=0xaeaea [41325.466166] iqk counter=6 reload=0 do_iqk_cnt=156 n_iqk_fail(mask)=0x00000 rf_reg=0xabcde [41804.767148] iqk counter=300 reload=0 do_iqk_cnt=157 n_iqk_fail(mask)=0x000ea rf_reg=0xaeaea [41826.729151] iqk counter=300 reload=0 do_iqk_cnt=158 n_iqk_fail(mask)=0x000ea rf_reg=0xaeaea [42751.157067] iqk counter=6 reload=0 do_iqk_cnt=159 n_iqk_fail(mask)=0x00000 rf_reg=0xabcde [42778.272059] iqk counter=300 reload=0 do_iqk_cnt=160 n_iqk_fail(mask)=0x000ea rf_reg=0xaeaea [43758.862997] iqk counter=6 reload=0 do_iqk_cnt=161 n_iqk_fail(mask)=0x00000 rf_reg=0xabcde [43786.057993] iqk counter=300 reload=0 do_iqk_cnt=162 n_iqk_fail(mask)=0x000ea rf_reg=0xaeaea [44722.416953] iqk counter=6 reload=0 do_iqk_cnt=163 n_iqk_fail(mask)=0x00000 rf_reg=0xabcde [45505.841872] iqk counter=300 reload=0 do_iqk_cnt=164 n_iqk_fail(mask)=0x000ea rf_reg=0xaeaea [45528.128872] iqk counter=300 reload=0 do_iqk_cnt=165 n_iqk_fail(mask)=0x000ea rf_reg=0xaeaea [46350.516810] iqk counter=6 reload=0 do_iqk_cnt=166 n_iqk_fail(mask)=0x00000 rf_reg=0xabcde [46895.590359] iqk counter=300 reload=0 do_iqk_cnt=167 n_iqk_fail(mask)=0x000ea rf_reg=0xaeaea [46916.526778] iqk counter=300 reload=0 do_iqk_cnt=168 n_iqk_fail(mask)=0x000ea rf_reg=0xaeaea [48190.225691] iqk counter=6 reload=0 do_iqk_cnt=169 n_iqk_fail(mask)=0x00000 rf_reg=0xabcde [48217.376689] iqk counter=300 reload=0 do_iqk_cnt=170 n_iqk_fail(mask)=0x000ea rf_reg=0xaeaea [49406.787608] iqk counter=6 reload=0 do_iqk_cnt=171 n_iqk_fail(mask)=0x00000 rf_reg=0xabcde [49433.853606] iqk counter=300 reload=0 do_iqk_cnt=172 n_iqk_fail(mask)=0x000ea rf_reg=0xaeaea [50226.350550] iqk counter=7 reload=0 do_iqk_cnt=173 n_iqk_fail(mask)=0x00000 rf_reg=0xabcde [51510.819466] iqk counter=300 reload=0 do_iqk_cnt=174 n_iqk_fail(mask)=0x000ea rf_reg=0xaeaea [51532.908461] iqk counter=300 reload=0 do_iqk_cnt=175 n_iqk_fail(mask)=0x000ea rf_reg=0xaeaea [52540.479405] iqk counter=6 reload=0 do_iqk_cnt=176 n_iqk_fail(mask)=0x00000 rf_reg=0xabcde [52955.240359] iqk counter=300 reload=0 do_iqk_cnt=177 n_iqk_fail(mask)=0x000ea rf_reg=0xaeaea [52976.144349] iqk counter=300 reload=0 do_iqk_cnt=178 n_iqk_fail(mask)=0x000ea rf_reg=0xaeaea [53836.870326] iqk counter=7 reload=0 do_iqk_cnt=179 n_iqk_fail(mask)=0x00000 rf_reg=0xabcde [54887.781217] iqk counter=300 reload=0 do_iqk_cnt=180 n_iqk_fail(mask)=0x000ea rf_reg=0xaeaea [54908.598250] iqk counter=300 reload=0 do_iqk_cnt=181 n_iqk_fail(mask)=0x000ea rf_reg=0xaeaea [55766.079171] iqk counter=6 reload=0 do_iqk_cnt=182 n_iqk_fail(mask)=0x00000 rf_reg=0xabcde [56984.879080] iqk counter=300 reload=0 do_iqk_cnt=183 n_iqk_fail(mask)=0x000ea rf_reg=0xaeaea [57005.691081] iqk counter=300 reload=0 do_iqk_cnt=184 n_iqk_fail(mask)=0x000ea rf_reg=0xaeaea [57748.083033] iqk counter=6 reload=0 do_iqk_cnt=185 n_iqk_fail(mask)=0x00000 rf_reg=0xabcde I will likely have to dive into this some more but I do not want it to further block the other rtw88/rtw89(/mt76) updates at this point as my other work for those seems to hold up and I'd love to get some in in time before 15.1-R. If anyone has the time/resources to help me debugging this issue on the 21ce and 22be chipsets, please reply here. Otherwise it'll have to wait and I'll add a note to the man page (if I do not forget) for now. Lots of health, /bz -- Bjoern A. Zeeb r15:7 --0-130366537-1774810947=:11296-- From nobody Sun Mar 29 20:06:16 2026 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4fkQPN5VH2z6XHdP for ; Sun, 29 Mar 2026 20:06:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R12" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4fkQPN3STdz3pdt for ; Sun, 29 Mar 2026 20:06:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1774814776; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=rwbuWTkoA0rwDA3TAjoWwgCzH/2/5MELQ0yVzjEG3HM=; b=plowVuPYEcY/dz+s7fcwTPoN0jCwe8I45+/Jrc2QaadcdUtBn9YSxrr5Yb+Q0WE3sTZqam +MYlWvQBJAGjEzpZFPbdoEsm+1vwyFWB9fp4lh3Gqx+LMe9Naz8kZOxFfz5SxIHrLqNiLt C7MFFTLhJkpyFwR1Tv6x7IvFbLJj/7ydJ5pa2h++W7EHmFQdm0nq9zp7rOGR0FLhrVwrqB LZTEnPk6Pxr+eWCNa6w4L6M8He+uFmyt7RN/INGND1j3KNlUkWY1UyAh7oLhBnZyvybnZ9 9NwsVNWDBjcT+8s9kpRXeCGbwT9xpwsjnNBpIyXfS8DF8dctri7QYwsx0dZRbg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1774814776; a=rsa-sha256; cv=none; b=orrV06kFb19z5nm9pUJK2LKgK9iQ1WluJottOMAX0TD7nP7KfU92t5DXi4/vP2lCkqeXOA 1Xq+/3uZu4A62IfuvRCUmaS6QcqpqRgQHBgGNiJxzZkphoR1bucBApDylyRwO2bDFAQ5mb NC1AUOm6lqyfOaGA7RBftoNeZHqvuWqJHHZgPdpTeKRX209dssL2Qw1rC0A0dsQiZlBzZP mulY8Rh3jn9RM2mQ0Aa7PKzJJu9zVo1bVXzMWmQqPiiwdxTIfsebtjXW5tBpwS/gxSgSa+ oxVi3eGvMg9yxg598yrY/KAUIQbw6t7je9eUASaynfgvJSHXV0YTyohqVYKstg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1774814776; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=rwbuWTkoA0rwDA3TAjoWwgCzH/2/5MELQ0yVzjEG3HM=; b=QJ+DL5l2Eyi9Cjgys6vZXFv0lO9+/5XSaOcVrMAFjBitm8YWiNiub6BMhPPbTSeBbA6WHa WE47MtcYuYprXiNXOmG3S+MFhOSngi9892n6bOXeDfU/y3UvYRtdkFJJP0Ud6BNirbUFLE QrkEcZHTYOmbApqjU9XKx3Uv0zl+lcRexsmyAvj9LHAjbR8+c3OkskJy0gu94DoPzoja4m U5Vuj75nPtQtNIxeZ9yviCxdU4sqS/9oewGfXiUrO0HI4SOyfqNjQ5YMcPp0XP/SplrwB6 htDfnabBJjUAEqtMsFNiwFxqYn3xqVaPfk+R0VJr/8T+TbQSuynWAtgAaV42Ig== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4fkQPN2rbvz1Pw6 for ; Sun, 29 Mar 2026 20:06:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 62TK6GfM061148 for ; Sun, 29 Mar 2026 20:06:16 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 62TK6GBj061147 for wireless@FreeBSD.org; Sun, 29 Mar 2026 20:06:16 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 290639] Bluetooth on Intel 9560 and AX201 does not work on any Alder Lake CPU variant (N100, N150) Date: Sun, 29 Mar 2026 20:06:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 14.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: wulf@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-wireless@freebsd.org Sender: owner-freebsd-wireless@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D290639 --- Comment #32 from Vladimir Kondratyev --- (In reply to Michel Kohanim from comment #31) > Does your patch remove the necessity for updating these mappings? 7260 requires extra HCI reset before other HCI commands execution, so we ha= ve to do initial device type detection by PID at beginning. --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Sun Mar 29 23:46:09 2026 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4fkWHD6sKsz6XfNT for ; Sun, 29 Mar 2026 23:46:16 +0000 (UTC) (envelope-from ben@benhutton.com.au) Received: from mail.myuniquemail.com (mail.myuniquemail.com [115.70.107.139]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4fkWHD01mvz3GNc; Sun, 29 Mar 2026 23:46:15 +0000 (UTC) (envelope-from ben@benhutton.com.au) Authentication-Results: mx1.freebsd.org; none Received: from [10.128.2.109] (unknown [10.128.10.1]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mail.myuniquemail.com (Postfix) with ESMTPSA id 087BF201279; Mon, 30 Mar 2026 07:46:10 +0800 (AWST) Content-Type: multipart/alternative; boundary="------------NIaEFSz40XSa54keoIVRdBZ2" Message-ID: <2c49a2c3-144f-45b2-959a-85388c82d488@benhutton.com.au> Date: Mon, 30 Mar 2026 07:46:09 +0800 List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-wireless@freebsd.org Sender: owner-freebsd-wireless@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: How is testing going? To: "Bjoern A. Zeeb" Cc: FreeBSD wireless mailing list References: <6p4r5o3-4218-sn14-o712-7944359sqno6@mnoonqbm.arg> <2b031f6d-936d-4ec0-89ec-a12a5b6597aa@benhutton.com.au> Content-Language: en-AU From: Ben Hutton In-Reply-To: X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:10143, ipnet:115.70.104.0/21, country:AU] X-Rspamd-Queue-Id: 4fkWHD01mvz3GNc X-Spamd-Bar: ---- This is a multi-part message in MIME format. --------------NIaEFSz40XSa54keoIVRdBZ2 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Bjoern, The previous version I tested was from commit 74aec9f02d9d8fbde250da1ecc881729c8baf489. It was around 7th March. I had to revert because the connection kept dropping out due to errors and would eventually crash the system. I sent through logs of it at the time. I can dig out the email if that helps. Currently the main issue I'm having is connecting to access points at 11ac when they are using channels above 100. Currently I have two access points. One is using channels 52,56,60,64 and the other 149,153,157,161. Currently my FreeBSD based laptop will only connect to the one with 149-161 with 11ng, the other connects fine at 11ac. I suspect this issue is due to missing entries in regdomain.xml so I'm currently experimenting with adding the following (generated by Claude Haiku 4.5) and adding it to the end of the 11ac in the APAC2 section:   30 IEEE80211_CHAN_HT20 IEEE80211_CHAN_VHT20 IEEE80211_CHAN_DFS     I haven't gotten as far as looking up the documentation around the frequency regulations in Australia yet but planning on. I'm still currently testing it, however tests so far have the current driver hitting the same speeds as my M1 MacBook Pro. Also it has been a big step up in stability. So far over the last day I've had no dropouts once connected. Will let you know if I have any further issues. Any advise on the channels issue above regarding testing, also any advise on where to get the information regarding the channels/frequency ranges? Kind regards Ben On 3/29/26 23:56, Bjoern A. Zeeb wrote: > On Sun, 29 Mar 2026, Ben Hutton wrote: > > Hi Ben, > >> Working allot better for me than the last update. > > Thanks for the feedback.  Can you elaborate a bit more? > > From which to which version did you go? > What's currently troubling? > > Sorry for asking but I need the details in order to try to make it > even better ;-) > > /bz > --------------NIaEFSz40XSa54keoIVRdBZ2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

Hi Bjoern,

The previous version I tested was from commit 74aec9f02d9d8fbde250da1ecc881729c8baf489. It was around 7th March.

I had to revert because the connection kept dropping out due to errors and would eventually crash the system. I sent through logs of it at the time. I can dig out the email if that helps.

Currently the main issue I'm having is connecting to access points at 11ac when they are using channels above 100. Currently I have two access points. One is using channels 52,56,60,64 and the other 149,153,157,161. Currently my FreeBSD based laptop will only connect to the one with 149-161 with 11ng, the other connects fine at 11ac. 

I suspect this issue is due to missing entries in regdomain.xml so I'm currently experimenting with adding the following (generated by Claude Haiku 4.5) and adding it to the end of the 11ac in the APAC2 section:

   <band>
     <freqband ref="AC2_5480_5700_20"/>
     <maxpower>30</maxpower>
     <flags>IEEE80211_CHAN_HT20</flags>
     <flags>IEEE80211_CHAN_VHT20</flags>
     <flags>IEEE80211_CHAN_DFS</flags>
   </band>


I haven't gotten as far as looking up the documentation around the frequency regulations in Australia yet but planning on.

I'm still currently testing it, however tests so far have the current driver hitting the same speeds as my M1 MacBook Pro. Also it has been a big step up in stability. So far over the last day I've had no dropouts once connected. 

Will let you know if I have any further issues. Any advise on the channels issue above regarding testing, also any advise on where to get the information regarding the channels/frequency ranges?

 

Kind regards
Ben

On 3/29/26 23:56, Bjoern A. Zeeb wrote:
On Sun, 29 Mar 2026, Ben Hutton wrote:

Hi Ben,

Working allot better for me than the last update.

Thanks for the feedback.  Can you elaborate a bit more?

From which to which version did you go?
What's currently troubling?

Sorry for asking but I need the details in order to try to make it even better ;-)

/bz

--------------NIaEFSz40XSa54keoIVRdBZ2--