| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
MFC after: 1 day
|
| |
|
|
|
|
|
|
|
|
| |
fourth would be a divergence from the prevailing style.)
Thanks to bde for catching this.
Pointed out by: bde
|
| |
|
|
|
|
| |
Make the dump routine do just writing of data.
|
|
|
|
|
|
| |
serial number probing.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and upgrade to using 10 byte cdbs.
As far as I tested, this works efficiently for most of the
SBP-II/Firewire devices but most of the umass devices still need
ad-hoc work around because umass-sim doesn't return any SCSI errors.
A sysctl nob is also added for the last resort.
I hope we don't need DA_Q_NO_6_BYTE quirks anymore.
Reviewed by: gibbs
MFC after: 1 week
|
| |
|
| |
|
| |
|
|
|
|
| |
reference.
|
| |
|
|
|
|
|
|
|
|
| |
Firewire/SBP-II devices.
- Add quirk for Logitec USB/Firewire HDD.
MFC after: 3 days.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
deprecated in favor of the POSIX-defined lowercase variants.
o Change all occurrences of NTOHL() and associated marcros in the
source tree to use the lowercase function variants.
o Add missing license bits to sparc64's <machine/endian.h>.
Approved by: jake
o Clean up <machine/endian.h> files.
o Remove unused __uint16_swap_uint32() from i386's <machine/endian.h>.
o Remove prototypes for non-existent bswapXX() functions.
o Include <machine/endian.h> in <arpa/inet.h> to define the
POSIX-required ntohl() family of functions.
o Do similar things to expose the ntohl() family in libstand, <netinet/in.h>,
and <sys/param.h>.
o Prepend underscores to the ntohl() family to help deal with
complexities associated with having MD (asm and inline) versions, and
having to prevent exposure of these functions in other headers that
happen to make use of endian-specific defines.
o Create weak aliases to the canonical function name to help deal with
third-party software forgetting to include an appropriate header.
o Remove some now unneeded pollution from <sys/types.h>.
o Add missing <arpa/inet.h> includes in userland.
Tested on: alpha, i386
Reviewed by: bde, jake, tmm
|
|
|
|
| |
Submitted by: Brian Schellenberger <bts@babbleon.org>
|
|
|
|
| |
Obtained from: ~bde/sys.dif.gz
|
|
|
|
|
|
|
|
|
| |
- Vendor&Device IDs for USB product,
- quirk for SCSI CAM.
PR: 34481
Submitted by: Olexander Kunytsa <kunia@x-telecom.net>
MFC in: 3 days
|
|
|
|
|
|
|
| |
peripheral drivers. Remove Ken's comment to the effect that this needed
to be done.
Staticise camnet_ih and cambio_ih.
|
|
|
|
| |
Submitted by: non
|
|
|
|
|
|
|
| |
PR: kern/33638
Submitted by: Olexander Kunytsa <kunia@x-telecom.net>
MFC after: 3 days
(pending re's approval)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
mutex releases to not require flags for the cases when preemption is
not allowed:
The purpose of the MTX_NOSWITCH and SWI_NOSWITCH flags is to prevent
switching to a higher priority thread on mutex releease and swi schedule,
respectively when that switch is not safe. Now that the critical section
API maintains a per-thread nesting count, the kernel can easily check
whether or not it should switch without relying on flags from the
programmer. This fixes a few bugs in that all current callers of
swi_sched() used SWI_NOSWITCH, when in fact, only the ones called from
fast interrupt handlers and the swi_sched of softclock needed this flag.
Note that to ensure that swi_sched()'s in clock and fast interrupt
handlers do not switch, these handlers have to be explicitly wrapped
in critical_enter/exit pairs. Presently, just wrapping the handlers is
sufficient, but in the future with the fully preemptive kernel, the
interrupt must be EOI'd before critical_exit() is called. (critical_exit()
can switch due to a deferred preemption in a fully preemptive kernel.)
I've tested the changes to the interrupt code on i386 and alpha. I have
not tested ia64, but the interrupt code is almost identical to the alpha
code, so I expect it will work fine. PowerPC and ARM do not yet have
interrupt code in the tree so they shouldn't be broken. Sparc64 is
broken, but that's been ok'd by jake and tmm who will be fixing the
interrupt code for sparc64 shortly.
Reviewed by: peter
Tested on: i386, alpha
|
|
|
|
|
| |
PR: 33407 (E885)
Submitted by: Brian Behlendorf <brian@hyperreal.org> (E885)
|
|
|
|
|
|
| |
o Add KLD dependency of ncv, nsp and stg drivers to scsi_low.
Submitted by: takawata
|
| |
|
|
|
|
|
| |
PR: kern/31250
Submitted by: Bryan Liesner <bleez@bellatlantic.net>
|
|
|
|
|
|
|
|
|
|
| |
It is legal to have a device with device type 0x1f, that just means
that the device is of unknown type. Instead, only check the peripheral
qualifier when deciding whether or not to reject a device based on its
inquiry information.
Tested by: julian
MFC after: 3 weeks
|
|
|
|
|
|
|
|
| |
this device properly reports that the sync cache command is
unsupported, the bug is that we still complain about it on the
console.
Noticed by: gibbs
|
|
|
|
|
| |
PR: 23536
Submitted by: amagai@nue.org
|
|
|
|
|
|
|
| |
firmware on the drive in question. The pattern also matched far
too many Hitachi drives.
Spotted by: dg
|
|
|
|
|
|
| |
PR: kern/23536
Submitted by: Y.Amagai <amagai@nue.org>
MFC after: 1 week
|
|
|
|
|
|
| |
time in the cases where it really sends the drive out to lunch, but it also
allows us to catch very wierd edge cases of strange drives that might take
a very long time (emulated disk drives over a network, e.g.).
|
|
|
|
|
|
|
|
| |
doesn't support the synchronise cache command.
PR: kern/21752
Submitted by: Nick R. Colakovic <nickc@corp.firstindustrial.com>
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
operations due to the synchronize cache command.
PR: kern/21674
Submitted by: W.Scholten <whs@xs4all.nl>
MFC after: 1 week
|
|
|
|
| |
Reviewed by: peter
|
|
|
|
| |
Submitted by: Jan Stocker <Jan.Stocker@t-online.de>
|
|
|
|
| |
Submitted by: Jos Vissers <jos@tunix.nl>
|
|
|
|
|
|
|
| |
10/12-byte-specific flags where specified.
Reviewed by: ken
MFC after: 1 day
|
|
|
|
|
|
|
| |
quirk regarding the C- series makes me suspect that all Olympus models have
the same quirks, but I cannot prove it.
Submitted by: Bernd Walter <ticso@cicely8.cicely.de>
|
|
|
|
| |
This will not affect either -current nor -stable.
|
|
|
|
|
| |
Submitted by: merry, Randy Bush <randy@psg.com>
MFC after: 3 days
|
|
|
|
|
|
| |
use securelevel_gt() instead of direct securelevel variable test.
Obtained from: TrustedBSD Project
|
| |
|
|
|
|
| |
useful once ATAPI support is turned on in the umass driver.
|
|
|
|
|
|
|
|
| |
attempts to set buffered mode was printing out "unable to set buffered
mode" no matter what. Oops.
Spotted by: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>
MFC after: 3 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Note ALL MODULES MUST BE RECOMPILED
make the kernel aware that there are smaller units of scheduling than the
process. (but only allow one thread per process at this time).
This is functionally equivalent to teh previousl -current except
that there is a thread associated with each process.
Sorry john! (your next MFC will be a doosie!)
Reviewed by: peter@freebsd.org, dillon@freebsd.org
X-MFC after: ha ha ha ha
|
|
|
|
|
| |
Reported by: Thomas Quinot <thomas@cuivre.fr.eu.org>
MFC after: 3 weeks
|
|
|
|
| |
Submitted by: Guido van Rooij <guido@gvr.org>
|
|
|
|
|
| |
Submitted by: Eugene M. Kim <gene@nttmcl.com>
PR: 29530
|
|
|
|
|
|
| |
retry count on.
MFC after: 4 weeks
|