All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Butterworth <harry@hebutterworth.freeserve.co.uk>
To: maw48@cl.cam.ac.uk
Cc: xen-devel@lists.sourceforge.net
Subject: USB virt 2.6 port status
Date: Fri, 18 Mar 2005 19:07:08 +0000	[thread overview]
Message-ID: <1111172828.6848.4.camel@localhost> (raw)

Progress this week:

The 2.6 front end loads, discovers the 2.4 back-end, installs a USB hcd
device, Linux turns on power to the virtual port, resets it and
discovers the attached device.

Linux sends the first URB.  The behaviour of the Linux USB hub driver
has changed since 2.4.  Where previously it would send a set address
request first it now starts with a get descriptor request.

This get descriptor request currently fails against my USB disgo key,
the hub driver tries to reset the port which isn't supported by the 2.4
back end and no further progress is made.

Some debugging showed that the existing Xen usbif inter-domain protocol
was passing the URB transfer-flags as defined in the usb.h header file
and the definition of the bits in these flags has changed between 2.4
and 2.6 such that the values passed by the 2.6 kernel are incorrect when
interpreted by the 2.4 kernel.

I need to fix the xen usbif protocol so the parameters passed are
expressed independent of the linux kernel headers.

I put in a quick hack for this and re-ran the test but the initial urb
still failed.

I'm not sure whether there are still 2.4/2.6 incompatibilities to fix in
the inter-domain protocol or if the disgo key simply can't cope with the
get descriptor request in which case explicitly handling the get
descritor request in the back-end or implementing resets in the back-end
to allow the front-end to pursue its retry strategy might be the next
step.

More debugging is required.

I'm on vacation for a week now and will resume working on this when I
return.



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

             reply	other threads:[~2005-03-18 19:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-18 19:07 Harry Butterworth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-18 19:19 USB virt 2.6 port status Ian Pratt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1111172828.6848.4.camel@localhost \
    --to=harry@hebutterworth.freeserve.co.uk \
    --cc=maw48@cl.cam.ac.uk \
    --cc=xen-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.