infrastructure that allows new ones to be added. The discovery methods
are prioritized, and only one can exist at a given priority.
The DKWEDGE_METHOD_GPT option causes GPT support to be included. GPT is
at priority 0; we prefer GPT above all others.
length of the command buffer (1) instead of 0. Otherwise, data will
have an implied offset of 0 and reads at non-0 locations will incorrectly
return the data from 0. Fix as suggested in the report.
kernel message buffer/log. Its off by default and can be switched on in the
kernel configuration on build time, be set as a variable in ddb and be set
using sysctl.
This adds the sysctl value
ddb.tee_msgbuf = 0
by default.
The functionality is especially added and aimed for developers who are not
blessed with a serial console and wish to keep all their ddb output in the
log. Specifying /l as a modifier to some selected commands will also put
the output in the log but not all commands provide one nor has the same
meaning for all commands.
This feature could in the future also be implemented as an ddb command but
that could lead to more bloat allthough maybe easier for non developpers to
use when mailing their backtraces from kernel crashes.
1) Fix small indenting issues
2) Removal of audio* at ... and midi* at ... entries and replace all them with
audio* at audiobus?
midi* at minibus?
3) Adding of USB audio/midi and IrDa entries
segment should succeed even if the segment would be marked removed; use this
to implement the Linux-compatible semantics of shmat(2)
this fixes the old Linux VMware3 graphics problem with local display,
and possibly other local Linux X clients using MIT-SHM
Use it for ST3200822A, which has a broken firmware and return an error
when accessing sector 0xfffffff with a LBA command.
Patch tested by David Brownlee.
for Linux-compatible shmat() behaviour - shmat() for the removed shared memory
segment must work from all callers, the shared memory id could be passed e.g.
to native X server via MIT-SHM
temporarily remove the functionality, the Linux-compatible semantics
will be reimplemented differently
the reset condition are processed properly; this fixes PR#26687 by
Jan Schaumann
many thanks to Mark Davies, who tracked the offending change down
and helped test patches
while here, g/c unused sigtrapmask and rearrange some code to pre-r1.190 form
for better readability
Fix tx queue (slist can be corrupted when tx interrupts hit within tx_encap.
Lower interrupt moderation timer to (improves performance).
Improve chip identification. (from linux sk98lin driver).
Keep tx queue running by kicking the tx bmu repeatedly.
Because we no longer return an error message when no disklabel was found
the scsipi/cd.c code took the label we generated. The problem is that the
readdisklabel code was clearing the partition information, which included
the default partition information setup by the cd.c code. Previously when
no disklabel was found we returned an error, which caused the cd.c code to
generate a new default label which included an a partition.
According to the man page for readdisklabel:
Unspecified fields in lp should be set to zero
Therefore we have no reason to clear the partition info, as it's already
clear or contains useful default partition info.
This means if we don't find a label on disk, the default label is left as
is. I would expect the driver to have setup a much more sensible default
label than we could fake at this level.
Also don't hard code the number of partitions to the maximum. This better
matches other platforms (i386)
This should fix PR's 26564 and 26809.
This allows CD installs on cats to work, as a cdxa partition is now
faked, so sysinst can mount it.
This does go against changes made for PR 21408, as it will cause the error
cd0: no disk label
to appear when running disklabel cd0.
Really readdisklabel's API should be updated to allow better error returns,
such that the driver can choose to fake the label, if readdisklabel didn't
find one.
Some devices do not transfer data with proper way on status phase
and it causes bus error in spc_datain_pio() which uses auto xfer
via DREG register on weird x68k hardware.
christos