Re: Mesa 11.0.8 update

On Mon, Dec 21, 2015 at 11:10:28PM +1100, Jonathan Gray wrote: > Here is a patch to update the version of Mesa in xenocara from 11.0.6 > to a newer version of the 11.0 stable branch 11.0.8 > > 11.0.7 notes http://www.mesa3d.org/relnotes/11.0.7.html > 11.0.8 announcement >

Re: initial 11n support for iwn (n, not m)

Works without issues on my Dell Studio 1555 since a day now. $ ifconfig iwn0 | grep media media: IEEE802.11 autoselect (HT-MCS7 mode 11n) $ dmesg | grep iwn iwn0 at pci2 dev 0 function 0 "Intel WiFi Link 5300" rev 0x00: msi, MIMO 3T3R, MoW, address 00:21:6a:56:2b:36 $ sysctl hw.product

Re: SQLite 3.9.2 update

On Sat, Dec 19, 2015 at 08:43:38AM +0100, Landry Breuil wrote: > On Mon, Dec 14, 2015 at 08:51:47PM +0100, Landry Breuil wrote: > > On Mon, Dec 14, 2015 at 01:09:38PM -0500, James Turner wrote: > > > SQLite 3.9.2 updated. Tested on amd64. I've included the json extension > > > but haven't enabled

Re: "Adding" the same IPv6 address twice

On 12/21/15 11:36, Martin Pieuchot wrote: > Currently if you try to configure the same IPv6 address twice via the > SIOCAIFADDR_IN6 ioctl(2) the kernel will return EEXIST and the address > will be unset: > > # ifconfig vether0 inet6 2001::1 > # ifconfig vether0 inet6 2001::1 > ifconfig:

Re: asmc(4) improvements

On Mon, Dec 21, 2015 at 10:38:24PM +0100, Mark Kettenis wrote: > However, since Apple's SMC implementation almost certainly changed > over the years, it would be good to test this diff on a wider range of > Apple hardware. Please check that all sensors are still present and > are properly updated

vlan(4): better checks for valid vlan ids

the spec says vlan 0 and vlan 4095 are reserved, so we probably shouldnt use them. this tweaks the vlan tag check only allow valid ids per the spec. ok? Index: if_vlan.c === RCS file: /cvs/src/sys/net/if_vlan.c,v retrieving

asmc(4) improvements

The asmc(4) driver is a bit slow. On my MacBookPro12,1 it takes a couple of minutes to probe all the sensors. And changing the keyboard backlight takes a couple of seconds. This is especially annoying when you're writing a diff to bind that functionality to the keys reserved for this purpose on

Re: Mesa 11.0.8 update

On 12/21/15 18:15, Matthieu Herrb wrote: > On Mon, Dec 21, 2015 at 11:10:28PM +1100, Jonathan Gray wrote: >> Here is a patch to update the version of Mesa in xenocara from 11.0.6 >> to a newer version of the 11.0 stable branch 11.0.8 >> >> 11.0.7 notes http://www.mesa3d.org/relnotes/11.0.7.html >>

ipmi(4) - Remove unused code

This is the first part of the big ipmi(4) patch I sent in another thread. This removes complicate polling timeout code. Serial communication with BMC is slow but considered as reliable. Communication failure is a fatal problem. Returning error doesn't make sense. This also removes unfinished

ipmi(4) - Don't check threshold erroneously

ipmi(4) has checked thresholds of some sensing values and reported false alarms. This patch reverts those checks. This also changes ipmi(4) to handle disabled sensors while allowing them to supply readings if they want. >From Jonathan Matthew. OK? diff --git a/sys/dev/ipmi.c b/sys/dev/ipmi.c

ipmi(4) - Stop watchdog internal timer properly

