USB_ModeSwitch

Josh wrote:Let me state one thing very clear: I don't like feeling pushed.
Or - to quote Greg Kroah-Hartman in his reply to you - "you need to be a bit more patient".

Now, will you stop that please? Don't talk about being pushed. You answered often enough within minutes. That's not always possible, I understand that very well. It is however a nice gesture to at least drop a comment on a patch that you get provided with.

Tell at least, you're too busy. That's what I guessed and waited for ack or nack. Having no communication is appalling eventually everyone.

If the project is overwhelming you, it might be a viable idea to integrate the community even more: set up a svn repo everyone can profit from and provide to.

That said about pushing. *g

Then, about stalking.. Nice of you following me on the net. I don't like it, though.

And lastly: keep it to the bits. Your shortcoming in handling things is yours, keep it so or change it (see above).

When I might send msgs too fast for others at times, they tell me. They usually don't do so more than a month later.

I intend to contribute to the project. That might be possible or not in the future. Depending on the communication, clearly.

Josh wrote: Regarding your code proposal, I decided to rewrite the function myself.

That's perfectly ok, I thought so as the code wasn't yet reentrant regarding multiple devices.

Josh wrote: I guess I should have contacted you before the release;

Well. Yeah..

Josh wrote:I did indeed miss the bit about the interface numbers. That said, it is probably system dependent if interfaces are assigned to a driver in an increasing order. I never had annother outcome on my machines and systems, but I have reports from others about differences between kernel device numbering order and interface order.

Ah, you intend that the sysfs path id and the ttyUSB id numbers don't have to be the same on various systems (issue of vocabulary..)? W/ order you mean, the sysfs 0 could very well become correlated to the ttyUSB3 device name? Ok, now I get it.

That didn't occur to the systems I handled here: debian w/ vanilla kernels, ubuntu w/ stock kernels. Hm. Ok, those reports you're hinting might also happen to be caused not only by different systems but probably more so by different kernel versions. That's the pci ordering issue as well..

Oh, pity.. Well then won't be that helpful, my patch, wouldn't it? So the issue here w/ the interleaving gsmmodem link correctness is still open. I'm looking forward for your ideas then in fixing that one..

Josh wrote: I'm not sure if that is a bug or just the state of things; I'll try to get information or dig into the source code.

Hm, are you sure that number correlation problem is exactly what those report you mentioned hint at? I mean, it seems somewhat natural that the sysfs 1 becomes ttyUSB1. And it was up to now perfectly consistent here.

That'd be somewhat strange if there happened to exist a sysfs 4 with ttyUSB4. But then I'm not yet into the tty code..

Ah, one last issue: In the reference file on the usb-modeswitch front page you mention my name - misspelled. If you wouldn't mind after all..

Thank you.

Cheers,

Nils

olia wrote:Then, about stalking.. Nice of you following me on the net. I don't like it, though.

I am a subscriber and occasional contributor to the linux-usb mailing list. No need to stalk. Just noted that you were - well, a little impatient. And I was not alone with that view.

olia wrote:Your shortcoming in handling things is yours, keep it so or change it (see above).

Now that's very rude. From my point of view that crosses the line.
How I handle things is my personal business. I'm not getting paid for it after all.

olia wrote:When I might send msgs too fast for others at times, they tell me. They usually don't do so more than a month later.

That's not the issue here. You were the one to complain about a late release. I call that pushing.

olia wrote:Ah, one last issue: In the reference file on the usb-modeswitch front page you mention my name - misspelled. If you wouldn't mind after all..

Will fix that, of course.

I wonder why the sysfs id and the ttyUSB id could/should be or not be corresponding.



This specific msg you're talking about was the result of my lack of xp about how long it would take for such a patch to get included. Together w/ the fact that a kernel release was immediate and the recommendation to ask if a patch might get dropped I did as recommended. I was politely asked to be patient with it.

Maybe that helps you getting the point.
Please try to get the big picture before judging, if at all.. your comment was way off.


# .. were the one to complain about a late release.
I only wondered about a comment on my patch. My intent was to
get to know whether it's working well out there, too. And if I made you feel getting pushed by asking about a release/integration (I was convinced the patch worked ok, as my xp w/ it on debian, ubuntu and kernels .33.4 and .32.x was positive) it was mainly because that would have been supportive as there wouldn't be any more need to patch every single client's installation.

Next time I'll try and be less enthusiastic about getting input.

I've been awaiting just a msg telling me: ok, I'll see to it, works, or not, or: please wait.

Cheers

I thank you for all of your contributions and I added you to the list of code contributors, but I suggest you look for annother project to support.