From: "Michal Nazarewicz" <mina86@mina86.com>
To: "Alan Stern" <stern@rowland.harvard.edu>
Cc: "Felipe Balbi" <balbi@ti.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] usb: gadget: mass_storage: add documentation
Date: Mon, 11 Jun 2012 18:08:49 +0200 [thread overview]
Message-ID: <op.wfqxszn43l0zgt@mpn-glaptop> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1206111021400.1607-100000@iolanthe.rowland.org>
> On Mon, 11 Jun 2012, Michal Nazarewicz wrote:
>> + Mass Storage Gadget (or MSG) acts as a USB Mass Storage device,
>> + appearing to the host as a disk or a CD-ROM drive. It supports
>> + multiple logical units (LUNs). Backing storage for each LUN is
>> + provided by a regular file or a block device, access can be limited
>> + to read-only, and gadget can indicate that it is removable and/or
>> + CD-ROM (the latter implies read-only access).
On Mon, 11 Jun 2012 17:25:15 +0200, Alan Stern <stern@rowland.harvard.edu> wrote:
> Does CD-ROM really imply read-only? If not, shouldn't it?
It indeed does:
curlun->ro = lcfg->cdrom || lcfg->ro;
>> + - ro=b[,b...]
>> +
>> + This parameter specifies whether each logical unit should be
>> + reported as read only. This will prevent host from modifying the
>> + backing files.
>> +
>> + Note that if this flag for given logical unit is false but the
>> + backing file could not be opened in read/write mode, the gadget
>> + will fall back to read only mode anyway.
>> +
>> + The default value for each logical unit is false.
>
> Shouldn't the default be true for logical units that are cdroms?
Indeed. I've changed this last line to: The default value for non-CD-ROM
logical units is false; for logical units simulating CD-ROM it is forced
to true.
> Very good. When you make the small changes listed above, you can add
>
> Acked-by: Alan Stern <stern@rowland.harvard.edu>
I'll resend it tomorrow in case anyone else has any comments.
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michał “mina86” Nazarewicz (o o)
ooo +----<email/xmpp: mpn@google.com>--------------ooO--(_)--Ooo--
prev parent reply other threads:[~2012-06-11 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 12:51 [PATCH 0/4] Minor g_mass_storage improvements Michal Nazarewicz
2012-06-11 12:52 ` [PATCH 1/3] usb: gadget: mass_storage: change default value of the removable parameter Michal Nazarewicz
2012-06-11 12:52 ` [PATCH 2/3] usb: gadget: mass_storage: remove unused options Michal Nazarewicz
2012-06-11 12:52 ` [PATCH 3/3] usb: gadget: mass_storage: add documentation Michal Nazarewicz
2012-06-11 15:25 ` Alan Stern
2012-06-11 16:08 ` Michal Nazarewicz [this message]
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=op.wfqxszn43l0zgt@mpn-glaptop \
--to=mina86@mina86.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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
all inboxes | Powered by JetHome®