When stopiing ipmi(4) watchdog, not only set action to disabled but also stop internal timer (clear don't stop flag). Without this our NEC servers fail to stop IPMI watchdog and reset during shutdown process. OK? diff --git a/sys/dev/ipmi.c b/sys/dev/ipmi.c index 91aa147..d88b7c1 100644 ---

uftdi: Attach Telldus TellStick Duo

Hello, I recently aquired a Telldus Tellstick Duo (http://www.telldus.se/products/tellstick_duo). It differs from the classic Tellstick in that it is both a transmitter and a receiver. The hardware: === # usbdevs -v [...] port 1 addr 2: full speed, power 90 mA, config 1, TellStick Duo(0x0c31),

Re: ipmi(4) - Remove unused code

> Date: Mon, 21 Dec 2015 22:31:22 +0900 > From: Masao Uebayashi > > This is the first part of the big ipmi(4) patch I sent in another thread. > > This removes complicate polling timeout code. Serial communication > with BMC is slow but considered as reliable.

Re: Thinkpad display brightness control

Please disregard my message below, sorry for the noise. The facts are wrong, I'm still having those plug/unplug brightness jumps. (no idea what coincidence took place yesterday.) Sorry, Marcus mcmer-open...@tor.at (Marcus MERIGHI), 2015.12.20 (Sun) 16:04 (CET): > I am somewhat confused; there

Re: asmc(4) improvements

> However, since Apple's SMC implementation almost certainly changed > over the years, it would be good to test this diff on a wider range of > Apple hardware. Please check that all sensors are still present and > are properly updated after applying this diff. Seems to be a significant

Re: asmc(4) improvements

On Tue, Dec 22, 2015 at 08:30:15AM +0100, Theo Buehler wrote: > Responsiveness of keyboard.backlight adjustment is now immediate > rather than delayed by about one second. I didn't test keyboard.backlight adjustment responsiveness initially on the MacBookAir7,2 but, as you said as well, it is

Re: initial 11n support for iwn (n, not m)

s...@stsp.name (Stefan Sperling), 2015.12.20 (Sun) 19:59 (CET): > On Sat, Dec 19, 2015 at 01:08:26PM +0100, Stefan Sperling wrote: > > On Fri, Dec 18, 2015 at 05:40:39PM -0500, David Hill wrote: > > > With sthen@'s patch I can associate, dhcp, and use net. > > > > Here's an updated iwn diff with

Re: initial 11n support for iwn (n, not m)

Hi Stefan, On Sun, Dec 20, 2015 at 07:59:19PM +0100, Stefan Sperling wrote: > On Sat, Dec 19, 2015 at 01:08:26PM +0100, Stefan Sperling wrote: > > On Fri, Dec 18, 2015 at 05:40:39PM -0500, David Hill wrote: > > > With sthen@'s patch I can associate, dhcp, and use net. > > > > Here's an updated

Re: [patch] nlist(3): out of bounds read

Ping? This is the same sanity check that's done in nm(1)'s ELF handling. On Thu, Dec 10, 2015 at 09:40:11AM -0800, Serguey Parkhomovsky wrote: > When dealing with a malformed ELF header, e_shentsize may be 0. This > causes an out of bounds read while finding the symbol table on line 141. > >

Re: [patch] mailwrapper(8): remove unneeded argument in addarg

Ping? On Mon, Dec 14, 2015 at 09:24:21AM -0800, Serguey Parkhomovsky wrote: > This patch removes the copy argument to addarg, which is unneeded. No > functional change. > > Index: mailwrapper.c > === > RCS file:

Re: ipmi(4) - Remove unused code

> > diff --git a/sys/dev/ipmi.c b/sys/dev/ipmi.c > > index a1156d8..91aa147 100644 > > --- a/sys/dev/ipmi.c > > +++ b/sys/dev/ipmi.c > > @@ -1082,11 +1017,7 @@ void > > ipmi_delay(struct ipmi_softc *sc, int period) > > { > > /* period is in 10 ms increments */ > > - if (cold ||

Re: ipmi(4) - Don't check threshold erroneously

> Date: Mon, 21 Dec 2015 22:47:19 +0900 > From: Masao Uebayashi > > ipmi(4) has checked thresholds of some sensing values and reported false > alarms. This patch reverts those checks. > > This also changes ipmi(4) to handle disabled sensors while allowing them to >

Re: ipmi(4) - Stop watchdog internal timer properly

> Date: Mon, 21 Dec 2015 22:43:46 +0900 > From: Masao Uebayashi > > When stopiing ipmi(4) watchdog, not only set action to disabled but also stop > internal timer (clear don't stop flag). Without this our NEC servers fail > to stop IPMI watchdog and reset during shutdown

Re: uftdi: Attach Telldus TellStick Duo

On 2015/12/21 14:12, Patrik Lundin wrote: > Hello, > > I recently aquired a Telldus Tellstick Duo > (http://www.telldus.se/products/tellstick_duo). It differs from the > classic Tellstick in that it is both a transmitter and a receiver. > > The hardware: > === > # usbdevs -v > [...] > port 1

hashfree, a counterpart to hashinit

Hello list, Another day another set of sizes for free(9). This time it's around the hashinit function. I introduce a hashfree counterpart to hide the details. Most of the api users are converted in the patch below, those not included just simply do not free the memory (pid hash table etc). All,

Re: uftdi: Attach Telldus TellStick Duo

On Mon, Dec 21, 2015 at 02:12:41PM +0100, Patrik Lundin wrote: > > Currently it is only attached as an ugen device: > === > ugen0 at uhub1 port 2 "Telldus TellStick Duo" rev 2.00/6.00 addr 2 > === > > The diff below makes it attach as an uftdi device: > === > uftdi0 at uhub2 port 1 configuration

Re: uftdi: Attach Telldus TellStick Duo

On Mon, Dec 21, 2015 at 05:40:14PM +0100, Patrik Lundin wrote: > > This was pretty discouraging: it appears the supported program works > better when the kernel knows less about the device. It uses libftdi, > which I guess is supposed to contact the generic device directly. > > Any input on how