Linux cryptographic layer development
 help / color / mirror / Atom feed
* Debugging Talitos
@ 2008-07-21 22:27 Barry G
  2008-07-21 22:50 ` Kim Phillips
  0 siblings, 1 reply; 3+ messages in thread
From: Barry G @ 2008-07-21 22:27 UTC (permalink / raw)
  To: linux-crypto, kim.phillips

Hello,

I am working on getting HW acceleration working via the talitos
driver for the 8347E.

We are running 2.6.25.4 with the realtime patchset and ubifs.
I have a testbed setup of machines like:
A<->B<->C<->D

I am running a talitos aware kernel on B and C.  (I cloned linux-2.6 and
copied talitos.[c|h] and changed Kconfig and Makefile in drivers/crypto.

Unfortunately, I am still seeing only about 20 Mbit/sec from iperf (same
as before I installed the talitos module).  I also don't see any talitos
stuff in the drivers:
# cat /proc/crypto | grep -i talitos
#

I do have a /sys/bus/of_platform/drivers/talitos folder with uevent,unbind,bind
though.

dmesg | grep -i talitos also returns nothing.

What is the best way to go about debugging the crypto stuff?  Should I jump
in and start printk'ing everything or ?  Do I need other changes from
the tree than the taliltos driver?

BTW, here is the relevent entry in the DTS:
crypto@30000 {
   device_type = "crypto";
   model = "SEC2";
   compatible = "talitos";
   reg = <30000 10000>;
   interrupts = <b 8>;
   interrupt-parent = < &ipic >;
   num-channels = <4>;
   channel-fifo-len = <18>;
   exec-units-mask = <0000007e>;
   descriptor-types-mask = <01010ebf>;
};

Thanks,

Barry

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2008-07-22 21:37 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-07-21 22:27 Debugging Talitos Barry G
2008-07-21 22:50 ` Kim Phillips
     [not found]   ` <61362e760807220836m59207c33y1c6b673fdd2d03@mail.gmail.com>
     [not found]     ` <61362e760807220941t4eebd229g45838c1c8209c1c5@mail.gmail.com>
2008-07-22 21:37       ` Barry G

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox