From: Niranjan <niranjan_cs2905@yahoo.com>
To: James Morris <jmorris@redhat.com>
Cc: Vladimir Kondratiev <vkondra@mail.ru>,
Matt Mackall <mpm@selenic.com>,
netdev@oss.sgi.com
Subject: Re: kernel bug at sched.c:564! + linux kernel 2.4.25
Date: Wed, 28 Jul 2004 09:30:29 -0700 (PDT) [thread overview]
Message-ID: <20040728163029.55069.qmail@web53001.mail.yahoo.com> (raw)
In-Reply-To: <Xine.LNX.4.44.0407281210270.11261-100000@dhcp83-76.boston.redhat.com>
The driver code is in kernel loadable module. The
linux-wlan-ng driver for the linux wireless cards has
two kernel loadable modules - prism2_cs and p80211.
I included the encrypt() and decrypt() function of
cryptoapi inside the p80211.o kernel module instead of
using cipher-<cipher_name>.o module for encryption and
decryption. The cipher context (cipher name and cipher
mode) and key (key length and cipher key) is still set
through cryptoapi.o module.
Warm Regards,
-Niranjan
--- James Morris <jmorris@redhat.com> wrote:
> On Wed, 28 Jul 2004, Niranjan wrote:
>
> > Hi,
> > I got the code working by including the encrypt()
> and
> > decrypt() function inside the WLAN driver.
> > Is there any better way to get the CrytoAPI code
> > working from the driver or some other CryptoAPI
> > implementation ?
>
> Where is the driver code?
>
>
> - James
> --
> James Morris
> <jmorris@redhat.com>
>
>
>
>
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail
next prev parent reply other threads:[~2004-07-28 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-24 22:33 kernel bug at sched.c:564! + linux kernel 2.4.25 Niranjan
2004-07-26 21:06 ` Matt Mackall
2004-07-27 18:02 ` Vladimir Kondratiev
2004-07-27 18:39 ` James Morris
2004-07-27 18:50 ` Vladimir Kondratiev
2004-07-27 18:57 ` James Morris
2004-07-28 15:55 ` Niranjan
2004-07-28 16:10 ` James Morris
2004-07-28 16:30 ` Niranjan [this message]
2004-07-27 22:23 ` Niranjan
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=20040728163029.55069.qmail@web53001.mail.yahoo.com \
--to=niranjan_cs2905@yahoo.com \
--cc=jmorris@redhat.com \
--cc=mpm@selenic.com \
--cc=netdev@oss.sgi.com \
--cc=vkondra@mail.ru \
/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;
as well as URLs for NNTP newsgroup(s).