Date: Sat, 5 Sep 2020 17:04:56 +0200 From: Klaus Cucinauomo <maciphone2@googlemail.com> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, freebsd-arm@freebsd.org Subject: Re: onboard wireless on rpi4 Message-ID: <E194EF9D-8D25-4AD2-A865-DFC7A6E877F4@googlemail.com> In-Reply-To: <09959D86-E3E3-43E9-8134-C2FC73343DBA@lists.zabbadoz.net> References: <20200904134619.GB80905@bastion.zyxst.net> <69934262-D9D3-4986-849D-9E8221D1E387@kronometrix.org> <1677459627.55.1599232125847@localhost> <75E08DC2-D229-45AA-85AE-CCF06FD0B490@kronometrix.org> <AAA3DC42-5C3E-4A1D-BE75-A20DE3BC300F@googlemail.com> <09959D86-E3E3-43E9-8134-C2FC73343DBA@lists.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Bj=C3=B6rn, thanks that you=E2=80=99re still willing to invest work in aarch64 wifi. > SDIO attach worked last year;=20 Ive tested that on RPI(4) extensively (of course with MMCCAM), but as you already know(I assume), a brcmfmac-driver needs a loader = mechanism for=20 the proprietary firmware -files and a mechanism to translate the = nvram-file. Nvram-translation can be done via an external program or can be built in = into the driver. So I really wonder how you got a brcmfmac- chip to work=20 without implementing those special drivers(and mechanisms) ???????? =E2=80=A6 I speak German like you :-) so maybe I understood you wrong = in the English language, sorry in advance .. > - 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. The list of platforms which will load the firmware/nvram could be much = longer than rpi/nanopi and as mentioned=20 in my earlier post it`s possible that 2 versions of the same board have = to load different firmware-files ( that was the case for nanopi , as far as I remember,(I didn=E2=80=99t = work much on aarch64 the last weeks)=E2=80=A6 So long Blabla of details :-) =E2=80=A6 what I really wanted to know/ask = you: ??? Are you working on the brcmfmac-driver AND the = firmware-loading-mechanism??? ??.. or are you doing things far more extended&advenced than my skills = and knowledge of this topic:-) ??? Thanks and best Regards Klaus =20 > Am 05.09.2020 um 14:15 schrieb Bjoern A. Zeeb = <bzeeb-lists@lists.zabbadoz.net>: >=20 > On 4 Sep 2020, at 17:35, Klaus Cucinauomo via freebsd-arm wrote: >=20 >> Yep, my question if really no one else is working on it, was directed = to Bj=C3=B6rn ;-), >> because I don=E2=80=99t want to work on a completely different = implementation, >> if Bj=C3=B6rn is perhaps a few steps further. >=20 > SDIO attach worked last year; WiFi (cfg80211) wasn=E2=80=99t = finished. And I am not tired of hearing people ask for it. You have = all the right to do so. >=20 > 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. >=20 >=20 > Two things which may help for the RPi/SDIO parts are: >=20 > - 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. >=20 > - 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. >=20 >=20 > Bjoern
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E194EF9D-8D25-4AD2-A865-DFC7A6E877F4>