From: Jan Kiszka <jan.kiszka@web.de>
To: "David S. Ahern" <daahern@cisco.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] EHCI support - device recognized, but no data
Date: Sat, 06 Mar 2010 17:42:25 +0100 [thread overview]
Message-ID: <4B9285F1.3060106@web.de> (raw)
In-Reply-To: <4B9077C9.4040309@cisco.com>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
David S. Ahern wrote:
> Jan:
>
> I spent some more time on the EHCI support today. With the attached
> patch (delta to the patch from yesterday) a USB key is recognized within
> the guest (FC-12):
>
> scsi 2:0:0:0: Direct-Access Kingston DT HyperX PMAP PQ: 0
> ANSI: 0 CCS
> sd 2:0:0:0: Attached scsi generic sg1 type 0
> sd 2:0:0:0: [sda] 15646720 512-byte logical blocks: (8.01 GB/7.46 GiB)
> sd 2:0:0:0: [sda] Write Protect is off
> sd 2:0:0:0: [sda] Mode Sense: 23 00 00 00
> sd 2:0:0:0: [sda] Assuming drive cache: write through
> sd 2:0:0:0: [sda] Assuming drive cache: write through
> sda: sda1 sda2
> sd 2:0:0:0: [sda] Assuming drive cache: write through
> sd 2:0:0:0: [sda] Attached SCSI removable disk
>
>
> Unfortunately, fdisk fails to show any data. I'll be out for a few days,
> so I won't get back to this until next week.
>
Cool! Actually, I'm more lucky: I can access the flash of my mobile as a
mass storage. Performance (linear reading) is half of native if
debugging is disabled (0.5 vs. 1 MByte/s). But one try also caused an
"USB stall".
Patch committed. I will also look for some cleanups (build breaks for
non-x86 targets) and more tests soon.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2010-03-06 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 3:17 [Qemu-devel] [PATCH] EHCI support - device recognized, but no data David S. Ahern
2010-03-06 16:42 ` Jan Kiszka [this message]
2010-03-06 18:25 ` Kevin Wolf
2010-03-07 11:32 ` Jan Kiszka
2010-03-09 17:44 ` David S. Ahern
2010-03-10 7:38 ` Jan Kiszka
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=4B9285F1.3060106@web.de \
--to=jan.kiszka@web.de \
--cc=daahern@cisco.com \
--cc=qemu-devel@nongnu.org \
/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.