From: "Randy.Dunlap" <rddunlap@osdl.org>
To: David Brownell <david-b@pacbell.net>
Cc: p.lavarre@ieee.org, stern@rowland.harvard.edu,
linux-scsi@vger.kernel.org, patmans@us.ibm.com,
mdharm-scsi@one-eyed-alien.net, alex@netchip.com,
jback@mpc-data.co.uk
Subject: Re: usb storage traces
Date: Tue, 16 Dec 2003 09:00:43 -0800 [thread overview]
Message-ID: <20031216090043.49eea96a.rddunlap@osdl.org> (raw)
In-Reply-To: <3FD0BCED.2070205@pacbell.net>
On Fri, 05 Dec 2003 09:14:21 -0800 David Brownell <david-b@pacbell.net> wrote:
| Pat LaVarre wrote:
| >>>What is FSG?
| >>
| >>...
| >>... File-backed Storage Gadget.
| >>It's a driver for a Linux-based USB _device_ (as opposed to _host_) that
| >>emulates a USB Mass Storage device, using a file or block device as
| >>backing storage in somewhat the same manner as the loop driver.
| >>... Unfortunately, ...
| >
| >
| > Wow, our lead FSG developer has no Linux USB _device_.
|
| Well, he does have the "dummy_hcd" which lets him test
| on the same machine running the USB host ... I'll leave
| it to experts to contrast that with CONFIG_SCSI_DEBUG.
|
| The driver was basically working before it hit real
| hardware.
|
|
| > Ouch. Some sponsor with money should fix that.
|
| Or Santa Claus ... ;)
or http://www.linux-usb.org/beanieForm.html
(sorry about my lateness, still catching up)
--
~Randy
MOTD: Always include version info.
next prev parent reply other threads:[~2003-12-16 17:01 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 18:30 usb storage traces Alan Stern
2003-12-04 18:44 ` Matthew Dharm
2003-12-04 20:59 ` Alan Stern
2003-12-04 21:27 ` Matthew Dharm
2003-12-04 21:33 ` Pat LaVarre
2003-12-04 21:34 ` Pat LaVarre
2003-12-04 21:37 ` Pat LaVarre
2003-12-04 21:38 ` Pat LaVarre
2003-12-04 22:24 ` Pat LaVarre
2003-12-04 22:28 ` Pat LaVarre
2003-12-05 3:56 ` Informational Exception mpage [was: usb storage traces] Douglas Gilbert
2003-12-05 15:32 ` Alan Stern
2003-12-05 16:02 ` Pat LaVarre
2003-12-05 15:01 ` usb storage traces Alan Stern
2003-12-05 17:18 ` bCWBCBLength is cb length no when Pat LaVarre
2003-12-05 18:55 ` Alan Stern
2003-12-05 19:29 ` Pat LaVarre
2003-12-05 17:19 ` usb storage traces Pat LaVarre
2003-12-05 18:22 ` Alan Stern
2003-12-05 5:08 ` Patrick Mansfield
2003-12-05 16:01 ` Alan Stern
2003-12-05 16:11 ` Pat LaVarre
2003-12-05 17:14 ` David Brownell
2003-12-05 17:35 ` Pat LaVarre
2003-12-05 18:21 ` Alan Stern
2003-12-05 18:41 ` Pat LaVarre
2003-12-05 18:24 ` David Brownell
2003-12-16 17:00 ` Randy.Dunlap [this message]
2003-12-16 17:07 ` Pat LaVarre
2003-12-05 4:31 ` Douglas Gilbert
[not found] <20031219091450.GC828@one-eyed-alien.net>
2003-12-19 14:51 ` Alan Stern
2003-12-19 16:21 ` Pat LaVarre
2003-12-20 23:56 ` Matthew Dharm
2003-12-21 2:26 ` Alan Stern
[not found] <1070649445.12411.347.camel@patibmrh9>
2003-12-05 19:27 ` Alan Stern
2003-12-05 20:27 ` Pat LaVarre
-- strict thread matches above, loose matches on Subject: below --
2003-12-04 16:13 Pat LaVarre
2003-11-10 22:04 Pat LaVarre
2003-11-11 21:59 ` Pat LaVarre
2003-11-13 18:42 ` Pat LaVarre
2003-09-22 23:07 [linux-usb-devel] Re: USB storage problems on OHCI Andries.Brouwer
2003-09-22 23:25 ` usb storage traces Pat LaVarre
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=20031216090043.49eea96a.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=alex@netchip.com \
--cc=david-b@pacbell.net \
--cc=jback@mpc-data.co.uk \
--cc=linux-scsi@vger.kernel.org \
--cc=mdharm-scsi@one-eyed-alien.net \
--cc=p.lavarre@ieee.org \
--cc=patmans@us.ibm.com \
--cc=stern@rowland.harvard.edu \
/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