Newer ThinkPads have ACPI goo to allow acpivout to control screen
backlight, so don't take over ws_[gs]et_param from it. This allows
for 100 levels of backlight control rather than the 10 or 15 that
are supported through acpithinkpad using its proprietary ACPI or
CMOS interfaces.
You can see
When responding to hardware keys to increment or decrement screen
brightness, don't just adjust by 1 BCL level as there may be 100
levels. Find the next brightness level that is at least 5% up or
down, and use that.
Index: dev/acpi/acpivout.c
On Sun, 8 Sep 2019 14:06:28 +0300
macfanbo...@gmail.com wrote:
> They break copying files with spaces:
>
> $ touch '/tmp/file with spaces'; mkdir '/tmp/dir with spaces'
>
> $ scp localhost:"'/tmp/file with spaces'" /tmp
> protocol error: filename does not match request
>
> $ scp -r
ftp currently uses utime(3) to set the modification time on the retrieved
file. It set the access time on the file to the current time when doing
so. By converting this to use utimensat(), we can avoid the silly call
to time(3) to get the current time for the atime by instead passing
This paves the way for having backlight control on the pinebook.
ok?
Index: dev/fdt/simplefb.c
===
RCS file: /cvs/src/sys/dev/fdt/simplefb.c,v
retrieving revision 1.5
diff -u -p -r1.5 simplefb.c
--- dev/fdt/simplefb.c 27 Aug 2018
> Date: Sun, 13 Oct 2019 01:58:43 +0200
> From: Klemens Nanni
>
> On Sat, Oct 12, 2019 at 05:38:13PM -0500, Scott Cheloha wrote:
> > Also, just count how many spaces we need to print ncpuonline,
> > then use that when printing the individual CPU lines.
> Yup, here's a minimal diff that does that
[not subscribed, please Cc, thanks]
Through the archives, me's watched this discussion with some bemusement.
Me'd like to see another option considered: just printing the device
name, instead of using the custom CPU* format.
No patch right now, might come tonight, claws full of other work :(
