> 2/ Split the i386 atomic_ucas_32 into two, one that's pcb aware and one
> that's not. And use the pcb aware one for the futex and the other one
> for the acpi locking. And of course the amd64 function in the diff
> bellow will match the non-pcb one from i386.
With the convention that the 'u' in
On Fri, Sep 21, 2012 at 12:15:51PM +0200, Mark Kettenis wrote:
> > Date: Wed, 19 Sep 2012 15:41:09 +0300
> > From: Paul Irofti
> >
> > I need this for acpi locking, okay?
> >
> > (I'd also like to get rid of the silly x86_* prefix to match the i386
> > function name, but that's a different topic
On sze, nov 14, 2012 at 13:44:30 +0100, Mark Kettenis wrote:
> Anybody around with the (currently non-working) Intel WiFi Link 1030
> wireless hardware that can test the following diff? You'll need an
> up-to-date firmware pckage and a bleeding edge -current tree.
[...]
===> ifconfig error when t
On Fri, Nov 16, 2012 at 06:16:12PM +, sbienddr...@googlemail.com wrote:
> Hi Mike,
>
> run0 is a external edimax usb device. Page fault occurs when
> netstart/dhclient is being processed. Boot up without this network
> device installed, insert device and manually sh /etc/netstart throws out
Christian Weisgerber wrote:
> Currently this is only implemented for IPv4. The diff below adds
> the missing pieces for IPv6, so that we will later be able to profit
> from checksum offload over IPv6.
Nobody? Nothing?
> Works for me for basic TCP/UDP use over IPv6.
> bridge(4) and pf(4) are c
