On some systems, attaching ahci(4) is one of the most noticeably slow parts
of the boot process, since each port with no device attached takes a whole
second to probe. I've made a few noises about fixing that over the years,
and here's a new one.
This rearranges the device detection phase so that
1 week bump.
--
Scott Cheloha
> On Aug 5, 2017, at 8:25 PM, Scott Cheloha wrote:
>
> Hi,
>
> In tetris(6) we use gettimeofday(2) to determine (roughly) how
> long we polled for user input. This then gets subtracted from
> the time remaining until we drop the block another row.
>
> This shoul
Hi,
Another gettimeofday(2) -> clock_gettime(2) w/ CLOCK_MONOTONIC.
This is a statistics printout, so you naturally don't want the
timer subject to jumping.
Also, you're supposed to include to use gettimeofday(2),
which we were not doing in dd.c, so I guess this fixes that in a
bit of a roundab
Reads ok to me, though I haven't tested. Don't worry about frozen-bubble,
it's broken anyway.
--
Sent from a phone, apologies for poor formatting.
On 12 August 2017 18:16:14 Andrew Fresh wrote:
Seems like a good idea to pick up the minor update to perl.
The full patch is here, but most of
Hello tech@
I've been stuck with fsck for way to many times now because of me
forgetting to connect the AC power. This patch will add -z and -Z
followed by the percentage. apmd will try to suspend or hibernate the
system if the AC is not connected and the estimated battery life goes
below the spec
iwm(4) resets the net80211 scan lock in iwm_stop(), but forgets to
wake up userland processes sleeping on this lock.
Usually, ieee80211_end_scan() would wake them but ieee80211_end_scan()
won't be called anymore after iwm_stop().
This is very visible with a suspend/resume cycle while a scan is run
iwm schedules a separate task just for calling ieee80211_end_scan().
That function is safe to call in interrupt context.
This wrinkle was already part of the original driver from 2015 but with
a workq instead of a task. Back then, the driver had to run two separate
scan commands in succession (for
Stop supporting prefix lifetimes that decrement in real time.
It complicates the code, it's off by default and RFC 4861 section
6.2.1 lists it as MAY.
After this we can stop regenerating the RA packets everytime we send
them.
Also I'm not convinced that this has a use case. I think it
comes from
On Sat, Aug 12, 2017 at 10:15:56AM -0700, Andrew Fresh wrote:
> The full patch is here, but most of it is documentation and tests:
> http://cvs.afresh1.com/~andrew/OpenBSD-perl-5.24.2.patch.txt
I have applied this on my laptop. Let's see whether anything breaks.
> Planning to do a single commit
Seems like a good idea to pick up the minor update to perl.
The full patch is here, but most of it is documentation and tests:
http://cvs.afresh1.com/~andrew/OpenBSD-perl-5.24.2.patch.txt
I successfully built a release with this on amd64 and unfortunately
broke my other architectures trying to do
I see no reason to change this. The first complaint in 25 years
sounds like "personal preference" or "desire to push a change".
> Currently, output originating from the kernel is displayed using
> WSCOL_WHITE on WSCOL_BLUE, which translates to NORMAL_WHITE on
> NORMAL_BLUE.
>
> When booting in B
> Date: Sat, 12 Aug 2017 17:06:18 +0200
> From: Frederic Cambus
>
> Hi tech@,
>
> Currently, output originating from the kernel is displayed using
> WSCOL_WHITE on WSCOL_BLUE, which translates to NORMAL_WHITE on
> NORMAL_BLUE.
>
> When booting in BIOS mode, NORMAL_WHITE is 0xaa in text mode
Hi tech@,
Currently, output originating from the kernel is displayed using
WSCOL_WHITE on WSCOL_BLUE, which translates to NORMAL_WHITE on
NORMAL_BLUE.
When booting in BIOS mode, NORMAL_WHITE is 0xaa in text mode
(which is very hard to read on a blue backgroud), and when framebuffer
attaches,
There is a bit too much layering going on and the
rasops_erasecols_rotated() and rasops_eraserows_rotated() functions
end up calling the vcons functions creating a nice infinite loop.
Simplest fix os for them to simply call rasops_putchar_rotated()
directly. I don't really see a valid reason not t
This makes iwm keep track of the firmware "stay on channel" time event
used during association.
Currently, iwm tells the firmware to schedule the time event, and forgets.
With this diff, iwm keeps track of the time event's scheduling and cancels
the time event if a deauth frame is received while
On Sat, Aug 12, 2017 at 10:04:25AM +0100, Stuart Henderson wrote:
> On 2017/06/29 10:03, Stuart Henderson wrote:
> > On 2017/06/27 14:58, Stuart Henderson wrote:
> > > If anyone's interested in newer unbound, I have an initial diff, it's
> > > 750K all-in (we are currently on 1.6.1 so there are a f
On 2017/06/29 10:03, Stuart Henderson wrote:
> On 2017/06/27 14:58, Stuart Henderson wrote:
> > If anyone's interested in newer unbound, I have an initial diff, it's
> > 750K all-in (we are currently on 1.6.1 so there are a few releases worth
> > of changes) so I won't send it inline, it's at
> > h
On August 11, 2017 5:23:38 PM GMT+02:00, Philip Guenther
wrote:
>
>Currently, if ksh starts as root and PS1 was exported but doesn't
>contain
>'#' or '\$' (which will be expanded to '#') then it'll override it with
>
>the root default of '# '. This is kind of a corner case, because PS1
>is
>
cd /usr/xenocara/lib
ftp https://mesa.freedesktop.org/archive/mesa-17.1.6.tar.gz
ftp http://jsg.id.au/mesa-update/mesa.diff.gz
tar zxf mesa-17.1.6.tar.gz
gunzip mesa.diff.gz
patch -p0 < mesa.diff
sed -i 's/mesa$/mesa-17.1.6/' Makefile
build xenocara as normal
Interested in radeon r300/r600 repor
19 matches
Mail list logo
