Re: apldc/aplhidev: enable LEDs in xorg

2023-04-09 Thread Mark Kettenis
> Date: Sun, 9 Apr 2023 22:56:01 +0200 > From: Tobias Heider > > This patch enables the capslock LED on apple m1/m2 laptops in xenocara. > Console mode was already working by setting the correct accessop, for > X we are missing an ioctl handler. > > Only tested on apldc but the aplhidev code

apldc/aplhidev: enable LEDs in xorg

2023-04-09 Thread Tobias Heider
This patch enables the capslock LED on apple m1/m2 laptops in xenocara. Console mode was already working by setting the correct accessop, for X we are missing an ioctl handler. Only tested on apldc but the aplhidev code looks identical so the fix should be the same. Index: apldc.c

Re: MALLOC_STATS: dump internal state and leak info via utrace(2)

2023-04-09 Thread Sebastien Marie
On Sun, Apr 09, 2023 at 12:17:35PM +0200, Otto Moerbeek wrote: > On Sun, Apr 09, 2023 at 10:08:25AM +0200, Claudio Jeker wrote: > > On Sun, Apr 09, 2023 at 09:15:12AM +0200, Otto Moerbeek wrote: > > > > I would prefer if every utrace() call is a full line (in other words ulog > > should be line

Re: MALLOC_STATS: dump internal state and leak info via utrace(2)

2023-04-09 Thread Otto Moerbeek
On Sun, Apr 09, 2023 at 10:08:25AM +0200, Claudio Jeker wrote: > On Sun, Apr 09, 2023 at 09:15:12AM +0200, Otto Moerbeek wrote: > > On Sun, Apr 09, 2023 at 08:20:43AM +0200, Otto Moerbeek wrote: > > > > > On Sun, Apr 09, 2023 at 07:53:31AM +0200, Sebastien Marie wrote: > > > > > > > On Fri, Apr

Re: MALLOC_STATS: dump internal state and leak info via utrace(2)

2023-04-09 Thread Sebastien Marie
On Sun, Apr 09, 2023 at 10:08:25AM +0200, Claudio Jeker wrote: > On Sun, Apr 09, 2023 at 09:15:12AM +0200, Otto Moerbeek wrote: > > On Sun, Apr 09, 2023 at 08:20:43AM +0200, Otto Moerbeek wrote: > > I would prefer if every utrace() call is a full line (in other words ulog > should be line

Re: MALLOC_STATS: dump internal state and leak info via utrace(2)

2023-04-09 Thread Claudio Jeker
On Sun, Apr 09, 2023 at 09:15:12AM +0200, Otto Moerbeek wrote: > On Sun, Apr 09, 2023 at 08:20:43AM +0200, Otto Moerbeek wrote: > > > On Sun, Apr 09, 2023 at 07:53:31AM +0200, Sebastien Marie wrote: > > > > > On Fri, Apr 07, 2023 at 09:52:52AM +0200, Otto Moerbeek wrote: > > > > > Hi, > > > > >

Re: MALLOC_STATS: dump internal state and leak info via utrace(2)

2023-04-09 Thread Sebastien Marie
On Sun, Apr 09, 2023 at 09:15:12AM +0200, Otto Moerbeek wrote: > On Sun, Apr 09, 2023 at 08:20:43AM +0200, Otto Moerbeek wrote: > > > > > Thanks! Your suggestions make a lot of sense. I'll rework the kdump > > part to make it more flexable for different purposes. > > Anothew aspect of safety is

Re: MALLOC_STATS: dump internal state and leak info via utrace(2)

2023-04-09 Thread Otto Moerbeek
On Sun, Apr 09, 2023 at 08:20:43AM +0200, Otto Moerbeek wrote: > On Sun, Apr 09, 2023 at 07:53:31AM +0200, Sebastien Marie wrote: > > > On Fri, Apr 07, 2023 at 09:52:52AM +0200, Otto Moerbeek wrote: > > > > Hi, > > > > > > > > This is work in progress. I have to think if the flags to kdump I'm

Re: MALLOC_STATS: dump internal state and leak info via utrace(2)

2023-04-09 Thread Otto Moerbeek
On Sun, Apr 09, 2023 at 07:53:31AM +0200, Sebastien Marie wrote: > On Fri, Apr 07, 2023 at 09:52:52AM +0200, Otto Moerbeek wrote: > > > Hi, > > > > > > This is work in progress. I have to think if the flags to kdump I'm > > > introducing should be two or a single one. > > > > > > Currently,