summaryrefslogtreecommitdiffstats
path: root/sys/netgraph/bluetooth/drivers/ubtbcmfw
Commit message (Collapse)AuthorAgeFilesLines
* more usb fallout changesmjacob2006-09-071-13/+19
|
* /* -> /*- for license, minor formatting changesimp2005-01-071-1/+3
|
* MFp4: Last references to dev/usb/usbdevs.h converted.imp2004-06-271-1/+2
|
* Second half of the dev_t cleanup.phk2004-06-171-7/+7
| | | | | | | | | | | The big lines are: NODEV -> NULL NOUDEV -> NODEV udev_t -> dev_t udev2dev() -> findcdev() Various minor adjustments including handling of userland access to kernel space struct cdev etc.
* Do the dreaded s/dev_t/struct cdev */phk2004-06-161-9/+9
| | | | Bump __FreeBSD_version accordingly.
* add missing #include <sys/module.h>phk2004-05-301-0/+1
|
* Device megapatch 4/6:phk2004-02-211-0/+2
| | | | | | | | Introduce d_version field in struct cdevsw, this must always be initialized to D_VERSION. Flip sense of D_NOGIANT flag to D_NEEDGIANT, this involves removing four D_NOGIANT flags and adding 145 D_NEEDGIANT flags.
* Device megapatch 1/6:phk2004-02-211-7/+0
| | | | | | | Free approx 86 major numbers with a mostly automatically generated patch. A number of strategic drivers have been left behind by caution, and a few because they still (ab)use their major number.
* Update Bluetooth code.emax2003-10-121-1/+1
| | | | | Reviewed by: M. Warner Losh <imp@bsdimp.com>; John Hay <jhay@freebsd.org> Approved by: M. Warner Losh <imp@bsdimp.com> (mentor)
* I don't know from where the notion that device driver should orphk2003-09-281-15/+1
| | | | | | | | | | | | | | even could call VOP_REVOKE() on vnodes associated with its dev_t's has originated, but it stops right here. If there are things people belive destroy_dev() needs to learn how to do, please tell me about it, preferably with a reproducible test case. Include <sys/uio.h> in bluetooth code rather than rely on <sys/vnode.h> to do so. The fact that some of the USB code needs to include <sys/vnode.h> still disturbs me greatly, but I do not have time to chase that.
* Part one of undating the bluetooth code to the newest versionjulian2003-05-101-0/+571
Submitted by: Maksim Yevmenkin <m_evmenkin@yahoo.com> Approved by: re@
OpenPOWER on IntegriCloud