Hi,
has anyone looked at the netbsd xscale-versions of bcopyin/bcopyout/kcopy?
this is from netbsd bcopyinout.S:
#if defined(__XSCALE__) || defined(_ARM_ARCH_6)
/*
* armv6 and v7 have pld and strd so they can use the xscale
* bcopyinout as well.
*/
#include "bcopyinout_xscale.S"
#else
Improved version, with thanks to anton@
[Should usage() be __dead?]
Ross
Index: pf.4
===
RCS file: /cvs/src/share/man/man4/pf.4,v
retrieving revision 1.88
diff -u -p -r1.88 pf.4
--- pf.429 Aug 2017 02:16:56 - 1.88
This patch adapts the Elantech handlers in pms to the new touchpad
infrastructure of wsmouse. The changes concern models that use the older
protocol versions 1, 2, and 3. You don't find that hardware at the next
corner nowadays, so if you have a laptop with one of those models, your
help would
On Sun, Oct 08, 2017 at 09:22:46AM -0500, joshua stein wrote:
> This adds support for Hybrid mode for Windows Precision Touchpads
> (ihidev/imt). If yours only works with one finger, this should fix
> that.
>
> This also changes the way SET_REPORTs are sent to put the touchpad
> into touchpad
On Oct 08 11:31:16, o...@drijf.net wrote:
> On Fri, Oct 06, 2017 at 02:12:01PM +0200, Jan Stary wrote:
>
> > Isn't "4 * a(1)" a more natural incarnation of pi than "2 * a(2^1)"?
>
> The point of this example is to (also) show that a() works on very
> large numbers.
My itch is that 4 * a(1)
On Sun, Oct 08, 2017 at 05:27:09PM +0200, Sebastian Benoit wrote:
> Robert Peichaer(rob...@peichaer.org) on 2017.10.08 09:56:15 +:
> > Up to now, the upgrade procedure from one to the next release meant
> > that you had to manually download and verify the new ramdisk kernel.
> >
> > What
This patch adds the wsmouse_configure call to iatp. I haven't
seen it running, so it would be nice if someone could confirm that
the change doesn't introduce regressions, and check whether it
works with both synaptics(4) and ws(4).
Index: iatp.c
The sdmmc stack provides DMA buffers for data transfers nowadays.
This was not the case yet when rtsx(4) was written so this driver
is still using a lame memcpy bounce-buffer approach.
With this diff regular data transfers go through a DMA-only code path.
The memcpy path is still needed to
> Robert Peichaer(rob...@peichaer.org) on 2017.10.08 09:56:15 +:
> > Up to now, the upgrade procedure from one to the next release meant
> > that you had to manually download and verify the new ramdisk kernel.
> >
> > What about if you just needed to boot into the existing bsd.rd and
> > it
Robert Peichaer(rob...@peichaer.org) on 2017.10.08 09:56:15 +:
> Up to now, the upgrade procedure from one to the next release meant
> that you had to manually download and verify the new ramdisk kernel.
>
> What about if you just needed to boot into the existing bsd.rd and
> it would support
On Fri, Oct 06, 2017 at 02:27:33PM +0200, Jan Stary wrote:
> Currently, the bc(1) manpage describes "-l" as
>
> Allow specification of an arbitrary precision math library
>
> I am not a native speaker, but "specification of a library"
> seems unclear here. It loads
This adds support for Hybrid mode for Windows Precision Touchpads
(ihidev/imt). If yours only works with one finger, this should fix
that.
This also changes the way SET_REPORTs are sent to put the touchpad
into touchpad mode, now as two bytes. This is needed on the
touchpad on my Huawei and
Just trying to make things a little more standard.
Ross
Index: pf.4
===
RCS file: /cvs/src/share/man/man4/pf.4,v
retrieving revision 1.88
diff -u -p -r1.88 pf.4
--- pf.429 Aug 2017 02:16:56 - 1.88
+++ pf.48
> I wrote some patches to allow pledging across execs.
> Currently, the exec pledge passes down the process tree.
>
> The initial version simply inherited the current pledge when
> execing with the `pledge("rexec")` promise, but after
> discussing with Theo at EuroBSD, a better design was
>
On Sun, Oct 08, 2017 at 02:43:48AM -0700, Ori Bernstein wrote:
> And pax, because I can
>
>
>
>
> diff --git bin/pax/ar_io.c bin/pax/ar_io.c
> index 40a6492405e..ce53a9ae51b 100644
> --- bin/pax/ar_io.c
> +++ bin/pax/ar_io.c
> @@ -1281,6 +1281,11 @@ ar_start_gzip(int fd, const char
> Up to now, the upgrade procedure from one to the next release meant
> that you had to manually download and verify the new ramdisk kernel.
Well you already could follow that procedure. That's what I've been
doing. The risk is that it also updates your bsd kernels, not just
bsd.rd in case you
Just move the assignment up a bit.
diff --git usr.bin/awk/main.c usr.bin/awk/main.c
index 82996bc6f71..ebff17d240a 100644
--- usr.bin/awk/main.c
+++ usr.bin/awk/main.c
@@ -64,13 +64,13 @@ int main(int argc, char *argv[])
setlocale(LC_ALL, "");
setlocale(LC_NUMERIC,
Up to now, the upgrade procedure from one to the next release meant
that you had to manually download and verify the new ramdisk kernel.
What about if you just needed to boot into the existing bsd.rd and
it would support downloading and verifying the bsd.rd of the next
release?
This diff changes
And pax, because I can
diff --git bin/pax/ar_io.c bin/pax/ar_io.c
index 40a6492405e..ce53a9ae51b 100644
--- bin/pax/ar_io.c
+++ bin/pax/ar_io.c
@@ -1281,6 +1281,11 @@ ar_start_gzip(int fd, const char *path, int wr)
/* System compressors are more likely to use
Slowcgi. Because if someone could fool it into
running the wrong binary, the outcome may be
suboptimal.
diff --git usr.sbin/slowcgi/slowcgi.8 usr.sbin/slowcgi/slowcgi.8
index d3ab4030bed..f8f07630204 100644
--- usr.sbin/slowcgi/slowcgi.8
+++ usr.sbin/slowcgi/slowcgi.8
@@ -24,6
This is my pledge(1). There are many like it, but this one is mine.
When directory pledges land, this should also get support for them.
Usage example:
pledge stdio echo hello world
More complicated, with enough pledges to run awk:
pledge "stdio rpath wpath cpath proc exec
I wrote some patches to allow pledging across execs.
Currently, the exec pledge passes down the process tree.
The initial version simply inherited the current pledge when
execing with the `pledge("rexec")` promise, but after
discussing with Theo at EuroBSD, a better design was
suggested. Because
On Fri, Oct 06, 2017 at 02:12:01PM +0200, Jan Stary wrote:
> Isn't "4 * a(1)" a more natural incarnation of pi than "2 * a(2^1)"?
The point of this example is to (also) show that a() works on very
large numbers.
-Otto
>
> Jan
>
>
> Index: bc.1
>
23 matches
Mail list logo
