On Mon, 25 Feb 2008 19:20:59 -0500
Mark Lord [EMAIL PROTECTED] wrote:
The optional .qc_defer() methods don't seem to be called
on the ata_exec_internal_sg() path.
At present, this is probably okay. But in the future,
as we add functionality for link power management
and hotplug polling,
The general idea: A daemon running in user space monitors input data
from an accelerometer. When the daemon detects a critical condition,
That sounds like a non starter. What if the box is busy, what if the
daemon or something you touch needs memory and causes paging ?
Given the accelerometer
When masking mask out the modes that are unsupported not the ones that
are supported. This makes life happier.
Signed-off-by: Alan Cox [EMAIL PROTECTED]
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla-2.6.25-rc2-mm1/drivers/ata/pata_hpt366.c
linux-2.6.25-rc2-mm1
Does anyone have in their posession the old errata docs for the HPT370
controller. I'm seeing two reports now where there is some kind of FIFO
corruption pattern (shifted data and duplicated dwords) on the drives
which are UDMA100 blacklisted, so presumably more is required for the
workaround.
From the patch description it can't be told whether the patch itself is
correct and only the patch description is bogus...
zero length PRD misparsing. If I remember rightly old IDE never generates
64K PRD slots because other hardware can't handle it either (CS5520/30
etc)
-
To unsubscribe from
O I don't see the connection between (no-)smp and ata. Something with
interrupt routing/IPI, missing irq ack? Booting another !SMP kernel
works fine. The problem also exists in 2.6.24-rc2.
Almost certainly interrupt routing try smp but with noapic and see if it
fails as well ?
-
To unsubscribe
On Fri, 22 Feb 2008 12:55:20 +0800
Huang, Shane [EMAIL PROTECTED] wrote:
Jeff:
SB700 SATA controller can support 64 bit DMA, the previous commit
badc2341579511a247f5993865aa68379e283c5c was added with
careless reference to SB600, which should be modified by this patch.
Does the SB700 have
Heck, if .dev_select() took a *device* instead of a *port*
as it's parameter, then I could probably manage it fine in there.
dev_select gets called during probing before the relevant structures are
neccessarily set up.
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the
On Fri, Feb 22, 2008 at 09:52:45AM -0500, Richardson, Charlotte wrote:
There is a hack in its probe routine that disables this. I've disabled the
hack and ran a long test of
hotplugs yesterday (added and removed a DVD drive connected to the ESB2 IDE -
this is Intel
device 0x269E) for 26
3) It is critical to ensure that the ATA ctl register is never
written to when no drive is attached. This means bracketing the SRST
sequence to first do a PCS detection before permitting the SRST.
If ctl is accessed with no drive attached, the machine locks up hard.
At least for PATA you
On Fri, 22 Feb 2008 20:57:54 +0100
Daniel Schroeder [EMAIL PROTECTED] wrote:
hi there,
this is an asus m2n32-sli deluxe with nvidia chipset. After updating the
bios from 1503 to 1701 following in dmesg, and ide drive doesn't work.
Kernel is 2.6.24.2
If it broke with the BIOS change you
. It does *not* automatically flush other sectors. Instead we must
re-issue the flush.
Signed-off-by: Alan Cox [EMAIL PROTECTED]
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla-2.6.25-rc2-mm1/drivers/ata/libata-core.c
linux-2.6.25-rc2-mm1/drivers/ata/libata-core.c
On Mon, 18 Feb 2008 13:50:02 +0100
Jan Evert van Grootheest [EMAIL PROTECTED] wrote:
Prefetch needs to be set for some ide devices to work when connected to
a ht6560b interface. This was not always done properly, causing a system
with a HD and CD on the primary interface to not work properly.
I think the ht6560b controller supports DMA.
The data sheet doesn't. It's a PIO controller capable of PIO4 with 32bit
host to cpu transfers are best.
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
I think, but didn't look real good nor test yet, that pata_legacy also
needs something comparable to select_proc? Or is that implemented in
some generic manner?
It sets it in the timing routine:
pata_legacy:ht6560b_set_piomode
-
To unsubscribe from this list: send the line
Hmm. But what do you then think that 2.2 did?
PIO4
I mean it now does 1.15M/s and in 2.2 it would do ~4M/s with DMA on.
It's never done DMA.
-
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 Mon, Feb 18, 2008 at 03:53:46PM -0500, Mark Lord wrote:
+ /* some SATA bridges need us to indicate data xfer direction
*/
+ if (atapi_dmadir || (dev-id[62] 0x8000))
The rest of the code uses ata_ inlines/defines in ata.h for things like this
and religiously checks
On Sun, 17 Feb 2008 16:41:42 +0100
Joris [EMAIL PROTECTED] wrote:
Hello List,
Odd problem on my machines: the sata disks appear to be a lot slower
when used via ata_piix vs the ahci driver.
I would expect that. AHCI allows the use of NCQ and unloads a ton of work
from the processor. It also
Am I interpreting this correctly as having to choose between fast iops
with low cpu (+ hotplug) with ahci and twice the linear read speed
with ata_piix?
Some drives do weird things when NCQ is used and turn off some of their
caching in that case so it depends on the drive what happens to
Thus, I have implemented the 32-bit mode to bring the performance back
to the level of the old IDE driver. I jumped from 1.5 MB/s to 2.5 MB/s,
which is an important difference at this level of performance, especially
when large files are read. The 32-bit mode is enabled using the ioctl
which
transfers
When ATA_DFLAG_32BIT_PIO is set in ata flags, PIO transfers
will be performed in 32-bit, just like with the plain old IDE
drivers.
Acked-by: Alan Cox [EMAIL PROTECTED]
Although I think ata_data_xfer_32() would be safer and easier to add to
controllers as we check the docs. But that can
So, why is ide-scsi still in the tree? Is there some use case besides
cdrecord? (Which can use /dev/hda already without the ide-scsi blob...)
With old IDE only ide-scsi can handle some of the more obscurely weird
devices, and some tape drives fail with ide-tape but work with ide-scsi
+
NAK. This is a sparse bug, fix sparse.
Yes, fair enough, but that's not all the patch is about.
1) it's using a max_t and min_t to force the comparisons as shorts, why
not just make it a static inline?
Because max_t and min_t also force the comparsion types
2) the static inline is a
On Fri, 15 Feb 2008 15:08:50 -0800
Harvey Harrison [EMAIL PROTECTED] wrote:
On Fri, 2008-02-15 at 22:53 +, Alan Cox wrote:
NAK. This is a sparse bug, fix sparse.
Yes, fair enough, but that's not all the patch is about.
1) it's using a max_t and min_t to force
/6-10 Acked-by: Alan Cox [EMAIL PROTECTED]
Alan
-
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
On Wed, 13 Feb 2008 21:14:32 -0800
Harvey Harrison [EMAIL PROTECTED] wrote:
Let's use ld for legacy_data instead of shadowing these static
int variables.
NAK - I purposefully used names that indicate what device the private
data is being used for in order to make it clear. Changing qdi and
declared here
Signed-off-by: Harvey Harrison [EMAIL PROTECTED]
Acked-by: Alan Cox [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
O I'm counting on kmalloc to return a cache aligned buffer. I found
some reason to think it does, but I don't remember offhand what that
Its defined to
reason was, or if it's configurable per-architecture. The buffer has
to be both physically and virtually contiguous, I was tempted to just
I hadn't considered that approach due to the way the ata_port is allocated:
libata-core.c:
host = scsi_host_alloc(ent-sht, sizeof(struct ata_port));
hosts.c:
struct Scsi_Host *scsi_host_alloc(struct scsi_host_template *sht, int
privsize)
{
shost =
Why does the calgary driver need this? Can we just use pci_get_device()
instead? Why do you need to walk the device list backwards? Do you get
false positives going forward?
It doesn't look to be performance critical so the driver can
pci_get_device until the end and use the final hit
I tell you what ... find me a parisc box that actually has IDE and we
might have told you ...
The NS87415 variant IDE has been tested on parisc and didn't blow up -
must just be lucky.
(actually, the pa8800's have IDE CD's on a cmd640 chip, but that oopses
on boot for no reason we've tracked
Has anyone else reported a problem like this? It requires
non-coherent DMA, and a lack of a cache invalidate instruction, and
one of the drivers that has this problem (it looks like sata_qstor
does too, I haven't looked at others), so maybe that doesn't cover
any other architectures.
Nobody
In the above example, even the reset sequence itself can cause hang if
the hardware is implemented slightly differently. The reason why
set_piomode() locks up but reset sequence doesn't is simple dumb luck.
I think the proper fix is to tell libata to detach the cdrom before
undocking.
Just
On Mon, Feb 11, 2008 at 11:29:07AM +0100, Holger Macht wrote:
In the above example, even the reset sequence itself can cause hang if
the hardware is implemented slightly differently. The reason why
set_piomode() locks up but reset sequence doesn't is simple dumb luck.
Another thing,
On Mon, Feb 11, 2008 at 11:04:46AM +0100, Holger Macht wrote:
Wouldn't the proper fix be to call ata_acpi_handle_hotplug _somewhere_?
(which is currently called nowhere AFAICS)
I think so. The T61 at least generated ACPI dock and undock messages for
IDE master/slaves and we can use those.
-
To
On Sun, 10 Feb 2008 14:44:16 -0500 (EST)
Robert P. J. Day [EMAIL PROTECTED] wrote:
in drivers/ata/libata-sff.c:
...
#if defined(CONFIG_NO_ATA_LEGACY)
/* Some platforms with PCI limits cannot address compat
port space. In that case we punt if their
Forcibly set more of the configuration at init time. This seems to fix at
least one problem reported. We don't know what most of these bits do, but
we do know what windows stuffs there.
Signed-off-by: Alan Cox [EMAIL PROTECTED]
diff -u --new-file --recursive --exclude-from /usr/src/exclude
Signed-off-by: Alan Cox [EMAIL PROTECTED]
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla-2.6.24-mm1/drivers/ata/pata_legacy.c
linux-2.6.24-mm1/drivers/ata/pata_legacy.c
--- linux.vanilla-2.6.24-mm1/drivers/ata/pata_legacy.c 2008-02-06
14:14:39.0 +
On Fri, 08 Feb 2008 10:45:21 -0500
Chuck Ebbert [EMAIL PROTECTED] wrote:
On 02/08/2008 10:21 AM, Alan Cox wrote:
+ ata_link_for_each_dev(dev, link) {
+ if (!ata_is_40wire(dev))
+ return 1
doesn't work. Lots of
cases in bugzilla show up as only the slave detecting the cable.
Signed-off-by: Alan Cox [EMAIL PROTECTED]
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla-2.6.24-mm1/drivers/ata/libata-core.c
linux-2.6.24-mm1/drivers/ata/libata-core.c
On Fri, 8 Feb 2008 16:25:08 +0100
Christoph Hellwig [EMAIL PROTECTED] wrote:
When trying to put some stress on qemu by running the xfs testsuite
I get the following:
debian:~/xfs-cmds/xfstests# sh check
[ 438.166822] SGI XFS with ACLs, security attributes, realtime, large block
numbers,
This has confused a few people so fix it
Signed-off-by: Alan Cox [EMAIL PROTECTED]
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla-2.6.24-mm1/drivers/ata/pata_amd.c
linux-2.6.24-mm1/drivers/ata/pata_amd.c
--- linux.vanilla-2.6.24-mm1/drivers/ata/pata_amd.c 2008
this, device is revalidated even after device error on
SETXFER.
This fixes kernel bugzilla bug 8563.
Tidy
Acked-by: Alan Cox [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
On Thu, 07 Feb 2008 10:18:53 +0900
Tejun Heo [EMAIL PROTECTED] wrote:
The first port of cx700 is SATA. Fix cable detection.
That should be set anyway by the drive detect but it does no harm and
fixes stuff if there is no drive.
Acked-by: Alan Cox [EMAIL PROTECTED]
-
To unsubscribe from
* Every driver for SFF controllers now uses ata_pci_default_filter()
unless the driver has custom implementation.
That is only needed for DMA capable devices. I guess it does no harm to
be consistent and call it anyway but you then say ..
* No reason to set ata_pci_default_filter() for
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
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
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
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
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
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
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
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
- Fix probe logic to support multiple devices better
- Fold in qdi and winbond support
- Fix promise 202C30 probe
- Restructure
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla-2.6.24/drivers/ata/pata_legacy.c
linux-2.6.24/drivers/ata/pata_legacy.c
---
Use qc_defer to serialize the two channels
Signed-off-by: Alan Cox [EMAIL PROTECTED]
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla-2.6.24/drivers/ata/pata_sl82c105.c
linux-2.6.24/drivers/ata/pata_sl82c105.c
--- linux.vanilla-2.6.24/drivers/ata/pata_sl82c105.c
On Wed, 23 Jan 2008 16:38:06 +0300
Sergei Shtylyov [EMAIL PROTECTED] wrote:
Hello.
Alan Cox wrote:
Why you chose to use ioread32() and iowrite32() if your device is
strictly
memory mapped? Those functions add some overhead, and boil down to readl()
and
There are distinct
On Tue, 22 Jan 2008 15:11:37 +0300
Anton Salnikov [EMAIL PROTECTED] wrote:
+static inline u32 ioread(u32 reg)
+{
+ return ioread32(base + reg);
+}
+
+static inline void iowrite(u32 val, u32 reg)
+{
+ iowrite32(val, base + reg);
+}
Why not just use
However, I'd like to see if we can track the problem through the SG_IO
direct path ... how many adjacent page bytes are corrupt? Just a few or
a large number (I'm wondering if it's an off by one or off by alignment
type bug)?
Which ATA controller is involved - in theory ATA DMA is byte
Why you chose to use ioread32() and iowrite32() if your device is
strictly
memory mapped? Those functions add some overhead, and boil down to readl()
and
There are distinct portability advantages but you shouldn't mix
ioread32/iowrite32 with ioremap as that isn't guaranteed to work.
transmission failure as timeouts. Of course, if we're ticking the timer
while the command is not in flight, that's a bug. If there are cases
where 30 secs isn't enough, can you please point me to those reports?
I have been, in bugzilla - the raid failure example where old IDE
eventually
Can you elaborate a bit? I don't really think completing a command
after 30sec timeout contributes a lot to driver stability.
Timeout, timeout, timeout, reset, timeout.. (repeat), failed I/O
This gives the end user no information about the fault, nor does it let
the upper layers of SCSI and
I still don't think it's worth the trouble. There's currently only one
reported device which forgets to raise IRQ on media error. The behavior
Most people wouldn't realise what is going on.
Old IDE says it works for PATA. For SATA I can see it might need more
care and you might simply
+static inline u32 ioread(u32 reg)
+{
+ return ioread32(base + reg);
+}
+
+static inline void iowrite(u32 val, u32 reg)
+{
+ iowrite32(val, base + reg);
+}
Why not just use ioread32/iowrite32 directly ?
Otherwise this looks way way better.
Alan
-
To unsubscribe from this list:
Could you point me to some bugreports?
I would like to know more about hosts/conditions for which it happens.
The timer reset path races the I/O path races the interrupt path. That
was the vomitously foul race that persuaded me to go libata instead. I
seem to remember explaining this all some
This puts winbond VLB in with the other ISA/VLB support and means we can
lose pata_winbond.c. With all the VLB/ISA probe in one space (and out of
the core libata) this makes legacy probing work sanely.
Also switch to devm_ for resource handling on the ports post probe
Signed-off-by: Alan Cox
ata_irq is always assigned so does not need to be initialised to zero.
Signed-off-by: Alan Cox [EMAIL PROTECTED]
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla-2.6.24-rc8-mm1/drivers/ata/pata_mpc52xx.c
linux-2.6.24-rc8-mm1/drivers/ata/pata_mpc52xx.c
Minor tidying up. Only real change is to return UNK not 80 wire when we
don't know the cable type. This didn't use to matter but with Tejun's
reworking of cable detection it may.
Signed-off-by: Alan Cox [EMAIL PROTECTED]
diff -u --new-file --recursive --exclude-from /usr/src/exclude
If no device is active return an error not zero.
Signed-off-by: Alan Cox [EMAIL PROTECTED]
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla-2.6.24-rc8-mm1/drivers/ata/pata_winbond.c
linux-2.6.24-rc8-mm1/drivers/ata/pata_winbond.c
--- linux.vanilla-2.6.24-rc8-mm1
Signed-off-by: Alan Cox [EMAIL PROTECTED]
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla-2.6.24-rc8-mm1/drivers/ide/pci/pdc202xx_old.c
linux-2.6.24-rc8-mm1/drivers/ide/pci/pdc202xx_old.c
--- linux.vanilla-2.6.24-rc8-mm1/drivers/ide/pci/pdc202xx_old.c 2008-01-19
On Sat, 19 Jan 2008 19:54:03 +0300
Sergei Shtylyov [EMAIL PROTECTED] wrote:
Hello.
Alan Cox wrote:
Signed-off-by: Alan Cox [EMAIL PROTECTED]
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla-2.6.24-rc8-mm1/drivers/ide/pci/pdc202xx_old.c
linux-2.6.24
+ /* udmatim Register */
+ palm_bk3710_base-config.udmatim = 0xFFF0;
+ palm_bk3710_base-config.udmatim |= level;
Direct memory access to I/O space - should be using read/write functions
Sigh, I was anticipationg that somebody would say that... :-)
Well
On Thu, 17 Jan 2008 21:50:56 +0300
Anton Salnikov [EMAIL PROTECTED] wrote:
This is Palmchip BK3710 IDE controller support for kernel version 2.6.24-rc8.
The IDE controller logic supports PIO, multiword DMA and ultra-DMA modes.
Supports interface to compact Flash (CF) configured in True-IDE
I can confirm Mark's observation that the access speeds are slower - around
half the speed of the earlier Linux PIO driver, and a quarter the performance
of WinXP. Test CF card was a SanDisk UltraII as the target, with CB1410
(Yenta compatible TI clone) as the host CB32 controller.
The
[ 9031.028000] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
frozen
[ 9031.028000] ata1.00: cmd c8/00:08:90:ca:ce/00:00:00:00:00/e0 tag 0 cdb
0x0
data 4096 in
[ 9031.028000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
We got bored of waiting
On Mon, 14 Jan 2008 20:46:08 -0800
Johnny Luong [EMAIL PROTECTED] wrote:
Hi,
If possible, I would like to know if its worthwhile simply just to get another
SATA drive / different controller / cable rather than trying to figure out
this PATA drive on SATA/PATA controller... see attached for
On Tue, Jan 15, 2008 at 03:52:09PM -0500, Jeff Garzik wrote:
{
-if (ata_id_is_sata(dev_id))
-return 0; /* SATA */
if ((dev_id[93] 0x2000) == 0x2000)
return 0; /* 80 wire */
return 1;
Alan, is this .24 material?
There were a lot of
In looking through my config file, I don't see CONFIG_IDE_PIIX.
Below is a list of all the config entries that contain the patter
PIIX:
CONFIG_BLK_DEV_PIIX=y
CONFIG_ATA_PIIX=y
CONFIG_PATA_MPIIX=y
CONFIG_PATA_OLDPIIX=y
Any suggestions on how I may turn of the conflicting piix support?
$ hdparm --Istdin hdparm.out
ATA device, with non-removable media
Model Number: Integrated Technology Express Inc
Serial Number: G!
Standards:
Likely used: 1
Configuration:
Logical max current
cylinders 0 0
Other than that, I guess the solutions would be to just set a 32-bit
mask on the device if either port has an ATAPI device connected (which
is fairly ugly, considering that you could do things like hotplug an
ATAPI device when the other port was in use, for example), or do
something to
Yes, I concur for the short term. The other two possible courses of
action either involve long discussions (the different device one) or
you'll never quite be sure you got all the paths (the GFP_DMA32 one).
At least with this one, you know everything will work.
The different device one is
Thanks. You do indeed have both the old IDE and new IDE drivers trying to
drive bits of the system. I don't see the CD-ROM in the dmesg at all
however ?
If you turn off CONFIG_ATA you should get just old IDE drivers and your
disk back working sanely.
Alan
-
To unsubscribe from this list: send
I have the same kernel and configuration on my Dell D600 (an older
version of the same laptop), and hdparm –d works just fine.
We you using the IDE driver for PATA devices and the SATA driver for SATA
devices ? If so the really nasty hacks for that were dropped as current
libata PATA support is
On Fri, 11 Jan 2008 14:49:46 -0500
Kristin Vadas Marsicano [EMAIL PROTECTED] wrote:
Both laptops have IDE drives. The kernel image booted on the two
laptops are exactly the same. Please let me know if this doesn't
answer your question -- I'm new to this and not quite sure I
understand the
My concern with disabling the new drivers is as follows: I use this
linux kernel and config image to boot machines over PXE and call a
shred program on each of the harddrives. If I turn off CONFIG_ATA,
will this limit my ability to support various new IDE and SATA drives
for running shred?
I was talking to Kristin this morning about doing that. I was
concerned that there is not anybody certifying that each individual
disk drive model / firmware release is properly implementing the
Security Erase function.
Are you aware of testing body, etc. that publishes a white-list of
trying to fix it for some time now finally got a machine with
pata_ali and non-working MWDMA2 ATAPI device on my desk a few weeks ago.
Oh good. I've been through a pile of ones that just work.
Which North and south does it have and what revision ?
I walked through IDE and libata codes and
On Wed, 9 Jan 2008 17:16:35 +
Alan Cox [EMAIL PROTECTED] wrote:
trying to fix it for some time now finally got a machine with
pata_ali and non-working MWDMA2 ATAPI device on my desk a few weeks ago.
Oh good. I've been through a pile of ones that just work.
Which North and south
On Tue, 08 Jan 2008 22:19:38 +0900
Tejun Heo [EMAIL PROTECTED] wrote:
Implement libata.force_cbl parameter to work around incorrect PATA
cable detection.
This seems to be a pretty hopeless hack as it assumes all your devices
are on the same cable (most boxes now have SATA and PATA). If we are
On Tue, 8 Jan 2008 17:26:05 +0100
Maciej Rutecki [EMAIL PROTECTED] wrote:
I have this message when resume from suspend to disk:
Looks fine to me.
-
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 Tue, 8 Jan 2008 20:23:52 +0100
Andi Kleen [EMAIL PROTECTED] wrote:
Is there a workaround for the long ugly boot messages on sees
with libata and qemu (0.9.0 CVS 070719)? It boots eventually, but it looks
quite ugly.
I suppose that's a qemu device model bug or could it be a Linux
Since I assume that qemu code base is wide spread and if a workaround
is not too ugly I think it would be nice if the kernel handled that.
Qemu behaves exactly the same way as a broken device in a situation where
data corruption may occur. It would be extremely bad to remove sanity
checking in
On Tue, 8 Jan 2008 22:37:16 +0100
Andi Kleen [EMAIL PROTECTED] wrote:
On Tue, Jan 08, 2008 at 09:19:31PM +, Alan Cox wrote:
Since I assume that qemu code base is wide spread and if a workaround
is not too ugly I think it would be nice if the kernel handled that.
Qemu behaves
This only forces PATA controllers to certain cable type. It's a last
resort method for installation or live media - just enough to get things
going.
In which case we only need to be able to force UDMA33 or less ?
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body
In which case we only need to be able to force UDMA33 or less ?
Cable detection goes wrong and 40c is detected as 80c. However, we got
In which case we only (see first question). I don't see why we need to
force anything but max speed UDMA 33
-
To unsubscribe from this list: send the line
On Sun, 06 Jan 2008 12:25:10 -0800
Linda Walsh [EMAIL PROTECTED] wrote:
Robert Hancock wrote:
If this is a Seagate, I believe that they don't have AAM enabled on
any of their newer drives (something about a lawsuit for patent
infringement on that feature, or something). Quite likely
On Fri, 04 Jan 2008 14:52:25 +0100
[EMAIL PROTECTED] wrote:
Hi,
this looks like a bug to me (see below)
happens on 2.6.24rc6 and i came across this by chance...
i`m here on notebook with vmware only, so i cannot test if this happens on
real hardware, too.
maybe someone can try
it to grab anything ST412 compatible even if it
is an unknown PCI device. That
allows libata to offer the same just get me a disk somehow fallback that old
IDE did.
Signed-off-by: Alan Cox [EMAIL PROTECTED]
Obsoletes: pata_qdi
diff -u --new-file --recursive --exclude-from /usr/src/exclude
Signed-off-by: Alan Cox [EMAIL PROTECTED]
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla-2.6.24-rc6-mm1/drivers/ata/pata_mpc52xx.c
linux-2.6.24-rc6-mm1/drivers/ata/pata_mpc52xx.c
--- linux.vanilla-2.6.24-rc6-mm1/drivers/ata/pata_mpc52xx.c 2008-01-02
16:03
1 - 100 of 855 matches
Mail list logo
