All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Frans Pop <elendil@planet.nl>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Subject: Re: No IDE drivers loaded for Toshiba Satellite 320 CDS
Date: Thu, 17 Apr 2008 07:12:35 +0900	[thread overview]
Message-ID: <480679D3.7030705@gmail.com> (raw)
In-Reply-To: <200804162008.27655.elendil@planet.nl>

Frans Pop wrote:
> On Wednesday 16 April 2008, Tejun Heo wrote:
>> Yeah, theoretically, you're right.  The problem is that what breaks when
>> things go wrong.  If you don't probe generic ports by default, harddisks
>> won't be detected on some legacy systems but you can always prompt the
>> user about loading the generic driver.  If you probe generic ports by
>> default, when things go wrong, you break modern machines in an
>> unrecoverable (w/o reset) way.  I'd rather choose bothering the user on
>> legacy machines.
> 
> The problem here is determining whether a machine is "legacy" or not.
> So far in this discussion I've seen no suggestions how to do that (except 
> maybe for my test whether /sys/bus/isa is present), which would mean asking 
> _all_ users, and that's a damned ugly option.

Asking when no harddisk is detected w/ the option to choose it 
explicitly should do for most cases.  No?

-- 
tejun

  reply	other threads:[~2008-04-16 22:12 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02 13:24 No IDE drivers loaded for Toshiba Satellite 320 CDS Frans Pop
2008-04-02 13:27 ` Frans Pop
2008-04-02 13:57 ` Lennart Sorensen
2008-04-02 14:29   ` Frans Pop
2008-04-02 15:46     ` Lennart Sorensen
2008-04-02 16:20       ` Frans Pop
2008-04-02 19:49         ` Lennart Sorensen
2008-04-03 17:47           ` Frans Pop
2008-04-03 19:31             ` Lennart Sorensen
2008-04-04  6:59               ` Frans Pop
2008-04-13  2:39             ` Tejun Heo
2008-04-13 13:59               ` Frans Pop
2008-04-14 13:52                 ` Lennart Sorensen
2008-04-14 13:56                   ` Alan Cox
2008-04-14 13:56                     ` Alan Cox
2008-04-14 15:29                     ` Frans Pop
2008-04-14 15:48                   ` Frans Pop
2008-04-14 13:47               ` Lennart Sorensen
2008-04-14 13:53                 ` Alan Cox
2008-04-14 13:53                   ` Alan Cox
2008-04-15  2:37                   ` Tejun Heo
2008-04-15 10:04                     ` Alan Cox
2008-04-15 23:25                       ` Tejun Heo
2008-04-15 14:47                     ` Lennart Sorensen
2008-04-15 23:31                       ` Tejun Heo
2008-04-16 18:08                         ` Frans Pop
2008-04-16 22:12                           ` Tejun Heo [this message]
2008-04-17 14:05                             ` Lennart Sorensen
2008-04-24  3:48                               ` Tejun Heo
2008-04-16 23:24                           ` Alan Cox
2008-04-02 16:33 ` Ondrej Zary
2008-04-02 20:05   ` Lennart Sorensen
2008-04-02 20:10     ` Ondrej Zary
2008-04-02 20:22       ` Lennart Sorensen
2008-04-02 20:34         ` Ondrej Zary
2008-04-03 17:50           ` Alan Cox

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=480679D3.7030705@gmail.com \
    --to=htejun@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=elendil@planet.nl \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    /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.