| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Approved by: philip (mentor)
|
|
|
|
|
|
| |
kproc_exit().
Discussed with: imp
|
|
|
|
|
|
|
|
| |
PR: 118391
Submitted by: "Pedro F. Giffuni" <giffunip at tutopia dot com>
Approved by: imp (mentor, implicit)
MFC after: 3 days
Committed at: BSDCan 2008
|
|
|
|
|
|
|
| |
PR: usb/118741
Submitted by: Yuri <yuri at tsoft dot com>
Approved by: imp (mentor, implicit)
MFC after: 3 days
|
|
|
|
|
|
|
| |
are not initialized. This fixes a panic on sparc64 where calling
bus_dmamap_sync(9) on NULL DMA maps is fatal.
Approved by: sam
|
|
|
|
|
|
|
|
|
|
| |
Add support for the Apple USB Ethernet adapter.
Work around the "latch in at the first working PHY address hack",
that fails for this adapter because it returns 0xffff when reading
from lower PHY addresses. Also add more debugging printfs
Obtained from: OpenBSD
MFC After: 3 days
|
|
|
|
|
|
|
|
|
|
| |
o correct mapping of CCK rates to PLCP; was using nonstandard Ralink
values which just happened to also be used by Zydas (so went unnoticed)
o change ieee80211_plcp2rate api to take a phy type instead of a flag
that indicates ofdm/!ofdm
o update drivers to match (restore per-driver code to map rate->PLCP)
Reviewed by: sephe, weongyo, thompsa
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o add IEEE80211_C_STA capability to indicate sta mode is supported
(was previously assumed) and mark drivers as capable
o add ieee80211_opcap array to map an opmode to the equivalent capability bit
o move IEEE80211_C_OPMODE definition to where capabilities are defined so it's
clear it should be kept in sync (on future additions)
o check device capabilities in clone create before trying to create a vap;
this makes driver checks unneeded
o make error codes return on failed clone request unique
o temporarily add console printfs on clone request failures to aid in
debugging; these will move under DIAGNOSTIC or similar before release
|
|
|
|
|
| |
Submitted by: Kris Moore <kris pcbsd com>
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Limit grabbing the lock to SIOCSIFFLAGS.
- Move ieee80211_start_all() to SIOCSIFFLAGS.
- Remove SIOCSIFMEDIA as it is not useful.
- Limit ether_ioctl to only SIOCGIFADDR. SIOCSIFADDR and SIOCSIFMTU have no
affect as there is no input/output path in the vap parent. The vap code
will handle the reinit of the mac address changes.
- Split off ndis_ioctl_80211 as it was getting too different to wired devices.
This fixes a copyout while locked and a lock recursion.
Reviewed by: sam
|
|
|
|
|
|
|
| |
Reviewed by: imp
(RELENG-7) Tested by: Oliver Herold <oliver@akephalos.de>
PR: usb/121052
MFC after: 1 month
|
|
|
|
|
| |
PR: 123148
Submitted by: Bill Squire
|
|
|
|
| |
Submitted by: William Grzybowski
|
|
|
|
| |
Noticed by: Paul B. Mahol
|
|
|
|
|
|
|
|
|
|
|
| |
Note this includes changes to all drivers and moves some device firmware
loading to use firmware(9) and a separate module (e.g. ral). Also there
no longer are separate wlan_scan* modules; this functionality is now
bundled into the wlan module.
Supported by: Hobnob and Marvell
Reviewed by: many
Obtained from: Atheros (some bits)
|
|
|
|
|
|
| |
Tested on HTC TyTN.
Submitted by: Alexander Logvinov <ports@logvinov.com>
|
|
|
|
|
|
| |
MFC after: 2 weeks
Reported by: Ilya Bakulin <webmaster@kibab.com>
Approved by: imp, cognet
|
|
|
|
|
|
|
| |
better grep-compliance and to standardize with the rest of the kernel.
Reviewed by: jhb
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
I've taken a slightly different approach than is used with the ICH8 controllers
in that each controller is not identified individually (eg USB A, USB B, etc).
Instead I've given then same description to each one even though the device ID
differs. This can easily be changed if desired, or ICH8 (and any others using
that approach) can be made to work as this does.
|
|
|
|
|
|
| |
PR: usb/122610
Submitted by: Randi Harper <randi@freebsdgirl.com>
MFC after: 3 days
|
|
|
|
|
|
| |
MFC after: 1 week
PR: usb/116574
Submitted by: Dave Grochowski malus.x of gmail
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
| |
derived drivers can use it
Submitted by: Jared Go
MFC after: 3 weeks
|
|
|
|
|
| |
Submitted by: Jared Go
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
work on architectures with a write-back cache as the PIO writes end up
in the cache which the sync(BUS_DMASYNC_POSTREAD) in usb_transfer_complete
then discards; compensate in the xfer methods that do PIO by pushing the
writes out of the cache before usb_transfer_complete is called.
This fixes USB on xscale and likely other places.
Sponsored by: hobnob
Reviewed by: cognet, imp
MFC after: 1 month
|
|
|
|
|
|
|
|
|
| |
all uses) involve a read but usbd_start_transfer only does a PREWRITE; change
this to BUS_DMASYNC_PREREAD | BUS_DMASYNC_PREWRITE as I'm not sure if any
users do write+read.
Reviewed by: cognet, imp
MFC after: 1 month
|
|
|
|
| |
- Add the Corega CG-WLUSB2GPX
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
monitor mode. This solves a problem that sometimes mangled frames
are passed.
Submitted by: Werner Backes <werner_at_bit-1.de>
Tested by: Werner Backes <werner_at_bit-1.de>
PR: kern/121608
Approved by: thompsa (mentor)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
hangs (one at boot, one at shutdown) in recent machines. First, only try
to take ownership of the EHCI controller if the BIOS currently owns the
controller. On a HP DL160 G5, the machine hangs when we try to take
ownership. Second, don't bother trying to give up ownership of the
controller during shutdown. It's not strictly required and a Dell DCS S29
hangs on shutdown after the config write.
Both of these changes match the behavior of the Linux EHCI driver. I also
think both of these hangs are caused by bugs in the BIOS' SMM handler
causing it to get stuck in an infinite loop in SMM.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
accept a mouse using the boot subclass. Instead, restore the original
hid_is_collection() test and fallback to testing the interface class,
subclass, and protocol if that fails.
MFC after: 1 week
PR: usb/118670
|
|
|
|
|
|
|
| |
as the buffer pointer in the call to axe_cmd(). This is needed to make
the code work on big-endian machines.
Ok'd: imp@
|
|
|
|
|
|
| |
commit :-/ Quickly fix before things get broken...
Pointyhat to: me
|
|
|
|
|
|
|
|
| |
CP2101/CP2102 based USB serial adapters.
Reviewed by: imp, emaste
Obtained from: OpenBSD
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
than rely on the lockmgr support [1]:
* bump the waiters only if the interlock is held
* let brelvp() return the waiters count
* rely on brelvp() instead than BUF_LOCKWAITERS() in order to check
for the waiters number
- Remove a namespace pollution introduced recently with lockmgr.h
including lock.h by including lock.h directly in the consumers and
making it mandatory for using lockmgr.
- Modify flags accepted by lockinit():
* introduce LK_NOPROFILE which disables lock profiling for the
specified lockmgr
* introduce LK_QUIET which disables ktr tracing for the specified
lockmgr [2]
* disallow LK_SLEEPFAIL and LK_NOWAIT to be passed there so that it
can only be used on a per-instance basis
- Remove BUF_LOCKWAITERS() and lockwaiters() as they are no longer
used
This patch breaks KPI so __FreBSD_version will be bumped and manpages
updated by further commits. Additively, 'struct buf' changes results in
a disturbed ABI also.
[2] Really, currently there is no ktr tracing in the lockmgr, but it
will be added soon.
[1] Submitted by: kib
Tested by: pho, Andrea Barberio <insomniac at slackware dot it>
|
|
|
|
|
|
|
| |
PR: usb/120980
Submitted by: Christophe Etcheverry <cetcheve at gmail dot com>
MFC after: 3 days
Approved by: imp (mentor, implicit for trivial changes)
|
| |
|
|
|
|
|
|
|
|
| |
Now ucom kernel module can unload properly.
o Update copyright year.
PR: usb/88966
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
PR: usb/95173
Submitted by: Goegele Hannes <diazepam@gmx.net>
Ben Kelly <bkelly at vadev dot org>
Tested by: blackend
Approved by: imp (mentor, blanket for simple patches)
X-MFC-After: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With write-allocate cache we get into the following scenario:
1. data has been updated in the memory by the USB HC, but
2. D-cache holds an un-flushed value of it
3. when affected cache line is being replaced, the old (un-flushed) value is
flushed and overwrites the newly arrived
This is possible due to how write-allocate works with virtual caches (ARM for
example).
In case of USB transfers it leads to fatal tags discrepancies in umass(4)
operation, which look like the following:
umass0: Invalid CSW: tag 1 should be 2
(probe0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR
(probe0:umass-sim0:0:0:0): Retrying Command
umass0: Invalid CSW: tag 1 should be 3
(probe0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR
(probe0:umass-sim0:0:0:0): Retrying Command
umass0: Invalid CSW: tag 1 should be 4
(probe0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR
(probe0:umass-sim0:0:0:0): Retrying Command
umass0: Invalid CSW: tag 1 should be 5
(probe0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR
(probe0:umass-sim0:0:0:0): Retrying Command
umass0: Invalid CSW: tag 1 should be 6
(probe0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR
(probe0:umass-sim0:0:0:0): error 5
(probe0:umass-sim0:0:0:0): Retries Exausted
To eliminate this, a BUS_DMASYNC_PREREAD sync operation is required in
usbd_start_transfer().
Credits for nailing this down go to Grzegorz Bernacki gjb AT semihalf DOT com.
Reviewed by: imp
Approved by: cognet (mentor)
|
|
|
|
|
|
|
| |
- Include lock.h in lockmgr.h as nested header in order to safely use
LOCK_FILE and LOCK_LINE. As long as this code will be replaced soon
we can tollerate for a while this namespace pollution even if the real
fix would be to let lockmgr() depend by lock.h as a separate header.
|
|
|
|
| |
sys/lock.h.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
standard rates.
Obtained from OpenBSD
src/sys/dev/usb/uftdi.c 1.29
src/sys/dev/usb/uftdireg.h 1.11
OpenBSD revisions noted by: ticso, on hackers
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Remove the "thread" argument from the lockmgr() function as it is
always curthread now
- Axe lockcount() function as it is no longer used
- Axe LOCKMGR_ASSERT() as it is bogus really and no currently used.
Hopefully this will be soonly replaced by something suitable for it.
- Remove the prototype for dumplockinfo() as the function is no longer
present
Addictionally:
- Introduce a KASSERT() in lockstatus() in order to let it accept only
curthread or NULL as they should only be passed
- Do a little bit of style(9) cleanup on lockmgr.h
KPI results heavilly broken by this change, so manpages and
FreeBSD_version will be modified accordingly by further commits.
Tested by: matteo
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now, lockmgr() function can only be called passing curthread and the
KASSERT() is upgraded according with this.
In order to support on-the-fly owner switching, the new function
lockmgr_disown() has been introduced and gets used in BUF_KERNPROC().
KPI, so, results changed and FreeBSD version will be bumped soon.
Differently from previous code, we assume idle thread cannot try to
acquire the lockmgr as it cannot sleep, so loose the relative check[1]
in BUF_KERNPROC().
Tested by: kris
[1] kib asked for a KASSERT in the lockmgr_disown() about this
condition, but after thinking at it, as this is a well known general
rule, I found it not really necessary.
|
|
|
|
| |
Approved by: thompsa (mentor)
|