From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Christoph Hellwig <hch@infradead.org>,
"Enrico Weigelt, metux IT consult" <info@metux.net>
Cc: linux-kernel@vger.kernel.org, axboe@kernel.dk, linux-ide@vger.kernel.org
Subject: Re: libata: sysctl knob for enabling tpm/opal at runtime
Date: Thu, 6 Jun 2019 16:20:46 +0200 [thread overview]
Message-ID: <3720d2a4-c8e8-0024-bc39-2aed5c4bf0a3@metux.net> (raw)
In-Reply-To: <20190605192320.GA16831@infradead.org>
On 05.06.19 21:23, Christoph Hellwig wrote:
> On Wed, Jun 05, 2019 at 01:36:25PM +0200, Enrico Weigelt, metux IT consult wrote:
>> Hello folks,
>>
>>
>> here's a patchset that allows enabling libata's tpm features (opal)
>> at runtime. Until now we need to boot with special kernel parameter,
>> in order to use OPAL - this patch also adds a sysctl knob for that.
>
> Or you can use the block/sed-opal.c code which doesn't require the
> tweak, and really is the proper way forward to use OPAL.
You're referring to the OPAL ioctl()s ?
hmm, it seems that sed-util doesn't use them at all, but directly
sends raw ata commands.
Shall I use a different userland tool ?
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
prev parent reply other threads:[~2019-06-06 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 11:36 Enrico Weigelt, metux IT consult
2019-06-05 11:36 ` [PATCH v2 1/2] drivers: libata: introduce sysctl directory Enrico Weigelt, metux IT consult
2019-06-05 11:36 ` [PATCH v2 2/2] drivers: libata: add sysctl: 'libata.allow_tpm' for self-encrypted devices Enrico Weigelt, metux IT consult
2019-06-05 19:23 ` libata: sysctl knob for enabling tpm/opal at runtime Christoph Hellwig
2019-06-06 14:20 ` Enrico Weigelt, metux IT consult [this message]
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=3720d2a4-c8e8-0024-bc39-2aed5c4bf0a3@metux.net \
--to=lkml@metux.net \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=info@metux.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®