Dear Adrian,
No problem then, I can wait :). Meanwhile, I have my trusty Realtek-based
USB dongle. Never too many of those!
As a side note, will the datasheets published by Cypress help any?
I mean, I'm not in a position to help with coding, especially not with
writing wireless device drivers in
HI,
no - it's a different PHY and different bus glue. :(
-a
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Dear Adrian,
I see, makes sense. I assumed bcm4322 and bcm4321 are similar. Trying to
pull a higher Broadcom driver version for fwcutter will not cut it then
(pun not intended)?
I wanted to try it, just out of curiosity.
Best regards,
Andy
On 18 November 2016 at 21:24, Adrian Chadd wrote:
> h
hiya,
I think the 4322 is a newer PHY which we don't have support for yet
(PHY-HT?). I think I tested the 4321 and that worked.
It's waiting for new bus code from landon, and then when that's done, I'll
finish the PHY port and we can test.
-adrian
On 18 November 2016 at 12:12, Andy Mender w
Dear Adrian,
I specifically rebuild that port after upgrading my kernel. I'm afraid the
bcm4322 chip requires firmware that's not in the old Broadcom drivers that
are used as a source for fwcutter. On GNU/Linux systems I typically need
the 6.x series, while the port you mentioned uses the 5.x and
there's a bwn firmware port you need to build.
bwn-firmware-kmod
-a
On 17 November 2016 at 22:35, Andy Mender wrote:
> Hello,
>
> I recompiled the kernel and did a world rebuild to include the bwn code we
> discussed last time. There is some progress - now the bwn module does not
> complain t
Hello,
I recompiled the kernel and did a world rebuild to include the bwn code we
discussed last time. There is some progress - now the bwn module does not
complain that some features are missing. However, the firmware is missing.
I installed the /net/bwn-firmware-kmod, though that does not seem t
Dear Adrian, Ben,
Bingo! That could've been it. I did NOT uncomment the lines you mentioned
in /usr/src/sys/modules/bwn prior to recompiling the kernel. I'll try to
rebuild the kernel with the lines added and write back with results.
Hope it works!
Best regards,
Andy
On 17 November 2016 at 07:4
hi,
Something's wrong with that compilation. Check modules/bwn/Makefile
and make sure you uncommented the bwn n_phy source files.
-adrian
On 16 November 2016 at 22:38, Andy Mender wrote:
> Dear Adrian, Ben,
>
> sysctl.net.wlan.devices returns only the urtwn0 interface (from a TP-LINK
> USB do
Dear Adrian, Ben,
sysctl.net.wlan.devices returns only the urtwn0 interface (from a TP-LINK
USB dongle I use to get any connection).
Below, please find the output of "dmesg | grep bwn":
andy@mb-2008:~ % dmesg | grep bwn
link_elf_obj: symbol bwn_nphy_op_allocate undefined
KLD file if_bwn.ko - coul
On Wed., 16 Nov. 2016 at 8:09 pm, Andy Mender
wrote:
> Dear Adrian,
>
> I set the mentioned option (BWN_GPL_PHY just below the bwn driver) in the
> kernel config file and recompiled the STABLE kernel.
> Now the additional message about BWN_GPL_PHY is gone, but there is some 2-3
> features listed
Dear Adrian,
I set the mentioned option (BWN_GPL_PHY just below the bwn driver) in the
kernel config file and recompiled the STABLE kernel.
Now the additional message about BWN_GPL_PHY is gone, but there is some 2-3
features listed as unsupported. The driver gets attached to the network
card as si
hi!
You need to compile with a specific kernel option added. add this:
options BWN_GPL_PHY
and recompile.
See if that works!
-a
On 10 November 2016 at 22:17, Andy Mender wrote:
> Fellow FreeBSD users and developers,
>
> I just returned to FreeBSD after some light distro-hopping and wanted
13 matches
Mail list logo
