hi!
On Fri, 14 May 2021 at 03:25, Daniel Cervus wrote:
> (a) When unconnected:
> wlan0: flags=8c43 metric 0
> mtu 1500
> ether ***
> inet6 ***%wlan0 prefixlen 64 scopeif 0x3
> groups: wlan
> ssid "" channel 3 (2422 MHz 11g)
> regdomain ROW country CN indoor ecm authmode OPEN privacy OFF
> txpow
hi!
(a) it'll say 802.11g but then the channel should say HT/20 or HT/40.
what's the actual output of ifconfig wlan0 ?
(b) yeah, that's a bsdconfig bug :-)
(c) that's fine, it's likely some crazy stuff like needing to do some
packet IO during a scan; it's printed like that in case things are
also
lemme go see (again). That's why I wanted to re-review it all before I
landed stuff!
-a
On Fri, 2 Apr 2021 at 13:41, Bjoern A. Zeeb
wrote:
>
> On 2 Apr 2021, at 6:44, Adrian Chadd wrote:
>
> > I've got this in my local tree now.
>
> That’s not a good idea?
&
I've got this in my local tree now. I have a note to go dig up which
draft I yanked this from and update it with reference to the draft and
the current spec.
Thanks for pointing this out!
-adrian
___
freebsd-wireless@freebsd.org mailing list
https://li
gt; I had tried using this section of code and found these flags are not
> satisfied, after changing them, I can negotiate VHT80, VHT160 fine with iwm,
> so I pointed out this problem. I am also wondering what's the badly wrong of
> you said in draft VHT implementation?
>
> thank
hm!
On Mon, 29 Mar 2021 at 08:02, qcwap <1051244...@qq.com> wrote:
>
> This patch corrects ieee80211_vht_get_vhtcap_ie for 160/80P80 channel width
> recognition.
>
> diff --git a/sys/net80211/ieee80211.h b/sys/net80211/ieee80211.h
> index 86ab1459cca..76c43629b33 100644
> --- a/sys/net80211/ieee8
hi!
Yeah, there's been some long standing calibration issues with the 9227
that i've never figured out :(
-a
On Wed, 3 Mar 2021 at 02:27, Domagoj Smolčić wrote:
>
> For about 5 years now I have:
> --
> ath1@pci0:3:2:0:class=0x028000 card=0x0300168c chip=0x002d168c
> rev=0x01 hdr=0x00
On Sun, 3 Jan 2021 at 03:08, Andriy Gapon wrote:
>
>
> Is there an easy way to tell which wireless ifconfig option is shared
> and which is per VAP?
> I mean, 'channel' is shared, 'ssid' is per VAP obviously.
> But how about the rest?
> Is that explicitly documented somewhere?
> Is there something
Hi
You have to update to -head because we are also updating APIs in
net80211 and such as part of it.
-a
On Fri, 4 Dec 2020 at 09:30, Berislav Purgar wrote:
>
> Hello
>
> Is possible to compile these driver on 12.2-RELEASE or do i need to switch on
> -head (13) ??
>
> Berry
>
>
>
> Sent from m
hi! I don't think we've added HT40 support yet!
-adrian
On Sun, 29 Nov 2020 at 18:59, tech-lists wrote:
>
> Hi,
>
> A Ralink/run device is plugged into the usb2 interface of a raspberry
> pi running -current.
>
> It seems to work ok other than being unassociated at boot but that's
> another iss
t there. :-)
Thanks!
-adrian
On Sun, 13 Sep 2020 at 13:27, Anthony Jenkins wrote:
> Thanks Adrian,
>
> Just wondering if there's anything I can do to help. I have the driver
> repo.
>
> Anthony
>
> On 2020-09-13 14:53, Adrian Chadd wrote:
> > hi!
>
16/09/2020 22:36, Adrian Chadd wrote:
> >
> >
> > On Wed, 16 Sep 2020 at 13:41, James Wright <
> james.wri...@digital-chaos.com <mailto:james.wri...@digital-chaos.com>>
> wrote:
> >
> > Hi wireless gurus,
> >
> > I'm trying
On Wed, 16 Sep 2020 at 13:41, James Wright
wrote:
> Hi wireless gurus,
>
> I'm trying to understand why this USB wifi dongle is so slow under
> FreeBSD.
> The max real-world download rate seems to be capped at ~900KB/sec (see
> wget below),
> but with exactly the same hardware and conditions
hi!
we're still working on this. It's going to take some time.
thanks,
-adrian
On Sun, 13 Sep 2020 at 11:12, Anthony Jenkins via freebsd-wireless <
freebsd-wireless@freebsd.org> wrote:
> I have a Killer 1535 802.11ac wireless card (chipset = Qualcomm Atheros
> QCA6174). I am using the ath1
On Sun, 9 Aug 2020 at 08:38, Bjoern A. Zeeb
wrote:
> Hi,
>
> I’ll just join in on the last email in the thread not replying to
> anything specific.
>
> Having gone through some of the stuff lately myself in order to put [1]
> out (which is also includes a few things to discuss) I’ll try to
> summ
On Tue, 21 Jul 2020 at 20:36, Aaron wrote:
> Still working on my mailing list etiquette ...
>
> On 7/21/2020 11:11 PM, Adrian Chadd wrote:
>
> > On Tue, 21 Jul 2020 at 20:03, Aaron > <mailto:notjanede...@gmail.com>> wrote:
> >
> > On 7/21/2020 10
On Tue, 21 Jul 2020 at 20:03, Aaron wrote:
> On 7/21/2020 10:53 PM, Adrian Chadd wrote:
> > As a data source yes, but I'd /love/ ours to be more structured.
> > Parsing the wireless-regdb format is ... lol.
> >
> >
> > -a
> Fair enough. This data a
As a data source yes, but I'd /love/ ours to be more structured. Parsing
the wireless-regdb format is ... lol.
-a
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to
On Tue, 21 Jul 2020 at 14:48, Aaron wrote:
> On 7/21/2020 5:41 PM, Adrian Chadd wrote:
>
> (cc'ing the list again, hehe :-)
> On Tue, 21 Jul 2020 at 14:35, Aaron wrote:
>
>> On 7/21/2020 5:33 PM, Adrian Chadd wrote:
>>
> Ok. Please do dig into it.
>>
&
(cc'ing the list again, hehe :-)
On Tue, 21 Jul 2020 at 14:35, Aaron wrote:
>
> On 7/21/2020 5:33 PM, Adrian Chadd wrote:
>
>
> Ok. Please do dig into it.
>
> Do try to treat the regdomain code as a black box - input is "what
> regulatory domain do we
On Tue, 21 Jul 2020 at 14:31, Aaron wrote:
>
> What do others think? What should we do?
> >>> I vote for recreating it as a CSV file. Would then be easier to work
> with
> >>> and easy to convert to other formats -- json/xml/...
> >> Lol, if anything we'd likely use a format that we already
On Tue, 21 Jul 2020 at 12:59, Chris wrote:
> > So, I'd really like to figure out how to simplify the regdomain.xml file.
> > But - we should come up with a firm plan first. Luckily this IS basically
> > all userland work. :-)
> >
> +1 for the offer to dig in, Aaron!
>
> > What do others think? W
hi!
On Tue, 21 Jul 2020 at 02:06, Aaron wrote:
> Howdy FreeBSD wireless mailing list,
>
> Looking to help, only item on this list
> (https://wiki.freebsd.org/WiFi/TodoStuff) I'm competent to address is
> "net80211 regulatory". I read the "regdomain" manpage ... no help there.
>
Yeah, it's ...o
On Mon, 13 Jul 2020 at 08:25, Emmanuel Vadot wrote:
>
>
> Compile and working ?
> Because that's easy to compile code if you add a lot of dummy stub
> functions.
I'm happy that this is going on; at the very least it'll point out a bunch
of missing bits from our net80211 API that should get im
On Fri, 10 Jul 2020 at 14:33, Emmanuel Vadot wrote:
> On Thu, 09 Jul 2020 11:36:59 +
> "Bjoern A. Zeeb" wrote:
>
> > On 9 Jul 2020, at 11:24, driesm.michi...@gmail.com wrote:
> >
> > Hi Dreis,
> >
> > > I was wondering what the current state of the following wireless cards
> > > is:
> > >
>
On Sat, 13 Jun 2020 at 11:26, Vladimir Botka wrote:
> > > > > .. buy and USB wifi adapter with support on 2,4GHz and 5GHz
> > > > > Can you help me to search one model with 2,4 and 5Ghz support?
>
> > > > I'm using if_run and if_rtwn devices here. :)
> > > > rtwn should work ok as an 11n AP; we'r
I'm actually using an RT3593. Right now whilst talking with you :)
-a
On Fri, 12 Jun 2020 at 00:53, Vladimir Botka wrote:
> Hi!
>
> On Thu, 11 Jun 2020 22:23:54 -0700
> Adrian Chadd wrote:
>
> > > Can you help me to search one model with 2,4 and 5Ghz suppor
On Thu, 11 Jun 2020 at 22:38, Vladimir Botka wrote:
> On Fri, 12 Jun 2020 07:33:46 +0200
> Vladimir Botka wrote:
>
> > On Fri, 12 Jun 2020 04:33:01 +
> > carmezsa via freebsd-wireless wrote:
> >
> > > ... USB wifi adapter with support on 2,4GHz and 5GHz
> >
> > I've found only one. It's Ral
hi!
On Thu, 11 Jun 2020 at 21:33, carmezsa via freebsd-wireless <
freebsd-wireless@freebsd.org> wrote:
> Hi,
> I am using pfsense firewall and It is on FreeBsd OS. I would like buy and
> USB wifi adapter with support on 2,4GHz and 5GHz but I am not use what USB
> devices I can buy and where.
>
>
Yeah, it's a bit wrong. look at the ifieee80211.c code to see. This
isn't the station in "list sta"; /there/ it's in power save. Scan it's
protection.
-a
On Mon, 25 May 2020 at 14:11, Andriy Gapon wrote:
>
> On 26/05/2020 00:00, Adrian Chadd wrote:
On Mon, 25 May 2020 at 12:48, Andriy Gapon wrote:
>
> On 25/05/2020 14:00, Lars Engels wrote:
> > Am 2020-05-25 08:48, schrieb Andriy Gapon:
> >> How to tell from ifconfig wlan scan output which networks are open?
> >> Thanks!
> > ^
> > ifconfig -v list scan
>
> So, still, how do I tell which of t
hi!
bz and i poked the phab admins to create a wireless group in
phabricator. It's a public group. I'm hoping we can put wireless and
potentially bluetooth bits into this tag as well.
It's a public group so please join it to keep track of wireless related patches.
Also if you've got the time, it
hi!
No, it's actually your AP changing width between 20MHz and 40MHz.
-adrian
On Fri, 22 May 2020 at 13:03, Kevin Oberman wrote:
>
> in the past few days my logs have been filled with "iwn0: null_update_chw:
> need callback" messages. No change to the driver for over a year, so it was
> proba
On Tue, 19 May 2020 at 16:07, Andriy Gapon wrote:
> >
> > Adrian, thank you very much for your suggestion.
> > Being a complete noob in this area, this is my stab at it:
> > https://reviews.freebsd.org/D24923
>
> Also, I see that there is some friction between how rfkill is handled at the
> driv
On Mon, 18 May 2020 at 00:57, Andriy Gapon wrote:
>
>
> I am trying to get my laptop fully functional and one of the things that
> currently does not work as expected is a Wi-Fi / Radio special key.
> It seems to be handled fully in hardware (but not 100% sure), but when I press
> it only bluetoot
Heh, it's not this - the unaligned print only happens when I run
tcpdump with an ether src or ether dst filter. If i just use ether
proto it doesn't happen.
So there is something unaligned going on inside libpcap /and/ somehow
ether dst is not working right at least on mips + 802.11 DLT.
-adria
On Mon, 4 May 2020 at 12:54, Adrian Chadd wrote:
>
> hi,
>
> This commit /seems/ to have broken things on FreeBSD-HEAD on mips74k.
> I haven't yet tried hostapd mode on x86 with this commit; I"ll do that
> soon.
>
> The TL;DR:
>
> * hostapd + wpa encry
hi,
This commit /seems/ to have broken things on FreeBSD-HEAD on mips74k.
I haven't yet tried hostapd mode on x86 with this commit; I"ll do that
soon.
The TL;DR:
* hostapd + wpa encryption + mips32 (mips74k in this instance) fails
on -HEAD! Woo!
* l2_packet_freebsd.c in hostapd uses a pcap filt
Hi!
I've documented the layout in the wiki:
wiki.freebsd.org/dev/ath(4) and wiki.freebsd.org/dev/ath_hal(4) . You
should start there.
The HAL code is a bit twisty:
* the driver - if_ath_*[ch] is common for everything;
* the if_ath_pci.c code detects the NIC and creates the if_ath context
and se
Hi!
Wait, someone's calling iwn_rate2ridx() with rate=0 ? That's highly
bogus and yes will lead to a firmware panic.
what's the caller? How's it being called with rate=0 ? It sounds like
something in the rate negotiation is failing...
-adrian
On Sun, 1 Dec 2019 at 05:24, wrote:
>
> https://bu
ore work.
-adrian
On Thu, 19 Sep 2019 at 15:21, Johannes Lundberg wrote:
>
> On 9/19/19 3:06 PM, Adrian Chadd wrote:
>
> So roaming in ifconfig/net80211 is what's set to manual.
>
> wpa_supplicant right now does RSSI threshold based roaming. All of the
> roaming
triggering bgscan too periodically rather than only when the RSSI is low.
-adrian
On Thu, 19 Sep 2019 at 15:04, Cy Schubert wrote:
> On September 19, 2019 8:20:07 AM PDT, Adrian Chadd
> wrote:
> >Roaming is done in wpa_supplicant when it's running.That's w
Roaming is done in wpa_supplicant when it's running.That's where the smarts
need to be. :(
-adrian
On Thu, 19 Sep 2019 at 05:44, Bjoern A. Zeeb
wrote:
> On 19 Sep 2019, at 12:28, Tom Jones wrote:
>
> Hi,
>
> freebsd-wireless might be a better list for all this ..
>
>
> > On Tue, Sep 17, 2019
hi!
If you can pull out bits from say the linux driver to update our drivers
then sure! Even if you don't succeed I bet you'll learn a lot!
-adrian
On Mon, 9 Sep 2019 at 12:45, lr x wrote:
> Hello!
>
> I'm a grad student taking an Operating Systems course this semester where I
> can officia
Yeah, the iwm code is missing all of the 11n/11ac handling code. :-)
-adrian
On Wed, 4 Sep 2019 at 01:42, wrote:
> Hello,
>
> I see - ok so its not possible with the iwm driver yet.
> Care to elaborate the details, whats missing etc.?
>
> regards,
>
> Am 2019-09-
RSN
> ---snip
>
> I've measured this aprox. 2MB/s with my laptop, which is also using
> FreeBSD 12.
> Its having an Intel wireless 3165 card.
>
> regards,
> Georg
>
> Am 04.09.19 um 00:58 schrieb Adrian Chadd:
>
hi!
No, you should be getting more than 2 megabits/sec.
Whats the output of "ifconfig wlan0 list sta" ?
-adrian
On Wed, 28 Aug 2019 at 16:41, Georg Bege wrote:
> Hello community,
>
> Im using a Wifi AP with an Atheros card now for quite some time, since a
> couple of FreeBSD revisions. I gu
-----
> On Aug 14, 2019, 12:09 AM, Adrian Chadd < adrian.ch...@gmail.com> wrote:
>
>
> hi!
>
> Thanks for doing this! if it's the same chipset but a different ID then
> yes, it's literally that easy most times. :)
>
> Nice work! If you file a PR then we'll
hi!
Thanks for doing this! if it's the same chipset but a different ID then
yes, it's literally that easy most times. :)
Nice work! If you file a PR then we'll try to get someone to commit it to
freebsd-head.
-a
On Sun, 11 Aug 2019 at 00:34, james.m.parsons via freebsd-wireless <
freebsd-wire
Hi!
So, you don't set the monitor flag like you do on linux. you create a
monitor VAP instead or you just use tcpdump with the right flags.
Try:
tcpdump -ni wlan0 -y IEEE802_11_PROTO
That'll put the NIC into monitor mode on the current channel, even in
station mode, and let you do normalt raffi
hi!
interesting! sorry, I haven't poked much at the broadcom stuff since
landon went and did his bhnd work a few years ago. I'll have to go see
what changed in fetching those EEPROM values and figure out why it's
not being read correctly. I have no timeline on this yet though!
-a
On Tue, 21 May
hi,
please raise a PR. Nothing in the driver has changed AFAIK; it's
possible there's a USB issue.
-a
On Wed, 15 May 2019 at 05:45, Michael Zhilin wrote:
>
> Hi,
>
> Did you raise PR?
> I suppose it's new issue.
>
> Thanks!
>
> On Wed, May 15, 2019 at 3:36 PM Sreenath Battalahalli via freebsd-
gards
>
> Stephen
>
>
> On Thu, 9 May 2019 at 19:55, Adrian Chadd wrote:
>
>> hi!
>>
>> Ok, so the 30 second version:
>>
>> * the AR54xx, AR91xx and later 11n chips had some changes to the
>> resolution of the timers that Sam used to control
t;>
>>> We are interested in "long range outdoor" (10-20km) with high gain
>>> antennas.
>>> Do you know "Mikrotik Nstreme/NV2" and "Ubiquity Airmax" ?
>>> Those have framing/polling done in software - wrapped aroun
hi!
It should be pretty self explanatory in the HAL code. Take a look at
ar5416_xmit.c (as that applies to the AR9227 too) and how those methods are
called by the driver.
-adrian
On Wed, 24 Apr 2019 at 03:57, malepati vishnuvardhan <
malepativishnuvardhan1...@gmail.com> wrote:
> Hi,
> I am C
gt; kernel: ath0: [HT] 2 RX streams; 2 TX streams
> kernel: ath0: AR9460 mac 640.3 RF5110 phy 3856.0
> kernel: ath0: 2GHz radio: 0x; 5GHz radio: 0x
> kernel: [ath] loaded
>
>
>
>
> вт, 23 апр. 2019 г. в 22:39, Adrian Chadd :
>
>> Do you have the kernel enviro
Do you have the kernel environment variable setup to say it's a WB222?
-a
On Tue, 23 Apr 2019 at 12:37, Serge Semenenko wrote:
> Could it matter that I load modules from rc.conf?
>
> kld_list="if_ath if_ath_pci linux linsysfs linprocfs xhci umass ums
> snd_hda /boot/modules/i915kms.ko /boot/m
ooo please send me a pull request with the device id update!
-a
On Sat, 20 Apr 2019 at 04:17, Serge Semenenko wrote:
> Hi
>
> It works for me with such section in devd.conf
>
> attach 200 {
>device-name "ubt[0-9]+";
>match "vendor" "0x0cf3";
>match "product" "0xe006";
>
It doesn't interoperate. Someone needs to grab the freebsd-mesh stuff and
fix it up. ;)
-a
On Fri, 19 Apr 2019 at 02:33, wrote:
> Hi,
>
> Looking at the FreeBSD/mesh wiki page (
> https://wiki.freebsd.org/WiFi/Mesh ) it says:
>
> "Development is occurring at the FreeBSD HEAD branch and an exper
Hi!
Ok, I'm going to have to find my NIC and see what's going on.
-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.or
hi,
On Thu, 18 Apr 2019 at 10:02, Matthias Apitz wrote:
> El día Thursday, April 18, 2019 a las 08:05:53AM -0700, Adrian Chadd
> escribió:
>
> > that means it SHOULD be ready for normal HCI operation. bcdDevice=1 is
> what
> > the driver uses to determine if it'
08:03, Alexey Dokuchaev wrote:
> On Thu, Apr 18, 2019 at 07:58:34AM -0700, Adrian Chadd wrote:
> > Ok, so it found and loaded in the bluetooth firmware into the
> > bluetooth NIC RAM.
>
> Why do you think so?
>
> > On Thu, 18 Apr 2019 at 07:50, Matthias Apitz wrote:
Ok, so it found and loaded in the bluetooth firmware into the bluetooth NIC
RAM.
https://www.freebsd.org/doc/handbook/network-bluetooth.html
Your goal is to have devices show up in in an inquiry command.
-a
On Thu, 18 Apr 2019 at 07:50, Matthias Apitz wrote:
>
> I have booted the other C72
It means there's a replay / out of order thing going on with the received
frames that are TKIP encrypted.
-adrian
On Wed, 17 Apr 2019 at 12:18, Yuri wrote:
> I use wpa_gui, and sometimes it fails to connect with the "Last message"
> field alternating between "Associating ..." and "TKIP count
Try loading firmware, see if it can do a bt scan.
Try also bringing up the 2g wifi and connect to a 2g station; see if that
also allows a bt scan to work.
-a
On Wed, 17 Apr 2019 at 11:17, Matthias Apitz wrote:
> Am Mittwoch, 17. April 2019 19:59:17 CEST schrieb Adrian Chadd
> :
no flashing occurs. it's running out of ram on the chip.
-a
On Wed, 17 Apr 2019 at 10:56, Matthias Apitz wrote:
> Am Mittwoch, 17. April 2019 18:59:08 CEST schrieb Adrian Chadd
> :
> > Did you copy it into /usr/share/ or did you pass the command line arg in
> to
> &
Did you copy it into /usr/share/ or did you pass the command line arg in to
set the base directory? :)
-a
On Wed, 17 Apr 2019 at 09:57, Matthias Apitz wrote:
> El día Wednesday, April 17, 2019 a las 02:35:51PM +, Alexey Dokuchaev
> escribió:
>
> > On Tue, Apr 16, 2019 at 12:34:12PM +0200,
i thought i had the various combinations working when i last poked at this
stuff. I'll have to go re-test it all.
-a
On Mon, 15 Apr 2019 at 10:35, Alexey Dokuchaev wrote:
> On Mon, Apr 15, 2019 at 02:52:17PM +0200, Matthias Apitz wrote:
> > I have not missed (or deleted) any mail in this thre
it's a userland program. :-) All ath3k in linux does is detect the hardware
and squeeze firmware into it. That's literally it.
-adrian
On Sun, 14 Apr 2019 at 21:48, Matthias Apitz wrote:
> El día domingo, abril 14, 2019 a las 09:42:46a. m. -0700, Adrian Chadd
> escribió:
&g
m. -0700, Adrian Chadd
> escribió:
>
> > ok, so you've added the WB222 coex bits. Does ath3k load OK?
> >
>
> I do not have this module:
>
> root@c720-r342378:/home/guru # uname -a
> FreeBSD c720-r342378 13.0-CURRENT FreeBSD 13.0-CURRENT GENERIC amd64
> root@c72
ok, so you've added the WB222 coex bits. Does ath3k load OK?
-a
On Sun, 14 Apr 2019 at 09:02, Matthias Apitz wrote:
> El día domingo, abril 14, 2019 a las 08:56:52a. m. -0700, Adrian Chadd
> escribió:
>
> > hi!
> >
> > Ok, so there's two parts:
> >
hi!
Ok, so there's two parts:
* loading in the firmware and/or bt nic setup (clock rate, etc) via
ath3kfw; and
* bluetooth coex/antenna setup in ath(4).
The latter I can do. The former may require USB stack debugging.
Which NIC is in the C720? Ar9485, right?
-adrian
On Sun, 14 Apr 2019 at 0
On Sat, 13 Apr 2019 at 12:14, Alexey Dokuchaev wrote:
> On Sat, Apr 13, 2019 at 11:44:25AM -0700, Adrian Chadd wrote:
> > Hm, is this a problem with our usb3 stack itself?
> >
> > If you send me a pull request against ath3k I'll merge it into my git
> > tree j
range outdoor" (10-20km) with high gain
> antennas.
> Do you know "Mikrotik Nstreme/NV2" and "Ubiquity Airmax" ?
> Those have framing/polling done in software - wrapped around the wireless
> driver.
> Is there equivalent developed in FreeBSD?
>
> Best
Hm, is this a problem with our usb3 stack itself?
If you send me a pull request against ath3k I'll merge it into my git tree
just for completeness.
Maybe we need to loop in hps@ with a bunch of usbdump output to see what
the transactions look like...
-adrian
On Sat, 13 Apr 2019 at 07:21, Ale
Well, yeah, qualcomm developers did a lot of the linux ath9k/ath3k support
:)
-a
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@fre
hi!
I know that a lot of the 11ac chips do TDMA but the vendors keep the
implementation and knobs close to their chest. We don't have any public
APIs for it. Sorry :(
-a
On Thu, 11 Apr 2019 at 10:23, Stephen Patrick wrote:
> Dear sirs,
>
> Is this feature working for point-to-point, and poin
>
> Hi,
>
I'm trying to figure out an ath sta mode crash and some ath10k things. I
have the AR9485 / AR9462 hardware here so please just keep poking me here
and on irc over the next couple weeks to get it working.
There's also some weird antenna coex stuff that needs setting up in the HAL
too tha
I have a tool to upload firmware - github.com/erikarn/ath3k. See if that
helps!
-a
On Thu, 11 Apr 2019 at 06:19, Alexey Dokuchaev wrote:
> On Thu, Apr 11, 2019 at 03:13:28PM +0200, Matthias Apitz wrote:
> > # usbconfig list
> > ...
> > ugen0.3: at usbus0, cfg=0 md=HOST
> > spd=FULL (12Mbps)
Hi! We're working on it in github.com/erikarn/athp/ . I'm fixing up the
transmit path in the driver right now to work around firmware behaviour and
Geramy is wrapping his head around DMA / busdma issues.
-adrian
On Fri, 8 Mar 2019 at 03:45, Domenico Panella wrote:
> Hi guys,
>
> I am a progra
Hm, it'd be good to see driver debugging. It'd be good there to see if the
actual auth frames are being exchanged and ACKed at the MAC level or not.
I've seen some pretty crappy behaviours both with how some APs wanna try
band steering (by dropping you off 2g when they see you've sent a probe on
5
hi,
I'm trying to update things with Geramy right now. We hit a snag where his
updates broke my QCA9880 NIC in STA mode, so we're working through that
right now.
-adrian
On Mon, 11 Feb 2019 at 09:51, Ben Widawsky wrote:
> On 19-02-04 00:29:29, Anthony Jenkins wrote:
>
> [snip]
>
> Hi Adrian
>
> Hi,
>
I'm .. mostly trying to help people. Geramy has been helping out hugely on
the ath10k port and I'm updating my laptops (again!) to the latest head so
I can continue rolling with that.
I'd like to get ath10k ready to put into the tree but there are a couple of
net80211 and driver holes t
Hi!
If you can put some code up then we can poke at it together and see how to
get the firmware load and USB framework bits into if_ath(4).
You don't want to load it via userland; you really want the driver to load
it at attach time and if it wants to power things fully down off or not.
(You can
Is that the QCA6174 chip? Yeah some of us are working on it right now.
(more so others than I atm..)
-a
On Fri, 28 Dec 2018 at 16:18, David Horwitt wrote:
> Is this chipset supported? I was under the impression that it was going to
> be included in 12.0, but see no mention in the release note
Hi!
Sorry for not replying earlier.
The 30 second version - you should look at uath and ath9k's usb code. It's
not ENTIRELY just a register access method - there are a bunch of things
that are done by firmware via calls - like setting the mode,
adding/removing nodes, etc. ath(4) will need a bunch
Hi,
There are some minor differences but the big one is "PCI (9227)" versus
"PCIe (AR9287).
-adrian
On Sun, 16 Dec 2018 at 20:47, malepati vishnuvardhan <
malepativishnuvardhan1...@gmail.com> wrote:
> Hi,
> As i am doing some research on atheros drivers of freebsd. I want to know,
> if Ather
hi!
There's only legacy support at the moment; MSI ended up being a bit buggy
so it's not implemented.
AR9287 has one receive queue and ten transmit queues.
-adrian
On Fri, 14 Dec 2018 at 03:10, malepati vishnuvardhan <
malepativishnuvardhan1...@gmail.com> wrote:
> Hi,
> My question is what
ugh, I wonder why 11n is not working for you. hm. ;(
-a
On Wed, 12 Dec 2018 at 13:30, Volodymyr Kostyrko wrote:
> On 21.11.18 18:50, Volodymyr Kostyrko wrote:
> > On 21.11.18 18:29, Adrian Chadd wrote:
> >> what's a channel survey give? is it on a very busy channel?
what's a channel survey give? is it on a very busy channel? Is there a
nearby device?
-a
On Wed, 21 Nov 2018 at 07:28, Volodymyr Kostyrko wrote:
> On 16.11.18 00:02, Adrian Chadd wrote:
> > ok, interesting. I'll see if I can reproduce it later next week. I
> haven
ok, interesting. I'll see if I can reproduce it later next week. I haven't
changed much on the AR9220 HAL...
-a
On Thu, 15 Nov 2018 at 14:01, Volodymyr Kostyrko wrote:
> On 15.11.18 23:31, Adrian Chadd wrote:
> > Hi!
> >
> > 11-stable to 12-stable shouldn&
Hi!
11-stable to 12-stable shouldn't have resulted in a regression?
interesting, okay. Which devices are they?
-adrian
On Thu, 15 Nov 2018 at 12:56, Volodymyr Kostyrko wrote:
> Hello.
>
> I'm not quite sure what happens so I'll just dump here what I have in
> mind so it would be easier to so
yeah, that we'll have to look into..
-a
On Mon, 12 Nov 2018 at 13:33, tech-lists wrote:
> On Mon, Nov 12, 2018 at 12:32:25PM -0800, Adrian Chadd wrote:
> >If it's showing up like that then it's not an AR9170 device; it's a
> >broadcom firmware device. :(
If it's showing up like that then it's not an AR9170 device; it's a
broadcom firmware device. :(
-a
On Mon, 12 Nov 2018 at 12:08, tech-lists wrote:
> Hi,
>
> context:
> freebsd-12-beta4 on amd64 and freebsd-12 on arm64, I'm trying right now
> with amd64 r340354.
>
> I have a Netgear WNDA3100
it should be fine; have you loaded if_ath_pci and the rest of the ath
driver bits? (ath_hal, ath_hal_ar5416, ath_hal_ar9280) ?
-adrian
On Sat, 3 Nov 2018 at 15:55, Volodymyr Kostyrko wrote:
> Hello.
>
> I have this card:
>
> ath0@pci0:4:5:0:class=0x028000 card=0x2093168c chip=0x002916
It'd be interesting to figure out how much each step is taking. Eg, USB
detect, firmware load, create interface, bstart wpa_supplicant, etc - that
should be quick. I wonder if scan is taking forever..
On Tue, 30 Oct 2018 at 16:03, Yuri wrote:
> I just measured: 20-40 seconds elapse between the
hi!
ok, hm. So, I wonder if there are some issues with the busdma code. Boot
your test device with say, 1G of memory instead (there's some boot hint you
can set that limits physical memory) which should avoid things like 64 bit
bounce buffer stuff into 32 bit memory space. Booting with 1G hopefull
hi!
So, net80211 itself shouldn't really differ that much for this particular
issue. There may be some functions that aren't called in monitor mode (like
sta_join) but you're not yet there.s
I'd look at the difference in the driver VAP setup and the newstate
function for different operating modes
hi,
I replied on iRC but, for reference.
The scanner array here is the per-mode scanner (AP, STA, etc.) that
implements how you should do channel scanning and selection. It's set by
net80211 by default and you normally don't need to go change it.
-adrian
On Sat, 28 Jul 2018 at 17:13, Farhan
quot;options INTRNG" to my kernel config, so that this "Unimplemented
> nexus_teardown_intr" code path isn't taken, but now I get several errors
> during compilation, so I guess that was a mistake.
>
> On 18-07-04 16:39:42, Adrian Chadd wrote:
> >Hi,
> &
1 - 100 of 1608 matches
Mail list logo