linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jan Neskudla <jan.neskudla.ext@nsn.com>
To: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: RapidIO - general questions
Date: Tue, 12 May 2009 11:17:52 +0200	[thread overview]
Message-ID: <1242119872.16400.113.camel@demuxf9c> (raw)

Hallo 

we'd likes to use a RapidIO as a general communication bus on our new
product, and so I have some questions about general design of Linux RIO
subsystem. I did not find any better mailing list for RapidIO
discussion. 

[1] - we'd like to implement following features 
    * Hot-plug (hot-insert/hot-remove) of devices
    * Error handling (port-write packets - configuration, handling of
them)
    * Static ID configuration based on port numbers 
    * Aux driver - basic driver, for sending messages over different
mboxes, handling ranges of doorbells	

    Is it here anyone who is working on any improvement, or anyone who
knows the development plans for RapidIO subsystem? 

[2] - I have a following problem with a current implementation of
loading drivers. The driver probe-function call is based on comparison
of VendorID (VID) and DeviceID (DID) only. Thus if I have 3 devices with
same DID and VID connected to the same network (bus), the driver is
loaded 3times, instead only once for the actual device Master port. 

Rionet driver solved this by enabling to call initialization function
just once, and it expect that this is the Master port. 

Is it this correct behavior  ? It looks to me that RapidIO is handled
like a local bus (like PCI) 
 
                                   Jan 

             reply	other threads:[~2009-05-12  9:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12  9:17 Jan Neskudla [this message]
2009-05-13 10:57 ` RapidIO - general questions Li Yang
2009-05-15  7:33   ` Jan Neskudla
2009-05-15  7:56     ` Li Yang
2009-05-20  7:00       ` Jan Neskudla
2009-05-20 23:42         ` Anderson, Trevor
2009-06-29 14:19         ` Jan Neskudla
2009-06-29 15:44           ` david.hagood
2009-07-01 14:46             ` Jan Neskudla

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=1242119872.16400.113.camel@demuxf9c \
    --to=jan.neskudla.ext@nsn.com \
    --cc=linuxppc-dev@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).