Yesterday's comments about setjmp caused me to dig more deeply into the
function today. Here are several fixes. There is still one possibly
outstanding issue with fpsr. When reading thru the calling convention
it seemed to indicate that the rounding mode was not to be assumed.
(Document is
http://
On Thu, Mar 09, 2017 at 10:38:20PM +0100, Mark Kettenis wrote:
> For some reason u-boot on the exynos platform decides to split up the
> memory in banks with a maximum size of 256MB. Since my Odroid XU4 has
> 2GB of memory, I end up with more memory segments than the two
> supported by our kernel.
This patch for ubcmtp makes it use the multitouch-input functions of
wsmouse. It's the first driver that would apply the "tracking" variant
(wsmouse_mtframe).
No wonders will result from the change, but the two-finger gestures that
involve movement - scrolling and click-and-drag with two fingers o
> Date: Thu, 9 Mar 2017 16:13:01 +0100
> From: Martin Pieuchot
>
> On 09/03/17(Thu) 14:48, Mark Kettenis wrote:
> > > Date: Thu, 9 Mar 2017 14:04:04 +0100
> > > From: Martin Pieuchot
> > >
> > > Many of us have x86 machines with a USB keyboard that's unusable in
> > > ddb(4). That's generally
For some reason u-boot on the exynos platform decides to split up the
memory in banks with a maximum size of 256MB. Since my Odroid XU4 has
2GB of memory, I end up with more memory segments than the two
supported by our kernel. The diff below increases the number of
segments to 32, which is what
Michael Forney wrote:
> > + exit(fd != -1);
>
> While you're at it, I think this exit status is backwards. Currently
> `doas -L` exits 0 if the open failed.
yeah, oops. fixed. thanks.
Prevent integer overflow in PF when calculating the adaptive timeout.
Mainly states of established TCP connections would be affected
resulting in immediate state removal once the numer of states is
bigger than adaptive.start.
Disabling adative timeouts with
set timeout { adaptive.start 0, adapt
Stuart Henderson(s...@spacehopper.org) on 2017.03.07 21:56:56 +:
> On 2017/03/07 13:24, Devin Reade wrote:
> > Expanding on my previous email, it looks like the git version of
> > acme-client has a different implementation than what was implemented
> > in the version first committed (and later
On Sun, Nov 27, 2016 at 12:31 AM, Hajime Edakawa
wrote:
> Dear tech,
>
> I guessed it more better to use fd instead of i.
>
> Would this be OK?
>
> Sincerely, tech
> Edakawa
>
> Index: doas.c
> ===
> RCS file: /cvs/src/usr.bin/doas/do
> Date: Thu, 9 Mar 2017 16:04:44 +0100
> From: Martin Pieuchot
>
> On 09/03/17(Thu) 15:04, Mark Kettenis wrote:
> > > Date: Thu, 9 Mar 2017 14:32:29 +0100
> > > From: Martin Pieuchot
> > >
> > > Diff below move per HC driver polling code to the stack. I know this
> > > code contains a use-afte
On 09/03/17(Thu) 14:48, Mark Kettenis wrote:
> > Date: Thu, 9 Mar 2017 14:04:04 +0100
> > From: Martin Pieuchot
> >
> > Many of us have x86 machines with a USB keyboard that's unusable in
> > ddb(4). That's generally because the BIOS presents a fake pckbd(4)
> > to the OS:
> >
> > pckbc0 at
On Thu, Mar 09, 2017 at 03:49:21PM +0100, Jeremie Courreges-Anglas wrote:
> Martin Pieuchot writes:
>
> > On 08/03/17(Wed) 12:03, Jeremie Courreges-Anglas wrote:
> >> [...]
> >> So here's a refreshed diff that initializes the counters directly from
> >> ip_init(). I remove the ipip_init() wrapp
On 09/03/17(Thu) 15:04, Mark Kettenis wrote:
> > Date: Thu, 9 Mar 2017 14:32:29 +0100
> > From: Martin Pieuchot
> >
> > Diff below move per HC driver polling code to the stack. I know this
> > code contains a use-after-free and this will be addressed in a later
> > diff. For the moment merge 4
Martin Pieuchot writes:
> On 08/03/17(Wed) 12:03, Jeremie Courreges-Anglas wrote:
>> [...]
>> So here's a refreshed diff that initializes the counters directly from
>> ip_init(). I remove the ipip_init() wrapper to make it clear that
>> ip_init() is responsible for the job.
>>
>> (Still) ok?
>
> Date: Thu, 9 Mar 2017 14:32:29 +0100
> From: Martin Pieuchot
>
> Diff below move per HC driver polling code to the stack. I know this
> code contains a use-after-free and this will be addressed in a later
> diff. For the moment merge 4 copies into 1 such that I don't have to
> fix all of them
> Date: Thu, 9 Mar 2017 14:04:04 +0100
> From: Martin Pieuchot
>
> Many of us have x86 machines with a USB keyboard that's unusable in
> ddb(4). That's generally because the BIOS presents a fake pckbd(4)
> to the OS:
>
> pckbc0 at isa0 port 0x60/5 irq 1 irq 12
> pckbd0 at pckbc0 (kb
Diff below move per HC driver polling code to the stack. I know this
code contains a use-after-free and this will be addressed in a later
diff. For the moment merge 4 copies into 1 such that I don't have to
fix all of them.
As a side effect, this fix xhci(4) polling mode. That means you can
now
Many of us have x86 machines with a USB keyboard that's unusable in
ddb(4). That's generally because the BIOS presents a fake pckbd(4)
to the OS:
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
Some
On 09/03/17(Thu) 08:48, Stefan Sperling wrote:
> This diff converts a struct ifnet pointer in pfsync's softc into an
> ifindex with corresponding if_get()/if_put() calls.
This avoid the panic but obfuscate the problem. What you want is a
detachhook such that if the parent interface is destroyed y
19 matches
Mail list logo
