linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: n0diamond@yahoo.co.jp
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	Jim Paris <jim@jtan.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Sergei Shtylyov <sshtylyov@ru.mvista.com>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	Mark Lord <liml@rtr.ca>
Subject: Re: Off-by-one in both LIBATA and IDE drivers
Date: Fri, 13 Mar 2009 08:45:06 -0600	[thread overview]
Message-ID: <49BA7172.80908@gmail.com> (raw)
In-Reply-To: <20090313074120.48682.qmail@web4108.mail.ogk.yahoo.co.jp>

Norman Diamond wrote:
> LIBATA with the patch to ata.h now handles all sectors on
> hard drives that it recognizes.
> 
> An example of a hard drive that it recognizes is one that
> is attached to an Intel ICH7M chipset when hda=noprobe
> hdc=noprobe have been specified in the boot command.
> 
> An example of a hard drive that it doesn't recognize is
> one that is attached to an Intel PIIX4 chipset when
> hda=noprobe hdc=noprobe have been specified in the boot
> command.
> 
> In either case, the boot parameters persuade the old IDE
> drivers not to grab the controllers.
> 
> With ICH7M, LIBATA takes over and runs both the hard drive
> and DVD at full speed.
> 
> With PIIX4, LIBATA initializes.  End of story.  Slax can't
> find its own CD.  If I only use hda=noprobe then the old
> IDE controller assigns hdc to the CD and Slax finds it,
> but the hard drive is still undetected.  Behaviour is the
> same under VMware as in a genuine old PC.
> 
> LIBATA's PIIX drivers are built in along with everything
> else.  They just seem not to get executed.
> 
> What am I missing?

I assume that ATA_PIIX is set in the configuration.. The lspci -vn and
dmesg output from when it fails to detect would be useful.

> 
> --------------------------------------
> Power up the Internet with Yahoo! Toolbar.
> http://pr.mail.yahoo.co.jp/toolbar/


  reply	other threads:[~2009-03-13 14:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-11  1:50 Off-by-one in both LIBATA and IDE drivers Norman Diamond
2009-03-11  3:03 ` Jim Paris
2009-03-11  3:28   ` Norman Diamond
     [not found]     ` <49B78859.5050807@ru.mvista.com>
2009-03-11 21:03       ` Norman Diamond
2009-03-12 11:20   ` Norman Diamond
2009-03-12 14:30     ` Mark Lord
2009-03-12 23:02       ` Norman Diamond
2009-03-13  7:41         ` Norman Diamond
2009-03-13 14:45           ` Robert Hancock [this message]
2009-03-14  2:05             ` Norman Diamond
2009-03-14  2:15               ` Robert Hancock
2009-03-14  8:48                 ` Alan Cox
2009-03-14  9:34                   ` Norman Diamond
2009-03-14 10:48                     ` Alan Cox
2009-03-14  8:46               ` Alan Cox
2009-03-11  8:27 ` Alan Cox
2009-03-11  8:38   ` Norman Diamond
2009-03-12  0:10     ` Robert Hancock
2009-03-12  2:28       ` Norman Diamond
2009-03-12  4:26         ` Robert Hancock

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=49BA7172.80908@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=jim@jtan.com \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=n0diamond@yahoo.co.jp \
    --cc=sshtylyov@ru.mvista.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).