src-test2/etc/devd, branch release/8.4.0FreeBSD source treehttps://cgit-dev.freebsd.org/src-test2/atom?h=release%2F8.4.02012-12-29T12:33:32ZMFC r235725, r239056, r241089, r243661 and r244252:2012-12-29T12:33:32ZHans Petter Selaskyhselasky@FreeBSD.org2012-12-29T12:33:32Zurn:sha1:824a0dd6f6c9b07dc15540c2d2fd12493457567c
Regenerate usb.conf
MFC r231575:2012-02-14T06:42:43ZHans Petter Selaskyhselasky@FreeBSD.org2012-02-14T06:42:43Zurn:sha1:571cffd26d033b163ab43bc8bfd50ecf3d03ad0b
Update /etc/devd/usb.conf
MFC r226903, r225777, r226221 and r226534:2011-11-01T08:24:01ZHans Petter Selaskyhselasky@FreeBSD.org2011-11-01T08:24:01Zurn:sha1:8992334c22a5ed5c27b5515dd678cff613431c9b
Add some new USB device IDs and some USB device quirks.
Improve the USB mass storage auto quirk detection.
PR: usb/161798, usb/160911
Merge r223566 from head:2011-10-12T21:38:48ZGavin Atkinsongavin@FreeBSD.org2011-10-12T21:38:48Zurn:sha1:3e860e371e92ffacd22d0d1fdf014cce88672c85
The SMCWUSBG is a zyd(4) device, not an uath(4) device. Remove from
the 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 is a partial merge, as it appears that the kernel parts of r223566
were already merged in r223605.
Discussed with: hselasky, kevlo
MFC r223486, r223489, r223490, r223511, r223512, r223513,2011-06-27T20:59:43ZHans Petter Selaskyhselasky@FreeBSD.org2011-06-27T20:59:43Zurn:sha1:2ef8f2565302955ae82b8b0e3d73fb11a550009e
r223515, r223518, r223519, r223521, r223534, r223535,
r223536, r223537, r223538, r223543, r223288, r223604 and r223566:
- Export all USB device ID's in so-called sections.
- Fix duplicate occurence of a USB ID in if_urtw and if_zyd.
- Add new tool to autogenerate nomatch entries for devd.
- Add new usb.conf file to auto-load USB drivers.
- Fix some issues related to the nomatch notifications.
PR: misc/157903
MFC r207020, r207027, r207072.2010-04-29T22:40:12ZAndrew Thompsonthompsa@FreeBSD.org2010-04-29T22:40:12Zurn:sha1:176b25ad5ca2d289110200e80116d88b213bca1b
Change usb devd events from fake attach to a notify. The ugen device is not a
proper device_t so it faked the devctl event to appear like one, this is now a
notify which allows more information to be passed.
We notify for both the device attach/detach and for each usb interface. A devd
rule can now match on the interface properties, including composite devices
which may have a uvideo interface and also usound and possibly uhid too.
An example to match a umass device with a scsi subclass and BBB protocol would be
notify 100 {
match "system" "USB";
match "subsystem" "INTERFACE";
match "type" "ATTACH";
match "intclass" "0x08";
match "intsubclass" "0x06";
match "intprotocol" "0x50";
action ...
};
The old attach devctl event has been retained for the moment to make merging to
8.1 easier. This was never compatible with 7.x or earlier due to the ugen regex
change needed.
Document the new USB notification types.
MFC r202610:2010-04-17T23:14:06ZWeongyo Jeongweongyo@FreeBSD.org2010-04-17T23:14:06Zurn:sha1:6fa37bd64a55b4493b4aa8769325f3a0fa9e6706
adds a hardware specific configuration file for uath(4).
Pointed by: sam
Reviewed by: imp, thompsa
revert r1873432009-01-16T20:42:43ZSam Lefflersam@FreeBSD.org2009-01-16T20:42:43Zurn:sha1:971e1ffd1d9113b8adb9233cfc85e487029e6632add FCC4 SKU to expose Public Safety Band (PSB) frequencies; this is2009-01-16T20:40:50ZSam Lefflersam@FreeBSD.org2009-01-16T20:40:50Zurn:sha1:bdb8f7ad514a25ab72b163d84b25aad1a07750ad
modeled after the Atheros SKU of the same name
Move another block of ASUS events to devd/asus.conf that were missed in r1862492008-12-23T15:47:31ZAndrew Thompsonthompsa@FreeBSD.org2008-12-23T15:47:31Zurn:sha1:8c2b8f8d4978bd45e7af8adc190d5ec7b74ac352