lkml.org 
[lkml]   [2004]   [May]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 2/2] Support for VIA PadLock crypto engine
    On Wed, 12 May 2004, Michal Ludvig wrote:

    > In fact I believe that the hardware-specific drivers (e.g. the S/390 one)
    > should be used in the cryptoapi as well and then the kernel should provide
    > a single, universal device with read/write/ioctl calls for all of them.
    > Not making a separete device for every piece of hardware on the market.
    > Am I wrong?

    Providing a userspace API is an orthogonal issue, and really needs to be
    designed in conjunction with the async hardware API.

    What I am suggesting is that you simply implement something like
    des_z990.c so that C3 users can load crypto alg modules which use their
    hardware.

    - James
    --
    James Morris
    <jmorris@redhat.com>


    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 14:03    [W:0.020 / U:33.228 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site