On Sun, Mar 27, 2016 at 12:28 PM, Mark Kettenis wrote:
> The diff below is a first stab at adding support for GPIOs as defined
> in ACPI 5.0. The primary target for this new ACPI feature is hardware
> reduced platforms like those based on Intel's Bay Trail SoC. The diff
Hi,
There was some discussion last year[1] regarding abuse of Aq macros
in mdoc where plain characters or other macros (eg, "In") would be
more appropriate. Here are some additional places where I believe
replacing Aq would make sense.
Notes:
- spamd-setup(8) is referring to pf tables.
On Sun, 27 Mar 2016 22:47:38 +0200, Matthieu Herrb wrote:
> OpenBSD has stopped using the SVr4 KDENABIO/KDDISABIO ioctls for at
> least 10 years. No need for special treatement on i386.
OK millert@
- todd
There is a fallout from the switch to binutils 2.17: the binaries
created by 2.17 aren't recognized by the in-tree gdb because it's built
with the bfd code from 2.15.
My understanding is that the in-tree gdb can't be made to run with bfd
from 2.17 without significant non-trivial changes, so I'd
> It seems per-page reference counting is used since forever. I think
> there's no reason to ever turn it off (and track referenced pages
> with less accuracy, causing leaks).
Actually, assuming the #undef code path works, it might work keeping
this and only defining UVM_AMAP_PPREF iff
On Thu, Mar 24, 2016 at 12:09:39PM +, Edd Barrett wrote:
> On Wed, Mar 23, 2016 at 09:35:50PM +0100, Mark Kettenis wrote:
> > So here is a diff that keeps yield() the same and adds the code in the
> > sched_yield(2) implementation instead.
>
> I'm going to now run with this diff for a while.
Hi,
OpenBSD has stopped using the SVr4 KDENABIO/KDDISABIO ioctls for at
least 10 years. No need for special treatement on i386.
ok?
Index: wsdisplay_compat_usl.c
===
RCS file:
Michael McConville wrote:
> Clang 3.7 gives this warning when building the kernel:
>
> > ../../../../dev/audio.c:1852:1: warning: stack frame size of 2504 bytes in
> > function 'wskbd_initvol' [-Wframe-larger-than=]
> > wskbd_initvol(struct audio_softc *sc, struct wskbd_vol *vol, char *cn, char
Not sure how much I can test here, but my tunnels are up.
As well as my bgp sessions (this is "ART box” now) on top.
I use aes-128-gcm.
This is vmware.
//mxb
> On 26 mars 2016, at 16:25, Mike Belopuhov wrote:
>
> On Fri, Mar 25, 2016 at 22:43 +0100, Mark Kettenis wrote:
Clang 3.7 gives this warning when building the kernel:
> ../../../../dev/audio.c:1852:1: warning: stack frame size of 2504 bytes in
> function 'wskbd_initvol' [-Wframe-larger-than=]
> wskbd_initvol(struct audio_softc *sc, struct wskbd_vol *vol, char *cn, char
> *dn)
> ^
-Wframe-larger-than was
I'm trying to install OpenBSD on a Supermicro X11SSL-F board (which has
an Intel C232 chipset, the kernel wedges after displaying:
xhci0 at pci0 dev 20 function 0 "Intel 100 Series xHCI" rev 0x31: msi
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 "Intel xHCI root hub" rev 3.00/1.00 addr 1
I
The diff below is a first stab at adding support for GPIOs as defined
in ACPI 5.0. The primary target for this new ACPI feature is hardware
reduced platforms like those based on Intel's Bay Trail SoC. The diff
adds a bytgpio(4) driver for the hardware found on that SoC. This
driver registers
On 07/03/16(Mon) 12:46, Martin Pieuchot wrote:
> bread_cluster() can be called unconditionally. The sequential check is
> a leftover of the read-ahead mechanism that FFS no longer used since the
> introduction of the Dynamic Buffer cache.
>
> ok?
Anyone?
>
> Index: ufs/ffs/ffs_vnops.c
>
On Sat, Mar 26, 2016 at 10:37:08PM +0100, Martin Pieuchot wrote:
> On 25/03/16(Fri) 13:23, Ulf Brosziewski wrote:
> > Again, my mail client insisted on the "flowed" text format,
> > sorry. Here is a clean version of the diff.
>
> Tested with:
>
> pms0: Synaptics clickpad, firmware 8.0
>
>
Hi,
I noticed that multiple functions from OpenBGPd declared an argument "u_int16_t
neighas" that is never used.
Here is a patch to remove it.
Denis
Index: parse.y
===
RCS file: /cvs/src/usr.sbin/bgpd/parse.y,v
retrieving revision
On Sun, 27 Mar 2016 16:20:18 +0100, Stuart Henderson wrote:
> /etc/netstart has a "route -qn delete 224.0.0.0/4" before it adds
> the multicast reject route:
>
> 270 # Multicast routing.
> 271 route -qn delete 224.0.0.0/4 >/dev/null 2>&1
> 272 [[ $multicast != YES ]] &&
> 273 route -qn
On 27/03/16(Sun) 16:20, Stuart Henderson wrote:
> Noticed while looking at the minidlna problem with ART, but this is
> not responsible for the problem.
>
> /etc/netstart has a "route -qn delete 224.0.0.0/4" before it adds
> the multicast reject route:
>
> 270 # Multicast routing.
> 271 route
Noticed while looking at the minidlna problem with ART, but this is
not responsible for the problem.
/etc/netstart has a "route -qn delete 224.0.0.0/4" before it adds
the multicast reject route:
270 # Multicast routing.
271 route -qn delete 224.0.0.0/4 >/dev/null 2>&1
272 [[ $multicast != YES ]]
On 2016/03/27 12:28, Martin Pieuchot wrote:
> On 26/03/16(Sat) 23:25, Stuart Henderson wrote:
> > On 2016/03/26 23:21, Stuart Henderson wrote:
> > > Sorry I don't have a simple test method,
> >
> > oh, there are some example programs in p5-IO-Socket-Multicast (in
> >
On 2016/03/27 14:32, Mark Kettenis wrote:
> > From: attila
> > Date: Sat, 26 Mar 2016 17:47:38 -0600
> >
> > Jyri Hovila [Turvamies.fi] writes:
> >
> > > I can report significant usability improvement on a single core
> > > ThinkPad T42 and a
Diff below changes when QH are added and removed to/from the async list.
It allows to cancel a transfer by simply unlinking its QH.
This should be enough to prevent the race in ehci_abort_xfer() resulting
in the infamous ehci_device_clear_toggle() panic.
I'd appreciate if people could test this
> Date: Sat, 26 Mar 2016 23:02:52 +0100
> From: Martin Pieuchot
>
> On 26/03/16(Sat) 19:19, Stefan Kempf wrote:
> > Stefan Kempf wrote:
> > > amap_extend is called when merging two adjacent areas of virtual address
> > > space. However, merging is done only for kernel
> > >
On 27/03/16(Sun) 14:42, Mark Kettenis wrote:
> > Date: Sun, 27 Mar 2016 12:00:04 +0200
> > From: Martin Pieuchot
> >
> > Diff below moves resetpriority() out of updatepri() and resched_proc()
> > out of resetpriority() in order to expose a double resched_proc() call
> > in
> Date: Sun, 27 Mar 2016 12:00:04 +0200
> From: Martin Pieuchot
>
> Diff below moves resetpriority() out of updatepri() and resched_proc()
> out of resetpriority() in order to expose a double resched_proc() call
> in setrunnable().
>
> This happens when a thread has slept for
> From: attila
> Date: Sat, 26 Mar 2016 17:47:38 -0600
>
> Jyri Hovila [Turvamies.fi] writes:
>
> > I can report significant usability improvement on a single core
> > ThinkPad T42 and a dual core ThinkPad X60.
>
> I hate to crap on this
It seems per-page reference counting is used since forever. I think
there's no reason to ever turn it off (and track referenced pages
with less accuracy, causing leaks).
So remove those #ifdefs.
ok?
Index: uvm/uvm_amap.c
===
RCS
On 26/03/16(Sat) 23:25, Stuart Henderson wrote:
> On 2016/03/26 23:21, Stuart Henderson wrote:
> > Sorry I don't have a simple test method,
>
> oh, there are some example programs in p5-IO-Socket-Multicast (in
> /usr/local/share/examples/p5-IO-Socket-Multicast), can't
Diff below moves resetpriority() out of updatepri() and resched_proc()
out of resetpriority() in order to expose a double resched_proc() call
in setrunnable().
This happens when a thread has slept for more than 1 second. Since
p_usrpri is equal or bigger than p_priority, if the first call
27 марта 2016 г. 11:05 пользователь "Stefan Sperling"
написал:
>
> On Sat, Mar 26, 2016 at 05:47:38PM -0600, attila wrote:
> > Now it will be a challenge to see if I can cvs up, back out the patch
> > and build a kernel without ringing the bell (100DegC). I freely admit
> > this
On Sat, Mar 26, 2016 at 05:47:38PM -0600, attila wrote:
>
> Now it will be a challenge to see if I can cvs up, back out the patch
> and build a kernel without ringing the bell (100DegC).
boot obsd ?
--
Matthieu Herrb
signature.asc
Description: PGP signature
On Sat, Mar 26, 2016 at 05:47:38PM -0600, attila wrote:
> Now it will be a challenge to see if I can cvs up, back out the patch
> and build a kernel without ringing the bell (100DegC). I freely admit
> this is an old, P.O.S. laptop and that there might be some HW issue
Did you check for dust in
Martin Pieuchot wrote:
> On 26/03/16(Sat) 19:19, Stefan Kempf wrote:
> > Stefan Kempf wrote:
> > > amap_extend is called when merging two adjacent areas of virtual address
> > > space. However, merging is done only for kernel
> > > virtual address space. It's not done for user space:
> > >
> > >
32 matches
Mail list logo