All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Tejun Heo <htejun@gmail.com>,
	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: Mon, 14 Apr 2008 17:48:43 +0200	[thread overview]
Message-ID: <200804141748.44306.elendil@planet.nl> (raw)
In-Reply-To: <20080414135214.GC7385@csclub.uwaterloo.ca>

On Monday 14 April 2008, you wrote:
> > I also think the way I've implemented in the Debian installer should be
> > relatively safe:
> > 1) ide-generic is only loaded _after_ any otherwise detected modules
> > 2) it is only loaded if an ISA bus is present
> > 3) it is only included in the initrd for the installed system if
> > loading it in the installer resulted in additional block devices
> > appearing
>
> OK, great for x86 perhaps, what about other systems?

As I've said before, that needs testing.

> In the past debian would load ide-generic last.  It worked great.  Keep
> doing that.  I am not aware of loading ide-generic after all the other
> drivers ever causing any harm in the older debian installers.

Maybe not, but having it loaded in _every_ installed Debian system even when 
it was completely unused is definitely something we want to get rid of.

Note that the old behavior relied on the fact that initramfs-tools also 
loaded ide-generic by default, which it now no longer does.

Cheers,
FJP

  parent reply	other threads:[~2008-04-14 15:48 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 [this message]
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
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=200804141748.44306.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=bzolnier@gmail.com \
    --cc=htejun@gmail.com \
    --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.