From: Saravanan S <sarans1987@gmail.com>
To: "Bounine, Alexandre" <Alexandre.Bounine@idt.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Standalone SRIO Driver for Linux
Date: Sat, 14 Jul 2012 11:54:47 +0530 [thread overview]
Message-ID: <CAEqOc-QzeNz0z33yegaa-9FVpbcCUaMix4-Gfkn0P8Y3487YsA@mail.gmail.com> (raw)
In-Reply-To: <8D983423E7EDF846BB3056827B8CC5D10285E9@corpmail1.na.ads.idt.com>
[-- Attachment #1: Type: text/plain, Size: 1939 bytes --]
Hi ,
Thanks for the reply . i will try to share some of my code later .
Looking forward to ur ideas.
Regards,
S.Saravanan
On Fri, Jul 13, 2012 at 6:18 PM, Bounine, Alexandre <
Alexandre.Bounine@idt.com> wrote:
> This should work. We use similar approach to test our mport HW drivers.**
> **
>
> ** **
>
> Alex.****
>
> ** **
>
> *From:* Linuxppc-dev [mailto:linuxppc-dev-bounces+alexandre.bounine=
> idt.com@lists.ozlabs.org] *On Behalf Of *Saravanan S
> *Sent:* Friday, July 13, 2012 2:16 AM
> *To:* linuxppc-dev@lists.ozlabs.org
> *Subject:* Standalone SRIO Driver for Linux****
>
> ** **
>
> Hi ,
>
> Iam currently working on the GE make DSP230 board consisting of Quad
> PowerPC8640 nodes interconnected by SRIO with Linux 2.6.34 . However the
> only way to access the SRIO is through rionet facility . Our requirement is
> to use the SRIO interconnect without the Ethernet overheads. This would
> definitely enable higher speeds (though I cant find any throughput figures
> for SRIO in Linux on the net ??? ). My query is that whether any attempt
> has been made to develop a standalone driver and API to access the
> messaging and doorbell services of SRIO . If no then request you to please
> provide inputs on the same. From my study I have the following thoughts for
> the driver :
>
> a) Have a character device interface for user .
> b) Basically use the rio support functions provided in rio.c like
> rio_add_inb_buffer , rio_add_outb_message to transfer and receive messages
> and add buffers .
> c) Maintain a dedicated ring of buffers in the driver and transfer data
> to and from the buffer to user space .
>
>
> Is this the right direction . Would really appreciate any inputs . thanks
> in advance.
>
> Regards,
>
> S.Saravanan****
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
[-- Attachment #2: Type: text/html, Size: 3843 bytes --]
next prev parent reply other threads:[~2012-07-14 6:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 6:15 Standalone SRIO Driver for Linux Saravanan S
2012-07-13 12:48 ` Bounine, Alexandre
2012-07-14 6:24 ` Saravanan S [this message]
2012-07-16 14:15 ` Bounine, Alexandre
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=CAEqOc-QzeNz0z33yegaa-9FVpbcCUaMix4-Gfkn0P8Y3487YsA@mail.gmail.com \
--to=sarans1987@gmail.com \
--cc=Alexandre.Bounine@idt.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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).