From: Jaehoon Chung <jh80.chung@samsung.com>
To: Johan RUDHOLM <johan.rudholm@stericsson.com>
Cc: Chris Ball <cjb@laptop.org>,
Jaehoon Chung <jh80.chung@samsung.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Peppe CAVALLARO <peppe.cavallaro@st.com>,
Shashidhar Hiremath <shashidharh@vayavyalabs.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: ANNOUNCE: new "mmc-utils" repository
Date: Wed, 15 Feb 2012 19:55:22 +0900 [thread overview]
Message-ID: <4F3B8F1A.4050601@samsung.com> (raw)
In-Reply-To: <E2E6AC6BFAD06343BA2D97432459C1B60723E982CA@EXDCVYMBSTM005.EQ1STM.local>
On 02/15/2012 12:31 AM, Johan RUDHOLM wrote:
> Hi Chris, Jaehoon,
>
> Chris Ball wrote:
>
>>
>> Hi,
>>
>> On Tue, Feb 14 2012, Jaehoon Chung wrote:
>>> What kernel version is supported? up to linux-3.3? did you know?
>>
>> I think the only requirement is the command submission ioctl, so it
>> should work in every kernel from 3.0 onwards.
>
> Actually, to be able to write to the ext csd via the ioctl, "mmc: core: check for zero length ioctl data" is also required. I think this went into 3.3-rc1.
Hi..Chris, Johan.
I think that mmc extcsd read/write <device> is something wrong..
If mmc extcsd write /dev/mmcblk0, then boot area1/2 is power-on-write-protect. right?
And i ran mmc extcsd read /dev/mmcblk0, and i printed the ext_csd[174](BOOT_WP_STATUS)
That's always 0x0.
That means Boot-area1/2 is not protected.
In do_write_extcsd(), i think that check with BOOT_WP_STATUS[174] whether protected or not.
not BOOT_WP[173].
How think about?
I will send the patch for this.
Best Regards,
Jaehoon Chung
>
> Kind regards, Johan
> --
> 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
>
next prev parent reply other threads:[~2012-02-15 10:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-12 17:03 ANNOUNCE: new "mmc-utils" repository Chris Ball
2012-02-13 19:50 ` Linus Walleij
2012-02-14 5:56 ` Jaehoon Chung
2012-02-14 8:07 ` Johan RUDHOLM
2012-02-14 8:31 ` Jaehoon Chung
2012-02-14 14:53 ` Chris Ball
2012-02-14 15:31 ` Johan RUDHOLM
2012-02-15 10:55 ` Jaehoon Chung [this message]
2012-02-15 12:06 ` Johan RUDHOLM
2012-02-16 20:49 ` Chris Ball
2012-02-14 8:04 ` Johan RUDHOLM
2012-02-14 11:06 ` Chris Ball
2012-02-15 12:55 ` Giuseppe CAVALLARO
2012-02-15 13:35 ` Chris Ball
2012-02-15 13:43 ` Giuseppe CAVALLARO
2012-02-20 14:09 ` Giuseppe CAVALLARO
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=4F3B8F1A.4050601@samsung.com \
--to=jh80.chung@samsung.com \
--cc=cjb@laptop.org \
--cc=johan.rudholm@stericsson.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=shashidharh@vayavyalabs.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.