9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: [9fans] usb ohci testing
Date: Thu,  1 Sep 2011 11:11:33 +0100	[thread overview]
Message-ID: <73411ad0a9fc60d4c5722cc195db8924@hamnavoe.com> (raw)

I have a small experimental change to /sys/src/9/pc/usbohci.c which
is needed to get my macbook's built-in bluetooth working with Plan 9
under virtualbox.  As a pleasing side effect, it speeds up reading of
usb1.0 flash disks by about a factor of ten.

Before submitting a patch I want to check that it also works on native
Plan 9, but I don't have suitable hardware.  Would someone running
native Plan 9 on a motherboard with an ohci host adapter like to help,
by building a kernel with the usbohci.c from /n/sources/contrib/miller,
testing that any usb1.0 devices still work, and measuring usb disk speed
before and after with something like:
  time dd -if /dev/sdU0.0/data -of /dev/null -bs 64k -count 16

Note that usb2.0 devices should not be affected by the change, because
they will be handled by the usbehci.c driver.  You can use usb/probe
to check which usb driver (uhci, ohci, ehci) is handling each plugged-in
device.

In theory you can force usb2.0 devices to be handled by ohci as well,
by setting *nousbehci=1 in plan9.ini to disable the ehci driver.  This
doesn't work for me on virtualbox (which gets thoroughly wedged when I
attach a usb2.0 flash drive), but it might work on real hardware.




             reply	other threads:[~2011-09-01 10:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-01 10:11 Richard Miller [this message]
2011-09-01 16:25 ` cinap_lenrek
2011-09-01 16:40   ` erik quanstrom
2011-09-01 16:42   ` cinap_lenrek
2011-09-01 16:47 ` cinap_lenrek
2011-09-01 16:55   ` Richard Miller
2011-09-01 17:23     ` cinap_lenrek
2011-09-01 17:55       ` Richard Miller
2011-09-01 18:22         ` cinap_lenrek
2011-09-01 18:50           ` Richard Miller
2011-09-02  5:06             ` erik quanstrom
2011-09-02  8:48             ` cinap_lenrek
2011-09-02  8:51               ` Richard Miller

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=73411ad0a9fc60d4c5722cc195db8924@hamnavoe.com \
    --to=9fans@hamnavoe.com \
    --cc=9fans@9fans.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).