linux-kernel - Re: [PATCH] USB: expose Huawei E1550 3G modem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4BCC63EB.4010204@redhat.com>
Date:	Mon, 19 Apr 2010 16:08:43 +0200
From:	Stefan Assmann <sassmann@...hat.com>
To:	digidietze@...isberghof.de
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-usb@...r.kernel.org
Subject: Re: [PATCH] USB: expose Huawei E1550 3G modem

On 19.04.2010 16:00, Josua Dietze wrote:
> Stefan Assmann schrieb:
>> The Huawei E1550 3G modem is hidden by default and can be
>> exposed by sending some magic initialization code. This
>> patch takes care of that.
> 
> This device (as all other Huaweis using this sequence) is 
> supported by the usb_modeswitch tool which takes of the 
> switching process. Once installed, no user interaction is 
> required except plugging.
> 
> Current policy is to leave switching to the userspace if it's 
> working there.

Hi Josua,

that's good news. This is part of hardware initialization, so let's move
it to the kernel. Or do you know any good reason why the kernel
shouldn't handle it?

  Stefan
--
Stefan Assmann         | Red Hat GmbH
Software Engineer      | Otto-Hahn-Strasse 20, 85609 Dornach
                       | HR: Amtsgericht Muenchen HRB 153243
                       | GF: Brendan Lane, Charlie Peters,
sassmann at redhat.com |     Michael Cunningham, Charles Cachera
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/