USB device connect resets 512M Raspberry Pi (most USB devices).

Well, it looks like RasPi has finally solved their USB problem: USB - the Elephant in our Room.  Yes, by locking that thread there won't be any more bad news about USB.  Actually, I sympathize since that thread did attract a certain number of unhelpful comments, but the reality is that USB is a problem and RasPi is probably better off having a single place for those complaints.

One of my all-time favorite comedies is I'm All Right, Jack (1959), a brilliant satire of post-war British labour-mangement relations.  In one scene, long-suffering labour-relations manager Terry-Thomas is looking through the employee suggestion box.  He's appalled by some of the suggestions, making hilarious facial expressions and muttering comments like "what a beastly thing to say" in his trademark voice.  But he says out loud that if they didn't provide the box then the workers would write those comments on the walls.

There is a new USB thread now.

http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=23544

It's supposed to be the "kinder, gentler" version.

How that's supposed to work isn't exactly clear, since the angst seems to be

continually fed by the perceived need to summarize and more prominently

acknowledge the issues for potential buyers, which doesn't appear likely to happen.

Maybe just getting "elephant" out of the title is considered a good enough reason

for the new thread. 

Adding this new thread brings the number of troubleshooting thread topics to 2500.

It's clear how that's supposed to work. Jamesh warns that all complains about the usb will be erased. So, you need to post a clear reproducable problem, or some suggestions to improve things. The elephant made clear that the usb problems very likely won't get fixed. Last time I asked, they answered being suprised there still were usb problems. They obvious didn't seem to realise that a lot of unhappy customers were following that thread, so the problem reports kept coming.

If they thought the problems were gone or just existing with a minority of users, why do they still work on the fiq solution? Or maybe they aren't? I haven't seen a single line of code from it yet. They want the community to help. How can that happen this way?

And when I asked why they needed a gpu implementation after the fiq one, I got no response either.

So they wonder why we are concerned about it? Experiences from the past I guess.

> all complains about the usb will be erased

and not just complaints, but concerns as well.

> And when I asked why they needed a gpu implementation after the fiq one, I got no response either.

I think any fiq solution is unlikely to be mainlined.

I think the goal of a gpu solution would be to use the standard linux

ehci usb driver, which would be a big advantage.

If the elephant in the room is USB, then I guess the ivory poachers are Broadcom (albeit removing the tusks at birth), and RPF are the reserve wardens turning a blind eye as they sell off their toothless pachiderms.   And this illustrates perfectly why one shouldn't push metaphors too far.

Bad metaphors aside, do we know whether the work being done on Pi by Broadcom staff is unofficial and carried out in their own spare time, or is it being done during Broadcom office hours?

If the elephant in the room is USB, then I guess the ivory poachers are Broadcom (albeit removing the tusks at birth), and RPF are the reserve wardens turning a blind eye as they sell off their toothless pachiderms.   And this illustrates perfectly why one shouldn't push metaphors too far.

Bad metaphors aside, do we know whether the work being done on Pi by Broadcom staff is unofficial and carried out in their own spare time, or is it being done during Broadcom office hours?

For what it's worth, Jamesh was always telling they only work on it in their spare time.

It's almost a month ago they started to talk about the fiq solution. Until now, not much was seen about it.

Progress can be followed on the dev Twitter. When someone asked how that worked, the question never got answered.

As long as sales are going well, they really don't seem to care much about the issue.

They announced their webcam, so for people having problems with usb webcams, they have a solution.

Morgaine Dinova wrote:

 

Bad metaphors aside, do we know whether the work being done on Pi by Broadcom staff is unofficial and carried out in their own spare time, or is it being done during Broadcom office hours?

I don't know what the standard practice is in the UK, but in the USA anti-moonlighting clauses in employment agreements explicitly forbid doing technical work for anyone else, whether for pay or for free.  The idea is that if a not-for-profit wants to use your "spare time", they should pay your employer for your services.  Otherwise it's "stealing from the company".  In fact, many USA companies consider all your time are belong to them, and if you've got all this extra time to do great, wonderful technical things then why aren't you using that time on work projects?  So my guess is that Broadcom has explicitly sanctioned use of "spare time" for RasPi, and whether it's done during "office hours" is moot.

A classic Dilbert cartoon takes this one step further:

Wally: Rex, how's your personal life going?

Rex: I don't have one.  That would be like stealing from the company.

It's not this way at all USA companies.  For example, in the old days Hewlett-Packard encourged employees to do fun projects on their own time and allowed them to take whatever parts they needed from the parts room to build fun things.  HP figured that if employees wanted to develop their knowledge and skills on their own time, providing parts was a cheap continuing education program.  The most famous success of this practice (my recollection of the legend) was when a young engineer named Steve Wozniak took a 6502 and other assorted parts and built the prototype of the Apple I.  He offered it to HP, but they weren't interested -- they told him it would be OK if he wanted to do something with it on his own.