Mark Kettenis writes:
> Can somebody test the following diff on Ivy Bridge or Haswell (Intel
> HD Graphics 2500/4000/4600/4700/5000/5100/5200)?
>
> When I added support for the command parser, I took a bit of a
> shortcut and implemented the hash tables as a single linked list.
> This diff fixes
On Mon, Jul 17, 2017 at 02:08:31AM +0200, Marco Bonetti wrote:
> Hello tech@,
> This is a diff that implements a new value (3) for machdep.lidaction to allow
> a laptop powerdown with a lid close. Since this functionality is very close
> to machdep.kbdreset=1, the diff follows the same behaviour
On Mon, Jul 17, 2017 at 11:08:13AM +0900, Bryan Linton wrote:
> On 2017-07-16 15:19:41, Mark Kettenis wrote:
> > Can somebody test the following diff on Ivy Bridge or Haswell (Intel
> > HD Graphics 2500/4000/4600/4700/5000/5100/5200)?
> >
> > When I added support for the command parser, I took a
On 2017-07-16 15:19:41, Mark Kettenis wrote:
> Can somebody test the following diff on Ivy Bridge or Haswell (Intel
> HD Graphics 2500/4000/4600/4700/5000/5100/5200)?
>
> When I added support for the command parser, I took a bit of a
> shortcut and implemented the hash tables as a single linked l
Hello tech@,
This is a diff that implements a new value (3) for machdep.lidaction to allow a
laptop powerdown with a lid close. Since this functionality is very close to
machdep.kbdreset=1, the diff follows the same behaviour and prevents setting
machdep.lidaction when securelevel is greater tha
On Sun, Jul 16, 2017 at 08:45:40PM +0200, Mark Kettenis wrote:
> > Date: Sun, 16 Jul 2017 10:05:54 -0700
> > From: Andrew Marks
> >
> > Hello,
> >
> > I happen to have a Haswell 4600 so I tried to apply this patch, I am
> > running a snapshot from 16 Jul 2017 and just updated my src. My
> > drm
On Sun, Jul 16, 2017 at 08:15:38PM +, Robert Peichaer wrote:
> > + ifconfig lo0 inet6 >/dev/null 2>&1 &&
>
> Please leave the if-then-fi construct intact. This short form is
> mostly used for on-line commands (with only a few exceptions).
OK.
> > + RULES="$RULES"'
>
> What is the
> Date: Sun, 9 Jul 2017 20:34:29 +0300
> From: Artturi Alm
>
> Hi,
>
> revived the diff below, i2c tested via pmic's shutdown(), for working
> "shutdown -p now" operation.
> there was only two i2c's w/"status: 'okay'" in the FDT, so not all of
> them do attach.
>
> related part of dmesg:
>
> c
On Thu, Jul 13, 2017 at 09:16:14PM -0400, Rob Pierce wrote:
> On Mon, Jul 10, 2017 at 01:21:58PM -0400, Rob Pierce wrote:
> > The following diff is loosely based on the approach that was taken for
> > pledging mountd. Other code/approaches leveraged from various networking
> > daemons.
> >
> > Thi
On Sun, Jul 16, 2017 at 03:24:19PM +0200, Klemens Nanni wrote:
> On Sun, Jul 16, 2017 at 12:41:09PM +, Robert Peichaer wrote:
> > On Sun, Jul 16, 2017 at 02:28:59PM +0200, Klemens Nanni wrote:
> > > On Sun, Jul 16, 2017 at 12:11:55PM +, Robert Peichaer wrote:
> > > > On Sun, Jul 16, 2017 at
On Tue, Jul 04, 2017 at 11:00:18PM +0200, Remi Locherer wrote:
> On Sun, Jun 25, 2017 at 11:47:09PM +0200, Remi Locherer wrote:
> > Hi,
> >
> > ospfd does not react nicely when running "sh /etc/netstart if".
> >
> > This is because adding the same address again do an interface results
> > in RTM_
> Date: Sun, 16 Jul 2017 10:05:54 -0700
> From: Andrew Marks
>
> Hello,
>
> I happen to have a Haswell 4600 so I tried to apply this patch, I am
> running a snapshot from 16 Jul 2017 and just updated my src. My
> drm_linux.h looks much different than the one your patch was meant for.
> cvs log
This is great newsi, thanks for your efforts implementing this. It is also
encouraging to hear this should be in 6.2 release. I'll commit to testing on my
hardware and report any bugs.
Regards,
Leighton
On Sat, Jul 15, 2017 at 05:05:52PM +, Florian Obser wrote:
> I didn't not hear any objec
Hello,
I happen to have a Haswell 4600 so I tried to apply this patch, I am
running a snapshot from 16 Jul 2017 and just updated my src. My
drm_linux.h looks much different than the one your patch was meant for.
cvs log shows it to be revision 1.56 so I'm not sure where the
discrepancy lies. My d
I've ok'd this type of diff from visa@ before. This piece is worth
doing.
However there are further problems to be resolved in this area, it is
not sufficient for all the problems. lld/binutils have a pile of
problems in this area.
Also, please don't send diffs which fix only one architecture, b
This diff fixes an athn(4) performance regression on 2GHz.
Before I added 11n support athn(4), the driver used to send RTS frames
at 2 Mbit/s while operating in the 2GHz band.
I changed this to 1 Mbit/s for consistency with other drivers.
However, it turns out that the chip does not do what I am a
On Sun, Jul 16, 2017 at 03:24:19PM +0200, Klemens Nanni wrote:
> + print -- "$RULES" | pfctl -nf -
That should be 'pfctl -ef -' of course.
On Sun, Jul 16, 2017 at 12:41:09PM +, Robert Peichaer wrote:
> On Sun, Jul 16, 2017 at 02:28:59PM +0200, Klemens Nanni wrote:
> > On Sun, Jul 16, 2017 at 12:11:55PM +, Robert Peichaer wrote:
> > > On Sun, Jul 16, 2017 at 01:37:56PM +0200, Klemens Nanni wrote:
> > > > This removes on level o
Can somebody test the following diff on Ivy Bridge or Haswell (Intel
HD Graphics 2500/4000/4600/4700/5000/5100/5200)?
When I added support for the command parser, I took a bit of a
shortcut and implemented the hash tables as a single linked list.
This diff fixes that.
For the hash function I used
Hi,
quite certain i won't come up w/anything better than what i have now,
can't get over my loathe towards Makefiles&co..
So, given above, i guess this is just for the archives, but if anyone is
up for fixing it for real, you'll have my thanks. :)
-Artturi
diff --git a/sys/conf/makegap.sh b/sys
Hi all,
Further simplification - 'ps | grep' can be replaced by pgrep(1)
and if-then-fi by &&.
> While there:
>
> - remove ':' (null utility) from the very first line of the file -
> I *do* understand what it does but it doesn't seem like it's needed
> at all, unless I'm missing something (a
On Sun, Jul 16, 2017 at 02:28:59PM +0200, Klemens Nanni wrote:
> On Sun, Jul 16, 2017 at 12:11:55PM +, Robert Peichaer wrote:
> > On Sun, Jul 16, 2017 at 01:37:56PM +0200, Klemens Nanni wrote:
> > > This removes on level of indent, avoids the ugly RULES="$RULES ..."
> > > repitition and spares
On Sun, Jul 16, 2017 at 12:11:55PM +, Robert Peichaer wrote:
> On Sun, Jul 16, 2017 at 01:37:56PM +0200, Klemens Nanni wrote:
> > This removes on level of indent, avoids the ugly RULES="$RULES ..."
> > repitition and spares a print.
> >
> > We could do a 'pfctl -ef -' right away but I kept cha
On Sun, Jul 16, 2017 at 01:37:56PM +0200, Klemens Nanni wrote:
> This removes on level of indent, avoids the ugly RULES="$RULES ..."
> repitition and spares a print.
>
> We could do a 'pfctl -ef -' right away but I kept changing and enabling
> clearly seperated. Regarding the leading newlines and
On Sun, Jul 16, 2017 at 11:55:09AM +, Robert Peichaer wrote:
> To the contrary what my previous answer might indicate, I don't care
> that much either. If you want to explicitely remove the blank, go for
> it.
Most problems I ever encountered while writing shell code were related
to (nested) qu
On Sun, Jul 16, 2017 at 01:55:02PM +0200, Klemens Nanni wrote:
> On Sun, Jul 16, 2017 at 10:26:25AM +, Robert Peichaer wrote:
> > But I'd like to stay strict matching the filenames.
> >
> > + for _liba in /usr/lib/lib{c,crypto}; do
> > + _libas="$_libas $(ls $_liba.so.+([0-9.]).a |
On Sun, Jul 16, 2017 at 01:23:00PM +0200, Klemens Nanni wrote:
> On Sun, Jul 16, 2017 at 10:26:25AM +, Robert Peichaer wrote:
> > On Sun, Jul 16, 2017 at 03:37:15AM +0200, Klemens Nanni wrote:
> > > Why looping over all existing archives, picking the latest version of
> > > the current archive,
On Sun, Jul 16, 2017 at 10:26:25AM +, Robert Peichaer wrote:
> But I'd like to stay strict matching the filenames.
>
> + for _liba in /usr/lib/lib{c,crypto}; do
> + _libas="$_libas $(ls $_liba.so.+([0-9.]).a | sort -V | tail -1)"
> + done
>
> > + _libas=${_libas# }
Agree
This removes on level of indent, avoids the ugly RULES="$RULES ..."
repitition and spares a print.
We could do a 'pfctl -ef -' right away but I kept changing and enabling
clearly seperated. Regarding the leading newlines and tabs of the inner
echo: pf perfectly munges those, no need to clear them.
On Sun, Jul 16, 2017 at 07:18:00AM +0200, Theo Buehler wrote:
> On Sun, Jul 16, 2017 at 03:34:07AM +0200, Klemens Nanni wrote:
> > $_l is not used and picking the latest archive versions is of no use
> > if /usr/lib cannot be written to.
> >
> > This patch applies cleanly before my next one but no
On Sun, Jul 16, 2017 at 10:26:25AM +, Robert Peichaer wrote:
> On Sun, Jul 16, 2017 at 03:37:15AM +0200, Klemens Nanni wrote:
> > Why looping over all existing archives, picking the latest version of
> > the current archive, skipping it in case it's already in our list of
> > selected latest ve
> But I'd like to stay strict matching the filenames.
>
> + for _liba in /usr/lib/lib{c,crypto}; do
> + _libas="$_libas $(ls $_liba.so.+([0-9.]).a | sort -V | tail -1)"
> + done
Yes, this is indeed better.
So Klemens, can you write a patch that uses this and removes the then
On Sun, Jul 16, 2017 at 03:37:15AM +0200, Klemens Nanni wrote:
> Why looping over all existing archives, picking the latest version of
> the current archive, skipping it in case it's already in our list of
> selected latest versions or adding it otherwise?
>
> The current code runs ls|sort|tail ab
On Sun, Jul 16, 2017 at 07:18:00AM +0200, Theo Buehler wrote:
> On Sun, Jul 16, 2017 at 03:34:07AM +0200, Klemens Nanni wrote:
> > $_l is not used and picking the latest archive versions is of no use
> > if /usr/lib cannot be written to.
> >
> > This patch applies cleanly before my next one but no
34 matches
Mail list logo
