From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: Deal with ATA8-ACS proposed Trusted/Treacherous Computing features
Date: Tue, 30 Oct 2007 09:27:39 -0400 [thread overview]
Message-ID: <4727314B.1090801@garzik.org> (raw)
In-Reply-To: <20071012173918.3f6d2760@the-village.bc.nu>
Alan Cox wrote:
> Historically word 48 in the identify data was used to mean 32bit I/O was
> supported for VLB IDE etc. ATA8 reassigns this word to the Trusted
> Computing Group, where it is used for TCG features. This means that an
> ATA8 TCG drive is going to trigger 32bit I/O on some systems which will
> be funny. Perhaps thats why T13 gave them the word.
>
> Anyway we need to sort this out ready for ATA8 so:
> - Reorder the ata.h header a bit so the ata_version function occurs early
> in it
> - Make dword_io check the ATA version
> - Add an ATA8 version checking TCG presence test
>
> While we are at it the current drafts have a flaw where it may not be
> possible to disable TCG features at boot (and opt out of the trusted
> model) as TCG intends because it relies on presence of a different
> optional feature (DCS). Handle this in software by refusing the TCG
> commands if libata.allow_tpm is not set. (We must make it possible as
> some environments such as proprietary VDR devices will doubtless want to
> use it to lock up content)
>
> Finally as with CPRM print a warning so that the user knows they may not
> be able to full access and use the device.
>
> Alan
>
> Signed-off-by: Alan Cox <alan@redhat.com>
seems fairly reasonable... 2.6.24-rc?
next prev parent reply other threads:[~2007-10-30 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 16:39 [PATCH] libata: Deal with ATA8-ACS proposed Trusted/Treacherous Computing features Alan Cox
2007-10-25 9:00 ` Jeff Garzik
2007-10-25 12:47 ` Alan Cox
2007-10-30 13:27 ` Jeff Garzik [this message]
2007-10-30 13:32 ` Alan Cox
2007-10-30 13:58 ` Jeff Garzik
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=4727314B.1090801@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).