mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Tejun Heo <htejun@gmail.com>
Cc: Frans Pop <elendil@planet.nl>,
	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 10:05:06 -0400	[thread overview]
Message-ID: <20080417140506.GC7385@csclub.uwaterloo.ca> (raw)
In-Reply-To: <480679D3.7030705@gmail.com>

On Thu, Apr 17, 2008 at 07:12:35AM +0900, Tejun Heo wrote:
> Asking when no harddisk is detected w/ the option to choose it 
> explicitly should do for most cases.  No?

I suppose it might, although I could still see an older machine have a
PCI controller as well as an ISA legacy controller on an ISA sound card,
and might even have a CDROM drive connected to the sound card.  Not very
likely though, but not imposible.  In that case you might detect the HD
connected to the HD, but not the CDROM connected to the sound card.
That might be confusing to the user.  On the other hand anyone running
such old hardware might just have a pretty good idea what they are doing
and could run in expert mode and tell the installer to also load the
generic driver.

I still think the correct solution is to always try loading it, posibly
with a boot option to make the installer not do so for any machines that
have issues with that.  Any such machines should then have bug reports
filed so that the driver that runs their chipset's IDE controller in a
native mode can ensure they reserve the legacy IDE ports so that nothing
else (like the generic driver) can go poking at them.

After all I thought the whole point of all the ports listed in
/proc/ioports was to indicate which io ports were currently reserved by
which driver so that no other driver could try to access them.  If it
doesn't in fact work that way then it probably should.

-- 
Len Sorensen

  reply	other threads:[~2008-04-17 14:05 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02 13:24 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 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-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
2008-04-17 14:05                             ` Lennart Sorensen [this message]
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=20080417140506.GC7385@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=elendil@planet.nl \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --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®