From owner-freebsd-arm@freebsd.org Sat Sep 5 12:15:45 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1E33C3CB08B for ; Sat, 5 Sep 2020 12:15:45 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:13b:39f::9f:25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BkD5r2QlGz4PwX for ; Sat, 5 Sep 2020 12:15:43 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 847A18D4A21A; Sat, 5 Sep 2020 12:15:36 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 0B49BE707B3; Sat, 5 Sep 2020 12:15:36 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id iMI_9TtcY5J1; Sat, 5 Sep 2020 12:15:34 +0000 (UTC) Received: from [127.0.0.1] (unknown [IPv6:fde9:577b:c1a9:4902:f0a0:4844:b815:25aa]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 7097FE707AF; Sat, 5 Sep 2020 12:15:34 +0000 (UTC) From: "Bjoern A. Zeeb" To: "Klaus Cucinauomo" Cc: "Stefan Parvu" , freebsd-arm@freebsd.org Subject: Re: onboard wireless on rpi4 Date: Sat, 05 Sep 2020 12:15:33 +0000 X-Mailer: MailMate (2.0BETAr6151) Message-ID: <09959D86-E3E3-43E9-8134-C2FC73343DBA@lists.zabbadoz.net> In-Reply-To: References: <20200904134619.GB80905@bastion.zyxst.net> <69934262-D9D3-4986-849D-9E8221D1E387@kronometrix.org> <1677459627.55.1599232125847@localhost> <75E08DC2-D229-45AA-85AE-CCF06FD0B490@kronometrix.org> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4BkD5r2QlGz4PwX X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of bzeeb-lists@lists.zabbadoz.net designates 2a01:4f8:13b:39f::9f:25 as permitted sender) smtp.mailfrom=bzeeb-lists@lists.zabbadoz.net X-Spamd-Result: default: False [-3.16 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a01:4f8:13b:39f::9f:25]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zabbadoz.net]; NEURAL_HAM_LONG(-0.97)[-0.972]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.85)[-0.846]; NEURAL_HAM_MEDIUM(-1.04)[-1.043]; FREEMAIL_TO(0.00)[googlemail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; RCVD_TLS_LAST(0.00)[]; MAILMAN_DEST(0.00)[freebsd-arm] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Sep 2020 12:15:45 -0000 On 4 Sep 2020, at 17:35, Klaus Cucinauomo via freebsd-arm wrote: > Yep, my question if really no one else is working on it, was directed > to Björn ;-), > because I don’t want to work on a completely different > implementation, > if Björn is perhaps a few steps further. SDIO attach worked last year; WiFi (cfg80211) wasn’t finished. And I am not tired of hearing people ask for it. You have all the right to do so. I recently got a PCIe card (different bus attachment) but it should help to move forward on the WiFi parts as well. Yes, it is a free time project at the moment but it also benefits from other ongoing WiFi work. Two things which may help for the RPi/SDIO parts are: - please try and use MMCCAM kernels and help, test, debug, report, .. all the things you find so (other people) can jump in as well so we can switch that on as default. Without that, no SDIO. - in case you are not only into RPi, the nanopi/rk33xx platforms with onboard SDIO WiFi need tiny little glue bits to turn the bits on; would be great if someone could just do that. Bjoern