From: "Pali Rohár" <pali@kernel.org>
To: linux-mmc@vger.kernel.org
Subject: Announce: sdioutils (lssdio & sdioids)
Date: Tue, 14 Feb 2023 20:57:02 +0100 [thread overview]
Message-ID: <20230214195702.ungo5roxliq7pjas@pali> (raw)
Hello! I would like to inform about new (or rather old) sdioutils
project, which is on github: https://github.com/sdioutils/
It aimed to be collection of SDIO programs for Linux systems.
Currently it contains two things which can be useful for both users and
developers:
* lssdio - https://github.com/sdioutils/lssdio - tool which prints all
connected and registered SDIO devices in similar format than lspci or
lsusb, including tree and verbose formats (Linux v5.10+ required for
printing all information)
* sdioids - https://github.com/sdioutils/sdioids - database file
sdio.ids of known SDIO devices, in format inspired by pci.ids and
which is already used by lssdio
This new sdioids contains updated and imported database file from the
old udev project (which seems to not be updated anymore).
If you look into the repository, both parts are more than year old and
I did not announced it before because more people promised to test or
improve database... but nothing happened, only promises. So I decided to
announce it now at least in this state. I think that it can be useful
even in the current state.
So if you want to improve it or add new SDIO cards into database, feel
free to open a pull request on project page. I think that having some
central point of sdio.ids database can be useful also for other
projects.
next reply other threads:[~2023-02-14 19:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 19:57 Pali Rohár [this message]
2023-02-15 13:15 ` Announce: sdioutils (lssdio & sdioids) Ulf Hansson
2023-02-15 19:05 ` Pali Rohár
2023-03-13 20:03 ` Pali Rohár
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=20230214195702.ungo5roxliq7pjas@pali \
--to=pali@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox