On Tuesday 11 July 2006 1:56 am, Ajay Jain wrote:
> May be yes, but then I have a counter observation. When I use another
> host I always see a reset - suspend - reset - get_device_descriptor -
> reset - set_address sequence. This is something that I observe
> invariably. When I use the old host,
On Tue, 11 Jul 2006, Ajay Jain wrote:
> > I don't know. Have you tried using any sort of USB sniffer program to
> > monitor the host's requests to the bus's root hub?
>
> I will definitely try it, can you suggest some sniffer program
> (windows based), as I have one such sniffer, that causes my
On 7/11/06, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 11 Jul 2006, Ajay Jain wrote:
>
> > > Remember the definitions of reset and suspend. Reset is an SE0 signal,
> > > which is the default bus state when no device is attached or the device's
> > > pull-up resistor hasn't been turned on. Su
On Tue, 11 Jul 2006, Ajay Jain wrote:
> > Remember the definitions of reset and suspend. Reset is an SE0 signal,
> > which is the default bus state when no device is attached or the device's
> > pull-up resistor hasn't been turned on. Suspend is a J signal, which is
> > the default bus state whe
On 7/10/06, Alan Stern <[EMAIL PROTECTED]> wrote:
> On Mon, 10 Jul 2006, Ajay Jain wrote:
>
> > Hi,
> > Am using a windows host and a proprietary device as a function. This
> > is the pre-enumeration stage that I am talking about. I see a very
> > different behavior with what is written in the stan
On Mon, 10 Jul 2006, Ajay Jain wrote:
> Hi,
> Am using a windows host and a proprietary device as a function. This
> is the pre-enumeration stage that I am talking about. I see a very
> different behavior with what is written in the standard or with the
> way windows is supposed to enumerate. The
