On Mon, Aug 14, 2017 at 04:26:10PM +1000, Jonathan Matthew wrote:
> On 14/08/17 01:40, Christian Weisgerber wrote:
> > Jonathan Matthew:
> >
> > > Better version that actually preserves the port command register state
> > > across
> > > resets, rather than throwing it away and replacing it with g
On 14/08/17 01:40, Christian Weisgerber wrote:
Jonathan Matthew:
Better version that actually preserves the port command register state across
resets, rather than throwing it away and replacing it with garbage:
This appears to break ahci on the OverDrive 1000:
...
ahci0 at simplebus0: AHCI 1
Jonathan Matthew:
> Better version that actually preserves the port command register state across
> resets, rather than throwing it away and replacing it with garbage:
This appears to break ahci on the OverDrive 1000:
...
ahci0 at simplebus0: AHCI 1.3
scsibus0 at ahci0: 32 targets
ahci0: stoppin
On Sun, Aug 13, 2017 at 02:09:49PM +1000, Jonathan Matthew wrote:
> 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,
>
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
