The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Kyle McMartin <kmcmartin@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] padlock: don't whinge when loaded on a non-VIA cpu
Date: Tue, 8 Jul 2008 15:04:27 -0400	[thread overview]
Message-ID: <20080708190427.GA28899@phobos.i.cabal.ca> (raw)

I've become seriously tired of seeing these messages on every machine
running an i386 Fedora kernel...

padlock: VIA PadLock not detected.
padlock: VIA PadLock Hash Engine not detected.

So let's eliminate them!

Signed-off-by: Kyle McMartin <kmcmartin@redhat.com>

---
diff --git a/drivers/crypto/padlock-aes.c b/drivers/crypto/padlock-aes.c
index bb30eb9..c11f456 100644
--- a/drivers/crypto/padlock-aes.c
+++ b/drivers/crypto/padlock-aes.c
@@ -384,6 +384,9 @@ static int __init padlock_init(void)
 {
 	int ret;
 
+	if (!(boot_cpu_data.x86_vendor == X86_VENDOR_CENTAUR))
+		return -ENODEV;
+
 	if (!cpu_has_xcrypt) {
 		printk(KERN_ERR PFX "VIA PadLock not detected.\n");
 		return -ENODEV;
diff --git a/drivers/crypto/padlock-sha.c b/drivers/crypto/padlock-sha.c
index c666b4e..9b360fb 100644
--- a/drivers/crypto/padlock-sha.c
+++ b/drivers/crypto/padlock-sha.c
@@ -253,6 +253,9 @@ static int __init padlock_init(void)
 {
 	int rc = -ENODEV;
 
+	if (!(boot_cpu_data.x86_vendor == X86_VENDOR_CENTAUR))
+		return -ENODEV;
+
 	if (!cpu_has_phe) {
 		printk(KERN_ERR PFX "VIA PadLock Hash Engine not detected.\n");
 		return -ENODEV;

             reply	other threads:[~2008-07-08 19:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-08 19:04 Kyle McMartin [this message]
2008-07-08 18:52 ` [PATCH] padlock: don't whinge when loaded on a non-VIA cpu Alan Cox
2008-07-08 19:37   ` Kyle McMartin
2008-07-08 21:21     ` Joe Perches
2008-07-08 22:08     ` Rik van Riel
2008-07-09  5:58     ` Herbert Xu
2008-07-08 20:04 ` Krzysztof Halasa

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=20080708190427.GA28899@phobos.i.cabal.ca \
    --to=kmcmartin@redhat.com \
    --cc=kyle@mcmartin.ca \
    --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