This patch removes the following obsolete functions:
- libata-core.c: __sata_phy_reset()
- libata-core.c: sata_phy_reset()
- libata-eh.c: ata_qc_timeout()
- libata-eh.c: ata_eng_timeout()
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
---
drivers/ata/libata-core.c | 78
I'm about to disappear (virtually) through Friday for vacation.
Tejun Heo has agreed to collect libata bug fix patches in my absence.
Thanks!
Jeff
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On 10.11.2007 00:32, Matthias Schniedermeyer wrote:
[...]
My computer/mainboard @work has such a broken BIOS. Of the 5
SATA-Ports this MB has only 1 (and 1 missing that is reported by
linux but i can't find on the MB) is configured as AHCI [...]
There is nothing broken here. You have a ICH8
On Sat, 2007-11-10 at 18:06 -0500, Jeff Garzik wrote:
Alan Cox wrote:
On Sat, 10 Nov 2007 17:11:39 -0500
Jeff Garzik [EMAIL PROTECTED] wrote:
Jeff Garzik wrote:
Whenever you want to update or add a page, just send a 'git pull'
request to me...
Or patches, if you wish to avoid
Hello,
I am using kernel 2.6.23 with the driver drivers/ata/ata_piix.c on my macbook
pro.
About every fourth boot hangs. I tried to narrow down the problem by putting in
dome printk
statements and found (at least on 2 hangs so far) that the msleep(150) in
piix_init_pcs
does not return:
On 11.11.2007 15:05, Thorsten Leemhuis wrote:
On 10.11.2007 00:32, Matthias Schniedermeyer wrote:
[...]
My computer/mainboard @work has such a broken BIOS. Of the 5
SATA-Ports this MB has only 1 (and 1 missing that is reported by
linux but i can't find on the MB) is configured as AHCI
On Friday 26 October 2007, Alan Cox wrote:
On Fri, 26 Oct 2007 21:30:02 +0400
Andrey Borzenkov [EMAIL PROTECTED] wrote:
Running legacy IDE drivers apparently works in DMA mode for both:
Thanks - can you send me an lspci -vvxxx off list
BTW in rc2 it does not even boot - it babbles
BTW in rc2 it does not even boot - it babbles something about
Unable to determine IRQ for 00:04.0 (which is IDE controller) and that is
the end of story. No IDE device is found.
Thats not an IDE breakage I suspect. Various people are reporting IRQ
related breakage with -rc2 so you should
On Friday 09 November 2007, Sergei Shtylyov wrote:
Make sure to not clear the other IDE channel's interrupt when clearing an IDE
interrupt via the MRDMODE register.
Thanks to Bart for finding a coding mistake.
Could you resend with Signed-off-by: and Tested-by: tags?
[ A reference to the
Jeff Garzik wrote:
I wouldn't push it out unless it looked OK in my browser.
But overall I tend to dislike wikis. They enable collaboration, but
tend to be uniformly ugly, cumbersome, and CPU intensive.
Besides collaboration, one thing I like about wikis is that updating the
page is an
Tejun Heo wrote:
Jeff Garzik wrote:
I wouldn't push it out unless it looked OK in my browser.
But overall I tend to dislike wikis. They enable collaboration, but
tend to be uniformly ugly, cumbersome, and CPU intensive.
Besides collaboration, one thing I like about wikis is that updating
Jeff Garzik wrote:
So, my preference is a wiki. I don't care which wiki it is as long as I
can edit and view it directly.
So noted, it sounds like a wiki it greatly preferred by all involved.
I'll look around for one I like.
Expect no action until Nov 16 at the earliest, of course...
Greg Hennessy wrote:
I have a LYCeSATA-4x pci card that is port multiplier compatible (it
works fine
under win xp) that is only showing one of 5 attached drives when
attached to
a Redhat 5 computer, with both 2.6.18-8.1.15.el5 and 2.6.23.1.
The SATA link shows as up for the one recognized
Matheus Izvekov wrote:
Indeed removing the jumper of sdb made it be recognised as SATA2. But
sdc, what the problem is really about, is neither SATA2, not has any
jumper whatsoever. but both the manufacturer and libata claim it
supports NCQ.
Anything i could do to help debug this? or
Hello,
Cable detection has always been broken for pata_amd. Recent changes
seem to have broken some other subset tho. The following patchset to
get it fixed once and for all is pending.
http://thread.gmane.org/gmane.linux.ide/24524
Thanks.
--
tejun
-
To unsubscribe from this list: send the
Robert Hancock wrote:
Norbert Preining wrote:
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x40 action 0x2
Serror 0x40 means a handshake error. Usually Serror indications are
due to a hardware problem (bad SATA cable, power or drive problem).
ata1.00: (BMDMA stat 0x25)
ata1.00: cmd
Hello,
I Stratford wrote:
The purpose of the mail is to document and share my experience in the
hope that someone might find it useful, either for debugging their own
TX4 300-centric system issues or figuring out what is up with
sata_promise and the TX4 300 in 3Gbps mode. I also wish to offer
17 matches
Mail list logo
