| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Submitted by: PseudoCylon <moonlightakkiy@yahoo.ca>
MFC after: 14 days
|
|
|
|
|
|
| |
Try to auto-detect keyboards which should use the BOOT protocol.
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
| |
setting (either default or if supported as set by SIOCSIFFIB, e.g.
from ifconfig).
Submitted by: Alexander V. Chernikov (melifaro ipfw.ru)
Reviewed by: julian
MFC after: 2 weeks
|
|
|
|
|
|
| |
in general.
MFC after: 1 week
|
|
|
|
| |
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
latter.
It appears that the addition to uath(4) came in through PR kern/135009,
which had tested another device, the SMCWUSBTG2, successfully with uath(4)
and included the SMCWUSBG as it "has the same chipset". I can find no
other evidence that these two do actually share the same chipset. Moreover,
Linux treats the SMCWUSBG as a zyd(4) device also.
This reverts r223537.
Discussed with: hselasky, kevlo
MFC after: 1 week
|
|
|
|
| |
MFC after: 14 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
| |
- Update bus_auto.conf accordingly.
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
dynamically loaded device drivers get a chance to run their event hooks.
- Decouple the USB suspend and resume lock from witness. It produces some
false warnings due to reusing the lock name among multiple devices.
MFC after: 3 days
|
|
|
|
|
|
| |
- Add checks for configuration and interface index.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
| |
is now required by bus_autoconf.
- Allow interface class matching even if device class is vendor specific.
- Update bus_autoconf tool to not generate system and subsystem match lines
for the nomatch event.
PR: misc/157903
MFC after: 14 days
|
|
|
|
|
|
|
|
|
|
|
|
| |
sorted according to the mode which they support:
host, device or dual mode
- Add generic tool to extract these data:
tools/bus_autoconf
Discussed with: imp
Suggested by: Robert Millan <rmh@debian.org>
PR: misc/157903
MFC after: 14 days
|
|
|
|
| |
MFC after: 7 days
|
|
|
|
|
|
|
| |
- Add basic template support for USB 3.0
- Export definition of template sysctl numbers through usb_ioctl.h
MFC after: 7 days
|
|
|
|
|
|
| |
PR: usb/158142
Submitted by: Robert Millan <rmh debian.org>
MFC after: 1 week
|
|
|
|
|
| |
Submitted by: Luiz Gustavo S. Costa <lgcosta@pfsense.org>
MFC after: 7 days
|
|
|
|
| |
MFC after: 14 days
|
|
|
|
|
|
|
|
|
| |
High-speed USB HUB by resetting the transaction translator (TT)
before trying re-enumeration. Also when clear-stall fails multiple times
try a re-enumeration.
Suggested by: Trevor Blackwell
MFC after: 14 days
|
|
|
|
|
| |
Suggested by: YongHyeon PYUN
MFC after: 7 days
|
|
|
|
|
|
|
| |
PHY. Newer models seem to use different LED mode that requires
enabling both GPIO1 and GPIO2.
Tested by: marcel
|
|
|
|
|
| |
Submitted by: Lev Serebryakov, lev @
MFC after: 14 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This brings USB bus more in line with how newbus is supposed to be used.
Also, because of the two-pass probing the following message was produced
by devd in default configuration when almost any USB device was
connected:
Unknown USB device: vendor <> product <> bus <>
This should be fixed now.
Note that many USB device drivers pass some information from probe
method to attach method via ivars. For this to continue working we rely
on the fact that the subr_bus code calls probe method of a winning driver
again before calling its attach method in the case where multiple
drivers claim to support a device. This is done because device
description is set in successful probe methods and we want to get a correct
device description from a winning driver. So now this logic is re-used
for setting ivars too.
Reviewed by: hselasky
MFC after: 1 month
|
|
|
|
|
|
|
| |
to <dev/pci/pcireg.h>.
Reviewed by: hselasky
MFC after: 3 days
|
|
|
|
|
| |
Submitted by: Jim Bryant
MFC after: 3 days
|
|
|
|
| |
Add PID for Simtec Electronics EntropyKey, a hardware random number generator.
|
|
|
|
|
|
| |
be needed any more.
MFC after: 7 days
|
|
|
|
|
| |
Submitted by: Dmitry Luhtionov
MFC after: 7 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(reporting IFM_LOOP based on BMCR_LOOP is left in place though as
it might provide useful for debugging). For most mii(4) drivers it
was unclear whether the PHYs driven by them actually support
loopback or not. Moreover, typically loopback mode also needs to
be activated on the MAC, which none of the Ethernet drivers using
mii(4) implements. Given that loopback media has no real use (and
obviously hardly had a chance to actually work) besides for driver
development (which just loopback mode should be sufficient for
though, i.e one doesn't necessary need support for loopback media)
support for it is just dropped as both NetBSD and OpenBSD already
did quite some time ago.
- Let mii_phy_add_media() also announce the support of IFM_NONE.
- Restructure the PHY entry points to use a structure of entry points
instead of discrete function pointers, and extend this to include
a "reset" entry point. Make sure any PHY-specific reset routine is
always used, and provide one for lxtphy(4) which disables MII
interrupts (as is done for a few other PHYs we have drivers for).
This includes changing NIC drivers which previously just called the
generic mii_phy_reset() to now actually call the PHY-specific reset
routine, which might be crucial in some cases. While at it, the
redundant checks in these NIC drivers for mii->mii_instance not being
zero before calling the reset routines were removed because as soon
as one PHY driver attaches mii->mii_instance is incremented and we
hardly can end up in their media change callbacks etc if no PHY driver
has attached as mii_attach() would have failed in that case and not
attach a miibus(4) instance.
Consequently, NIC drivers now no longer should call mii_phy_reset()
directly, so it was removed from EXPORT_SYMS.
- Add a mii_phy_dev_attach() as a companion helper to mii_phy_dev_probe().
The purpose of that function is to perform the common steps to attach
a PHY driver instance and to hook it up to the miibus(4) instance and to
optionally also handle the probing, addition and initialization of the
supported media. So all a PHY driver without any special requirements
has to do in its bus attach method is to call mii_phy_dev_attach()
along with PHY-specific MIIF_* flags, a pointer to its PHY functions
and the add_media set to one. All PHY drivers were updated to take
advantage of mii_phy_dev_attach() as appropriate. Along with these
changes the capability mask was added to the mii_softc structure so
PHY drivers taking advantage of mii_phy_dev_attach() but still
handling media on their own do not need to fiddle with the MII attach
arguments anyway.
- Keep track of the PHY offset in the mii_softc structure. This is done
for compatibility with NetBSD/OpenBSD.
- Keep track of the PHY's OUI, model and revision in the mii_softc
structure. Several PHY drivers require this information also after
attaching and previously had to wrap their own softc around mii_softc.
NetBSD/OpenBSD also keep track of the model and revision on their
mii_softc structure. All PHY drivers were updated to take advantage
as appropriate.
- Convert the mebers of the MII data structure to unsigned where
appropriate. This is partly inspired by NetBSD/OpenBSD.
- According to IEEE 802.3-2002 the bits actually have to be reversed
when mapping an OUI to the MII ID registers. All PHY drivers and
miidevs where changed as necessary. Actually this now again allows to
largely share miidevs with NetBSD, which fixed this problem already
9 years ago. Consequently miidevs was synced as far as possible.
- Add MIIF_NOMANPAUSE and mii_phy_flowstatus() calls to drivers that
weren't explicitly converted to support flow control before. It's
unclear whether flow control actually works with these but typically
it should and their net behavior should be more correct with these
changes in place than without if the MAC driver sets MIIF_DOPAUSE.
Obtained from: NetBSD (partially)
Reviewed by: yongari (earlier version), silence on arch@ and net@
|
|
|
|
|
| |
PR: kern/144642
Submitted by: Arthur Hartwig <a_hartwig at fastmaildot fm>
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
will generate a short terminated USB transfer if
the maximum NCM frame size is greater than what
the driver can handle.
Reported by: Matthias Benesch
MFC after: 7 days
Approved by: thompsa (mentor)
|
|
|
|
|
|
| |
Reported by: Mike Tancsa
MFC after: 3 days
Approved by: thompsa (mentor)
|
|
|
|
|
|
|
|
| |
bus driver at detach, hence ehci_detach() does exactly this since r199718.
Submitted by: Luiz Otavio O Souza
MFC after: 7 days
Approved by: thompsa (mentor)
|
|
|
|
|
|
|
|
|
|
|
| |
SCSI status errors to CAM (that was wrong, as it too often turned retriable
wire errors into non-retriable REQUEST SENSE errors), do it only for STALL
errors on control pipe of the CBI devices. STALL on control pipe is just
a one of the ways to report error for CBI devices.
PR: usb/150401, usb/154593.
Reviewed by: hselasky
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
stopped rapidly in succession.
Reported by: J.R. Oldroyd
MFC after: 7 days
Approved by: thompsa (mentor)
|
|
|
|
|
|
| |
Submitted by: Luiz Otavio O Souza
MFC after: 7 days
Approved by: thompsa (mentor)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Add more fields for USB device and host mode
- Add more information to USB PF header so that decoding
can easily be done by software analyzer tools like
Wireshark.
- Optimise usbdump to display USB streams in text format
more efficiently.
- Software using USB PF must be recompiled after
this commit, due to structure changes.
MFC after: 7 days
Approved by: thompsa (mentor)
|
|
|
|
| |
- Make functions static
|
|
|
|
|
|
| |
Reported by: Luiz Otavio O Souza
MFC after: 14 days
Approved by: thompsa (mentor)
|
|
|
|
| |
While here, add the SMC SMCWUSB-G
|
|
|
|
|
|
| |
Reported by: Garrett Cooper
MFC after: 14 days
Approved by: thompsa (mentor)
|
|
|
|
|
|
| |
Reported by: gavin
MFC after: 14 days
Approved by: thompsa (mentor)
|
|
|
|
|
|
|
|
|
|
|
|
| |
report descriptor information, sysctl utility
will show it for us.
- Modify sysctl node description to make it more
understanable.
Found by: Alexander Best <arundel@freebsd.org>
Submitted by: Eygene Ryabinkin <rea@freebsd.org>
MFC after: 14 days
Approved by: thompsa (mentor)
|
|
|
|
|
|
|
|
| |
value is updated after that we read it in the queue-head. This patch can
fix problems with BULK timeouts. The issue was found on a Nvidia chipset.
MFC after: 14 days
Approved by: thompsa (mentor)
|
|
|
|
|
| |
MFC after: 14 days
Approved by: thompsa (mentor)
|
|
|
|
|
|
| |
PR: usb/155229
Submitted by: Yoshiaki UCHIKAWA
MFC after: 1 week
|