Date: Fri, 11 Jan 2019 13:57:32 -0500 From: waddlesplash <waddlesplash@gmail.com> Cc: wireless@freebsd.org Subject: Re: wireless coordination and who's working on what? Message-ID: <CAEesM75f111pms2MMiZZQ=hRZ1p2QAOwrSvzwHEVhSAgOXPabg@mail.gmail.com> In-Reply-To: <BDD2289A-D362-48C3-8635-FBD4B0711C22@FreeBSD.org> References: <BDD2289A-D362-48C3-8635-FBD4B0711C22@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 7, 2019 at 9:47 AM Bjoern A. Zeeb <bz@freebsd.org> wrote: > I=E2=80=99d love to start coordinating efforts and get an overview on who= =E2=80=99s > got his hands dirty in what and who has plans for other =E2=80=9Ctodos=E2= =80=9D. > > Can you please reply to me (here) or (privately *)? I=E2=80=99ll summari= se > the current state for everyone in a week or two. I've recently finished upgrading Haiku to FreeBSD 12 net80211 and drivers. I don't have any major plans at the moment personally, but some things you might want to note: * there are a variety of iwm patches available in DragonFlyBSD that haven't yet been merged into FreeBSD * general driver stability issues, iwn/ath/iwm at least (mostly failures to initialize on hardware that is theoretically supported, or other general timing issues) * use-after-free panics in certain scenarios (it seems some of these should be caught by INVARIANTS, but I've only reproduced them on Haiku, not on FreeBSD) Additionally, if you want to keep an eye on Haiku's bugtracker, you can use this query to see tickets reported just in the "network drivers" category: https://dev.haiku-os.org/query?status=3Dassigned&status=3Din-progress&statu= s=3Dnew&status=3Dreopened&type=3Dbug&component=3D%5EDrivers%2FNetwork&col= =3Did&col=3Dsummary&col=3Dstatus&col=3Downer&col=3Dtype&col=3Dpriority&col= =3Dmilestone&desc=3D1&order=3Did -waddlesplash
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAEesM75f111pms2MMiZZQ=hRZ1p2QAOwrSvzwHEVhSAgOXPabg>