Re: SIOCS80211 ioctl and 8.99.32

2019-01-28 Thread Paul Goyette
This should be fixed now. An additional commit is pending to change the name of the hook, but no functional change is intended there! On Mon, 28 Jan 2019, Ryo ONODERA wrote: Hi, From: Patrick Welche , Date: Mon, 28 Jan 2019 10:58:54 + Just tried a 8.99.32 kernel and get Successfully

Re: SIOCS80211 ioctl and 8.99.32

2019-01-28 Thread Paul Goyette
On Mon, 28 Jan 2019, bch wrote: On Mon, Jan 28, 2019 at 1:51 PM Paul Goyette wrote: I notice that christos made some changes here overnight while I was (gasp) sleeping! Can you check to see if his changes fix your problem? It didn???t appear fixed w/i the last 0.5h or so, if that

daily CVS update output

2019-01-28 Thread NetBSD source update
Updating src tree: P src/doc/CHANGES P src/external/mit/xorg/server/drivers/xf86-video-modesetting/Makefile P src/share/misc/acronyms.comp P src/share/misc/style P src/sys/arch/xen/x86/autoconf.c P src/sys/compat/common/compat_43_mod.c P src/sys/compat/common/compat_mod.h P

Re: SIOCS80211 ioctl and 8.99.32

2019-01-28 Thread bch
On Mon, Jan 28, 2019 at 1:51 PM Paul Goyette wrote: > I notice that christos made some changes here overnight while I was > (gasp) sleeping! Can you check to see if his changes fix your > problem? > It didn’t appear fixed w/i the last 0.5h or so, if that helps... -bch > > On Mon, 28 Jan

Re: SIOCS80211 ioctl and 8.99.32

2019-01-28 Thread Paul Goyette
On Mon, 28 Jan 2019, bch wrote: On Mon, Jan 28, 2019 at 1:51 PM Paul Goyette wrote: I notice that christos made some changes here overnight while I was (gasp) sleeping! Can you check to see if his changes fix your problem? It didn???t appear fixed w/i the last 0.5h or so, if that

Re: SIOCS80211 ioctl and 8.99.32

2019-01-28 Thread Paul Goyette
I notice that christos made some changes here overnight while I was (gasp) sleeping! Can you check to see if his changes fix your problem? On Mon, 28 Jan 2019, Ryo ONODERA wrote: Hi, From: Patrick Welche , Date: Mon, 28 Jan 2019 10:58:54 + Just tried a 8.99.32 kernel and get

Re: SIOCS80211 ioctl and 8.99.32

2019-01-28 Thread bch
On 1/28/19, Paul Goyette wrote: > I will investigate as soon as possible. But it may take some time Formatting strings like this: ./external/bsd/wpa/dist/wpa_supplicant/wpa_supplicant.c: [...] 5308 wpa_msg(wpa_s, MSG_ERROR, "Failed to initialize driver " 5309

Re: SIOCS80211 ioctl and 8.99.32

2019-01-28 Thread Ryo ONODERA
Hi, From: Paul Goyette , Date: Mon, 28 Jan 2019 19:04:24 +0800 (PST) > I will investigate as soon as possible. But it may take some time. Thank you very much. I can wait. > On Mon, 28 Jan 2019, Ryo ONODERA wrote: > >> Hi, >> >> From: Patrick Welche , Date: Mon, 28 Jan 2019 >> 10:58:54 +

Re: SIOCS80211 ioctl and 8.99.32

2019-01-28 Thread Paul Goyette
I will investigate as soon as possible. But it may take some time. On Mon, 28 Jan 2019, Ryo ONODERA wrote: Hi, From: Patrick Welche , Date: Mon, 28 Jan 2019 10:58:54 + Just tried a 8.99.32 kernel and get Successfully initialized wpa_supplicant ioctl[SIOCS80211, op=16, arg_len=0]:

Re: SIOCS80211 ioctl and 8.99.32

2019-01-28 Thread Ryo ONODERA
Hi, From: Patrick Welche , Date: Mon, 28 Jan 2019 10:58:54 + > Just tried a 8.99.32 kernel and get > > Successfully initialized wpa_supplicant > ioctl[SIOCS80211, op=16, arg_len=0]: Inappropriate ioctl for device > iwn0: Failed to initialize driver interface > > when running

SIOCS80211 ioctl and 8.99.32

2019-01-28 Thread Patrick Welche
Just tried a 8.99.32 kernel and get Successfully initialized wpa_supplicant ioctl[SIOCS80211, op=16, arg_len=0]: Inappropriate ioctl for device iwn0: Failed to initialize driver interface when running wpa_supplicant. (8.99.30 userland from 22 Jan - works with 22 Jan kernel) Cheers, Patrick