This is surely a bug. Can someone please suggest how it should
be fixed?
Thanks.
Begin forwarded message:
Date: Tue, 28 Jun 2005 09:14:28 +
From: "d binderman" <[EMAIL PROTECTED]>
To: linux-kernel@vger.kernel.org
Subject: variable used before set
Hello there,
I just tried to compile th
So, one thing that's terribly ugly about SATA ATAPI is that we need to
pad DMA transfers to the next 32-bit boundary, if the length is not
evenly divisible by 4.
Messing with the scatterlist to accomplish this is terribly ugly
no matter how you slice it. One way would be to create my own
scatter
On Fri, 29 Jul 2005 01:05:48 +0200 Pierre Ossman wrote:
> randy_dunlap wrote:
>
> >
> >oh drat. Please test 2.6.12.2 with the following patch segment
> >backed out (-R, reversed). I don't see any other patches that could
> >be the cause. If this isn't the problem, I would have to begin
> >to s
randy_dunlap wrote:
>
>oh drat. Please test 2.6.12.2 with the following patch segment
>backed out (-R, reversed). I don't see any other patches that could
>be the cause. If this isn't the problem, I would have to begin
>to suspect some kind of toolchain problem.
>
>
>
It seems the blame fall
Firstly many thanks to LSI who responded so promptly to an e-mail which
wasn't even addressed to them :), we really appreciate the support.
I went back to the datacenter yesterday for another try, and managed to
get both boxes booting with SuSe Pro 9.3 (instead of Debian). However,
the amusing
Luben, et. al.
Any updates on the SAS transport class code? Are we likely to see this
happening in the 2.6.14 time frame? After the BOF at OLS, I figured we
would be moving quick on this...
Eric, have you tried to get your code ported to Luben's patch?
Thanks,
-tduffy
signature.asc
Descript
On 07/28/05 16:27, Tom Duffy wrote:
> Luben, et. al.
>
> Any updates on the SAS transport class code? Are we likely to see this
> happening in the 2.6.14 time frame? After the BOF at OLS, I figured we
> would be moving quick on this...
It really depends on when 2.6.14 is coming out.
I'm doing d
Doug Maxey wrote:
On Thu, 21 Jul 2005 21:35:24 EDT, Jeff Garzik wrote:
As soon as I finish SATA ATAPI (this week[end]), I'll take a look at
this. A quick review of the patches didn't turn up anything terribly
objectionable, though :)
I would like to offer to test when you are ready. Som
On Thu, 28 Jul 2005, James Bottomley wrote:
> On Wed, 2005-07-27 at 22:10 -0700, Andrew Vasquez wrote:
> > Would you also apply the attached patch which adds the appropriate
> > FW_LOADER pre-requisite and a separate entry for ISP24xx support.
>
> That's what I see reading the code; however, it l
On Thu, 21 Jul 2005 21:35:24 EDT, Jeff Garzik wrote:
>As soon as I finish SATA ATAPI (this week[end]), I'll take a look at
>this. A quick review of the patches didn't turn up anything terribly
>objectionable, though :)
>
I would like to offer to test when you are ready. Some older and new SAT
On Wed, 2005-07-27 at 22:10 -0700, Andrew Vasquez wrote:
> Would you also apply the attached patch which adds the appropriate
> FW_LOADER pre-requisite and a separate entry for ISP24xx support.
That's what I see reading the code; however, it looks like it's *only*
the 24xx that needs it (qla24xx_l
information and downloads see:
http://www.torque.net/sg/sdparm.html
ChangeLog for sdparm-0.94 [20050728]
- add CD/DVD (MM) capabilities and mechanical status mode page
- add Background medium scan (SBC-2 pending) mode subpage
- add '--command=' option with these s:
ready, start,
> > > A similar problem was noted with RHEL4, it seems the modules.pcimap
> > > and pci.ids file were correct, but the pcitable file contained entries
> > > for all ql[ae]23xx based HBAs to load qla2300.ko.
> > >
> > > It's my understanding that this was fixed for RHEL4 U1. Which distro
> > > are
13 matches
Mail list logo
