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-next>] [day] [month] [year] [list]
Message-ID: <87obrzjqfs.fsf@nemi.mork.no>
Date:	Wed, 14 Mar 2012 13:51:51 +0100
From:	Bjørn Mork <bjorn@...k.no>
To:	"Nin Lil'izi" <nin-lil-izi@...protected.phoenixhaven.net>
Cc:	Greg KH <gregkh@...uxfoundation.org>, linux-usb@...r.kernel.org,
	Dan Williams <dcbw@...hat.com>,
	Oliver Neukum <oliver@...kum.org>, netdev@...r.kernel.org
Subject: Re: [PATCH net-next/usb-next v3 0/5] cdc-wdm/qmi_wwan: subdriver support

"Nin Lil'izi" <nin-lil-izi@...protected.phoenixhaven.net> writes:

> Please forgive me for spamming this list.
> But is this module going to make it into the 3.3.0 final release?
>
> I've been testing it on my laptop while travelling on trains and things
> using recent git pulls. And it releaves so much frustration vs the
> option module.
> As in spotty signal areas it drops in and out seamlessly without having
> to manually reconnect everytime the train passes through a deadspot. And
> generally the connection is noticiably more stable in this use case :D
>
> Anyway I'd like to try it on my home connection which is run off an atom
> device in a radio blackspot from hell. Which results in stuff having to
> be reconnected very often, even with huge external antenna attached. So
> this is like a dream come true in frustration saving but it takes
> 12hours to build a kernel. And cross compilation is labour intensive
> when you don't have the toolchain setup first. So am waiting for this to
> hit a stable release before building it on that machine to save my sanity.

Thanks for the nice feedback.  

This was submitted far too late for it to be considered 3.3 material.
Not much to do about that.  Most of the developement happened after
3.3-rc1 anyway.  So I'm afraid you'll have to wait a couple months more
for the 3.4 release.

I understand that wasn't the message you wanted, but it does give us all
a chance to test it thoroughly on different types of hardware. And maybe
even prepare some userspace tools :-)

Which brings me to a couple of questions I have for you: What radio
hardware do you use (lsusb -v), and which userspace tools?

But we should maybe continue any userspace tool discussion here instead,
where it's a bit more on topic:
http://lists.freedesktop.org/mailman/listinfo/libqmi-devel


Bjørn
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