From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Thu, 21 Jul 2005 16:49:51 +0100 (BST) Received: from smtp002.bizmail.yahoo.com ([IPv6:::ffff:216.136.172.126]:53917 "HELO smtp002.bizmail.yahoo.com") by linux-mips.org with SMTP id ; Thu, 21 Jul 2005 16:49:35 +0100 Received: (qmail 4331 invoked from network); 21 Jul 2005 15:51:31 -0000 Received: from unknown (HELO ?192.168.1.107?) (ppopov@embeddedalley.com@63.194.214.47 with plain) by smtp002.bizmail.yahoo.com with SMTP; 21 Jul 2005 15:51:30 -0000 Subject: Re: Is there some work done on db1550 for the security engine? From: Pete Popov Reply-To: ppopov@embeddedalley.com To: "Robin H. Johnson" Cc: "'linux-mips@linux-mips.org'" , rolf liu In-Reply-To: <20050721083640.GA26677@curie-int.orbis-terrarum.net> References: <2db32b720507201012712e5cd1@mail.gmail.com> <20050721083640.GA26677@curie-int.orbis-terrarum.net> Content-Type: text/plain Organization: Embedded Alley Solutions, Inc Date: Thu, 21 Jul 2005 08:51:28 -0700 Message-Id: <1121961088.5303.1.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-4) Content-Transfer-Encoding: 7bit Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 8588 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: ppopov@embeddedalley.com Precedence: bulk X-list: linux-mips On Thu, 2005-07-21 at 01:36 -0700, Robin H. Johnson wrote: > On Wed, Jul 20, 2005 at 10:12:04AM -0700, rolf liu wrote: > > Is there any driver availble to use the security engine inside au1550? > Not in the tree, or that I've seen floating around yet. Pete might know > if there is one available somewhere else. I know there is a commercial stack; don't remember who provided it. > Failing that, (and this is an idea I've been toying with for a while) > why not strike a deal with somebody here to write it for you: you can > provide the hardware, and they can write it, for some reasonable > compensation. > > Lack of hardware to test on is probably the biggest stumbling block to > supporting it presently. Well, I have the hardware :) Pete