Am Freitag, 5. Januar 2007 23:15 schrieb Alan Stern:
> > > Furthermore, this would mean that the device continues to draw 500 mA of
> > > current even though the descriptor reverts back to indicating only 100
> > > mA.
> > > That doesn't make sense.
> >
> > I agree. Based on further experiment
On Fri, 5 Jan 2007, Mike King wrote:
> > > What I see with the analyzer is that the secret command immediately
> > > preceeds
> > > the set-config. And, yes, a second set-config causes the device to
> > > restore the power-on default device descriptor indicating 100ma.
> >
> > How do you know t
>
> Am Donnerstag, 4. Januar 2007 17:39 schrieb Mike King:
> > CLASS_SPECIFIC CMD (secret command) value=0, index=1, length=0
> > SET_CONFIGURATION config value = 1,index=0,length=0
> > reset
> > reset
> > reset
> > GET_DESCRIPTOR DEVICE
> > SET_ADDRESS
> > GET_DESC
>
> On Thu, 4 Jan 2007, Mike King wrote:
>
> > Alan,
> >
> > >
> > > On Thu, 4 Jan 2007, Mike King wrote:
> > >
> > > > > > > > Anytime a SET_CONFIGURATION is sent to the device without being
> > > > > > > > preceeded
> > > > > > > > by the secret vendor specific command the device reverts to
On Thu, 4 Jan 2007, Mike King wrote:
> Alan,
>
> >
> > On Thu, 4 Jan 2007, Mike King wrote:
> >
> > > > > > > Anytime a SET_CONFIGURATION is sent to the device without being
> > > > > > > preceeded
> > > > > > > by the secret vendor specific command the device reverts to the
> > > > > > > pre
Am Donnerstag, 4. Januar 2007 17:39 schrieb Mike King:
> CLASS_SPECIFIC CMD (secret command) value=0, index=1, length=0
> SET_CONFIGURATION config value = 1,index=0,length=0
> reset
> reset
> reset
> GET_DESCRIPTOR DEVICE
> SET_ADDRESS
> GET_DESCRIPTOR DEVICE
> G
Alan,
>
> On Thu, 4 Jan 2007, Mike King wrote:
>
> > > > > > Anytime a SET_CONFIGURATION is sent to the device without being
> > > > > > preceeded
> > > > > > by the secret vendor specific command the device reverts to the
> > > > > > previous
> > > > > > device descriptor data indicating 100m
On Thu, 4 Jan 2007, Mike King wrote:
> > > > > Anytime a SET_CONFIGURATION is sent to the device without being
> > > > > preceeded
> > > > > by the secret vendor specific command the device reverts to the
> > > > > previous
> > > > > device descriptor data indicating 100ma.
When you say "precee
Am Donnerstag, 4. Januar 2007 12:26 schrieb David Brownell:
> On Thursday 04 January 2007 12:27 am, Oliver Neukum wrote:
>
> > > I'll check tomorrow and see. Does HUB electronics include over-current
> > > sensing to detect that a device that says it wants 100ma is in fact
> > > attemping to draw
On Thursday 04 January 2007 12:27 am, Oliver Neukum wrote:
> > I'll check tomorrow and see. Does HUB electronics include over-current
> > sensing to detect that a device that says it wants 100ma is in fact
> > attemping to draw 500ma ?
>
> No, protection is per hub, not port.
... on some hardwa
Am Donnerstag, 4. Januar 2007 09:09 schrieb Mike King:
> >
> > Am Donnerstag, 4. Januar 2007 07:30 schrieb Mike King:
> > > Let me repeat this. Upon seeing the secret command, the next call to
> > > a SET_CONFIGURATION will cause the BB to reset itself and actually change
> > > the device descr
>
> Am Donnerstag, 4. Januar 2007 07:30 schrieb Mike King:
> > Let me repeat this. Upon seeing the secret command, the next call to
> > a SET_CONFIGURATION will cause the BB to reset itself and actually change
> > the device descriptor from indicating it uses the default power setting of
> > 1
>
> Am Donnerstag, 4. Januar 2007 08:25 schrieb Mike King:
> > >
> > > Am Donnerstag, 4. Januar 2007 07:58 schrieb Mike King:
> > > > >
> > > > > Am Donnerstag, 4. Januar 2007 07:30 schrieb Mike King:
> > > > > > Anytime a SET_CONFIGURATION is sent to the device without being
> > > > > > precee
Am Donnerstag, 4. Januar 2007 07:30 schrieb Mike King:
> Let me repeat this. Upon seeing the secret command, the next call to
> a SET_CONFIGURATION will cause the BB to reset itself and actually change
> the device descriptor from indicating it uses the default power setting of
> 100ma to the h
Am Donnerstag, 4. Januar 2007 08:25 schrieb Mike King:
> >
> > Am Donnerstag, 4. Januar 2007 07:58 schrieb Mike King:
> > > >
> > > > Am Donnerstag, 4. Januar 2007 07:30 schrieb Mike King:
> > > > > Anytime a SET_CONFIGURATION is sent to the device without being
> > > > > preceeded
> > > > > by
>
> Am Donnerstag, 4. Januar 2007 07:58 schrieb Mike King:
> > >
> > > Am Donnerstag, 4. Januar 2007 07:30 schrieb Mike King:
> > > > Anytime a SET_CONFIGURATION is sent to the device without being
> > > > preceeded
> > > > by the secret vendor specific command the device reverts to the previous
Am Donnerstag, 4. Januar 2007 07:58 schrieb Mike King:
> >
> > Am Donnerstag, 4. Januar 2007 07:30 schrieb Mike King:
> > > Anytime a SET_CONFIGURATION is sent to the device without being preceeded
> > > by the secret vendor specific command the device reverts to the previous
> > > device descript
>
> Am Donnerstag, 4. Januar 2007 07:30 schrieb Mike King:
> > Anytime a SET_CONFIGURATION is sent to the device without being preceeded
> > by the secret vendor specific command the device reverts to the previous
> > device descriptor data indicating 100ma. A normal reset causes it
> > to defau
Am Donnerstag, 4. Januar 2007 07:30 schrieb Mike King:
> Anytime a SET_CONFIGURATION is sent to the device without being preceeded
> by the secret vendor specific command the device reverts to the previous
> device descriptor data indicating 100ma. A normal reset causes it
> to default to the nor
USB Gurus,
In getting the Blackberry device working on Linux I have run into
a snag. I know what is wrong and I am looking for suggestions as to
the best approach to making it work. Right now, the only way I see
this happening is by making some changes to USB core. So I am hoping
those of you
20 matches
Mail list logo
