From: Igor Kononenko <i.kononenko@yadro.com>
To: Felipe Balbi <balbi@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: <openbmc@lists.ozlabs.org>,
Igor Kononenko <i.kononenko@yadro.com>,
<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH 4/6] fms: Support the DVD/BD images size over 2.1Gb
Date: Sun, 27 Jun 2021 00:18:17 +0300 [thread overview]
Message-ID: <20210626211820.107310-5-i.kononenko@yadro.com> (raw)
In-Reply-To: <20210626211820.107310-1-i.kononenko@yadro.com>
Adds the ability to use the FMS image size greater than 2.1Gb. This
limitation is due to the maximum number of available frames on the
CD-ROM media.
An incoming implementation of additional media formats (DVD-ROM, BD-ROM)
should support both formats' possible capacity.
End-user-impact: Now, the FMS able to use a medium-image backend file,
which size is more significant than 2.1Gb
Signed-off-by: Igor Kononenko <i.kononenko@yadro.com>
---
drivers/usb/gadget/function/storage_common.c | 9 +--------
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/drivers/usb/gadget/function/storage_common.c b/drivers/usb/gadget/function/storage_common.c
index b883b8b7b05b..468f7622b11d 100644
--- a/drivers/usb/gadget/function/storage_common.c
+++ b/drivers/usb/gadget/function/storage_common.c
@@ -242,15 +242,8 @@ int fsg_lun_open(struct fsg_lun *curlun, const char *filename)
num_sectors = size >> blkbits; /* File size in logic-block-size blocks */
min_sectors = 1;
- if (curlun->cdrom) {
+ if (curlun->cdrom)
min_sectors = 300; /* Smallest track is 300 frames */
- if (num_sectors >= 256*60*75) {
- num_sectors = 256*60*75 - 1;
- LINFO(curlun, "file too big: %s\n", filename);
- LINFO(curlun, "using only first %d blocks\n",
- (int) num_sectors);
- }
- }
if (num_sectors < min_sectors) {
LINFO(curlun, "file too small: %s\n", filename);
rc = -ETOOSMALL;
--
2.32.0
next prev parent reply other threads:[~2021-06-26 21:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210626211820.107310-1-i.kononenko@yadro.com>
2021-06-26 21:18 ` [PATCH 1/6] usb:gadget:mass-storage: Improve the signature of SCSI handler function Igor Kononenko
2021-06-27 14:18 ` Alan Stern
[not found] ` <ded6e647-6dd9-ebd0-0ea5-b20e113bf57f@yadro.com>
2021-06-27 16:39 ` Alan Stern
2021-06-26 21:18 ` [PATCH 2/6] usb:gadget:mass-storage: refactoring the SCSI command handling Igor Kononenko
2021-06-26 23:29 ` kernel test robot
2021-06-27 14:23 ` Alan Stern
[not found] ` <bc8059b1-0f56-fc3b-6ec8-0bf1043fc9e5@yadro.com>
2021-06-28 1:06 ` Alan Stern
2021-06-26 21:18 ` [PATCH 3/6] fms: Add TOC/PMA/ATIP DVD-ROM capabilities Igor Kononenko
2021-06-27 14:29 ` Alan Stern
[not found] ` <3f9c6e4a-18b7-db11-8b23-f0473a649d06@yadro.com>
2021-06-28 14:31 ` Alan Stern
2021-06-26 21:18 ` Igor Kononenko [this message]
2021-06-26 21:18 ` [PATCH 5/6] FMS: Add the SCSI Get Configuration command Igor Kononenko
2021-06-27 0:44 ` kernel test robot
2021-06-27 4:42 ` kernel test robot
2021-06-28 9:53 ` Christoph Hellwig
2021-06-26 21:18 ` [PATCH 6/6] FMS: Add SCSI Read Disc Information command Igor Kononenko
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=20210626211820.107310-5-i.kononenko@yadro.com \
--to=i.kononenko@yadro.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=openbmc@lists.ozlabs.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 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).