mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: libsata doesn't like bus without master
Date: Sun, 11 Feb 2007 17:58:46 -0200	[thread overview]
Message-ID: <20070211195846.GC26874@khazad-dum.debian.net> (raw)
In-Reply-To: <45CF619D.6000704@shaw.ca>

On Sun, 11 Feb 2007, Robert Hancock wrote:
> Then in that case you should set the remaining drive as master. That's 
> just the way PATA is. A lot of BIOSes won't even detect a drive that's 
> set as slave with no master present.

I have seen at least three *thousand* boxes configured that way in the last
five years.  From at least a hundred different vendors (almost all of them
small "system assembler" vendors that mix generic and customer-specified
parts).

For some stupid reason, it appears that the norm around here (Brazil) is
that "no brand" boxes get assembled with ATAPI devices in slave mode.
Usually they attach it to the second channel using an 40-wire cable, even if
there is nothing using the first channel.

There is an amazing ammount of hardware out there which needs PATA drivers
to deal as gracefully as possible on a ATAPI PATA device alone as slave on a
channel, and I'd say at that point it is best to just deal with ATA PATA
devices in that configuration, too.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  parent reply	other threads:[~2007-02-11 19:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.OcrmlkSFqen95BGHXWJdR6KGswQ@ifi.uio.no>
     [not found] ` <fa.mIV6AQH7D5yiY39XNxbu0M2/1Kc@ifi.uio.no>
     [not found]   ` <fa.3Ti1gtH2JY4DWsqr3J1loC7lcc0@ifi.uio.no>
2007-02-11 18:34     ` Robert Hancock
2007-02-11 18:41       ` Patrick Ale
2007-02-11 19:58       ` Henrique de Moraes Holschuh [this message]
2007-02-11 20:09         ` Patrick Ale
2007-02-21 20:41 Vincent Legoll
2007-02-21 20:47 ` Vincent Legoll
2007-02-21 21:01   ` Patrick Ale
2007-02-21 21:04     ` Patrick Ale
2007-02-21 22:07     ` Vincent Legoll
2007-02-22  8:12     ` Paul Rolland
2007-02-22  8:38       ` Patrick Ale
     [not found] <fa.kM2jAt0lhoofVm0+pIia0W2vzoo@ifi.uio.no>
2007-02-11 17:39 ` Robert Hancock
2007-02-11 17:52   ` Patrick Ale
2007-02-13 16:05   ` Mark Lord
  -- strict thread matches above, loose matches on Subject: below --
2007-02-11 10:27 Patrick Ale
2007-02-13 20:17 ` Tejun Heo

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=20070211195846.GC26874@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®