mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Artur Frysiak <wiget@pld.org.pl>
To: linux-kernel@vger.kernel.org
Subject: Re: Why no modules for IDE chipset support?
Date: Wed, 25 Jul 2001 19:05:03 +0200	[thread overview]
Message-ID: <20010725190502.D29439@free.buy.pl> (raw)
In-Reply-To: <15198.37357.879359.519563@hertz.ikp.physik.tu-darmstadt.de> <20010725113445.B25434@hapablap.dyn.dhs.org>
In-Reply-To: <20010725113445.B25434@hapablap.dyn.dhs.org>

On Wed, Jul 25, 2001 at 11:34:45AM -0500, Steven Walter wrote:
> On Wed, Jul 25, 2001 at 11:31:25AM +0200, Uwe Bonnes wrote:
> > Hallo,
> > 
> > why are the IDE chipset support driver not modularized? Is there anything
> > fundamental that inhibits using these drivers as a modules?
> 
> They are availible as modules.  See "ATA/IDE/MFM/RLL support," which is
> a tristate.  If you select that as a module, then all the chipsets you
> select for support later will be compiled into one large module.
> 
> This is probably a bad idea, though, because if you compile IDE support
> as a module, you will not be able to mount your root partition if it is
> on an IDE disk.

This is not true. If you use initrd and load ide-mod, ide-probe-mod and
ide-disk modules on it then you may mount yours root partition.
For eg. we (PLD http://www.pld.org.pl/) have modular ide, scsi, reiserfs and
ext2 (sic!). Small tool called geninitrd make initrd based on
information from /etc/fstab, /etc/modules.conf and other configuration
files.
You may grab geninitrd from ftp://ftp.pld.org.pl/software/geninitrd/

Regards
-- 
Artur Frysiak
http://www.pld.org.pl/

  reply	other threads:[~2001-07-25 17:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-25  9:31 Uwe Bonnes
2001-07-25 16:34 ` Steven Walter
2001-07-25 17:05   ` Artur Frysiak [this message]
2001-07-25 17:23     ` Tomasz Kłoczko

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=20010725190502.D29439@free.buy.pl \
    --to=wiget@pld.org.pl \
    --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®