From: Hans-Christian Egtvedt <egtvedt@samfundet.no>
To: linux-mmc@vger.kernel.org
Subject: Backporting eMMC v5 support to Linux 3.4
Date: Fri, 21 Mar 2014 13:28:44 +0100 [thread overview]
Message-ID: <20140321122844.GA5417@samfundet.no> (raw)
Hello,
I have a device, which has received an eMMC v5 device, and thus the 3.4
kernel the vendor provides does not identify the flash chip anymore.
Looking at the kernel history, it seems very easy to backport support for it.
Would it be as easy as cherry picking commit 6636bad8?
mmc: core: Update the ext-csd.rev check for eMMC5.1
And just when I'm on backporting, perhaps fetching commit 7c4f10ac
mmc: core: production year for eMMC 4.41 and later
Or have I forgotten anything vital?
--
Hans-Christian Egtvedt
reply other threads:[~2014-03-21 12:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140321122844.GA5417@samfundet.no \
--to=egtvedt@samfundet.no \
--cc=linux-mmc@vger.kernel.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 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.