public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roger Quadros <roger.quadros@nokia.com>
To: ext Alan Stern <stern@rowland.harvard.edu>
Cc: <gregkh@suse.de>, <linux-usb@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] usb: gadget: storage: Add fsg_get_toc helper
Date: Wed, 9 Mar 2011 17:37:36 +0200	[thread overview]
Message-ID: <4D779EC0.5010702@nokia.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1103091005570.1965-100000@iolanthe.rowland.org>

On 03/09/2011 05:10 PM, ext Alan Stern wrote:

>> +	case 2:
>> +		/* Raw TOC */
>> +		memset(buf, 0, 37);	/* Header + A0, A1&  A2 descriptors */
>> +		buf[1] = 37;		/* 4 + 3*11 */
>
> There's no reason to do it this way.  The compiler is a lot better than
> you are at addition.  Just put 4 + 3*11 in the assignment statement,
> and in the comment explain what the numbers mean.

OK.

>
>> +		buf[2] = 1;		/* First complete session */
>> +		buf[3] = 2;		/* Last complete session */
>> +
>> +		buf += 4;
>> +		/* A0 point */
>> +		buf[0] = 1;		/* Session number */
>> +		buf[1] = 0x16;		/* Data track, copying alowed */
>> +		/* 2 - Track number 0 ->  TOC */
>> +		buf[3] = 0xA0;		/* Point A0 */
>> +		/* 4, 5, 6 - Min, sec, frame is zero */
>> +		/* 7 - zero */
>> +		buf[8] = 1;		/* Pmin: 1st track number */
>> +		/* 9 - disc type 0: CD-ROM/DA with 1st track in mode 1 */
>> +		/* 10 - pframe 0 */
>> +
>> +		buf += 11;
>> +		/* A1 point*/
>> +		buf[0] = 1;		/* Session number */
>> +		buf[1] = 0x16;		/* Data track, copying alowed */
>> +		/* 2 - Track number 0 ->  TOC */
>> +		buf[3] = 0xA1;		/* Point A1 */
>> +		/* 4, 5, 6 - Min, sec, frame is zero */
>> +		/* 7, zero */
>> +		buf[8] = 1;		/* Pmin: last track number */
>> +		/* 9, 10 - pmin and pframe are 0 */
>> +
>> +		buf += 11;
>> +		/* A2 point*/
>> +		buf[0] = 1;		/* Session number */
>> +		buf[1] = 0x16;		/* Data track, copying alowed */
>> +		/* 2 - Track number 0 ->  TOC */
>> +		buf[3] = 0xA2;		/* Point A2 */
>> +		/* 4, 5, 6 - Min, sec, frame is zero */
>> +		/* 7, 8, 9, 10 - zero, Pmin, Psec, Pframe of Lead out */
>> +		store_cdrom_address(&buf[7], msf, curlun->num_sectors);
>
> These things could be put into a loop, instead of a separate function.

Yes loop is better than function for this case.

>
>> +		return 37;
>
> It might be a good idea to use a variable instead of having all these
> "37"s floating around.  It would make future updates more reliable.

OK.

-- 
regards,
-roger

  reply	other threads:[~2011-03-09 15:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 12:21 [PATCH 0/3] usb: gadget: storage: Make CD-ROM emulation work with Mac OS-X Roger Quadros
2011-03-09 12:21 ` [PATCH 1/3] usb: gadget: storage: Add fsg_get_toc helper Roger Quadros
2011-03-09 12:21   ` [PATCH 2/3] usb: gadget: file_storage: Make CD-ROM emulation work with Mac OS-X Roger Quadros
2011-03-09 12:21     ` [PATCH 3/3] usb: gadget: f_mass_storage: " Roger Quadros
2011-03-09 13:41   ` [PATCH 1/3] usb: gadget: storage: Add fsg_get_toc helper Sergei Shtylyov
2011-03-09 14:08     ` Roger Quadros
2011-03-09 15:10   ` Alan Stern
2011-03-09 15:37     ` Roger Quadros [this message]
2011-03-09 16:07   ` Alan Stern
2011-03-10 14:54     ` Roger Quadros

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=4D779EC0.5010702@nokia.com \
    --to=roger.quadros@nokia.com \
    --cc=gregkh@suse.de \
    --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