Hi Jeff,
what is the status of this patch?
I'd like to have this patch, and a second part that adds support for
the SoC devices, to be merged into 2.6.25. please note that my patch
collides with Mark's patches, I don't mind to rebase mine above Mark's
patches, but, in that case I need to wait
not one problem but lots---is sufficiently widespread that a Mini HOWTO,
say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil down to
- error messages looking different - Most bugs I get are
On Tuesday 29 January 2008, Alan Cox wrote:
not one problem but lots---is sufficiently widespread that a Mini HOWTO,
say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil down to
- error messages
As slight change here, I was going to use the same .config as 2.6.24-rc8, but
just discovered that neither rc8 nor final is finding the drivers for my
If it is not finding a driver that is nothing to do with libata. It means
it's not being loaded by the distribution, or the distribution kernel
Is this 4GB or =4GB? I've seen contradictory reports, and I've got 4GB.
Depends how the memory is mapped. Any memory physically above the 4GB
boundary
Alan
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info
saeed bishara wrote:
On 1/16/08, Mark Lord [EMAIL PROTECTED] wrote:
saeed bishara wrote:
I attached the new patch
..
Try again, please.
This time, post the patch *inline* in the body of the email,
so that it can more easily be seen, read, and commented on.
Beware of many email clients that
Mark Lord wrote:
Create host-owned DMA memory pools, for use in allocating/freeing per-port
command/response queues and SG tables. This gives us a way to guarantee we
meet the hardware address alignment requirements, and also reduces
memory that
might otherwise be wasted on alignment gaps.
Alan Cox wrote:
not one problem but lots---is sufficiently widespread that a Mini HOWTO,
say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil down to
- sata_nv with 4GB of RAM, knowing
Gene Heskett writes:
On Tuesday 29 January 2008, Alan Cox wrote:
As slight change here, I was going to use the same .config as 2.6.24-rc8,
but just discovered that neither rc8 nor final is finding the drivers for
my
If it is not finding a driver that is nothing to do with libata.
On Tuesday 29 January 2008, Mark Lord wrote:
Gene Heskett wrote:
..
Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number
when dmesg says its found ok at ata2.00? I've turned on an option that
says something about using the bios for device access this build, but I'll
be
Gene Heskett wrote:
..
Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number
when dmesg says its found ok at ata2.00? I've turned on an option that says
something about using the bios for device access this build, but I'll be
surprised if that's it. :)
..
It should
saeed bishara wrote:
Hi Jeff,
what is the status of this patch?
I'd like to have this patch, and a second part that adds support for
the SoC devices, to be merged into 2.6.25. please note that my patch
collides with Mark's patches, I don't mind to rebase mine above Mark's
patches, but, in that
On Jan 28, 2008 3:43 PM, Mark Lord [EMAIL PROTECTED] wrote:
Gene Heskett wrote:
On Monday 28 January 2008, Mark Lord wrote:
..
Another way is to use the make_bad_sector utility that
is included in the source tarball for hdparm-7.7, as follows:
make_bad_sector --readback /dev/sda
saeed bishara wrote:
Hi Jeff,
what is the status of this patch?
I'd like to have this patch, and a second part that adds support for
the SoC devices, to be merged into 2.6.25. please note that my patch
collides with Mark's patches, I don't mind to rebase mine above Mark's
patches, but, in that
On Tuesday 29 January 2008, Alan Cox wrote:
not one problem but lots---is sufficiently widespread that a Mini HOWTO,
say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil down to
- error messages
On Tuesday 29 January 2008, Jeff Garzik wrote:
Gene Heskett wrote:
Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number
when dmesg says its found ok at ata2.00? I've turned on an option that
says something about using the bios for device access this build, but I'll
be
Jason Gaston wrote:
This patch adds the Intel ICH10 SATA RAID Controllers DeviceID's.
Signed-off-by: Jason Gaston [EMAIL PROTECTED]
--- linux-2.6.24/drivers/ata/ahci.c.orig2008-01-24 14:58:37.0
-0800
+++ linux-2.6.24/drivers/ata/ahci.c 2008-01-28 14:58:22.0 -0800
On Tuesday 29 January 2008, Mikael Pettersson wrote:
Gene Heskett writes:
On Tuesday 29 January 2008, Alan Cox wrote:
As slight change here, I was going to use the same .config as
2.6.24-rc8, but just discovered that neither rc8 nor final is finding
the drivers for my
If it is not
Mark Lord wrote:
Gene Heskett wrote:
..
Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx'
number when dmesg says its found ok at ata2.00? I've turned on an
option that says something about using the bios for device access
this build, but I'll be surprised if that's it. :)
On Tuesday 29 January 2008, Florian Attenberger wrote:
On Mon, 28 Jan 2008 14:13:21 -0500
Gene Heskett [EMAIL PROTECTED] wrote:
I had to reboot early this morning due to a freezeup, and I had a
bunch of these in the messages log:
==
Jan 27 19:42:11 coyote kernel:
On Tuesday 29 January 2008, Daniel Barkalow wrote:
On Tue, 29 Jan 2008, Gene Heskett wrote:
For starters, enable CONFIG_BLK_DEV_SR.
That could stand to be moved or renamed, it is well buried in the menu for
the REAL scsi stuffs, which I don't have any of. Enabled building now.
The SCSI
-Original Message-
From: Jeff Garzik [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 29, 2008 9:14 AM
To: Gaston, Jason D
Cc: linux-ide@vger.kernel.org; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: [PATCH 2.6.24] ata_piix: IDE mode SATA patch for Intel
ICH10
DeviceID's
Jason Gaston
things in the kernel that refer to SCSI probably should say storage (or
ATA, really, but that would make the acronyms confusing).
SCSI is a command protocol. It is what your CD-ROM drive and USB storage
devices talk (albeit with a bit of an accent).
Alan
-
To unsubscribe from this list: send
Don't know. Is there an easy way to find out?
E820 map on boot shows you I think.
By the way, and on a totally different subject. I wonder if this:
MODULE_DESCRIPTION(low-level driver for AMD PATA IDE);
mightn't be changed to something like:
MODULE_DESCRIPTION(low-level driver for AMD and
On Tue, 29 Jan 2008, Gene Heskett wrote:
For starters, enable CONFIG_BLK_DEV_SR.
That could stand to be moved or renamed, it is well buried in the menu for
the
REAL scsi stuffs, which I don't have any of. Enabled building now.
The SCSI support type (disk, tape, CD-ROM) section of
Alan Cox wrote:
Is this 4GB or =4GB? I've seen contradictory reports, and I've got 4GB.
Depends how the memory is mapped. Any memory physically above the 4GB
boundary
Don't know. Is there an easy way to find out?
By the way, and on a totally different subject. I wonder if
On Tue, 2008-01-29 at 05:28 +0100, Andi Kleen wrote:
The ideal solution would be to do mapping against a different struct
device for each port, so that we could maintain the proper DMA mask for
each of them at all times. However I'm not sure if that's possible.
I cannot imagine why it
Mark Lord wrote:
saeed bishara wrote:
Hi Jeff,
what is the status of this patch?
I'd like to have this patch, and a second part that adds support for
the SoC devices, to be merged into 2.6.25. please note that my patch
collides with Mark's patches, I don't mind to rebase mine above Mark's
Greg Freemyer wrote:
On Jan 28, 2008 3:43 PM, Mark Lord [EMAIL PROTECTED] wrote:
Gene Heskett wrote:
On Monday 28 January 2008, Mark Lord wrote:
..
Another way is to use the make_bad_sector utility that
is included in the source tarball for hdparm-7.7, as follows:
make_bad_sector
Jason Gaston wrote:
This patch adds the Intel ICH10 IDE mode SATA Controller DeviceID's.
Signed-off-by: Jason Gaston [EMAIL PROTECTED]
--- linux-2.6.24/drivers/ata/ata_piix.c.orig2008-01-24 14:58:37.0
-0800
+++ linux-2.6.24/drivers/ata/ata_piix.c 2008-01-28 14:58:22.0
ACK the changes; but both git-am(1) and patch(1) report that this is a
corrupt patch. patch(1) says,
[EMAIL PROTECTED] libata-dev]$ patch -sp1 /g/tmp/mbox
patch: malformed patch at line 151: *hpriv, int idx,
(patch is generally more forgiving than git-am)
ok, I'll send the patch
Gene Heskett wrote:
Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number
when dmesg says its found ok at ata2.00? I've turned on an option that says
something about using the bios for device access this build, but I'll be
surprised if that's it. :)
I think you mean
On Tue, 29 Jan 2008, Alan Cox wrote:
things in the kernel that refer to SCSI probably should say storage (or
ATA, really, but that would make the acronyms confusing).
SCSI is a command protocol. It is what your CD-ROM drive and USB storage
devices talk (albeit with a bit of an accent).
rgheck wrote:
Alan Cox wrote:
not one problem but lots---is sufficiently widespread that a Mini
HOWTO, say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil down to
- sata_nv with 4GB of
Gene Heskett wrote:
On Tuesday 29 January 2008, Mark Lord wrote:
Gene Heskett wrote:
..
Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number
when dmesg says its found ok at ata2.00? I've turned on an option that
says something about using the bios for device access this
On Tue, 29 Jan 2008, Alan Cox wrote:
not one problem but lots---is sufficiently widespread that a Mini HOWTO,
say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil down to
- error
The SCSI error reporting really ought to include a simple interpretation
of the error for end users (The drive doesn't support this command A
sector's data got lost The drive timed out The drive failed The
drive is entirely gone). There's too much similarity between the message
you get
On Tuesday 29 January 2008, Jeff Garzik wrote:
Gene Heskett wrote:
On Tuesday 29 January 2008, Jeff Garzik wrote:
Gene Heskett wrote:
Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx'
number when dmesg says its found ok at ata2.00? I've turned on an
option that says
Needless parens all over the code like this...
Also, you could have made it either 2 (getting rid of |= operator) or 4
lines (read/write, =, and |=).
mode |= dev 4;
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL
Hi Jeff,
I've the two patches ready and rebased on the version that you have
in the master branch, specifically on the commit libata: convert to
chained sg.
Do you prefer to get those rebased patches?
Saeed
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a
Well, it looks as if my problems weren't solved after all. I took out a
Plextor PX-W4012TA and re-installed me cherished Plextor PX-W1610A---the
latter burns at 1X, which produces glorious sounding CDs. Anyway, with
this change, my problems have re-appeared. See the dmesg excerpt below.
The
On Tue, 29 Jan 2008 12:56:37 -0800 (PST)
[EMAIL PROTECTED] wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=9845
Summary: libata still broken for Pegasos on 2.6.24
Product: Platform Specific/Hardware
Version: 2.5
KernelVersion: 2.6.24
Hello.
Bartlomiej Zolnierkiewicz wrote:
Always set DMA masks in ide_pci_setup_ports() to make sure that the valid
masks for a host are set.
Signed-off-by: Bartlomiej Zolnierkiewicz [EMAIL PROTECTED]
Acked-by: Sergei Shtylyov [EMAIL PROTECTED]
MBR, Sergei
-
To unsubscribe from this list:
That could stand to be moved or renamed, it is well buried in the menu for
the
REAL scsi stuffs, which I don't have any of.
Yes you do - USB storage and ATAPI are SCSI
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More
Jeff Garzik wrote:
Mark Lord wrote:
Create host-owned DMA memory pools, for use in allocating/freeing
per-port
command/response queues and SG tables. This gives us a way to
guarantee we
meet the hardware address alignment requirements, and also reduces
memory that
might otherwise be wasted
rgheck wrote:
Mark Lord wrote:
rgheck wrote:
Alan Cox wrote:
not one problem but lots---is sufficiently widespread that a Mini
HOWTO, say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil
Mark Lord wrote:
rgheck wrote:
Alan Cox wrote:
not one problem but lots---is sufficiently widespread that a Mini
HOWTO, say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil down to
-
Hello.
Anton Salnikov wrote:
This is Palmchip BK3710 IDE controller support for kernel version 2.6.24.
The IDE controller logic supports PIO, multiword DMA and ultra-DMA modes.
Supports interface to compact Flash (CF) configured in True-IDE mode.
Signed-off-by: Anton Salnikov [EMAIL
On Tue, 29 Jan 2008, Alan Cox wrote:
The SCSI error reporting really ought to include a simple interpretation
of the error for end users (The drive doesn't support this command A
sector's data got lost The drive timed out The drive failed The
drive is entirely gone). There's too much
I've seen a lot of verbosity out of SCSI messages, but I haven't seen a
straightforward interpretation of the problem in there. It's all
information useful for debugging, not information useful for system
administration.
It tells you what is going on. Unfortunately that frequently requires
--- On Mon, 1/28/08, Andi Kleen [EMAIL PROTECTED] wrote:
The ideal solution would be to do mapping against a
different struct
device for each port, so that we could maintain the
proper DMA mask for
each of them at all times. However I'm not sure if
that's possible.
I cannot imagine why
--- On Mon, 1/28/08, Robert Hancock [EMAIL PROTECTED] wrote:
The trick is that if an ATAPI device is connected, we (as
far as I'm
aware) can't use ADMA mode, so we have to switch that
port into legacy
mode.
Can you double check this with the HW architect of the
HW DMA engine of the ASIC?
On Tuesday 29 January 2008, Alan Cox wrote:
That could stand to be moved or renamed, it is well buried in the menu for
the REAL scsi stuffs, which I don't have any of.
Yes you do - USB storage and ATAPI are SCSI
By the linux software definition maybe. But I've defined scsi as that which
uses
By the linux software definition maybe. But I've defined scsi as that which
uses a 50 wire cable using 50 contact centronics connectors since the
mid '70's, and which often needs a ready supply of nubile virgins t
25, 50 or 68, with multiple voltage levels, plus of course it might be
over
On Monday 28 January 2008, Borislav Petkov wrote:
Hi Bart,
[...]
the BKL in idetape_write_release() with finer-grained locking etc,
probably also
some pipeline improvements, removal of OnStream support, etc. but that'll
come
later.
On-Stream support has been long gone
Gene,
If you still want to try it, I did manage to get the old IDE subsystem
working. The issue with pata_amd concerns modprobe.conf. You probably
have an alias to it there, as Fedora seems to insert these. (I don't
know if they're actually needed or not.) If you comment out that line,
then
Gene Heskett wrote:
I doubt libata has that capability now, or ever will, cuz these ide/atapi
devices are generally dumber than rocks about that. But any device claiming
to be scsi-II is supposed to be able to do those sorts of things while the
cpu is off crunching numbers for BOINC or
This patch is based on an original patch from Kuan Luo of NVIDIA,
posted under subject fixed a bug of adma in rhel4u5 with HDS7250SASUN500G.
His description follows. I've reworked it a bit to avoid some unnecessary
repeated checks but it should be functionally identical.
The patch is to solve the
Luben Tuikov wrote:
--- On Mon, 1/28/08, Robert Hancock [EMAIL PROTECTED] wrote:
The trick is that if an ATAPI device is connected, we (as
far as I'm
aware) can't use ADMA mode, so we have to switch that
port into legacy
mode.
Can you double check this with the HW architect of the
HW DMA
Robert Hancock wrote:
This patch is based on an original patch from Kuan Luo of NVIDIA,
posted under subject fixed a bug of adma in rhel4u5 with HDS7250SASUN500G.
His description follows. I've reworked it a bit to avoid some unnecessary
repeated checks but it should be functionally identical.
Tejun Heo wrote:
Robert Hancock wrote:
This patch is based on an original patch from Kuan Luo of NVIDIA,
posted under subject fixed a bug of adma in rhel4u5 with HDS7250SASUN500G.
His description follows. I've reworked it a bit to avoid some unnecessary
repeated checks but it should be
61 matches
Mail list logo
