libata uses it under the assumption that other parts of the system are
aware of this variable.
May I assume that the API has changed such that this is no longer necessary?
Yes. The original motivation for dev-power.power_state was to let
the writes to /sys/devices/.../power/state support a
The HITACHI HDS7250SASUN500G and HITACHI HDS7225SBSUN250 drives
do not need to be blacklisted, the NCQ problem has been resolved
with the sata_nv: fix for completion handling patch.
Signed-off-by David Milburn [EMAIL PROTECTED]
---
libata-core.c |2 --
1 files changed, 2 deletions(-)
diff
would know better
than I whether it's the right thing to do. The patch got newline wrapped
and whitespace damaged, however. Can you repost (even as attachment) so
people can try it out?
Robert,
Here is Kuan's patch as an attachment.
David
for 2.6.9-55
diff -Nupr a/drivers/ata/sata_nv.c b
Blacklist HITACHI HDS7225SCSUN250G* and SEAGATE STN7225SASUN250G*
drives from using NCQ.
Signed-off-by David Milburn [EMAIL PROTECTED]
---
libata-core.c |2 ++
1 files changed, 2 insertions(+)
diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
index 597e07c..c117afa 100644
there is an issue with
a configuration.
Dave
--
-Open up your eyes, open up your mind, open up your code ---
/ Dr. David Alan Gilbert| Running GNU/Linux on Alpha,68K| Happy \
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC HPPA | In Hex
From: Russell King [EMAIL PROTECTED]
Date: Wed, 14 Nov 2007 09:55:07 +
On Tue, Nov 13, 2007 at 05:55:51PM -0800, David Miller wrote:
I've created [EMAIL PROTECTED]
By doing so you've just said (implicitly) that you can not tolerate
someone having a different opinion from your own.
I
From: Rene Herman [EMAIL PROTECTED]
Date: Wed, 14 Nov 2007 12:46:24 +0100
[EMAIL PROTECTED] is not subscriber-only. Same as that arm list,
it's _moderated_ for non-subscribers and given that I and other moderators
have been doing our best to moderate quickly (I tend to stay logged in to
From: David Miller [EMAIL PROTECTED]
Date: Wed, 14 Nov 2007 03:56:57 -0800 (PST)
The fact that it farts at me every time I post to this thread.
See? I got another one and I have received at least 10 of the
following over the past 2 days.
That's rediculious.
And because a human adds
From: Ingo Molnar [EMAIL PROTECTED]
Date: Wed, 14 Nov 2007 15:08:47 +0100
In fact this thread is the very example: David points out that on netdev
some of those bugs were already discussed and resolved. Had it been all
on lkml we'd all be aware of it.
That's a rediculious argument.
One
on the other lists)
David Lang
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Andrew Morton [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 03:49:16 -0800
Do you believe that our response to bug reports is adequate?
Do you feel that making us feel and look like shit helps?
I guess I'm just masterbating here all night long with the 46
bug fixes I've reviewed fully and
From: Andrew Morton [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 04:12:59 -0800
On Tue, 13 Nov 2007 03:58:24 -0800 (PST) David Miller [EMAIL PROTECTED]
wrote:
From: Andrew Morton [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 03:49:16 -0800
Do you believe that our response to bug reports
From: Mark Lord [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 13:18:43 -0500
Mind you, no arguing that this is effective when that poor bloke has
a day free to download the git-tree and build/reboot a dozen times.
Like the internet, this time spent is beneficial because it's
pushing the work out to
From: Russell King [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 23:40:33 +
ARM ep93xx defconfig has been broken since 2.6.23-git1 due to:
drivers/net/arm/ep93xx_eth.c:420: error: implicit declaration of function
'__netif_rx_schedule_prep'
caused by: [NET]: Make NAPI polling independent
From: Sam Ravnborg [EMAIL PROTECTED]
Date: Wed, 14 Nov 2007 06:56:06 +0100
If so, MANITAINERS claims that it is subscribers-only. That would cause
some bug reporters to give up and go away.
Find some other mailing list; I'm not hosting *nor* am I willing to run a
non-subscribers
I would like those to be removed, but to be conservative we should
first get some testing feedback that confirms this just like those
provided to me from the AMD folks for the RS690, RX790 and RD580
cases.
The patch works fine for my laptop with the RS480 chipset (with a
SB400 southbridge).
From: David Gaarenstroom [EMAIL PROTECTED]
Date: Sun, 28 Oct 2007 21:11:13 +0100
I would like those to be removed, but to be conservative we should
first get some testing feedback that confirms this just like those
provided to me from the AMD folks for the RS690, RX790 and RD580
cases
2007/10/25, David Miller [EMAIL PROTECTED]:
Now that we have dealt with the real issue, in that some ATI SATA and
USB controllers needed the INTX_DISABLE quirk, we can remove these AMD
chipset global MSI disabling quirks.
IMHO we should remove *all* former ATI AMD chipset global MSI
disabling
From: Shane Huang [EMAIL PROTECTED]
Date: Wed, 24 Oct 2007 14:43:21 +0800
This patch and the third one seems can make my SB700 SATA controller
work under MSI(simply tested on 2.6.23-rc5).
So you may withdraw the RS690/RD580/RX790 MSI disablement patches
necessary.
Signed-off-by: David S. Miller [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
This reverts commit e3008dedff4bdc96a5f67224cd3d8d12237082a0.
The real bug was an INTX issue in the tg3 ethernet chip, and
cured by commit c129d962a66c76964954a98b38586ada82cf9381
Signed-off-by: David S. Miller [EMAIL PROTECTED]
---
drivers/pci/quirks.c|1 -
include/linux/pci_ids.h
and disable MSI in all buses behind it.
Signed-off-by: Michael Chan [EMAIL PROTECTED]
Cc: Anantha Subramanyam [EMAIL PROTECTED]
Cc: Naren Sankar [EMAIL PROTECTED]
Signed-off-by: David S. Miller [EMAIL PROTECTED]
---
drivers/pci/quirks.c|3 +++
include/linux/pci_ids.h |1 +
2 files
Tigon3 chips,
and thus we can remove the workaround code from the tg3.c driver.
Signed-off-by: David S. Miller [EMAIL PROTECTED]
Acked-by: Michael Chan [EMAIL PROTECTED]
---
drivers/net/tg3.c|9 -
drivers/pci/msi.c| 18 --
drivers/pci/quirks.c | 24
Signed-off-by: David S. Miller [EMAIL PROTECTED]
---
drivers/pci/quirks.c | 20
1 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
index 9e8c7af..d8f2d89 100644
--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
)
aea6a433f50cd89b9cbd10850fd0b32f961f9883 (PCI: disable MSI on RD580)
f122392f679ebed39db08074f935d770504623eb (PCI: disable MSI on RX790)
This is based upon testing and feedback from
Shane Huang [EMAIL PROTECTED].
Signed-off-by: David S. Miller [EMAIL PROTECTED]
---
drivers/pci/quirks.c|3 ---
include
a faulty disk
from an array, it could also activate a LED (usually a different LED than
the disk activity LED) on the corresponding enclosure so that the admin
knows when standing in front of the storage server which disk to pull out
and replace.
--
David Härdeman
-
To unsubscribe from this list
From: Jeff Garzik [EMAIL PROTECTED]
Date: Tue, 23 Oct 2007 06:01:17 -0400
David Miller wrote:
My suggestion is:
...
Sounds good to me also.
Ok, it seems I've sort-of self-nominated myself to implement
this so I'll try to work on it tomorrow :-)
-
To unsubscribe from this list: send the line
From: David Miller [EMAIL PROTECTED]
Date: Tue, 23 Oct 2007 03:06:22 -0700 (PDT)
Ok, it seems I've sort-of self-nominated myself to implement
this so I'll try to work on it tomorrow :-)
I have a working implementation, fully tested on a machine
with Tigon3 ethernet chips that have the quirk
.
Signed-off-by: David S. Miller [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
This reverts commit e3008dedff4bdc96a5f67224cd3d8d12237082a0.
The real bug was an INTX issue in the tg3 ethernet chip, and
cured by commit c129d962a66c76964954a98b38586ada82cf9381
Signed-off-by: David S. Miller [EMAIL PROTECTED]
---
drivers/pci/quirks.c|1 -
include/linux/pci_ids.h
and disable MSI in all buses behind it.
Signed-off-by: Michael Chan [EMAIL PROTECTED]
Cc: Anantha Subramanyam [EMAIL PROTECTED]
Cc: Naren Sankar [EMAIL PROTECTED]
Signed-off-by: David S. Miller [EMAIL PROTECTED]
---
drivers/pci/quirks.c|3 +++
include/linux/pci_ids.h |1 +
2 files
Tigon3 chips,
and thus we can remove the workaround code from the tg3.c driver.
Signed-off-by: David S. Miller [EMAIL PROTECTED]
---
drivers/net/tg3.c|9 -
drivers/pci/msi.c| 18 --
drivers/pci/quirks.c | 18 ++
include/linux/pci.h |9
Signed-off-by: David S. Miller [EMAIL PROTECTED]
---
drivers/pci/quirks.c | 20
1 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
index 591eaa4..5795a3d 100644
--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
From: Daniel Barkalow [EMAIL PROTECTED]
Date: Wed, 24 Oct 2007 00:58:45 -0400 (EDT)
I'm not sure all of the pci_intx() calls in msi.c should be skipped when
the quirk applies; I think some of them might be there so that the legacy
interrupt won't be delivered while MSI is turned off (since
From: Michael Chan [EMAIL PROTECTED]
Date: Tue, 23 Oct 2007 21:59:39 -0700
David Miller wrote:
+DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_BROADCOM,
+ PCI_DEVICE_ID_TIGON3_5780,
+ quirk_msi_intx_disable_bug);
+DECLARE_PCI_FIXUP_FINAL
From: Michael Ellerman [EMAIL PROTECTED]
Date: Wed, 24 Oct 2007 15:30:21 +1000
That looks like 6 hunks doing exactly the same thing? What about
creating a pci_intx_quirked() (or something) that checks the flag and
then does/or does not call pci_intx().
Good idea, I'll add that to the patch.
-
From: Krzysztof Halasa [EMAIL PROTECTED]
Date: Tue, 23 Oct 2007 01:40:18 +0200
Jeff Garzik [EMAIL PROTECTED] writes:
In general it is documented that INTX_DISABLE should apply only to
INTx# so devices that disable MSI based on that bit are out of spec.
The wording is:
10: This bit
From: Daniel Barkalow [EMAIL PROTECTED]
Date: Mon, 22 Oct 2007 17:31:04 -0400 (EDT)
It's likewise documented (although maybe arguable in wording) that the
device shouldn't send legacy interrupts if MSI is in use, regardless of
INTX_DISABLE, but this also happens in the field.
I think that
Paul Rolland (???) wrote:
Hell, IRQ 23 is shared between libata and my modem !!!
Tried using the modem?
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Try the attached.
David
---
[PATCH] VFS: Make BSG declarations dependent on CONFIG_BLOCK
From: David Howells [EMAIL PROTECTED]
Make BSG function declarations dependent on CONFIG_BLOCK as they are not
compilable if the block layer is compiled out.
Signed-off-by: David Howells [EMAIL PROTECTED
Support the use of '*' in model_num and model_rev entries
in ata_device_blacklist[].
Signed-off-by: Alan Cox [EMAIL PROTECTED]
Signed-off-by: David Milburn [EMAIL PROTECTED]
---
libata-core.c | 16 ++--
1 files changed, 14 insertions(+), 2 deletions(-)
diff --git a/drivers/ata
Support the use of '*' in model_num and model_rev entries
in ata_device_blacklist[].
CC: [EMAIL PROTECTED]
Signed-off-by: David Milburn [EMAIL PROTECTED]
---
drivers/ata/libata-core.c | 11 +--
1 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/drivers/ata/libata-core.c b
Yes, I patched the 2.6.22.1 vanilla kernel with the libata patch from here.
http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.22.1-20070803.tar.bz2
--David Madsen
On 8/3/07, Tejun Heo [EMAIL PROTECTED] wrote:
David Madsen wrote:
* The long boot delay on ASUS boards with on-board PMP
The updated kernel log with the debug patch is attached.
--David Madsen
On 8/4/07, Tejun Heo [EMAIL PROTECTED] wrote:
David Madsen wrote:
Yes, I patched the 2.6.22.1 vanilla kernel with the libata patch from here.
http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.22.1-20070803
On Wed, Jul 18, 2007 at 05:53:39PM +0900, Tejun Heo wrote:
David Shaw wrote:
It fails whether I use a raw /dev/sdd or partition it into one large
/dev/sdd1, or partition into multiple partitions. sata_sil24 seems to
work by itself, as does dm, but as soon as I mix sata_sil24+dm, I get
== corruption
* Partition /dev/sdd into /dev/sdd1 and /dev/sdd2, mke2fs and use
those partitions == no corruption
* Partition /dev/sdd into /dev/sdd1 and /dev/sdd2, create 2 dm linear
mappings on /dev/sdd1, mke2fs and use those dm devices ==
corruption
David
-
To unsubscribe from this list
On Wed, Jul 11, 2007 at 12:28:32AM +0900, Tejun Heo wrote:
Hello,
David Shaw wrote:
I'm having a problem with data corruption using devmapper on a SATA
disk using sata_sil24. I've done some work tracking it down, and
hopefully you folks can point me further in the right direction
On Thu, 2007-07-05 at 09:28 -0700, Linus Torvalds wrote:
On Wed, 4 Jul 2007, David Woodhouse wrote:
Oh, and here's another one for you. My Bluetooth mouse just stopped
working and hidd is deadlocked...
Looks like it is stuck on hidp_session_sem.
Nothing after 2.6.21 seems to have
On Thu, 2007-07-05 at 09:28 -0700, Linus Torvalds wrote:
On Wed, 4 Jul 2007, David Woodhouse wrote:
Oh, and here's another one for you. My Bluetooth mouse just stopped
working and hidd is deadlocked...
Looks like it is stuck on hidp_session_sem.
Oh, I suck. I failed to noticed
-mapper does the corruption happen. There
is nothing of interest logged in /var/log/messages or dmesg (I see the
usual messages around 'mount', but that's it).
Any suggestions? Many thanks,
David
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL
on sparc32 by
Mark Fortescue, who reported the new problem.
Also, fix the conditions for FORCED_DEBUG, which hadn't been adjusted to
the new sizes. Again noticed by Mark.
Signed-off-by: David Woodhouse [EMAIL PROTECTED]
diff --git a/mm/slab.c b/mm/slab.c
index a9c4472..b344e67 100644
--- a/mm/slab.c
On Tue, 2007-07-03 at 18:45 +0200, Michal Piotrowski wrote:
Hi all,
Here is a list of some known regressions in 2.6.22-rc7.
Oh, and here's another one for you. My Bluetooth mouse just stopped
working and hidd is deadlocked...
hidd D 1FE27798 5940 1695 1 (NOTLB)
Call Trace:
On Tue, Jul 03, 2007 at 07:50:26PM +0200, Bartlomiej Zolnierkiewicz wrote:
Hi,
On Tuesday 03 July 2007, Michal Piotrowski wrote:
IDE
Subject: 2.6.22-rcX: hda: lost interrupt
References : http://lkml.org/lkml/2007/6/29/121
Submitter : David Chinner [EMAIL PROTECTED]
Status
; and getting more
significant as you add more threads - I'm curious what happens
on 8 threads or more.
Dave
--
-Open up your eyes, open up your mind, open up your code ---
/ Dr. David Alan Gilbert| Running GNU/Linux on Alpha,68K| Happy \
\ gro.gilbert @ treblig.org | MIPS,x86,ARM
On Fri, 2007-06-22 at 01:52 +0200, Adrian Bunk wrote:
Users should use the libata based drivers for SATA drives.
NAK. Not all IDE drivers are converted yet. Not even all the relatively
common ones.
--
dwmw2
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a
On Fri, 2007-06-22 at 11:39 +0800, David Woodhouse wrote:
On Fri, 2007-06-22 at 01:52 +0200, Adrian Bunk wrote:
Users should use the libata based drivers for SATA drives.
NAK. Not all IDE drivers are converted yet. Not even all the relatively
common ones.
Ignore me. I thought you were
data.
Any help would be greatly appreciated.
Thanks,
David.
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
}
ide: failed opcode was: 0xef
David
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Michal Piotrowski [EMAIL PROTECTED]
Date: Tue, 05 Jun 2007 16:54:35 +0200
Sparc64
Subject: arch/sparc64/time.c doesn't compile on Ultra 1 (no PCI)
References : http://bugzilla.kernel.org/show_bug.cgi?id=8540
Submitter : Horst H. von Brand [EMAIL PROTECTED]
Status : patch
Mark Lord wrote:
David Greaves wrote:
I have 2 ide disks. If I enable SMART and hibernate/suspend2disk,
SMART is
disabled when I resume.
Just a thought: This *may* be fixable at the drive, with hdparm -K1.
Thanks Mark, good idea.
Just tried and it didn't help though :(
in fact, hda gave
kernel: hdb: max request size: 512KiB
Jun 1 21:56:25 cu kernel: hdb: 585940320 sectors (31 MB) w/2048KiB Cache,
CHS=36473/255/63, UDMA(133)
Jun 1 21:56:25 cu kernel: hdb: cache flushes supported
Jun 1 21:56:25 cu kernel: hdb: hdb1 hdb2
anything else needed?
David
-
To unsubscribe from
=
Thanks,
David
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Jeff Garzik [EMAIL PROTECTED]
Date: Wed, 09 May 2007 18:46:16 -0400
Bartlomiej Zolnierkiewicz wrote:
Bartlomiej Zolnierkiewicz (11):
ide: fix UDMA/MWDMA/SWDMA masks (v3)
ide: rework the code for selecting the best DMA transfer mode (v3)
ide: add ide_tune_dma()
a kernel package that would enable PMP so I can see all 5 drives
in my library, and not only the first one?
Ciao,
...David
--
// david lebel [EMAIL PROTECTED]
// http://www.lebel.org/
// pgp: 3633 6999 D47E 73ED 099F 4341 08A4 8E48 EF56 61D1
-
To unsubscribe from this list: send the line
On Saturday 31 March 2007 9:53 am, Linus Torvalds wrote:
On Sat, 31 Mar 2007, Thomas Gleixner wrote:
Right, but clock - sources/events need to be extremly late suspended and
early resumed. How can we ensure this ?
Make them be at the top of the device tree by adding them early. That's
to enumerate ... e.g. clocksources and clockevents
at a clearly defined point during suspend and resume.
This patch has a potential downside for devices that have multiple
power dependencies and which just happened to work before.
Signed-off-by: David Brownell [EMAIL PROTECTED]
--- g26.orig/drivers
On Saturday 31 March 2007 11:18 am, David Brownell wrote:
( please remove obsolute [EMAIL PROTECTED] from further messages!! )
On Saturday 31 March 2007 10:02 am, Ingo Molnar wrote:
i dont think there's any particular problem here because suspend/resume
wont be done during bootup
On Saturday 31 March 2007 8:13 pm, Jeff Chua wrote:
On 4/1/07, David Brownell [EMAIL PROTECTED] wrote:
for those will all get grouped together ... suspended very late and
resumed very early, regardless of when they get registered. Pretty
much the driver model parts of what Linus
On Wednesday 28 March 2007 2:27 pm, Maxim wrote:
On Wednesday 28 March 2007 22:59:26 David Brownell wrote:
When HPET is active it eats RTC IRQ,
Only when HPET timers 0 and 1 are set up for Legacy Replacement Mode.
In the more sensible Standard Mode, they have their own IRQs.
So
On Thursday 29 March 2007 4:29 pm, Maxim Levitsky wrote:
On Friday 30 March 2007 00:33:35 David Brownell wrote:
On Wednesday 28 March 2007 2:27 pm, Maxim wrote:
So the only way out is to emulate RTC using HPET,
It is done this way in old rtc driver, rtc-cmos should do the same
On Wednesday 28 March 2007 9:38 am, Linus Torvalds wrote:
It's a *device*, dammit. It should save and resume like one (probably as a
system device). The set_mode() etc stuff is at a completely different
(higher) conceptual level.
Agreed, except about probably as a system device.
Last I
On Wednesday 28 March 2007 1:19 pm, Maxim wrote:
On Wednesday 28 March 2007 21:38:55 David Brownell wrote:
Also, making HPET use the legacy mode seems like a step backwards.
It is not 'legacy' mode,
It is a legacy replacement mode.
Typo, sorry.
It this mode HPET takes over IRQ0
On Wednesday 28 March 2007 1:42 pm, Linus Torvalds wrote:
I won't disagree - it might well be much nicer to just show it in the
real device tree. I'm not 100% sure where in the tree it would go,
though. It should probably be inside the root entry, before any of the
PCI buses.
Mixing
From: Alan Cox [EMAIL PROTECTED]
Date: Fri, 23 Mar 2007 20:08:19 +
u64 is always unsigned long long (and its debug anyway)
It's plain unsigned long on sparc64 and some other 64-bit platforms.
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to
On Sat, 2007-02-10 at 09:03 -0500, Tejun Heo wrote:
Matteo Croce wrote:
On Friday 09 February 2007 15:54:53 you wrote:
On Fri, 2007-02-09 at 15:27 +0100, Matteo Croce wrote:
+ { PCI_VDEVICE(INTEL, 0x27c4), board_ahci }, /* ICH7M */
Wasn't this PCI ID proposed for addition a while ago, and
On Sat, 2007-02-10 at 06:46 +0100, Markus Trippelsdorf wrote:
sata_via :00:0f.0 : failed to iomap PCI BAR 0
Zero probably isn't allowed any more. We have to use PCI BAR 1 and
upwards only or the poor driver authors will get confused :)
--
dwmw2
-
To unsubscribe from this list: send the
On Fri, 2007-02-09 at 15:27 +0100, Matteo Croce wrote:
+ { PCI_VDEVICE(INTEL, 0x27c4), board_ahci }, /* ICH7M */
Wasn't this PCI ID proposed for addition a while ago, and subsequently
rejected? Or am I missing something?
- DML
-
To unsubscribe from this list: send the line unsubscribe
On Fri, 2007-02-09 at 18:39 +0100, Matteo Croce wrote:
On Friday 09 February 2007 15:54:53 you wrote:
On Fri, 2007-02-09 at 15:27 +0100, Matteo Croce wrote:
+ { PCI_VDEVICE(INTEL, 0x27c4), board_ahci }, /* ICH7M */
Wasn't this PCI ID proposed for addition a while ago, and subsequently
User applications using the HDIO_DRIVE_TASK ioctl specific
ATA registers to be returned to userspace.
Signed-off-by: David Milburn [EMAIL PROTECTED]
Acked-by: Tejun Heo [EMAIL PROTECTED]
Acked-by: Jeff Garzik [EMAIL PROTECTED]
Signed-off-by: Andrew Morton [EMAIL PROTECTED]
---
diff --git
User applications using the HDIO_DRIVE_TASK ioctl through libata
expect specific ATA registers to be returned to userspace. Verified
that ata_task_ioctl correctly returns register values to the
smartctl application.
Signed-off-by: David Milburn [EMAIL PROTECTED]
---
diff --git a/drivers/ata
on a check condition similiar to ata_cmd_ioctl().
Please ACK or comment.
Thanks,
David
--- linux-2.6.19-rc5/drivers/ata/libata-scsi.c.smart
+++ linux-2.6.19-rc5/drivers/ata/libata-scsi.c
@@ -273,8 +273,8 @@ int ata_task_ioctl(struct scsi_device *s
{
int rc = 0;
u8 scsi_cmd[MAX_COMMAND_SIZE
On Thu, 2006-02-16 at 16:09 +0100, Martin Devera wrote:
From: Martin Devera [EMAIL PROTECTED]
Add hotswap capability to Serverworks/BroadCom SATA controlers. The
controler has SIM register and it selects which bits in SATA_ERROR
register fires interrupt.
The solution hooks on COMWAKE
and in need of some testing.
Search the list archives for
* libata-dev
* ATA passthru (a.k.a. SMART) support
Look for messages Jeff Garzik and John W. Linville
HTH
David
--
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More
unsubscribe linux-ide
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
woops ;P
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Thank you much for breaking this down so well.
Hello, Kanniball.
I've digged lkml previously and what I've found out are
* It's basically because of faulty SATA implementation of the
affected seagate hard drives combined with standard-compliant but
peculiar behavior of silicon image
=0xd0 { Busy }
ide: failed opcode was: unknown
hda: drive not ready for command
ide0: reset: success
Thanks
David
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
lesson to individual Linux users that want to
know the best source for information on hardware compatiblity, that is
looking through the kernel xconfig with 'Prompt for development and/or
incomplete code/drivers' unchecked ;]
Ive learned my lesson and hopefully helped atleast one other person.
-David
Hi,
With kernel 2.6.10 on Intel (Dell Powervault 745N) When I insert the
sata_vsc module via 'modprobe sata_vsc' from the command line, the module
immediately recognizes the controller card and when it then enumerates the
attached disks, I am getting errors logged in syslog for each disk as
89 matches
Mail list logo
