Hi Nils, As my original intention (and I still stick to it) is to not divert from upstream; and as I don't intend to favor one or the other side: I'm hereby asking upstream his opinion.
Josh: What's your statement on this ? (See http://bugs.debian.org/587776 for details) Thanks in advance, Cheers, OdyX Le jeudi 1 juillet 2010 17:08:54, vous avez écrit : > This patch adds functionality to the 1.1.2-3 version of usb-modeswitch: > > Multiple interrupt devices as the Olivetti OliCard100 only work reliably > w/ this patch. The gsmmodem link doesn't get set correclty w/o this patch. > > Details can be found here: > http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?t=391&postdays=0 > &postorder=asc&start=15 > > -- citation start > [..] > USB_ModeSwitch log from Sun May 23 16:02:19 CEST 2010 > symlink call > dirList: {} devices pci0000:00 0000:00:1a.7 usb1 1-3 1-3:1.3 ttyUSB2 tty > ttyUSB2 tty: ttyUSB2 > ttyNo: 2 > Path: /devices/pci0000:00/0000:00:1a.7/usb1/1-3/1-3:1.3/ttyUSB2/tty/ttyUSB2 > ifDir: /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-3/1-3 > port: ttyUSB2 > dev_top: 1-3 > className: > /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-3/1-3:1.3/bInterfaceClass > classType: ff > found INT: /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-3/1-3:1.3/ep_84/type > INT-portList: 3 > INFO: 2 smaller than or equal to 3 > returning symlinkname: gsmmodem2 > > In the last call (the one for ttyUSB2) here's the correlation between path > element __1.3__/ttyUSB2 and "found INT: > /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-3/1-3:__1.3__/ep_84/type" [..] > > [..] The id in the path name from udev and the one from the lowest found > interrupt must be identical [..] > -- citation end > > > Unfortunately, upstream only re-implemented half of it in an updated > version: just the lowest found interrupt port is used, no path id > correlation is done. > > However, at the installations on our sites this correlation is mandatory. > W/o it the link doesn't get set reliably. > > The patch correlation has been rejected so far as reports from users > have been received by upstream. Those reports received have not been > further detailed by upstream except that there might be a misleading > correlation in kernels/systems. > > We're running on debian, ubuntu and kernels .33.4 and .32.x w/ success, no > such thing as a bad path id correlation occurred to us so far. > > It was suggested to report this bug/patch to the dbts as upstream's > personality is objecting further cooperation (see above link ff), this > feature however is required for this device and other users w/ a multi > interrupt device might profit this way. > > Thank you. > > > Cheers, > > > Nils -- Didier Raboud, proud Debian Maintainer (DM). CH-1020 Renens [email protected] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
