On Wed, 8 Sep 2004, Kyle Harris wrote:
> Can I look at urb->dev->devpath? It looks like this is constant and refers to
> the port number?
That's a great idea! It never would have occurred to me. Yes, the first
character of that string will always be the port number below the root hub
(so eith
On Tuesday 07 September 2004 07:01 pm, Alan Stern wrote:
>
> The easiest thing for now is to ignore the second port in each pair.
> Unless you can specify in a TD that it should use both ports?
Can I look at urb->dev->devpath? It looks like this is constant and refers to
the port number?
Thank
On Tuesday 07 September 2004 07:01 pm, Alan Stern wrote:
>
> The easiest thing for now is to ignore the second port in each pair.
> Unless you can specify in a TD that it should use both ports?
You mean not use the second port at all? That's not an option. I have hw with
all 4 ports. I had a 2.4
On Wednesday 08 September 2004 7:29 am, Alan Stern wrote:
> On Tue, 7 Sep 2004, David Brownell wrote:
>
> > On Tuesday 07 September 2004 4:01 pm, Alan Stern wrote:
> > >
> > > A cleaner solution is to treat the pair of ports as a single root hub,
and
> > > keep track of which port each device li
On Tue, 7 Sep 2004, David Brownell wrote:
> On Tuesday 07 September 2004 4:01 pm, Alan Stern wrote:
> >
> > A cleaner solution is to treat the pair of ports as a single root hub, and
> > keep track of which port each device lies below. The problem with this
> > approach is that the existing data
On Tuesday 07 September 2004 4:01 pm, Alan Stern wrote:
>
> A cleaner solution is to treat the pair of ports as a single root hub, and
> keep track of which port each device lies below. The problem with this
> approach is that the existing data structures don't give you any place to
> store that
On Tue, 7 Sep 2004, Kyle Harris wrote:
> I'm fairly new to USB, please forgive my ignorance. The Cypress HC requires
> that each TD specifiy the port, address, and ep. So it seems that the URB
> data would be sent to a single port. I don't understand how this would work
> if data is sent to the
On Tue, 7 Sep 2004, Kyle Harris wrote:
> How do I determine which port a urb is destined to? I'm assuming it is in the
> urb or dev struct somewhere.
URBs aren't directed toward particular ports. The packets will be sent
out _all_ the ports by the hardware. That's why it's called a root _hub_
On Tuesday 07 September 2004 10:59 am, Alan Stern wrote:
> On Mon, 6 Sep 2004, Kyle Harris wrote:
> > Hi,
> >
> > My HC (Cypress CY7C67300) has 2 independent serial engines (SIEs) that
> > each control 2 downstream ports. I currently register each SIE as
> > standalone HCDs, each with 2 ports. The
On Mon, 6 Sep 2004, Kyle Harris wrote:
> Hi,
>
> My HC (Cypress CY7C67300) has 2 independent serial engines (SIEs) that each
> control 2 downstream ports. I currently register each SIE as standalone HCDs,
> each with 2 ports. The first port for each SIE works fine. But. I'm not sure
> how to i
Hi,
My HC (Cypress CY7C67300) has 2 independent serial engines (SIEs) that each
control 2 downstream ports. I currently register each SIE as standalone HCDs,
each with 2 ports. The first port for each SIE works fine. But. I'm not sure
how to insure both ports of the SIE are registered. Should t
11 matches
Mail list logo
