Bug#552270: orion5x crypto module not enabled

To: remur@gmx.net, 552270@bugs.debian.org
Subject: Bug#552270: orion5x crypto module not enabled
From: Martin Michlmayr <tbm@cyrius.com>
Date: Mon, 26 Oct 2009 00:16:10 +0800
Message-id: <[🔎] 20091025161610.GI2742@deprecation.cyrius.com>
Reply-to: Martin Michlmayr <tbm@cyrius.com>, 552270@bugs.debian.org
In-reply-to: <[🔎] 200910242359.12655.remur@gmx.net>
References: <[🔎] 200910242359.12655.remur@gmx.net>

* Karsten König <remur@gmx.net> [2009-10-24 23:59]:
> Martin Michlmayr backported the CESA patches from 2.6.32 to 2.6.31 but didn't
> enable them as module even though changelog indicates that
>    * [armel/orion5x] Enable CRYPTO_DEV_MV_CESA.

I enabled it for orion5x but not for kirkwood because afaik there are
differences between the CESA in Orion5x and Kirkwood.  I'll ask if the
current driver works on Kirkwood too.
-- 
Martin Michlmayr
http://www.cyrius.com/

Reply to:

References:
- Bug#552270: orion5x crypto module not enabled
  - From: Karsten König <remur@gmx.net>

Prev by Date: Processed: tagging 512339
Next by Date: Processed: retitle 512482 to Limited brightness control on Fujitsu-Siemens laptop, severity of 512482 is normal
Previous by thread: Bug#552270: orion5x crypto module not enabled
Next by thread: firmware-nonfree_0.20_amd64.changes is NEW
Index(es):
- Date
- Thread