From: "Pali Rohár" <pali.rohar@gmail.com>
To: linux-mmc@vger.kernel.org
Cc: Vratislav Podzimek <vpodzime@redhat.com>
Subject: Distinguish eMMC and uSD in userspace
Date: Tue, 5 Sep 2017 16:19:03 +0200 [thread overview]
Message-ID: <201709051619.03417@pali> (raw)
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
Hello!
I would like to ask... if I get /dev/mmcblk device, how to check in
userspace if it is non-removable eMMC memory or it is removable SD card?
udisks project would like to report correct information and provides
correct "icon" to GUI file managers about state if device is removable
or not.
See reported ticket:
https://github.com/storaged-project/udisks/issues/358
Apparently RM filed in lsblk nor removable sysfs entry
(/sys/block/mmcblk0/removable) could not be used as both of them could
not be used for distinguish between eMMC or uSD card.
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
reply other threads:[~2017-09-05 14:19 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=201709051619.03417@pali \
--to=pali.rohar@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=vpodzime@redhat.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 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).