mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Patrick Allaire" <patrick.allaire@isaacnewtontech.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: DPT I2O RAID and Linux I2O
Date: Wed, 2 May 2001 17:11:35 -0400	[thread overview]
Message-ID: <HEEIIHGBKLFOBPOOOJHCIECBCHAA.patrick.allaire@isaacnewtontech.com> (raw)
In-Reply-To: <E14uh2D-0002LG-00@the-village.bc.nu>


If I understand correctly, some vendor would put I2O messaging hardware but
they would use it in a non-standard way ? So, if they dont support the I2O
protocol with their hardware, I will have to do it in another  way...

Is there a simple way to find out if my device support I2O protocol ? Maybe
its written in the BAR or in the CSR, but does linux find those devices
automaticly ? or do I have to do it in my module ? If I must do it myself,
do you know any device that is doing something like I do ? so I could look
at the code.

Thank again.



> > Is this I2O implementation supporting PCI devices ?
>
> Yes
>
> > Yesterday I post something about that, I have a CompactPCI
> computer with 2
> > computers in it. One master and one slave. The slave one, is has a non
> > transparent pci-to-pci bridge : DEC (INTEL) 21554, wich support I2O
> > messaging, I want both computer to communicate by this mean,
> but I cant seam
>
> I2O messaging and I2O protocol are two things. Most sane vendors use I2O
> messaging hardware to implement something that looks a little
> more like a device
> control protocol than SNA.
>
> Alan
>
>
>
>


  reply	other threads:[~2001-05-02 21:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-01  1:22 Alan Cox
2001-05-01  7:29 ` Denis Perchine
2001-05-01 18:34 ` Patrick Allaire
2001-05-01 20:46   ` Alan Cox
2001-05-02 21:11     ` Patrick Allaire [this message]
2001-05-02 21:19       ` Alan Cox
2001-05-02 21:18         ` Patrick Allaire
2001-05-02 21:32           ` Alan Cox
2001-05-04 19:19             ` Patrick Allaire
2001-05-04 21:45               ` Alan Cox

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=HEEIIHGBKLFOBPOOOJHCIECBCHAA.patrick.allaire@isaacnewtontech.com \
    --to=patrick.allaire@isaacnewtontech.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®