Variables HW_PHYSMEM and HW_USERMEM were deprecated 13 years ago,
maybe we can remove them from sysctl(2)?
It was originally in sysctl(3) if someone want to do some history
research
https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/lib/libc/gen/Attic/sysctl.3#rev1.178
Index: sysctl.2
Solene Rapenne wrote:
> Variables HW_PHYSMEM and HW_USERMEM were deprecated 13 years ago,
> maybe we can remove them from sysctl(2)?
>
> It was originally in sysctl(3) if someone want to do some history
> research
>
Stuart Henderson wrote:
> On 2021/10/05 18:11, Solene Rapenne wrote:
> > Variables HW_PHYSMEM and HW_USERMEM were deprecated 13 years ago,
> > maybe we can remove them from sysctl(2)?
>
> "deprecated" doesn't mean removed or disabled, it just means that one
> shouldn't use them. These are still
On 2021/10/05 18:11, Solene Rapenne wrote:
> Variables HW_PHYSMEM and HW_USERMEM were deprecated 13 years ago,
> maybe we can remove them from sysctl(2)?
"deprecated" doesn't mean removed or disabled, it just means that one
shouldn't use them. These are still in system headers and supported by
OK?
diff --git ifconfig.c ifconfig.c
index 7d86e887561..33aea910d80 100644
--- ifconfig.c
+++ ifconfig.c
@@ -246,7 +246,6 @@ voidsetgroupattribs(char *, int, char *[]);
intprintgroup(char *, int);
void setautoconf(const char *, int);
void settemporary(const char *, int);
-void
AUTH -> AUTH state transitions happen if the access point uses band-steering.
This was originally implemented to fix interop with some Aruba APs.
A recent commit I made to iwm/iwx drivers probably broke this.
Here is a fix.
ok?
diff b1c80baf1b7d4bf6f528498fe67f3d1db4353371 /usr/src
blob -
> Date: Tue, 5 Oct 2021 12:42:21 +
> From: Visa Hankala
>
> On Mon, Oct 04, 2021 at 05:04:11PM +0200, Mark Kettenis wrote:
> > > Date: Mon, 4 Oct 2021 13:42:48 +
> > > From: Visa Hankala
> > >
> > > On the Zynq-7000, the lowest 512KiB of physical address space usually
> > > contains
When roaming between APs, all data in struct net80211_node is replaced
as soon as we have decided to switch to a different AP.
This means that the BSSID of our old AP is no longer stored in ic_bss
once we enter iwm_newstate(). We do however use this address in firmware
commands while tearing
On Mon, Oct 04, 2021 at 05:04:11PM +0200, Mark Kettenis wrote:
> > Date: Mon, 4 Oct 2021 13:42:48 +
> > From: Visa Hankala
> >
> > On the Zynq-7000, the lowest 512KiB of physical address space usually
> > contains RAM that is usable by the CPUs. However, many other bus
> > masters, such as
Send a probe request to our new AP when we are about to roam to it.
When the code modified below runs, we have just replaced ic_bss (ni)
with our new AP a few lines above.
Sending a probe request isn't strictly required but it might help to
initialize state in our AP in case our background scan
Make sure to use HT for data frames only in case our Tx rate is fixed.
Non-data frames are not supposed to use HT.
This change applies if the Tx rate has been fixed for testing purposes
with a command such as 'ifconfig iwm0 media HT-MCS13 mode 11n'.
I've only found this by code inspection, not
While debugging iwm roaming issues which are now fixed in -current,
I noticed a small difference between our driver and the Linux driver:
Set the assoc ID assigned by our AP when updating the firmware station
with the ADD_STA command. Not sure if this strictly required but it
doesn't seem to
12 matches
Mail list logo
