Attachment 924098 Details for Bug 1126710 – Update to 2.2.0

[patch] Update to 2.2.0

Update-to-2.2.0.patch (text/plain), 8.09 KB, created by poma on 2014-08-05 06:20:44 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: poma

Created: 2014-08-05 06:20:44 UTC

Size: 8.09 KB

patch

obsolete

>
>Update to 2.2.0
>
>---
> device_reference.txt | 187 ++-------------------------------------------------
> sources              |   2 +-
> usb_modeswitch.spec  |   9 ++-
> 3 files changed, 12 insertions(+), 186 deletions(-)
>
>diff --git a/device_reference.txt b/device_reference.txt
>index 16c638c..d34ec3e 100644
>--- a/device_reference.txt
>+++ b/device_reference.txt
>@@ -1,7 +1,7 @@
> #
>-# Device and Configuration Reference (UTF-8 encoding used)
>+# Device Reference (UTF-8 encoding used)
> #
>-# Last modified: 2013-11-13
>+# Last modified: 2014-05-29
> #
> # Collection of configurations for usb_modeswitch, a mode switching
> # tool for controlling flip flop (multiple mode) USB devices
>@@ -21,191 +21,14 @@
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> 
> 
>-# For custom settings:
>-# Numbers can be decimal or hexadecimal, MessageStrings MUST be
>-# hexadecimal without prepended "0x". Digits 9-16 in the known
>-# MessageStrings are arbitrary; I set them to "12345678"
>-
>-# What it all means (short command line flags appended):
>-#
>-#
>-# * DefaultVendor            -v <hex number>
>-# * DefaultProduct           -p <hex number>
>-#
>-# This is the ID the USB device shows after having been plugged in.
>-# The program needs this, either on the command line or in the config
>-# file; if not found -> no action.
>-#
>-#
>-# * TargetVendor             -V <hex number>
>-# * TargetProduct            -P <hex number>
>-#
>-# These are the IDs of the USB device after successful mode switching.
>-# They are optional, but I recommend to provide them for better analysis.
>-# You definitely need them if you enable CheckSuccess (see below)
>-#
>-#
>-# * TargetProductList        (file only) <comma separated hex strings>
>-#
>-# Like TargetProduct, but more than one possibility. Only used in automated
>-# config files (in /etc/usb_modeswitch.d).
>-#
>-#
>-# * TargetClass              -C <hex number>
>-#
>-# Some weird devices don't change IDs. They only switch the device class.
>-# If the device has the target class -> no action (and vice versa)
>-#
>-#
>-# * MessageEndpoint          -m <hex number>
>-#
>-# A kind of address inside the interface to which the "message"
>-# (the sequence that does the actual switching) is directed.
>-# Obsolete since version 0.9.7, only useful for testing
>-#
>-#
>-# * MessageContent           -M <hex string>
>-#
>-# A hex string containing the "message" sequence; it will be
>-# sent as a USB bulk transfer
>-#
>-#
>-# * MessageContent2, ...3    -2/-3 <hex string>
>-#
>-# Additional "messages". Use with "NeedResponse"!
>-#
>-#
>-# * ReleaseDelay             -w <milliseconds>
>-#
>-# Waiting time after message transfers. Helps with some sensitive devices
>-# that don't want any traffic after the mode switch initialisation
>-#
>-#
>-# * ResponseEndpoint         -r <hex number>
>-# * NeedResponse <0/1>       -n
>-#
>-# Some devices were reported to require receiving the response of the
>-# bulk transfer to do the switching properly. Usually not needed.
>-# Starting from version 1.0.0 the ResponseEndpoint is autodetected
>-# if not given
>-#
>-#
>-# * DetachStorageOnly <0/1>  -d
>-#
>-# Some early devices just needed to be detached from the usb-storage
>-# driver to initiate the mode switching. Now paractically obsolete for
>-# switching, but still comes handy sometimes
>-#
>-#
>-# * HuaweiMode <0/1>         -H
>-#
>-# Some early Huawei devices can be switched by a special control
>-# message. Don't use with recent devices
>-#
>-#
>-# * SonyMode <0/1>           -O
>-#
>-# Some Sony-Ericsson devices can be switched by a special control
>-# message. May take a long time (20+ seconds).
>-#
>-#
>-# * SierraMode <0/1>         -S
>-# * KobilMode <0/1>          -T
>-# * GCTMode <0/1>            -G
>-# * SequansMode <0/1>        -N
>-# * MobileActionMode <0/1>   -A
>-# * QisdaMode <0/1>          -B
>-# * QuantaMode <0/1>         -E
>-# * PantechMode <0/1>        -F
>-# * BlackberryMode <0/1>     -Z
>-# * CiscoMode <0/1>          -L
>-#
>-#
>-# Flags to support devices that need special control messages.
>-# The names are referring to the respective manufacturers.
>-#
>-#
>-# * ResetUSB <0/1>           -R
>-#
>-# Few devices or systems need a rougher treatment. If the switching seems
>-# to do something but your system does not reflect it, try this somewhat
>-# brutal method to do a reset after switching.
>-# Mind that if your device switched OK before, this may set it back to
>-# storage mode ...
>-#
>-#
>-# * Interface                -i <hex number>
>-# * Configuration            -u <hex number>
>-# * AltSetting               -a <hex number>
>-#
>-# More USB parameter to help with tricky devices and for doing lots
>-# of cruel experiments ...
>-#
>-## Note:
>-## AltSetting/Configuration changes and ResetUSB are executed after all
>-## other steps and can be combined or used on their own (e.g. a reset
>-## might have the same effect as a manual replug)
>-#
>-#
>-# * InquireDevice <0|1>      -I (disables inquiry)
>-#
>-# The standard since 1.0.0 is to do a SCSI inquiry on the default device
>-# before other actions. This might be a future way to identify a device
>-# without ambiguities. If it causes trouble with your device, just disable.
>-#
>-#
>-# * CheckSuccess             -s <number>
>-#
>-# Check continuously if the switch succeeded for max <number> seconds.
>-# First, an interface access test: most devices vanish after
>-# switching and can't be accessed anymore.
>-# Second, a recount of target devices: one more than at the initial
>-# count, at the same bus with a higher device number -> device
>-# switched fine.
>-# It's safe to give a higher value than needed; checking stops as
>-# soon as the target device is found
>-#
>-#
>-# * NoDriverLoading <0|1>    (no command line parameter)
>-#
>-# The binary tells the wrapper script NOT to check for and initiate
>-# binding of the serial driver after switching.
>-# Mostly useful for non-modem devices.
>-#
>-#
>-# * WaitBefore <seconds>     (no command line parameter)
>-#
>-# Waiting time before taking any action. Helps with some sensitive setups.
>-#
>-#
>-# * NoMBIMCheck <0|1>        (no command line parameter)
>-#
>-# Disable the check for new MBIM standard devices, which is always done
>-# by default.
>-#
>-#
>-#
>-# -> All other entries in config files are just ignored <-
>-
>-# Additional command line flags:
>-#
>-# Verbose output             -W
>-# No output at all           -q
>-# Use config file            -c <file>
>-# Use stdin for long config  -t
>-# Give long config as string -f <multiline string using config file syntax>
>-# Give bus number for ID'ing -b
>-# Give dev number for ID'ing -g
>-
>-
>-# For filling in all this information for an unknown device,
>-# see instructions and links on the homepage:
>-# http://www.draisberghof.de/usb_modeswitch
>+# For a parameter reference see file REFERENCE in the data package
> #
> # If you find working codes and configurations, please contribute
> # them!
> 
> 
>+
>+
> #######################################################
> # Option GlobeSurfer Icon (aka "Vodafone EasyBox")
> #
>diff --git a/sources b/sources
>index e6c0526..c79f650 100644
>--- a/sources
>+++ b/sources
>@@ -1 +1 @@
>-1f0dc900df88254bd1102444cb73efbc  usb-modeswitch-2.1.1.tar.bz2
>+f323fe700edd6ea404c40934ddf32b22  usb-modeswitch-2.2.0.tar.bz2
>diff --git a/usb_modeswitch.spec b/usb_modeswitch.spec
>index 3306f62..0691c9e 100644
>--- a/usb_modeswitch.spec
>+++ b/usb_modeswitch.spec
>@@ -1,8 +1,8 @@
> %define source_name	usb-modeswitch
> 
> Name:		usb_modeswitch
>-Version:	2.1.1
>-Release:	2%{?dist}
>+Version:	2.2.0
>+Release:	1%{?dist}
> Summary:	USB Modeswitch gets mobile broadband cards in operational mode
> Summary(de):	USB Modeswitch aktiviert UMTS-Karten
> Group:		Applications/System
>@@ -17,7 +17,7 @@ Patch0: rhbz948451-fix-manual-pages.patch
> BuildRequires:	libusbx-devel
> BuildRequires:	jimtcl-devel
> BuildRequires:	systemd-devel
>-Requires:	usb_modeswitch-data >= 20121109
>+Requires:	usb_modeswitch-data >= 20140529
> 
> %description
> USB Modeswitch brings up your datacard into operational mode. When plugged
>@@ -75,6 +75,9 @@ install -p -m 755 usb_modeswitch.sh $RPM_BUILD_ROOT%{_prefix}/lib/udev/usb_modes
> 
> 
> %changelog
>+* Tue Aug  5 2014 poma <poma@gmail.com> 2.2.0-1
>+- Update to 2.2.0
>+
> * Sun Jun 08 2014 Fedora Release Engineering <rel-eng@lists.fedoraproject.org> - 2.1.1-2
> - Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild
> 
>-- 
>2.0.4
>

Actions: View | Diff

Attachments on bug 1126710: 924098