On 2019/04/15 21:45, Matthieu Herrb wrote:
> Hi,
>
> the diff below updates pixman to 0.38.4.
>
> Since upstream is too lazy to provide a ChangeLog, here are the main
> changes from 0.36, picked up from their git log:
>
> - Implement floating point gradient computation,
> - Use maximum
Hi,
the diff below updates pixman to 0.38.4.
Since upstream is too lazy to provide a ChangeLog, here are the main
changes from 0.36, picked up from their git log:
- Implement floating point gradient computation,
- Use maximum precision for pixman-bits-image
As always with pixman, the shared
On Mon, Apr 15, 2019 at 09:03:54PM +0200, Hiltjo Posthuma wrote:
> Hi,
>
> I noticed in the default config file /etc/X11/xenodm/Xresources
> there is a rule:
>
> xlogin*login.translations: #override \
> CtrlR: abort-display()\n\
> [...]
>
> The xenodm(1) man page says:
> "
>
Hi,
I noticed in the default config file /etc/X11/xenodm/Xresources
there is a rule:
xlogin*login.translations: #override \
CtrlR: abort-display()\n\
[...]
The xenodm(1) man page says:
"
abort-display
Terminates the server, disabling it. This action is not
Your deletion is highly excessive.
Hiltjo Posthuma wrote:
> Hi,
>
> I noticed the man page hostname(7) still references the environment variable
> HOSTALIASES. This functionality seems to be removed in the commit:
>
>
Hi,
I noticed the man page hostname(7) still references the environment variable
HOSTALIASES. This functionality seems to be removed in the commit:
https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/lib/libc/asr/asr.c?rev=1.50=text/x-cvsweb-markup
Below is a patch to change it in the man page. I'm
On Mon, Apr 15 2019 16:56:52 +0200, Stefan Sperling wrote:
> The ifconfig mode command is broken; It is supposed to force a wireless
> interface into 11a/b/g/n media mode. This stopped working some time ago,
> probably during my work on background scanning. Problem spotted by mlarkin@
> who
The ifconfig mode command is broken; It is supposed to force a wireless
interface into 11a/b/g/n media mode. This stopped working some time ago,
probably during my work on background scanning. Problem spotted by mlarkin@
who noticed that interfaces were using 11g mode while forced to 11b mode.
ieee80211_media_change() will return ENETRESET if the interface is
switched into 11a/b/g/n mode from any other mode.
ifmedia_ioctl() considers this an error and reverts ifmedia's state
to the previous setting, even though net80211 has actually succeeded.
The result is that if_media and net80211
Two fixes for code within #ifdef IFMEDIA_DEBUG:
1) Print the 'mode' part of the media word.
2) Only print media options which are set in the media word, rather
than printing all available options.
diff 23a4e4a1e8913390694e35727d2131b2938cb472 /usr/src
blob -
On 2019/04/15 08:16, David Gwynne wrote:
> > # ifconfig vlan0 | grep encap
> > encap: vnetid none parent none txprio packet
> >
> >
> > Shouldn't there be completely interoperability? If so, that seems like
> > one more reason for removing the old interface, with or without
Hi,
with kettenis' change from 2015(?) we can configure a ppb(4)'s bus
information. Unfortunately the hotplug fixup code runs before that
change has a chance, and it will program a single bus (with no amount
of children) below it. I think that part of the hotplug fixup can go
away.
The hotplug
Hi,
with kettenis' change from 2015(?) we are able to configure ppb(4)'s
that are hotplugged. I think on detach we should make sure to free the
bus range that was allocated for that device dynamically. Otherwise
plug and pull can starve the extent.
Feedback?
Patrick
diff --git
13 matches
Mail list logo
