Tony T wrote: > CBRF= Community-Build-Radio-Firmware > Its not clear if wlanpoke is included in the CBRF. > (I Appreciate the work youve done with wlanpoke, and posted on GitHub > is great, but I think it would be a better idea to have youre own > thread on wlanpoke as it is impossible to follow any discussions on > wlanpoke when its in two threads.) The initial version flat zip files were included in posts on the 'CBRF' thread here. A beginner here, I don't know about the CBRF software distribution. The software was (and is) intended only as a stopgap or fallback and diagnostic tool. Presumably an installation and configuration package is required, and here I am clueless. Also, the software has been under active development, unfinished, "EUA only," and not ready for "prime time."
My first posts were to the CBRF thread on troubleshooting the "Wireless Connectivity Loss" issue. The wlanpoke script grew out of this investigation, and was posted there. (This and other instrumentation provided data that lead to an investigation into the radio's "wireless network stack" from the chip to the user mode clients. This investigation was stymied by the GPL'd open source driver source code being held secret, but now...) I suggested a new 'developer' thread about wireless connectivity, but the CBRF thread seemed willing keep the discussion there. That thread is required to build the firmware for debugging and modification, and the thread is well suited to topics of experimentation, so it it the main thread. Noticing frustrated user-oriented thread activity regarding lost connections (e.g., this thread), I started posting there (here) as well, referring to the CBRF thread for more information. It seemed that users who had problems with connections gravitated to threads about "lost connections," or "wifi 6," etc., and missed the firmware thread. This thread is perfectly titled; most seeking help would read it. So now it is two threads, with main posts on CBRF, and, later, notices here. I am new to GitHub (this spelling requires documentation change, another revision!), and just reacquainted (and still uncomfortable) with git. GitHub has an "Issues" section, which has been used, but I'd rather issues be handled in the CBRF thread because it is read closely by users who can react quickly and propose changes to the other like-minded readers. Sorry for the difficulties from two threads. I subscribe to both as an email for every new post, like an old-time mailing list. This has helped. ------------------------------------------------------------------------ POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558 View this thread: http://forums.slimdevices.com/showthread.php?t=109953
_______________________________________________ Radio mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/radio
