Amdgpu card support

First of all, thanks for including this, but should a diff be submitted to the man page that states it supports everything between SI and Vega? If I'm reading the documentation and past posts correctly, amdgpu uses Xorg's Glamor and Mesa to output anything. Mesa is at 19.0.8, so it should support

Re: mira sfer overflow panic (was: Re: 11n support for athn(4))

On Thu, Jan 26, 2017 at 10:38:44AM +0100, Stefan Sperling wrote: > On Thu, Jan 26, 2017 at 06:36:06AM +0000, Peter Kay wrote: > > sfer overflow > > Interesting. This is the first time I've ever seen this panic trigger. > > Can you apply this patch and try to trigger it aga

Re: 11n support for athn(4)

On 17 January 2017 at 12:25, Stefan Sperling wrote: > On Tue, Jan 17, 2017 at 11:56:09AM +0100, Stefan Sperling wrote: >> Without more details, all I can do is guess. >> I made one guess already (antennas) and sadly I guessed wrong. > > Another thing where your setup differs from

Re: 11n support for athn(4)

  Original Message   From: s...@stsp.name Sent: 17 January 2017 12:25 p.m. To: syllops...@syllopsium.co.uk; tech@openbsd.org Subject: Re: 11n support for athn(4) On Tue, Jan 17, 2017 at 11:56:09AM +0100, Stefan Sperling wrote: >> Without more details, all I can do is guess. >> I made one guess

Re: 11n support for athn(4)

  Original Message   From: s...@stsp.name Sent: 17 January 2017 10:00 a.m. To: syllops...@syllopsium.co.uk Cc: tech@openbsd.org Subject: Re: 11n support for athn(4) On Mon, Jan 16, 2017 at 11:58:51PM +, Peter Kay wrote: >> >> Three, yes, but note that unless the antenn

Re: 11n support for athn(4)

On 16 January 2017 at 23:30, Stefan Sperling <s...@stsp.name> wrote: > On Mon, Jan 16, 2017 at 07:18:04PM +0000, Peter Kay wrote: >> I'm still having issues with this. >> >> When the access p64 bytes from 192.168.1.251: icmp_seq=678 ttl=255 >> time=4.502 ms o

Re: 11n support for athn(4)

ptions on one of the Android phones I have lying around. On 14 January 2017 at 12:53, Stefan Sperling <s...@stsp.name> wrote: > On Sat, Jan 14, 2017 at 12:42:09PM +, Peter Kay wrote: >> On 14 January 2017 at 12:02, Stefan Sperling <s...@stsp.name> wrote: >> > On S

Re: 11n support for athn(4)

On 14 January 2017 at 11:23, Stefan Sperling <s...@stsp.name> wrote: > On Sat, Jan 14, 2017 at 11:03:24AM +0000, Peter Kay wrote: >> On 12 January 2017 at 15:06, Stefan Sperling <s...@stsp.name> wrote: > So your first test might not have had 11n enabled since the first tw

Re: 11n support for athn(4)

On 12 January 2017 at 15:06, Stefan Sperling wrote: > On Tue, Jan 10, 2017 at 12:27:47AM +0100, Stefan Sperling wrote: >> On Mon, Jan 09, 2017 at 01:54:55PM +0100, Stefan Sperling wrote: >> > This diff adds 11n support to the athn(4) driver. >> > Requires -current net80211 code

Re: 11n support for athn(4)

is working. On 11 January 2017 at 23:28, Peter Kay <syllops...@syllopsium.co.uk> wrote: > On 11 January 2017 at 22:05, Stefan Sperling <s...@stsp.name> wrote: > >> >> You haven't updated all of src/sys. > > I'm obviously being really dumb, but what is wrong

Re: 11n support for athn(4)

On 11 January 2017 at 22:05, Stefan Sperling wrote: > > You haven't updated all of src/sys. I'm obviously being really dumb, but what is wrong with cd /usr tar zxf sys.tar.gz (from 6.0) cvs -qd anon...@anoncvs.au.openbsd.org:/cvs update -dP sys cd sys patch -p0 <

Re: 11n support for athn(4)

On 9 January 2017 at 23:27, Stefan Sperling wrote: > On Mon, Jan 09, 2017 at 01:54:55PM +0100, Stefan Sperling wrote: >> This diff adds 11n support to the athn(4) driver. >> Requires -current net80211 code from today. > > A better diff which fixes several bugs. > I'm getting

Re: Support power saving with athn(4) in host AP mode

It's working reasonably well here, but there's glitches with Android devices. After a while they either say the AP is 'out of range' or 'saved' with the non functional option to connect. That's with both an Androided ICS HP Touchpad and a Sony Ericcson Xperia Pro with latest official ICS. Sadly

Re: Source Overview

From: Bret S. Lambert blamb...@openbsd.org Or, in short, we need to not deter people straight away, and accept that perhaps sometimes decent programmers start from ones that make lots of mistakes. Perhaps a ports TODO similar to the NetBSD ports TODO might help; it doesn't require quite the