public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Meelis Roos <mroos@linux.ee>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	"Darrick J. Wong" <djwong@us.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Remove libsas PCI dependencies
Date: Thu, 26 Jul 2007 09:30:09 -0400	[thread overview]
Message-ID: <46A8A1E1.3040707@garzik.org> (raw)
In-Reply-To: <1185454007.3501.34.camel@localhost.localdomain>

James Bottomley wrote:
> Realistically, even for parisc, I can't see anyone producing a non-PCI
> SAS device (even though I'd like one).

A non-PCI device embedded on an SoC or system bus is highly -likely-, IMO.

SAS+SATA silicon (w/out firmware assist as with aic94xx) is the 
direction that Marvell and Broadcom have gone.  I would say it's 
practically inevitable that someone will embed a SAS+SATA chip eventually.


> This should become enum dma_data_direction if we're going to go the
> generic route.

Updated.

	Jeff



      parent reply	other threads:[~2007-07-26 13:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26  8:31 libsas: pci_iommu_ops undefined on !PCI Meelis Roos
2007-07-26  9:21 ` [PATCH] Remove libsas PCI dependencies Jeff Garzik
2007-07-26 12:46   ` James Bottomley
2007-07-26 13:06     ` Matthew Wilcox
2007-07-26 13:28     ` [PATCH v2] " Jeff Garzik
2007-07-26 17:31       ` Meelis Roos
2007-07-26 17:46         ` Jeff Garzik
2007-07-26 17:51           ` Meelis Roos
2007-07-26 18:05           ` James Bottomley
2007-07-26 13:30     ` Jeff Garzik [this message]

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=46A8A1E1.3040707@garzik.org \
    --to=jeff@garzik.org \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@linux-foundation.org \
    --cc=djwong@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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