| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After I removed all the unit2minor()/minor2unit() calls from the kernel
yesterday, I realised calling minor() everywhere is quite confusing.
Character devices now only have the ability to store a unit number, not
a minor number. Remove the confusion by using dev2unit() everywhere.
This commit could also be considered as a bug fix. A lot of drivers call
minor(), while they should actually be calling dev2unit(). In -CURRENT
this isn't a problem, but it turns out we never had any problem reports
related to that issue in the past. I suspect not many people connect
more than 256 pieces of the same hardware.
Reviewed by: kib
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When I changed kern_conf.c three months ago I made device unit numbers
equal to (unneeded) device minor numbers. We used to require
bitshifting, because there were eight bits in the middle that were
reserved for a device major number. Not very long after I turned
dev2unit(), minor(), unit2minor() and minor2unit() into macro's.
The unit2minor() and minor2unit() macro's were no-ops.
We'd better not remove these four macro's from the kernel, because there
is a lot of (external) code that may still depend on them. For now it's
harmless to remove all invocations of unit2minor() and minor2unit().
Reviewed by: kib
|
|
|
|
|
|
|
|
|
| |
patches
for target mode that are forthcoming.
Reviewed by: Scott Long
MFC after: 2 days
|
|
|
|
|
|
|
|
| |
because the media was removed, the periph would get its refcount dropped
and ultimately freed before getting unlocked. This created a dangling
pointer that was easy to trip over. This fixes a common source of
crashes with removaable media, but problems remain and will get tracked
down.
|
|
|
|
|
| |
Submitted by: Andre Albsmeier <Andre.Albsmeier@siemens.com>
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
| |
http://www.t10.org/lists/1spc-lst.htm
Note opcodes for scanner and communication devices are taken from the previous
revision because they are not listed in the files any more.
Also, note newly added ASCs are all marked with 'XXX TBD' and take SS_RDEF action
for now. Some ASCs need SS_TUR for error recovery or SS_FATAL to prevent further
retrials. We should deal with them later.
Reviewed by: scottl, ken
|
| |
|
|
|
|
|
|
|
| |
PR: 125398
Submitted by: Tino Engel <goaengel at gmx dot net>
Approved by: imp (mentor, implicit)
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
the referenced data is only obtained/changed in the device open handler,
and the ioctl handler can only run after the open handler. Also fix a
few nearby style issues.
Submitted by: Matt Jacob
|
|
|
|
|
|
|
|
| |
device supports retrieving a serial number. Instead, first query the
list of VPD pages it does support, and only query the serial number if
it's supported, else silently move on. This eliminates a lot of noise
during verbose booting, and will likely eliminate the need for most
NOSERIAL quirks.
|
| |
|
|
|
|
| |
Submitted by: Matt Jacob
|
|
|
|
| |
Approved by: cognet (mentor)
|
|
|
|
|
|
|
| |
Submitted by: R.Mahmatkhanov <cvs-src@yandex.ru>
Reviewed by: scottl
Approved by: rwatson (mentor)
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
it's 1.00 not 1.0.
PR: usb/96546
Submitted by: Eugene Grosbein
MFC after: 1 month
|
| |
|
|
|
|
|
|
|
|
|
| |
for that argument. This will allow DDB to detect the broad category of
reason why the debugger has been entered, which it can use for the
purposes of deciding which DDB script to run.
Assign approximate why values to all current consumers of the
kdb_enter() interface.
|
|
|
|
| |
Reported by: Michael Jung
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
to kproc_xxx as they actually make whole processes.
Thos makes way for us to add REAL kthread_create() and friends
that actually make theads. it turns out that most of these
calls actually end up being moved back to the thread version
when it's added. but we need to make this cosmetic change first.
I'd LOVE to do this rename in 7.0 so that we can eventually MFC the
new kthread_xxx() calls.
|
| |
|
|
|
|
|
|
|
|
| |
due to error.
PR: kern/114636
Submitted by: Tijl Coosemans
Approved by: re (hrs)
|
|
|
|
| |
Approved by: re (blanket)
|
|
|
|
|
|
| |
Submitted by: Jason Harris
PR: 107495
Approved by: re@ (blanket)
|
|
|
|
|
|
| |
Submitted by: Mark Andrews
PR: 103702
Approved by: re@ (blanket)
|
|
|
|
|
|
| |
submitted by: Toni Schmidbauer
PR: 96133
Approved by: re@ (blanket)
|
|
|
|
|
|
| |
Submitted by: Jeff Anton
PR: 108810
Approved by: re@ (blanket)
|
|
|
|
|
|
| |
Submitted by: Gipsy<wint3r@securimail.com>
PR: 108427
Approved by: re@ (blanket)
|
|
|
|
|
|
| |
Submitted by: User & <dhenin@cypries.cyclopes.org>
PR: 94439
Approved by: re (blanket)
|
|
|
|
|
|
| |
Submitted by: Arnoud Engelfriet
PR: 68412
Approved by: re (blanket)
|
|
|
|
|
|
| |
PR: 92306
Submitted by: Soren Dossing
Approved by: re (blanket)
|
|
|
|
|
|
| |
Submitted by: Ed Schouten
PR: 107101
Approved by: re (blanket for device supprot)
|
|
|
|
|
|
|
| |
now takes a device_t to be the parent of the bus that is being created.
Most SIMs have been updated with a reasonable argument, but a few exceptions
just pass NULL for now. This argument isn't used yet and the newbus
integration likely won't be ready until after 7.0-RELEASE.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
sysctl_handle_int is not sizeof the int type you want to export.
The type must always be an int or an unsigned int.
Remove the instances where a sizeof(variable) is passed to stop
people accidently cut and pasting these examples.
In a few places this was sysctl_handle_int was being used on 64 bit
types, which would truncate the value to be exported. In these
cases use sysctl_handle_quad to export them and change the format
to Q so that sysctl(1) can still print them.
|
|
|
|
| |
in detail the procedure for getting device quirks into the CAM subsystem.
|
|
|
|
| |
actual formal process he's trying to get established for quirks..
|
|
|
|
|
| |
Submitted by: Joakim Bentholm`
MFC after: 3 days
|
|
|
|
| |
Submitted by: Cyril Nguyen Huu <cyril ci0 org>
|
|
|
|
|
|
|
| |
tell if there has been data returned (for some broken
residual checking points).
MFC after: 3 days
|
|
|
|
| |
ioctl. This should make SIM removal a bit more robust.
|
|
|
|
| |
difficult.
|
|
|
|
| |
eliminating a lot of duplicated code, this also fixes a locking edge case.
|
| |
|
|
|
|
| |
panics on boot.
|
| |
|