public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Greg KH <greg@kroah.com>
Cc: Giacomo Catenazzi <cate@debian.org>,
	Linux Kernel List <linux-kernel@vger.kernel.org>,
	"Eric S. Raymond" <esr@thyrsus.com>
Subject: Re: Autoconfiguration: Original design scenario
Date: Tue, 15 Jan 2002 19:16:25 +0000	[thread overview]
Message-ID: <20020115191625.F1822@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3C4401CD.3040408@debian.org> <20020115105733.B994@flint.arm.linux.org.uk> <3C442395.8010500@debian.org> <20020115183432.GC27059@kroah.com>
In-Reply-To: <20020115183432.GC27059@kroah.com>; from greg@kroah.com on Tue, Jan 15, 2002 at 10:34:32AM -0800

On Tue, Jan 15, 2002 at 10:34:32AM -0800, Greg KH wrote:
> Russell, when /sbin/hotplug is part of the initramfs in 2.5, the driver
> will automatically be loaded for your new card, IF you have all the
> different modules already built.  You will not need autoconfigure, just
> a good vendor kernel :)

Chuckle.  I believe you still need to pass the module parameters, even
though it can detect the chip.  I have no idea why, and I no longer have
the ISDN card within my administrative control.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  parent reply	other threads:[~2002-01-15 19:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-15 10:17 Autoconfiguration: Original design scenario Giacomo Catenazzi
2002-01-15 10:57 ` Russell King
2002-01-15 12:41   ` Giacomo Catenazzi
2002-01-15 18:34     ` Greg KH
2002-01-15 18:31       ` Eric S. Raymond
2002-01-15 23:07         ` Greg KH
2002-01-15 23:02           ` Eric S. Raymond
2002-01-15 19:16       ` Russell King [this message]
2002-01-16  8:12       ` Giacomo Catenazzi
2002-01-16 15:51   ` Kai Germaschewski

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=20020115191625.F1822@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=cate@debian.org \
    --cc=esr@thyrsus.com \
    --cc=greg@kroah.com \
    --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