linux-kernel - Re: [PATCH] Remove libsas PCI dependencies

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <46A8A1E1.3040707@garzik.org>
Date:	Thu, 26 Jul 2007 09:30:09 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	James Bottomley <James.Bottomley@...elEye.com>
CC:	Meelis Roos <mroos@...ux.ee>,
	linux-scsi <linux-scsi@...r.kernel.org>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	"Darrick J. Wong" <djwong@...ibm.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] Remove libsas PCI dependencies

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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/