RE: another testmgr question

[Pascal Van Leeuwen <pvanleeuwen@insidesecure.com>]

> > you can simply do this in the driver instead:
> >
> >         if (req->cryptlen == 0)
> >                 return 0;
>
> +1. It seems like a firmware update in the hardware or a software
> update to the driver are the ways to proceed.
>

Hardware typically does not involve firmware for things like this.
And you cannot update silicon.

>
> Why isn't the driver able to work around the hardware bugs?
>

1) It's NOT a bug. A bug is something that is not intentional, but
this is well specified behavior of the hardware.
Hardware always has limitations for the simple reason that some
things are simply too complex, costly or risky to implement in HW.

2) Of course you can always workaround things in the driver, but
breaking out all those exception cases slows down the normal cases.
Plus it adds tremendous complexity and bloat to the driver itself.

There should be SOME margin for not having to support everything
but the kitchen sink. Also keeping in mind that most of this HW
existed long before the Crypto API was even conceived.

> I don't think it is wise to remove tests from the Test Manager.
>
Well, in this particular case they are tests intended for development
and not for production use, so I guess it's OK to keep them for that.
Although I would like to see the testing continue if a test fails,
such that I have the option to ignore the ones I don't care about ...

Regards,
Pascal van Leeuwen
Silicon IP Architect, Multi-Protocol Engines @ Inside Secure
www.insidesecure.com