Add an entry about Broadcom being unlikely ever to release documentation
about their chipsets used in the 43xx cards. Taken from: a post from the long-suffering wpaul
This commit is contained in:
parent
c0e893424e
commit
1c2d76ce2f
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=21325
1 changed files with 19 additions and 0 deletions
|
@ -3038,6 +3038,25 @@ Protocol "SysMouse"</programlisting>
|
||||||
</answer>
|
</answer>
|
||||||
</qandaentry>
|
</qandaentry>
|
||||||
|
|
||||||
|
<qandaentry>
|
||||||
|
<question id="support-broadcom">
|
||||||
|
<para>Is there a native driver for the Broadcom 43xx cards?</para>
|
||||||
|
</question>
|
||||||
|
|
||||||
|
<answer>
|
||||||
|
<para>No, and there is not likely to be.</para>
|
||||||
|
|
||||||
|
<para>Broadcom refuses to publically release programming
|
||||||
|
information for their wireless chipsets, most likely because
|
||||||
|
they use software controlled radios. In order to get FCC type
|
||||||
|
acceptance for their parts, they have to ensure that users
|
||||||
|
cannot arbitrarily set things like operating frequencies,
|
||||||
|
modulation parameters and power output. But without knowing
|
||||||
|
how to program the chipsets, it is nearly impossible to write
|
||||||
|
a driver.</para>
|
||||||
|
</answer>
|
||||||
|
</qandaentry>
|
||||||
|
|
||||||
<qandaentry>
|
<qandaentry>
|
||||||
<question id="serial-console-prompt">
|
<question id="serial-console-prompt">
|
||||||
<para>How do I get the boot: prompt to show on the serial
|
<para>How do I get the boot: prompt to show on the serial
|
||||||
|
|
Loading…
Reference in a new issue