public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Kim <jh4u.kim@samsung.com>
To: 'Jaehoon Chung' <jh80.chung@samsung.com>,
	ulf.hansson@linaro.org, linux-mmc@vger.kernel.org
Subject: RE: [PATCH] mmc: block: Change MMC_IOC_MAX_BYTES
Date: Tue, 18 Oct 2016 19:54:23 +0900	[thread overview]
Message-ID: <0bba01d2292d$fcad7920$f6086b60$@samsung.com> (raw)
In-Reply-To: <e99052e2-de80-57a2-30ae-0baea2328cce@samsung.com>

Hi,

Yes, right. "include/uapi/linux/mmc/ioctl.h"


-----Original Message-----
From: linux-mmc-owner@vger.kernel.org
[mailto:linux-mmc-owner@vger.kernel.org] On Behalf Of Jaehoon Chung
Sent: Tuesday, October 18, 2016 7:52 PM
To: Jeremy Kim; ulf.hansson@linaro.org; linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: block: Change MMC_IOC_MAX_BYTES

Hi,

On 10/18/2016 07:39 PM, Jeremy Kim wrote:
> 
> It is used for limitation of buffer size during IOCTL such as FFU. 
> However, eMMC FW size is bigger than (512L*256).
> (For instance, currently, Samsung eMMC FW size is over 300KB.) So, it 
> needs to increase to execute FFU.
> 
> 
> Signed-off-by: Jeonghan Kim <jh4u.kim@samsung.com>
> ---
>  ioctl.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Where is ioctl.h? "include/uapi/linux/mmc/ioctl.h"?

Best Regards,
Jaehoon Chung

> 
> diff --git a/ioctl.h b/ioctl.h
> index 7e385b8..700a551 100644
> --- a/ioctl.h
> +++ b/ioctl.h
> @@ -69,6 +69,6 @@ struct mmc_ioc_multi_cmd {
>   * is enforced per ioctl call.  For larger data transfers, use the normal
>   * block device operations.
>   */
> -#define MMC_IOC_MAX_BYTES  (512L * 256)
> +#define MMC_IOC_MAX_BYTES  (512L * 1024)
>  #define MMC_IOC_MAX_CMDS    255
>  #endif /* LINUX_MMC_IOCTL_H */
> --
> 1.9.1
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" 
> in the body of a message to majordomo@vger.kernel.org More majordomo 
> info at  http://vger.kernel.org/majordomo-info.html
> 
> 
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the
body of a message to majordomo@vger.kernel.org More majordomo info at
http://vger.kernel.org/majordomo-info.html



  reply	other threads:[~2016-10-18 10:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20161018103940epcas1p1da351e49f18c5707eea3b817a5d2f865@epcas1p1.samsung.com>
2016-10-18 10:39 ` [PATCH] mmc: block: Change MMC_IOC_MAX_BYTES Jeremy Kim
2016-10-18 10:51   ` Jaehoon Chung
2016-10-18 10:54     ` Jeremy Kim [this message]
     [not found] <CGME20161019113147epcas1p23270c03a8ea440a88dd0d6ab85af8051@epcas1p2.samsung.com>
2016-10-19 11:31 ` Jeremy Kim
2016-10-21  6:38   ` Jaehoon Chung
2016-10-21  8:21   ` Ulf Hansson

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='0bba01d2292d$fcad7920$f6086b60$@samsung.com' \
    --to=jh4u.kim@samsung.com \
    --cc=jh80.chung@samsung.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ulf.hansson@linaro.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