All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Slagter <erik@slagter.name>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Mark Lord <liml@rtr.ca>, linux-ide@vger.kernel.org
Subject: Re: libata and PATA devices
Date: Sat, 13 Aug 2005 17:50:50 +0200	[thread overview]
Message-ID: <1123948250.11048.9.camel@localhost.localdomain> (raw)
In-Reply-To: <42FE12D6.1070600@pobox.com>

[-- Attachment #1: Type: text/plain, Size: 832 bytes --]

On Sat, 2005-08-13 at 11:33 -0400, Jeff Garzik wrote:
> Erik Slagter wrote:
> > result: the pata harddisk is recognised by libata_piix and
> > assigned /dev/sda, the dvd drive is found by the generic ide driver.
> > (dmesg output attached)

> Great!  That's precisely what's supposed to happen.  Except, the hard 
> drive appears to be SATA, not PATA:
> 
> > ata1: SATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0xBFA0 irq 14
> > ata1: dev 0 cfg 49:2b00 82:346b 83:5b29 84:4003 85:3469 86:1a09 87:4003 88:203f
> > ata1: dev 0 ATA, max UDMA/100, 156301488 sectors:
> > ata1: dev 0 configured for UDMA/100
> 
> Everything appears to be working just fine.  DVD appears via IDE driver, 
> SATA drive appears via libata.

Nope. The harddisk is not SATA, it's PATA. See the links I posted
earlier. That's the whole point.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-08-13 15:51 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-07 17:48 libata and PATA devices Andreas Klöckner
2005-08-08  1:43 ` Tejun Heo
2005-08-08  3:02   ` Jeff Garzik
2005-08-08 10:10     ` Erik Slagter
2005-08-09 13:48       ` Mark Lord
2005-08-09 14:10         ` Mark Lord
2005-08-09 18:01           ` Jeff Garzik
2005-08-09 17:05         ` Erik Slagter
2005-08-09 18:02           ` Jeff Garzik
2005-08-09 17:59         ` Jeff Garzik
2005-08-11  3:57         ` Jeff Garzik
2005-08-11  9:37           ` Erik Slagter
2005-08-11 10:03             ` Bartlomiej Zolnierkiewicz
2005-08-11 10:17               ` Erik Slagter
2005-08-11 10:26                 ` Bartlomiej Zolnierkiewicz
2005-08-11 15:29                   ` Erik Slagter
2005-08-11 15:57                     ` Bartlomiej Zolnierkiewicz
2005-08-11 16:48                       ` Erik Slagter
2005-08-11 17:05           ` Mark Lord
2005-08-11 17:19             ` Jeff Garzik
2005-08-11 19:38               ` Erik Slagter
2005-08-11 20:19                 ` Wes Newell
2005-08-11 20:21                 ` Jeff Garzik
2005-08-11 20:25                   ` Jeff Garzik
2005-08-13 11:30                   ` Erik Slagter
2005-08-13 15:33                     ` Jeff Garzik
2005-08-13 15:50                       ` Erik Slagter [this message]
2005-08-13 15:56                         ` Jeff Garzik
2005-08-13 16:03                           ` Erik Slagter
2005-08-13 16:44                             ` Jeff Garzik
2005-08-13 16:53                               ` Erik Slagter
2005-08-15 21:39                                 ` Mark Lord
2005-08-16  7:21                                   ` Erik Slagter
2005-08-13 15:56                       ` Tyler
2005-08-13 15:57                         ` Jeff Garzik
2005-08-13 16:05                           ` Erik Slagter
2005-08-13 16:42                             ` Jeff Garzik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1123948250.11048.9.camel@localhost.localdomain \
    --to=erik@slagter.name \
    --cc=jgarzik@pobox.com \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.