Re: ugenctl for attaching USB devices to ugen instead of their specific driver
On Sun, December 6, 2015 22:10, Ian Darwin wrote: > > > On 2015-12-06 12:23 PM, Stuart Henderson wrote: >> On 2015/12/06 06:02, Mickael Torres wrote: >>> Hello, >>> >>> This is a kernel patch plus a utility called ugenctl I use to allow >>> selected USB devices to attach as ugen(4) instead of their more specific >>> driver. My use case is a Microchip "PICkit 2 Microcontroller Programmer" >>> that attaches as uhid(4), but the command line utility pk2cmd wants a >>> udev(4) device. There maybe are some other use cases. >> If a device is generally pointless with uhid, we can just knock it >> out completely in the kernel, see the UQ_BAD_HID mechanism. I think this >> applies to your device. >> >> The bigger problem is "dual use" devices; e.g. some want UPS to attach >> to upd(4), others want ugen(4) for use with NUT/apcupsd. Your code is >> partially useful for these, but because it just changes things at attach, >> won't survive a reboot - if it could instead force a device to detach >> and reattach to ugen it would help a lot more cases. >> > One fairly common (I believe) use is with USB printers that attach as ulpt > but CUPS wants as ugen - for these, this is useful as it stands - just > run it > from rc. Do people want their UPS to sometimes be upd and other times be > a ugen? I can see there might be "I want to change this now" cases, but I > suspect the majority could be done once at each boot and be quite useful. > > I guess no. I have to configure kernel after every update to make my ups attach as ugen and not upd. So this tool would be useful for me with a config file so I can configure it once and don't bother on every reboot/update.
Re: sync bioctl manual
On Thu, October 22, 2015 00:45, Jason McIntyre wrote: > On Thu, Oct 22, 2015 at 12:35:53AM +0300, Kirill Bychkov wrote: >> On Thu, October 22, 2015 00:16, Jason McIntyre wrote: >> > On Wed, Oct 21, 2015 at 11:19:12PM +0300, Kirill Bychkov wrote: >> >> Hi! >> >> After halex@ removed a restriction to use passfile for creation of >> >> crypto volume, man page wasn't changed to explain new behaviour. >> >> OK? >> >> >> > >> > why not just remove the sentence? if you really want to keep it, i >> >> An idea was to explicitly tell about this possibility because people still >> may >> think it's forbidden. >> > > yes, i see that. but it cuts both ways - in a release or two, no one > will remember we've put this there, and it will sound odd. > > i'd just zap it. Makes sense. > jmc > >> > suggest using "can" instead of "could also". >> >> I'll change it, if the line will remain in manual. >> >> > >> > jmc >> > Index: bioctl.8 === RCS file: /cvs/src/sbin/bioctl/bioctl.8,v retrieving revision 1.97 diff -u -r1.97 bioctl.8 --- bioctl.812 Sep 2015 14:21:25 - 1.97 +++ bioctl.822 Oct 2015 08:10:10 - @@ -260,7 +260,6 @@ .It Fl p Ar passfile Passphrase file used when crypto volumes are brought up. This file must be root owned and have 0600 permissions. -This option cannot be used during the initial creation of the crypto volume. .It Fl r Ar rounds When creating an encrypted volume, specifies the number of iterations of the PBKDF2 algorithm used to convert a passphrase into a key.
sync bioctl manual
Hi! After halex@ removed a restriction to use passfile for creation of crypto volume, man page wasn't changed to explain new behaviour. OK? Index: bioctl.8 === RCS file: /cvs/src/sbin/bioctl/bioctl.8,v retrieving revision 1.97 diff -u -r1.97 bioctl.8 --- bioctl.812 Sep 2015 14:21:25 - 1.97 +++ bioctl.821 Oct 2015 20:15:47 - @@ -260,7 +260,7 @@ .It Fl p Ar passfile Passphrase file used when crypto volumes are brought up. This file must be root owned and have 0600 permissions. -This option cannot be used during the initial creation of the crypto volume. +This option also could be used during the initial creation of the crypto volume. .It Fl r Ar rounds When creating an encrypted volume, specifies the number of iterations of the PBKDF2 algorithm used to convert a passphrase into a key
Re: sync bioctl manual
On Thu, October 22, 2015 00:16, Jason McIntyre wrote: > On Wed, Oct 21, 2015 at 11:19:12PM +0300, Kirill Bychkov wrote: >> Hi! >> After halex@ removed a restriction to use passfile for creation of >> crypto volume, man page wasn't changed to explain new behaviour. >> OK? >> > > why not just remove the sentence? if you really want to keep it, i An idea was to explicitly tell about this possibility because people still may think it's forbidden. > suggest using "can" instead of "could also". I'll change it, if the line will remain in manual. > > jmc > >> Index: bioctl.8 >> === >> RCS file: /cvs/src/sbin/bioctl/bioctl.8,v >> retrieving revision 1.97 >> diff -u -r1.97 bioctl.8 >> --- bioctl.8 12 Sep 2015 14:21:25 - 1.97 >> +++ bioctl.8 21 Oct 2015 20:15:47 - >> @@ -260,7 +260,7 @@ >> .It Fl p Ar passfile >> Passphrase file used when crypto volumes are brought up. >> This file must be root owned and have 0600 permissions. >> -This option cannot be used during the initial creation of the crypto >> volume. >> +This option also could be used during the initial creation of the crypto >> volume. >> .It Fl r Ar rounds >> When creating an encrypted volume, specifies the number of iterations of >> the PBKDF2 algorithm used to convert a passphrase into a key >> > >
one more fxp card
Hi. I've ordered two card from ebay and they are working fine on amd64. OK to commit? Index: fxp.4 === RCS file: /cvs/src/share/man/man4/fxp.4,v retrieving revision 1.45 diff -u -r1.45 fxp.4 --- fxp.4 15 Jan 2015 20:37:36 - 1.45 +++ fxp.4 26 Jun 2015 22:30:46 - @@ -63,6 +63,8 @@ Intel PRO/100 M .It Intel PRO/100 S +.It +Matrox NS-QNIC Quad-Port PCI .El .Pp The following media types and options (as given to
Re: samba4 slow startup, shared libs?
On Fri, June 5, 2015 14:27, Mark Kettenis wrote: Date: Fri, 5 Jun 2015 11:15:38 +0100 From: Stuart Henderson st...@openbsd.org net/samba4 is in the ports tree but not currently enabled in the build, we're still only using samba 3.x for various reasons, but unfortunately samba 3 is getting decreasingly useful as more Windows setups move to newer versions. One of the issues is that startup of samba4 on OpenBSD is very slow indeed, seemingly before control is transferred to the program. From the LD_DEBUG output with timestamps (using the very handy ts(1) from moreutils): # LD_DEBUG=1 smbd -D 21 | ts %.s ..snip.. 1433498513.546306 examining: '/usr/local/lib/libhogweed.so.1.1' 1433498513.546323 loading: libnettle.so.1.2 required by /usr/local/lib/libhogweed.so.1.1 1433498513.546339 loading: libgmp.so.9.0 required by /usr/local/lib/libhogweed.so.1.1 1433498513.546354 linking dep /usr/local/lib/libnettle.so.1.2 as child of /usr/local/lib/libhogweed.so.1.1 1433498513.546370 linking dep /usr/local/lib/libgmp.so.9.0 as child of /usr/local/lib/libhogweed.so.1.1 1433498513.546386 examining: '/usr/local/lib/libgmp.so.9.0' 1433498584.125659 flags /usr/libexec/ld.so = 0x0 1433498584.125783 obj /usr/libexec/ld.so has smbd as head 1433498584.149165 relocation took 0.023504 1433498584.149215 StartEnd Type Open Ref GrpRef Name 1433498584.149249 04bec650 04bec691 exe 10 0 smbd 1433498584.149272 04c19b74e000 04c19bb6 rlib 0107 0 /usr/lib/libpthread.so.19.0 1433498584.149293 04c18f3df000 04c18f812000 rlib 075 0 /usr/local/lib/libsamba-util.so.0.0 ..snip.. - a 74 second delay after examining: '/usr/local/lib/libgmp.so.9.0'. Does anyone have suggestions for finding out what's going on here? Full text snipped from the above is at http://junkpile.org/samba4-lddebug.txt My first guess would have been that it is spending a lot of time on initial relocations. But the line: 1433498584.149165 relocation took 0.023504 pretty much rules that out. My suggestion would be to add a few more DL_DEB() statements inside of ld.so/loader.c:_dl_boot(), starting just after the _dl_load_dep_libs() call in that function and try to narrow it down. Vadim made an attempt to improve things. May be this can share some light. http://marc.info/?l=openbsd-portsm=140051145330799w=2 http://marc.info/?l=openbsd-portsm=140078438824316w=2 I've searched old mails and found that 4.0.3 was starting with normal speed. I have ldd output for 4.0.3 and 4.0.17 to compare.
Re: autoinstall(8) tweaks
On Tue, April 7, 2015 13:02, Alex Wilson wrote:
On the topic of local tweaks to autoinstall, I was trying to use it for
a bunch of blades with very limited disk the other day, and I really
wanted to make them just create a single slice for / and some swap.
I ended up doing:
--- a/distrib/amd64/common/install.md
+++ b/distrib/amd64/common/install.md
@@ -125,7 +125,11 @@ start of the disk, NOT the start of the OpenBSD MBR
partition.
__EOT
- disklabel $FSTABFLAG $_f -E $_disk
+ if _autorespond disklabel $_def; then
+ print $resp | disklabel $FSTABFLAG $_f -E $_disk
+ else
+ disklabel $FSTABFLAG $_f -E $_disk
+ fi
}
md_congrats() {
So that then I could put
Use (W)hole disk, use the = W
Use (A)uto layout, (E)dit auto layout, or create (C)ustom layout = C
disklabel = D\na b\n\n4g\n\na a\n\n\n\n/\np\nq\n
in my install.conf
Would you be interested in a patch to add this on all the platforms? Or
some other nicer way of doing it? (should it be Disklabel rather than
little d, for consistency?)
I like the idea, because previously I had to build custom bsd.rd with tweaked
disklabel
to disable autopartitioning and just create one partition.
On 06/04/15 23:48, Nathanael Rensen wrote:
A couple of autoinstall(8) tweaks that I find useful.
I find it convenient to be able to specify a path to the response file.
I also prefer to use the DHCP supplied hostname rather than the MAC
address.
Index: install.sub
===
RCS file: /cvs/src/distrib/miniroot/install.sub,v
retrieving revision 1.829
diff -u -p -r1.829 install.sub
--- install.sub 5 Apr 2015 12:37:14 - 1.829
+++ install.sub 6 Apr 2015 13:33:02 -
@@ -304,7 +304,7 @@ retrap() {
# Fetch response file for autoinstall.
get_responsefile() {
-local _rf _ifdev _mac _mode _server _lf
+local _rf _ifdev _mac _mode _server _lf _path
action=
[[ -f /auto_upgrade.conf ]] _rf=/auto_upgrade.conf _mode=upgrade
@@ -328,16 +328,18 @@ get_responsefile() {
[[ -n $_ifdev ]] dhclient $_ifdev || break
_lf=/var/db/dhclient.leases.$_ifdev
_server=$(sed /^ *next-server /!d;s///;s/;$//;q $_lf)
-_mode=$(sed -E '/^ *filename
auto_(install|upgrade);$/!d;s//\1/;q' $_lf)
+_mode=$(sed -E '/^ *filename
(.*\/)?auto_(install|upgrade);$/!d;s//\2/;q' $_lf)
+_path=$(sed -E '/^ *filename (.*\/)[^/]+;$/!d;s//\1/;q' $_lf)
hostname $(sed -E '/^ *option host-name (.*);$/!d;s//\1/;q'
$_lf)
done
# Fetch response file if server and mode are known, otherwise tell which
-# one was missing. First try to fetch mac-mode.conf, then mode.conf.
+# one was missing. First try to fetch mac-mode.conf, then
+# hostname-mode.conf, and finally mode.conf.
if [[ -n $_server -n $_mode ]]; then
_mac=$(ifconfig $_ifdev | sed 's/.*lladdr \(.*\)/\1/p;d')
-for _rf in {$_mac-,}$_mode; do
-_url=http://$_server/$_rf.conf
+for _rf in {$_mac-,$(hostname -s)-,}$_mode; do
+_url=http://$_server/$_path$_rf.conf
echo Fetching $_url
if ftp -Vo /ai.$_mode.conf $_url 2/dev/null; then
action=$_mode
Index: autoinstall.8
===
RCS file: /cvs/src/share/man/man8/autoinstall.8,v
retrieving revision 1.11
diff -u -p -r1.11 autoinstall.8
--- autoinstall.823 Oct 2014 21:33:21 - 1.11
+++ autoinstall.86 Apr 2015 13:31:22 -
@@ -47,22 +47,16 @@ It behaves as if the user selected '(A)u
always fetches the response file via the netboot interface.
.Ss Fetching the response file
.Nm
-uses HTTP to fetch one of the files
-.Pa install.conf
-or
-.Ar MAC_address Ns - Ns Pa install.conf
-for install answers, or one of
-.Pa upgrade.conf
-or
-.Ar MAC_address Ns - Ns Pa upgrade.conf
-for upgrade answers.
-The URL used to fetch the file is constructed from information provided in
-the
+uses HTTP to fetch a response file which provides answers to
+install or upgrade questions.
+The URL used to fetch the response file is constructed from
+information provided in the
.Xr dhcpd.conf 5
-statements
-.Ic next-server
+.Ic next-server ,
+.Ic filename
and
-.Ic filename .
+.Ic host-name
+options.
If the
.Ar filename
is
@@ -71,6 +65,7 @@ then the URLs tried are, in order:
.Sm off
.Bd -unfilled -offset indent
.No http:// Ar next-server No / Ar MAC_address No -install.conf
+.No http:// Ar next-server No / Ar host-name No -install.conf
.No http:// Ar next-server No /install.conf
.Ed
.Sm on
@@ -79,7 +74,7 @@ where
.Ar MAC_address
is a string of six hex octets separated by colons
representing the MAC
-address of the
more airports
Hi. This patch adds/fixes/extends airport data for some exUSSR airports I've been to. OK? Index: share/misc/airport === RCS file: /cvs/src/share/misc/airport,v retrieving revision 1.47 diff -u -r1.47 airport --- share/misc/airport 7 Jan 2015 16:08:50 - 1.47 +++ share/misc/airport 11 Jan 2015 08:18:53 - @@ -11,7 +11,9 @@ AAA:Anaa, Anaa, French Polynesia AAE:Rabah Bitat, Annaba, Algeria AAL:Aalborg, Denmark +AAQ:Vityazevo, Anapa, Russia AAR:Aarhus, Aarhus, Denmark +ABA:Abakan, Russia ABE:Lehigh Valley International, Pennsylvania, USA ABI:Abilene Regional, Abilene, Texas, USA ABJ:Port Bouet, Abidjan, Cote d'ivoire @@ -39,6 +41,7 @@ ADQ:Kodiak, Alaska, USA ADZ:Gustavo Rojas Pinilla International, San Andres Island, Colombia AEP:Jorge Newberry, Buenos Aires, Argentina +AER:Sochi, Russia AES:Vigra, Aalesund, Norway AET:Allakaket, Alaska, USA AEX:Alexandria International, Louisiana, USA @@ -553,7 +556,7 @@ FRM:Fairmont Municipal, Minnesota, USA FRO:Floro, Norway FRS:Flores, Guatemala -FRU:Bishkek, Kyrgyzstan +FRU:Manas, Bishkek, Kyrgyzstan FSC:Figari, Corsica, France FSD:Joe Foss Field, Sioux Falls, South Dakota, USA FSM:Fort Smith Municipal, Arkansas, USA @@ -701,6 +704,7 @@ HRO:Boone County, Harrison, Arkansas, USA HSI:Hastings, Nebraska, USA HSV:Huntsville International, Alabama, USA +HTA:Chita, Russia HTI:Hamilton Island, Queensland, Australia HUF:Terre Haute Hulman Regional, Indiana, USA HUI:Hue, Vietnam @@ -845,7 +849,8 @@ KEP:Nepalganj, Nepal KER:Kerman, Iran KGC:Kingscote, South Australia, Australia -KGD:Kaliningrad, Russia +KGD:Khrabrovo, Kaliningrad, Russia +KGP:Kogalym, Russia KHE:Kherson International, Kherson, Ukraine KHH:Kaohsiung, Taiwan KHI:Karachi, Pakistan @@ -856,7 +861,7 @@ KIT:Kithira, Greece KIV:Kishinev, Moldova KIX:Kansai International, Osaka, Japan -KJA:Krasnojarsk, Russia +KJA:Yemelyanovo, Krasnoyarsk, Russia KKN:Hoeyburtmoen, Kirkenes, Norway KLO:Kalibo, Philippines KLR:Kalmar, Sweden @@ -894,7 +899,7 @@ KTR:Tindal, Katherine, Northern Territory, Australia KTW:Pyrzowice, Katowice, Poland KUA:Padang Geroda, Kuantan, Malaysia -KUF:Samara, Russia +KUF:Kurumoch, Samara, Russia KUL:Subang Kuala Lumpur International, Malaysia KUM:Yakushima, Japan KUN:Kaunas, Lithuania @@ -907,6 +912,7 @@ KWI:Kuwait International KWG:Kryvyi Rih International, Dnipropetrovs'k, Ukraine KWL:Guilin, China +KXK:Khurba, Komsomolsk-on-Amur, Russia KZI:Kozani, Greece KZN:Kazan, Russia KZS:Kastelorizo, Greece @@ -1043,6 +1049,7 @@ MCP:Macapa, Amapa, Brazil MCT:Seeb, Muscat, Oman MCW:Mason City, Iowa, USA +MCX:Uytash, Makhachkala, Dagestan, Russia MCY:Maroochydore, Sunshine Coast, Queensland, Australia MDC:Samratulang, Manado, Indonesia MDE:La Playas, Medellin, Colombia @@ -1120,6 +1127,7 @@ MRK:Marco Island, Florida, USA MRS:Marseille, France MRU:Sir Seewoosagur Ramgoolam Airport, Mauritius +MRV:Mineralnye Vody, Russia MRY:Monterey, California, USA MSJ:Misawa, Japan MSL:Muscle Shoals, Muscle Shoals / Florence / Sheffield, Alabama, USA @@ -1166,6 +1174,7 @@ NCL:Newcastle International, England, United Kingdom NDJ:N'djamena, N Djamena, Chad NEC:Necochea, Buenos Aires, Argentina +NER:Chulman, Neryungri, Russia NEV:Nevis, Leeward Islands, Saint Kitts And Nevis NGO:Komaki, Nagoya, Japan NGS:Nagasaki, Japan @@ -1429,7 +1438,7 @@ ROR:Airai, Koror, Palau ROS:Fisherton, Rosario, Santa Fe, Argentina ROU:Rousse, Bulgaria -ROV:Rostov, Russia +ROV:Rostov-on-Don, Russia ROW:Industrial Air Center, Roswell, New Mexico, USA RPR:Raipur, India RRG:Rodrigues Island, Mauritius @@ -1575,6 +1584,7 @@ STR:Echterdingen, Stuttgart, Germany STS:Sonoma County, Santa Rosa, California, USA STT:Cyril E King, St Thomas Island, US Virgin Islands, USA +STW:Stavropol, Russia STX:St Croix Island, US Virgin Islands, USA SUB:Juanda, Surabaya, Indonesia SUE:Sturgeon Bay, Wisconsin, USA @@ -1587,7 +1597,7 @@ SVO:Sheremetyevo, Moscow, Russia SVQ:Sevilla, Spain SVU:Savusavu, Savusavu, Fiji -SVX:Ekaterinburg, Russia +SVX:Koltsovo, Ekaterinburg, Russia SVZ:San Antonio, Venezuela SWA:Shantou, China SWF:Stewart, Newburgh/Poughkeepsie, New York, USA @@ -1648,7 +1658,7 @@ TIV:Tivat, Montenegro TIZ:Tari, Papua New Guinea TJA:Tarija, Bolivia -TJM:Tyumen, Russia +TJM:Roshchino, Tyumen, Russia TKK:Truk, Caroline Islands, Micronesia TKQ:Kigoma, Tanzania TKS:Tokushima, Japan @@ -1683,6 +1693,7 @@ TRV:Trivandrum, India TRZ:Civil, Tiruchirapally, India TSA:Sung Shan, Taipei, Taiwan +TSE:Astana, Kazakhstan TSR:Timisoara, Romania TSS:East 34Th Street Heliport, New York, New York, USA TSV:Townsville, Queensland, Australia @@ -1716,6 +1727,7 @@ UAQ:San Juan, Argentina UBJ:Ube, Japan UCA:Utica/Oneida County, New York, USA +UCT:Ukhta, Russia UDJ:Uzhgorod International, Zakarpattia, Ukraine UDR:Udaipur, India UEL:Quelimane, Mozambique @@ -1787,7 +1799,7 @@ VTZ:Vishakhapatnam, India VUP:Valledupar,
atheros 9485
Index: pcidevs === RCS file: /cvs/src/sys/dev/pci/pcidevs,v retrieving revision 1.1746 diff -u -p -u -r1.1746 pcidevs --- pcidevs 8 Oct 2014 07:41:27 - 1.1746 +++ pcidevs 9 Oct 2014 09:43:28 - @@ -1835,6 +1835,7 @@ product ATHEROS AR93000x0030 AR9300 product ATHEROS AR9485 0x0032 AR9485 product ATHEROS AR9462 0x0034 AR9462 product ATHEROS AR9565 0x0036 AR9565 +product ATHEROS AR9485 0x0037 AR9485 product ATHEROS AR5210_AP 0x0207 AR5210 product ATHEROS AR5212_IBM 0x1014 AR5212 product ATHEROS AR5210_DEFAULT 0x1107 AR5210 OK? BTW, this card is not fully supported. After adding it's ID to if_athn_pci.c it gives me calibration error when I'm running `dhclient athn0`. I can test diffs or send it to one of the developers.
Re: atheros 9485
On Thu, October 9, 2014 14:02, Stefan Sperling wrote: On Thu, Oct 09, 2014 at 01:48:23PM +0400, Kirill Bychkov wrote: Index: pcidevs === RCS file: /cvs/src/sys/dev/pci/pcidevs,v retrieving revision 1.1746 diff -u -p -u -r1.1746 pcidevs --- pcidevs 8 Oct 2014 07:41:27 - 1.1746 +++ pcidevs 9 Oct 2014 09:43:28 - @@ -1835,6 +1835,7 @@ product ATHEROS AR9300 0x0030 AR9300 product ATHEROS AR9485 0x0032 AR9485 product ATHEROS AR9462 0x0034 AR9462 product ATHEROS AR9565 0x0036 AR9565 +product ATHEROS AR9485 0x0037 AR9485 product ATHEROS AR5210_AP 0x0207 AR5210 product ATHEROS AR5212_IBM 0x1014 AR5212 product ATHEROS AR5210_DEFAULT 0x1107 AR5210 OK? I'm not sure about this. AR9485 is already in there as 0x0032. According to FreeBSD's ath_hal/ah_devid.h the ID 0x0037 maps to AR_PCIE... ? Linux ath9k calls it: PCI-E AR/AR9485 Missed that, sorry. It looks that there are a lot of names for this chip... This card is AzureWave AW-NE195H. Some says it's Atheros AR and some - that it's AR5B125... BTW, this card is not fully supported. After adding it's ID to if_athn_pci.c it gives me calibration error when I'm running `dhclient athn0`. I can test diffs or send it to one of the developers. Yes, this is a known issue. I've been trying to hunt this down for a while. Still no idea what's wrong with it. AFAIK the ar9003.c and ar9380.c files contain code which was never tested on real hardware by damien (see the CVS logs of these files). I see.
Re: Nut 2.7.2p2 with APC USB UPS on OpenBSD 5.6 current woes
On Fri, September 19, 2014 16:37, Stan Gammons wrote: I have an apc usb ups that was working with OpenBSD 5.5 stable, but when I installed 5.6 current nut no longer recognizes the status change when the UPS goes on battery. When you do upsc apcusb@localhost with AC power removed from the unit, it indicates the UPS is still online rather than being on battery. After some debugging help from the folks on the nut list, the only thing I see is a libusb error that says libusb_get_interrupt: Function not implemented Any ideas what might have changed in libusb1 to cause this to no longer work? Stan Hi. Do you have upd0 device and sensors.upd in sysctl hw output? If they are present, you can try to disable upd and uhidev from ukc and test nut. Note that yours USB keyboard wouldn't work with uhidev disabled.
Re: upd(4) proposal
On Fri, February 14, 2014 17:07, Andre de Oliveira wrote: hello. blambert@ suggested me to write a driver for exposing usb-based uninterruptable power systems devices data as sysctl(8) sensors, thus enabling people to write shutdown policies using sensorsd(8), which can replaces apcupsd in some cases. I received some feedback from reyk@ and blambert@, hope it's now ok for tech@ comments. -a Hi. Tested with upd0 at uhub2 port 1 American Power Conversion Back-UPS RS 500 FW:30.j5.I USB FW:j5 rev 1.10/0.06 addr 2 kirby@humppalaki:ttyp0kirby % sysctl hw.sensors.upd0 hw.sensors.upd0.volt0=1.20 VDC (battery nominal volt) hw.sensors.upd0.volt1=0.00 VDC (battery current volt) hw.sensors.upd0.indicator0=Off (battery charging) hw.sensors.upd0.indicator1=Off (battery discharging) hw.sensors.upd0.indicator2=On (battery present) hw.sensors.upd0.indicator3=Off (shutdown imminent) hw.sensors.upd0.indicator4=On (acpower present) hw.sensors.upd0.percent0=100.00% (battery load) Currently the problem is when UPS is attached as /dev/updX, apcupsd stops working. So shpuld /dev/upd be enabled by default? And another moment. What is about MODBUS? Are you going to support other APC protocols? I'm monitoring apcupsd mailing lists and it doesn't look like APC is giving all the documentation for developers on demand. As it looks to me, this driver is going to have half of apcupsd usb devices support to be really useful. But SNMP support would be nice. Just my thoughts... diff --git a/.gitignore b/.gitignore new file mode 100644 index 000..a43f9f5 --- /dev/null +++ b/.gitignore @@ -0,0 +1 @@ +**.swp diff --git a/share/man/man4/Makefile b/share/man/man4/Makefile index beaffb8..76b20e7 100644 --- a/share/man/man4/Makefile +++ b/share/man/man4/Makefile @@ -61,7 +61,7 @@ MAN=aac.4 ac97.4 acphy.4 \ uk.4 ukbd.4 \ ukphy.4 ulpt.4 umass.4 umbg.4 umct.4 umidi.4 umodem.4 ums.4 umsm.4 \ unix.4 uow.4 uoaklux.4 uoakrh.4 uoakv.4 \ - upgt.4 upl.4 uplcom.4 ural.4 urio.4 url.4 urlphy.4 \ + upd.4 upgt.4 upl.4 uplcom.4 ural.4 urio.4 url.4 urlphy.4 \ urndis.4 urtw.4 urtwn.4 usb.4 usbf.4 uslcom.4 usps.4 \ uthum.4 uticom.4 utpms.4 utwitch.4 utrh.4 uts.4 uvideo.4 uvisor.4 \ uvscom.4 uyap.4 \ diff --git a/share/man/man4/upd.4 b/share/man/man4/upd.4 new file mode 100644 index 000..5a9054d --- /dev/null +++ b/share/man/man4/upd.4 @@ -0,0 +1,96 @@ +.\ $OpenBSD$ +.\ +.\ Copyright (c) 2014 Andre de Oliveira deoliveira...@googlemail.com +.\ +.\ Permission to use, copy, modify, and distribute this software for any +.\ purpose with or without fee is hereby granted, provided that the above +.\ copyright notice and this permission notice appear in all copies. +.\ +.\ THE SOFTWARE IS PROVIDED AS IS AND THE AUTHOR DISCLAIMS ALL WARRANTIES +.\ WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF +.\ MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR +.\ ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +.\ WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN +.\ ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF +.\ OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +.\ +.Dd $Mdocdate: February 8 2014 $ +.Dt UPD 4 +.Os +.Sh NAME +.Nm upd +.Nd USB Power Devices battery voltage and load sensor +.Sh SYNOPSIS +.Cd upd* at uhub? +.Sh DESCRIPTION +The +.Nm +exposes data from USB Power Devices (such as an UPS), as hardware sensors +via +.Xr sysctl 3 . +The following devices are supported by the +.Nm +driver: +.Bl -column +.Pp +.It Li American Power Conversion Smart-UPS 750 +.It Li American Power Conversion Back-UPS CS 350 +.El +.Pp +The following sensors are provided by the +.Nm +driver, which can be monitored using +.Xr sensorsd 8 : +.Bl -column +.Pp +.It Battery Nominal Voltage +.It Battery Current Voltage +.It Battery Charging +.It Battery Discharging +.It Battery Present +.It Shutdown Imminent +.It AC Power Present +.It Battery Current Load +.El +.Sh EXAMPLES +In this example, the upd0 device is a regular UPS. +We use an entry on +.Xr sensorsd 8 +to take an action when the battery level is below a 70%: +.Pp +.Bd -literal -offset indent +hw.sensors.upd0.percent0:low=70:command=/etc/sensorsd/lowbattwarn %l +.Ed +.Pp +The contents of lowbattwarn could be: +.Pp +.Bd -literal -offset indent +#!/bin/ksh + +if [ $# -lt 1 ]; then +return; +fi + +if [ $1 -lt 70 ]; then +logger ups battery warning-level, halting +/sbin/halt -p +fi +.Ed +.Sh SEE ALSO +.Xr intro 4 , +.Xr uhub 4 , +.Xr sensorsd 8 , +.Xr sysctl 8 +.Sh HISTORY +The +.Nm +driver first appeared in .Ox +.Sh AUTHORS +The +.Nm +driver was written by Andre de Oliveira deoliveira...@googlemail.com, +sponsored by Esdenera Networks GmbH. +.Sh BUGS +When the battery is not present even with Battery Presence
Re: Request for Funding our Electricity
On Wed, January 15, 2014 00:03, Bob Beck wrote: Just to bring this issue back to the forefront. In light of shrinking funding, we do need to look for a source to cover project expenses. If need be the OpenBSD Foundation can be involved in receiving donations to cover project electrical costs. But the fact is right now, OpenBSD will shut down if we do not have the funding to keep the lights on. If you or a company you know are able to assist us, it would be greatly appreciated, but right now we are looking at a significant funding shortfall for the upcoming year - Meaning the project won't be able to cover 20 thousand dollars in electrical expenses before being able to use money for other things. That sort of situation is not sustainable. Hi. Could we collect this sum on special bank account, to gather correct sum for covering electricity expenses? Or OpenBSD Foundation will pay a bill from it's funds? Simplier - should I send money to Foundation right now or should I wait info about direct-electricity-expenses-acccount? Unfortunately I can't send $20k, but if 200 community members send $100 each... I hope this will help to have another year for searching a company Theo was mentioning in his irst letter. On Fri, Dec 20, 2013 at 5:08 PM, Theo de Raadt dera...@cvs.openbsd.org wrote: I am resending this request for funding our electricity bills because it is not yet resolved. We really need even more funding beyond that, because otherwise all of this is simply unsustainable. This request is the smallest we can make. --- Hi everyone. The OpenBSD project uses a lot of electricity for running the development and build machines. A number of logistical reasons prevents us from moving the machines to another location which might offer space/power for free, so let's not allow the conversation to go that way. We are looking for a Canadian company who will take on our electrical expenses -- on their books, rather than on our books. We would be happiest to find someone who will do this on an annual recurring basis. That way the various OpenBSD efforts can be supported, yet written off as an off-site operations cost by such a company. If we reduce this cost, it will leave more money for other parts of the project. We think that a Canadian company is the best choice for accounting reasons. If a company in some other jurisdiction feels they can also do this successfully, we'd be very happy to hear from them as well. I am not going to disclose the actual numbers here. Please contact me for details if serious. Thanks.
add new device to cdce.4
Hi! This Yota dongle works fine. I think adding this into manual would be useful for russian OpenBSD users. umass1 at uhub0 port 1 configuration 1 interface 0 GCT SEMICONDUCTOR Inc Modem Yota rev 2.00/1.00 addr 4 umass1: using SCSI over Bulk-Only scsibus4 at umass1: 2 targets, initiator 0 cd0 at scsibus4 targ 1 lun 0: GDM Mass, , SCSI0 5/cdrom removable cd0 detached scsibus4 detached umass1 detached cdce0 at uhub0 port 1 configuration 1 interface 0 GCT SEMICONDUCTOR Inc Modem Yota rev 2.00/1.00 addr 4 cdce0: address 2a:cb:01:dd:01:00 ehci_idone: ex=0xd349f200 is done! Index: cdce.4 === RCS file: /cvs/src/share/man/man4/cdce.4,v retrieving revision 1.18 diff -u -r1.18 cdce.4 --- cdce.4 16 Jul 2013 16:05:48 - 1.18 +++ cdce.4 11 Dec 2013 09:10:58 - @@ -66,6 +66,8 @@ .It Sony Ericsson F3705g .It +Yota LU156 +.It Zyxel P-971M .El .Pp
rsu.4 update
Hi. This adapter is working. OK to commit? Index: rsu.4 === RCS file: /cvs/src/share/man/man4/rsu.4,v retrieving revision 1.15 diff -u -p -u -r1.15 rsu.4 --- rsu.4 20 Aug 2013 13:46:53 - 1.15 +++ rsu.4 6 Dec 2013 10:58:06 - @@ -86,6 +86,7 @@ The following adapters should work: .Pp .Bl -tag -width Ds -offset indent -compact .It ASUS USB-N10 +.It ASUS WL-167G V3 .It Belkin F7D1101 v1 .It D-Link DWA-131 A1 .It Hercules HWGUn-54
Re: Weard security report
On Wed, November 6, 2013 19:24, sven falempin wrote: Hello, Hi I love daily scripts and used it to follow some activity on server(s) One of my server got this entry: Running security(8): == /var/db/cloud.json diffs (-OLD +NEW) == --- /dev/null Fri Oct 25 01:30:33 2013 +++ /var/db/cloud.json Thu Oct 17 17:21:15 2013 [...] Previous security: == /var/db/cloud.json diffs (-OLD +NEW) == --- /var/backups/var_db_cloud.json.current Sat Jul 27 01:30:11 2013 +++ /var/db/cloud.json Wed Aug 7 16:28:55 2013 [..] /dev/null !!!??? What possibly could happened ?? /dev/null tells that cloud.json in newly created file, so it's diffed against /dev/null. PS: Is that possible to keep more than one backup in /var/backup ?
Re: Fix gem(4) by attaching the right PHY on PowerMac G5
On Fri, March 8, 2013 13:42, Martin Pieuchot wrote:
kirby@ reported [0] back in February that the gem(4) on his PowerMac
G5 wasn't working. Apparently the logic to determine which PHY to use
doesn't work with these machines when the firmware has powered down the
chip. At least that's what FreeBSD and linux code say and it seems to
correspond to the behavior I observed: when the NIC is used for
netbooting the correct PHY is attached.
Diff below is taken from FreeBSD and force the use of the internal PHY
on Apple models. This makes the gem(4) on my PowerMac G5 usable even if
I don't netboot. I also verified that it does not introduce a regression
on my G4.
Ok?
My G5's gem now works. Thanks!
gem0 at pci7 dev 15 function 0 Apple K2 GMAC rev 0x00: irq 41, address
00:0a:95:8f:3d:84
brgphy0 at gem0 phy 1: BCM54K2 10/100/1000baseT PHY, rev. 0
No regression on my PoweBook4,3.
[0] http://marc.info/?l=openbsd-miscm=136074529112590w=2
Index: gem.c
===
RCS file: /cvs/src/sys/dev/ic/gem.c,v
retrieving revision 1.98
diff -u -p -r1.98 gem.c
--- gem.c 1 Dec 2012 10:04:58 - 1.98
+++ gem.c 7 Mar 2013 16:52:31 -
@@ -275,11 +275,14 @@ gem_config(struct gem_softc *sc)
MII_OFFSET_ANY, mii_flags);
}
- /*
+ /*
* Fall back on an internal PHY if no external PHY was found.
+ * Note that with Apple (K2) GMACs GEM_MIF_CONFIG_MDI0 can't be
+ * trusted when the firmware has powered down the chip
*/
child = LIST_FIRST(mii-mii_phys);
- if (child == NULL sc-sc_mif_config GEM_MIF_CONFIG_MDI0) {
+ if (child == NULL
+ (sc-sc_mif_config GEM_MIF_CONFIG_MDI0 || GEM_IS_APPLE(sc))) {
sc-sc_mif_config = ~GEM_MIF_CONFIG_PHY_SEL;
bus_space_write_4(sc-sc_bustag, sc-sc_h1,
GEM_MIF_CONFIG, sc-sc_mif_config);
Index: gemvar.h
===
RCS file: /cvs/src/sys/dev/ic/gemvar.h,v
retrieving revision 1.26
diff -u -p -r1.26 gemvar.h
--- gemvar.h 20 Sep 2010 07:40:41 - 1.26
+++ gemvar.h 7 Mar 2013 16:50:39 -
@@ -151,6 +151,10 @@ struct gem_softc {
#define GEM_APPLE_GMAC 3 /* Apple GMAC */
#define GEM_APPLE_K2_GMAC4 /* Apple K2 GMAC */
+#define GEM_IS_APPLE(sc)
\
+ ((sc)-sc_variant == GEM_APPLE_GMAC || \
+ (sc)-sc_variant == GEM_APPLE_K2_GMAC)
+
u_int sc_flags; /* */
#define GEM_GIGABIT 0x0001 /* has a gigabit PHY */
Re: Workaround for an rsu(4) bug
On Tue, February 5, 2013 14:10, Stuart Henderson wrote: On 2013/02/05 05:18, Brad Smith wrote: On Tue, Feb 05, 2013 at 12:26:47AM +0100, Mark Kettenis wrote: Date: Tue, 29 Jan 2013 21:04:30 -0500 From: Brad Smith b...@comstyle.com To a certain extent this seems to make rsu(3) work a little better, but now I am seeing ``rsu0: could not send join command'' messages which never happened before. Hmm, I wonder which of the two rsu_fw_cmd() calls in rsu_join_bss() is failing. The other issue I'm experiencing is when the driver does a scan either from the kernel doing so or from me issuing ifconfig scan will result in rsu_site_survey() failing (rsu0: could not send site survey command) after a few invocations of the function to issue the fw command. Over all though rsu(3) is still mainly unusable at least for the chipset in the adapter I am using; it is way too unreliable. It might be worth trying a different firmware. Looks like the Linux people had some issues with some firmware versions judging from the log messages in their git firmware repo. You'll want rtl8712u.bin from: http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=tree;f=rtlwifi;hb=HEAD With this newer firmware I can do many manual scans in a row and the over all stability of connections associated with an AP is more stable too. Also IPv6 seems to work consistently now. It was cutting in and and out before as if multicast traffic was being dropped. It is not 100% perfect as I was still able to reproduce the site survey errors after quite a few scans but compared to the current firmware package it seems to be quite an improvement. Could you (and other rsu(4) users) test this updated firmware package please: http://junkpile.org/rsu-firmware-1.2.tgz Slightly related, I have problems scanning from iwn; 30 second delay with wchan 80211scan and no scan results. Network is unusable afterwards until I down+up the interface. iwn0 at pci2 dev 0 function 0 Intel Centrino Advanced-N 6205 rev 0x34: msi, MIMO 2T2R, MoW, address 8c:70:5a:62:b7:f8 Hi! I still have some problems with 1.2 firmware and rsu wifi on 5.3-beta: Feb 20 12:25:45 barton /bsd: rsu0: could not send join command Feb 20 12:25:47 barton /bsd: rsu0: could not send site survey command Feb 20 12:29:22 barton /bsd: ehci_idone: ex=0x8017f800 is done! Feb 20 12:29:22 barton dhclient[14203]: dispatch_imsg in main: pipe closed Feb 20 12:29:22 barton dhclient[10353]: receive_packet failed on rsu0: Input/output error Feb 20 12:29:22 barton dhclient[10353]: ioctl(SIOCGIFFLAGS) on rsu0: Device not configured Feb 20 12:29:22 barton dhclient[14203]: SIOCDIFADDR failed (10.219.11.4): Device not configured Feb 20 12:29:22 barton /bsd: rsu0 detached Feb 20 12:29:23 barton /bsd: rsu0 at uhub0 Feb 20 12:29:23 barton /bsd: port 3 Manufacturer Realtek ASUS EZ N Network Adapter rev 2.00/2.00 addr 2 Feb 20 12:29:24 barton /bsd: rsu0: MAC/BB RTL8712 cut 3, address c8:60:00:5e:11:bb Feb 20 13:23:23 barton /bsd: rsu0: could not send join command Feb 20 13:23:25 barton /bsd: rsu0: could not send site survey command Feb 20 13:24:52 barton /bsd: ehci_idone: ex=0x8017f800 is done! Feb 20 13:24:52 barton dhclient[10599]: receive_packet failed on rsu0: Input/output error Feb 20 13:24:52 barton dhclient[10599]: ioctl(SIOCGIFFLAGS) on rsu0: Device not configured Feb 20 13:24:52 barton dhclient[1735]: dispatch_imsg in main: pipe closed Feb 20 13:24:52 barton dhclient[1735]: SIOCDIFADDR failed (10.219.11.4): Device not configured Feb 20 13:24:52 barton /bsd: rsu0 detached Feb 20 13:24:55 barton /bsd: rsu0 at uhub0 Feb 20 13:24:55 barton /bsd: port 3 Manufacturer Realtek ASUS EZ N Network Adapter rev 2.00/2.00 addr 2 Feb 20 13:24:55 barton /bsd: rsu0: MAC/BB RTL8712 cut 3, address c8:60:00:5e:11:bb I need to unplug and plug it to reconnect to AP (AP is based on 5.3-beta amd64 from 12 Feb + ral0 Ralink RT2790) But it became more stable with this firmware than before. dmesg.barton Description: Binary data
axe(4) support for D-Link DUB-E100 rev C1
Hi. A friend of mine get D-Link DUB-E100, but it is build on another chip
revision. This diff adds support for this adapter. Tested on amd64 for a
couple of days, but without high load.
Needs further testing or OK to commit?
Index: if_axe.c
===
RCS file: /cvs/src/sys/dev/usb/if_axe.c,v
retrieving revision 1.112
diff -u -r1.112 if_axe.c
--- if_axe.c14 Nov 2012 17:00:23 - 1.112
+++ if_axe.c18 Nov 2012 14:27:07 -
@@ -160,6 +160,7 @@
{ { USB_VENDOR_COREGA, USB_PRODUCT_COREGA_FETHER_USB2_TX }, 0},
{ { USB_VENDOR_DLINK, USB_PRODUCT_DLINK_DUBE100}, 0 },
{ { USB_VENDOR_DLINK, USB_PRODUCT_DLINK_DUBE100B1 }, AX772 },
+ { { USB_VENDOR_DLINK, USB_PRODUCT_DLINK_DUBE100C1 }, AX772 | AX772B },
{ { USB_VENDOR_GOODWAY, USB_PRODUCT_GOODWAY_GWUSB2E}, 0 },
{ { USB_VENDOR_IODATA, USB_PRODUCT_IODATA_ETGUS2 }, AX178 },
{ { USB_VENDOR_JVC, USB_PRODUCT_JVC_MP_PRX1}, 0 },
Index: usbdevs
===
RCS file: /cvs/src/sys/dev/usb/usbdevs,v
retrieving revision 1.591
diff -u -r1.591 usbdevs
--- usbdevs 14 Nov 2012 16:53:49 - 1.591
+++ usbdevs 18 Nov 2012 14:27:07 -
@@ -1420,6 +1420,7 @@
/* D-Link products */
/*product DLINK DSBS25 0x0100 DSB-S25 serial */
product DLINK DUBE100 0x1a00 10/100 Ethernet
+product DLINK DUBE100C10x1a02 DUB-E100 rev C1
product DLINK DSB650TX40x200c 10/100 Ethernet
product DLINK DWL120E 0x3200 DWL-120 rev E
product DLINK DWA130C 0x3301 DWA-130 rev C
new umsm(4) device
Hi. Recently I've bought new Huawei E352 modem. I'm using it for some time without any problems. ok to commit? Index: umsm.4 === RCS file: /cvs/src/share/man/man4/umsm.4,v retrieving revision 1.81 diff -u -r1.81 umsm.4 --- umsm.4 24 May 2012 09:08:38 - 1.81 +++ umsm.4 27 Sep 2012 13:19:40 - @@ -64,6 +64,7 @@ .It Li Huawei Mobile E181 Ta USB .It Li Huawei Mobile E182 Ta USB .It Li Huawei Mobile E220 Ta USB +.It Li Huawei Mobile E352 Ta USB .It Li Huawei Mobile E510 Ta USB .It Li Huawei Mobile E1750 Ta USB .It Li Huawei Mobile E1752 Ta USB
Garmin GPS reciever
OK to add this one? Index: usbdevs === RCS file: /cvs/src/sys/dev/usb/usbdevs,v retrieving revision 1.589 diff -u -r1.589 usbdevs --- usbdevs 3 Oct 2012 08:04:23 - 1.589 +++ usbdevs 8 Oct 2012 16:42:11 - @@ -1890,6 +1890,7 @@ /* Garmin International products */ product GARMIN GPSMAP60CSX 0x0003 GPSmap 60Csx product GARMIN IQUE36000x0004 Ique 3600 +product GARMIN DAKOTA200x23c0 Dakota 20 product GARMIN GPSMAP62S 0x2459 GPSmap 62s /* GCT Semiconductor products */
new pci ids
Hi. Here is the bunch of pci devices, found in some laptops and desktops I get in my hands. OK to commit? Index: pcidevs === RCS file: /cvs/src/sys/dev/pci/pcidevs,v retrieving revision 1.1651 diff -u -r1.1651 pcidevs --- pcidevs 8 Jul 2012 09:48:38 - 1.1651 +++ pcidevs 11 Jul 2012 20:36:55 - @@ -155,6 +155,7 @@ vendor SIEMENS 0x110a Siemens vendor ZNYX0x110d Znyx Networks vendor ACCTON 0x1113 Accton +vendor ATMEL 0x1114 Atmel vendor VORTEX 0x1119 Vortex vendor EFFICIENTNETS 0x111a Efficent Networks vendor IDT 0x111d IDT @@ -906,6 +907,7 @@ /* ASMedia products */ product ASMEDIA ASM10420x1042 ASM1042 xHCI +product ASMEDIA ASM10800x1080 ASM1083/1085 PCIE-PCI /* Asustek products */ product ASUSTEK HFCPCI 0x0675 ISDN @@ -1258,6 +1260,7 @@ product ATI RADEON_X700_PCIE_S 0x5e6d Radeon X700 PCIE Sec product ATI RADEON_X700_SE 0x5e4f Radeon X700 SE product ATI RADEON_X700_SE_S 0x5e6f Radeon X700 SE Sec +product ATI RADEON_HD6670 0x6758 Radeon HD 6670 product ATI RADEON_HD5800 0x6899 Radeon HD 5800 product ATI RADEON_HD5700 0x68b8 Radeon HD 5700 product ATI RADEON_HD5670 0x68d8 Radeon HD 5670 @@ -1440,6 +1443,7 @@ product ATI RADEON_HD5700_HDA 0xaa58 Radeon HD 5700 Audio product ATI RADEON_HD5600_HDA 0xaa60 Radeon HD 5600 Audio product ATI RADEON_HD5470_HDA 0xaa68 Radeon HD 5470 Audio +product ATI RADEON_HD6670_HDA 0xaa90 Radeon HD 6670 Audio product ATI RADEON_HD6400_HDA 0xaa98 Radeon HD 6400 Audio product ATI RS100_AGP 0xcab0 RS100 AGP product ATI RS200_AGP 0xcab2 RS200 AGP @@ -1487,6 +1491,9 @@ product ATHEROS AR5211_FPGA11B 0xf11b AR5211Ref product ATHEROS AR5211_LEGACY 0xff12 AR5211Ref +/* Atmel products */ +product ATMEL AT76C506 0x0506 AT76C506 + /* Atronics products */ product ATRONICS IDE_2015PL0x2015 IDE-2015PL @@ -3586,6 +3593,7 @@ product ITEXPRESS IT8213F 0x8213 IT8213F product ITEXPRESS IT8330G 0x8330 IT8330G product ITEXPRESS ITF_ISA 0x ITF ISA +product ITEXPRESS IT8892 0x8892 IT8892 /* JMicron */ product JMICRON JMC250 0x0250 JMC250 @@ -3988,6 +3996,7 @@ product CMI CMI87380x0111 CMI8738/C3DX Audio product CMI CMI8738B 0x0112 CMI8738B Audio product CMI HSP56 0x0211 HSP56 AMR +product CMI CMI87880x8788 CMI8788 Oxygen HD Audio /* Netoctave */ product NETOCTAVE NSP2K0x0100 NSP2K @@ -4703,6 +4712,7 @@ product NVIDIA MCP77_RAID_30x0ada MCP77 RAID product NVIDIA MCP77_RAID_40x0adb MCP77 RAID product NVIDIA GF108_HDA 0x0bea GF108 HD Audio +product NVIDIA GF116_HDA 0x0bee GF116 HD Audio product NVIDIA MCP89_HB0x0d60 MCP89 Host product NVIDIA MCP89_MEM_1 0x0d68 MCP89 Memory product NVIDIA MCP89_MEM_2 0x0d69 MCP89 Memory @@ -4733,6 +4743,7 @@ product NVIDIA MCP89_OHCI 0x0d9c MCP89 USB product NVIDIA MCP89_EHCI 0x0d9d MCP89 USB product NVIDIA GEFORCE_425M0x0df0 GeForce 425M +product NVIDIA GEFORCEGTX550TI 0x1244 GeForce GTX 550 Ti /* Oak Technologies products */ product OAKTECH OTI10070x0107 OTI107 @@ -4880,6 +4891,7 @@ product PHILIPS SAA71330x7133 SAA7133 TV product PHILIPS SAA71340x7134 SAA7134 TV product PHILIPS SAA71350x7135 SAA7135 TV +product PHILIPS SAA72310x7231 SAA7231 TV /* Phison products */ product PHISON PS5000 0x5000 PS5000
