Re: [diff] lpbl(4): driver for TI LP8550 backlight controller (found in e.g. MacBook Air 6,2)

2016-01-11 Thread Sviatoslav Chagaev
On Sun, 10 Jan 2016 21:28:31 +0100 Joerg Jung wrote: > On Sun, Jan 10, 2016 at 04:59:22AM +0200, Sviatoslav Chagaev wrote: > > Hi, > > > > I'm running -current on Apple MacBook Air 6,2. I installed using Jasper's > > instructions [1], OpenBSD is the only OS and boots via EFI. > >

Re: Clustering read for MSDOSFS

2016-01-11 Thread Mathieu -
Martin Pieuchot wrote: > On 03/01/16(Sun) 23:10, Martin Pieuchot wrote: > > Reading files on msdos-formated USB sticks under OpenBSD is really slow. > > *One* of the reasons is that only one block is currently read-ahead if > > possible. > > > > Diff below converts msdosfs_read() to use

Re: ffs: cluster_write() is a joke

2016-01-11 Thread Mathieu -
David Gwynne wrote: > On Thu, Jan 07, 2016 at 05:56:17PM +0100, Martin Pieuchot wrote: > > I spent some time trying to implement clustering writes for MSDOSFS > > before I could figure out that our cluster_write() functions is not > > doing anything but delaying the calls do bawrite(). Awesome! >

Re: remove net80211 turbo mode

2016-01-11 Thread Stefan Sperling
On Mon, Jan 11, 2016 at 11:11:08AM +0100, Mark Kettenis wrote: > Agreed. I don't have any working ath(4) hardware to test this. This > diff introduces some long (>80 characters) lines; you might want to > fix that before you commit it. Sure, I will fix the long lines. I'm building a release

remove net80211 turbo mode

2016-01-11 Thread Stefan Sperling
This diff removes turbo mode, which is a proprietary extension offered by Atheros devices of the ath(4) 11a/b/g generation. This seems to be a channel bonding technique, similar to 11n 40 MHz channels but not interoperable with 11n. I'd like to remove this because the implementation looks

Re: remove net80211 turbo mode

2016-01-11 Thread Stuart Henderson
On 2016/01/11 11:11, Mark Kettenis wrote: > > Date: Mon, 11 Jan 2016 10:30:27 +0100 > > From: Stefan Sperling > > > > This diff removes turbo mode, which is a proprietary extension offered > > by Atheros devices of the ath(4) 11a/b/g generation. This seems to be > > a channel

Let ipsecctl auto-generate isakmpd.policy from ipsec.conf

2016-01-11 Thread Julian Hsiao
Hi, I recently ran into a rather surprising issue with using ipsecctl / ipsec.conf, where evidently phase 2 parameters from the remote side were accepted unconditionally. Here's my post in misc@ I'd for a little more context: The thing

Re: remove net80211 turbo mode

2016-01-11 Thread Mark Kettenis
> Date: Mon, 11 Jan 2016 10:30:27 +0100 > From: Stefan Sperling > > This diff removes turbo mode, which is a proprietary extension offered > by Atheros devices of the ath(4) 11a/b/g generation. This seems to be > a channel bonding technique, similar to 11n 40 MHz channels but not

Re: wsevent.c uiomove() conversion

2016-01-11 Thread Stefan Kempf
Martin Natano wrote: > Below the uiomove() conversion for dev/wscons/wsevent.c. 'cnt' could > as well be a size_t, but using u_int makes clear, that it will never > exceed UINT_MAX, and that 'ev->get = cnt;' won't overflow. Makes sense to me. ok? > Index: dev/wscons/wsevent.c >

Re: UTF-8 support for colrm(1)

2016-01-11 Thread Steffen Nurpmeso
Stephane Chazelas wrote: |2016-01-11 16:10:28 +0100, Steffen Nurpmeso: |[...] |> And your diff includes |> |> +.Pp |> +For compatibility with |> +.St -p1003.1-2008 |> +.Xr fold 1 , |> +if a double-width character is followed by two backspace

Re: UTF-8 support for colrm(1)

2016-01-11 Thread Stephane Chazelas
2016-01-11 16:10:28 +0100, Steffen Nurpmeso: [...] > And your diff includes > > +.Pp > +For compatibility with > +.St -p1003.1-2008 > +.Xr fold 1 , > +if a double-width character is followed by two backspace characters > +instead of the usual one, both are regarded as belonging to

Re: remove net80211 turbo mode

2016-01-11 Thread Chris Cappuccio
Stuart Henderson [st...@openbsd.org] wrote: > > +1, I wondered if we should do this when reading the 11n diffs. > > If people need more speed it's likely that they will get better > performance with 20MHz channels on a newer radio/MAC than 40MHz > on a 10-year-old one. > > Free the spectrum!

Re: ext2fs: Kill unused cluster_write()

2016-01-11 Thread Martin Pieuchot
On 07/01/16(Thu) 17:51, Martin Pieuchot wrote: > Since the introduction of the Dynamic Buffer Cache, cluster_write() is a > noop. Since here it has never been enable, let's kill this code. That's an easy one, any ok? > Index: ufs/ext2fs/ext2fs_readwrite.c >

Re: Clustering read for MSDOSFS

2016-01-11 Thread Martin Pieuchot
On 11/01/16(Mon) 10:44, Mathieu - wrote: > Martin Pieuchot wrote: > > On 03/01/16(Sun) 23:10, Martin Pieuchot wrote: > > > Reading files on msdos-formated USB sticks under OpenBSD is really slow. > > > *One* of the reasons is that only one block is currently read-ahead if > > > possible. > > > >

Re: Use of bread_cluster() in ffs_read()

2016-01-11 Thread Martin Pieuchot
On 03/01/16(Sun) 23:16, Martin Pieuchot wrote: > I don't understand why the check for reading ahead one block has been > kept for clustering read when the Dynamic buffer cache got introduced. > > Since bread_cluster() replaces cluster_read() I believe this can go > away. Any ok? > Index:

Re: UTF-8 support for colrm(1)

2016-01-11 Thread Stephane Chazelas
2016-01-11 15:50:55 +, Stephane Chazelas: [...] > $ printf '|\uFF21\b\b|\n' > || > $ printf '|\uFF21\b|\n' > | | > > in both xterm and gnome-terminal. As in, you need two backspace > characters to delete that character. With only one, the cursor > moves back one column, and if you write

[PATCH] uname, arch/machine -> %c, %a update in PKG_PATH

2016-01-11 Thread Raf Czlonka
Hi all, Given that PKG_PATH and pkg.conf(5)'s installpath, now supports %c, %a, etc. sequences, it might be worth advertising it a bit more by changing all relevant uname(1), arch(1)/machine(1) occurrences or (hard-coded release versions or hardware architectures for that matter) in the

Re: UTF-8 support for colrm(1)

2016-01-11 Thread Steffen Nurpmeso
Hallo Ingo, i CC: the POSIX list since that is an interesting conclusion of yours! Ingo Schwarze wrote: |Ingo Schwarze wrote on Wed, Dec 23, 2015 at 07:44:05PM +0100: |>>> For example, colrm(1). |> So, remember this rule: |> |>