Applied patch #4 and #19 to libata.
Please do not include "Hello," or "Description:" in your patch
description, as I must hand-edit these out manually.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordom
Hi,
Can you please let me know, what all files does the OS look into to
load modules?
I see the following messages during boot rather installation:
==
Finished bus probing
modules to insert tg3 aic79xx
==
which files does the OS look into to load tg3 and aic79xx after
finishing bus probin
On Wed, Feb 23, 2005 at 04:51:38PM -0800, Andrew Morton wrote:
>
>
> Begin forwarded message:
Never use the dpt_i2o driver but rather i2o_block/i2o_scsi
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Begin forwarded message:
Date: Wed, 23 Feb 2005 18:18:46 +0100
From: <[EMAIL PROTECTED]>
To: linux-kernel@vger.kernel.org
Subject: 2.6.11-rc4-mm1 and dpt_i2o Adaptec I2O RAID controller
Hi all,
i'm trying to get an Adaptec 2015S Zero Channel Raid Controller up and running
in a very new Asus
Mike Christie wrote:
Andrew Vasquez wrote:
On Wed, 23 Feb 2005, Mike Christie wrote:
Andrew Vasquez wrote:
Speaking of which, are there any major objections to the patches
proposed here:
Add scsi_target_[un]block() and scsi_target_remove() generics
http://marc.theaimsgroup.com/?l=linux-scsi&m=1108
Andrew Vasquez wrote:
On Wed, 23 Feb 2005, Mike Christie wrote:
Andrew Vasquez wrote:
Speaking of which, are there any major objections to the patches
proposed here:
Add scsi_target_[un]block() and scsi_target_remove() generics
http://marc.theaimsgroup.com/?l=linux-scsi&m=110867050306738&w=2
[RFC]
Hi Jeff,
On Wed, 2005-02-23 at 16:03 -0500, Jeff Garzik wrote:
> Comments from an initial scan of the code. This does not include any
> review of iSCSI interaction itself.
>
>
> 1) the TRACE stuff uses too much stack space
Aside from TRACE_ERROR, the other TRACE_ defs are not compiled in
On Wed, 23 Feb 2005, Mike Christie wrote:
> Andrew Vasquez wrote:
> >
> >Speaking of which, are there any major objections to the patches
> >proposed here:
> >
> >Add scsi_target_[un]block() and scsi_target_remove() generics
> >http://marc.theaimsgroup.com/?l=linux-scsi&m=110867050306738&w=2
> >
>
I notice that Scanmaker II is already in the list, apparently in the wrong
place. Maybe you could fix that in the same patch, so the entries are
conveniently together.
Also: the only reason this caught my eye is that just a few days ago, I
discovered my Scanmaker I has the same problem (respon
Hi all,
i'm trying to get an Adaptec 2015S Zero Channel Raid Controller up and running
in a very new Asus Mainboard (NCL-DS)
with Dual Xeons.
I already tried kernel 2.4.29 and plain 2.6.10 but both just lock up when
loading the dpt_i2o driver.
With 2.6.11-rc4-mm1 i could gather the following outp
Is there a way to set and/or determine what is the maximum number of
blocks that can be sent to a target at one time?
Thanks,
Chad
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/ma
Comments from an initial scan of the code. This does not include any
review of iSCSI interaction itself.
1) the TRACE stuff uses too much stack space
2) style: way too many interal headers; feel free to disagree, though,
this is maintainer's preference.
3) non-standard function definitions:
+
On Sun, Feb 20, 2005 at 09:09:36PM -0500, Jeff Garzik wrote:
> Irrelevant. It matters to automated patch snarfers, lkml.org users, etc.
Jeff,
I just cut the patch using standard cvs diff.
I know SubmittingPatches wants -p0 but I also knew
that willy doesn't mind -p1 and he's the maintainer.
> In
Andrew Vasquez wrote:
On Wed, 23 Feb 2005, Mike Christie wrote:
The attached patch copies the code from the fc transport
class which allows a LLD to block and unblock a device.
The block/unblock code is used by the iscsi-sfnet
driver in replacement of a internal timer doing the
same thing.
I under
The following is the first public release of the PyX Technologies iSCSI
Initiator Core Stack v1.6.1.20 for Linux 2.6.11-rc4. This is a full
featured iSCSI Initiator stack that is capable of mulitplexing coast to
coast across multiple independant backbone providers using various
network transports
To try and escape the madness of adding a zillion USB card readers
to the SCSI whitelist, I flipped the scan all lun's by default switch
in the fedora kernel recently to see just what breaks, in the hope
of moving from a whitelist solution to a blacklist.
Here's the first (hopefully of not too man
Introduce a generic SPI function to print the negotiated transfer
agreement. It's based on the implementation in sym53c8xx_2/sym_misc.c.
>From a quick look, 53c700, ncr53c8xx and sym2 can use it easily.
Other drivers need to be converted to use the SPI transport layer first.
In order to calculat
On Wed, 23 Feb 2005, Mike Christie wrote:
> The attached patch copies the code from the fc transport
> class which allows a LLD to block and unblock a device.
> The block/unblock code is used by the iscsi-sfnet
> driver in replacement of a internal timer doing the
> same thing.
>
> I understand t
Hello!
Thanks for your response!
well, i installed SLES 8 and the system found its PERC 2/dc
as an i2o block device.
it loads all i2o_core, i2o_block, i2o_config, and i2o_pci
and at i2o_pci it says to wait for more devices in the background
but it does get an timeout back.
so i believe the i
hi list,
does anybody can help to guide me through an update
of an megaraid driver?
i have a Dell Perc 2/dc controller in my Dell 2450 Server and
SuSE Server 8.
if i use the standard megaraid driver, then the server crashes
and stands... (no error log entry)
i found many sites for updates but n
Matthew Wilcox write:
> That sounds like the bus is in single-ended mode (which is limited to
> 40MB/s) rather than LVD. Check cabling, terminators, etc.
This is the more likely scenario regarding the limits in performance.
The CHIM in the card's Firmware is different than the PD CHIM in the
Lin
Kernel: 2.6.10-rc4 w/ 3 tape patches from Kai Makisara
SCSI: 53C1030 controller, tape drive is on one channel of the
controller.
Tape: Overland Changer w/ Seagate LTO-1 drive
Typical transfer speed: 12MB/s
After adding a Megaraid Zero Channel Raid Controller to that
computer the transfer speed
James, please apply this to your queue for post 2.6.11.
Thanks.
Jamie.
From: Guennadi Liakhovetski <[EMAIL PROTECTED]>
Removes the page_to_
On Mon, Feb 21, 2005 at 11:01:27PM +0100, Guennadi Liakhovetski wrote:
> On Sun, 6 Feb 2005, Guennadi Liakhovetski wrote:
>
> > Two weeks since I posted this patch - ping...
>
> ...and another two weeks since you, Jamie, replied to me privately. Just
> wanted to say, it would be good to get this
From: Gerd Knorr <[EMAIL PROTECTED]>
This patch adds a device driver for scsi media changer devices (tape
libraries for example).
It exists for quite some time (since 2.2.x or so ...), is used by several
people and also is in some vendor kernels (debian, suse, maybe others as
well). People bug
- workaround for gcc-2.95 macro expansion bug
- fix a warning:
drivers/scsi/ch.c:100: warning: `ch_ioctl_compat' declared `static' but never
defined
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---
25-akpm/drivers/scsi/ch.c |4 +++-
1 files changed, 3 insertions(+), 1 deletion(-)
The attached patch copies the code from the fc transport
class which allows a LLD to block and unblock a device.
The block/unblock code is used by the iscsi-sfnet
driver in replacement of a internal timer doing the
same thing.
I understand that the target code is under construction
and our group as
27 matches
Mail list logo
