All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: easiest way to deactivate a driver at boot time?
Date: Thu, 15 Dec 2016 03:49:01 -0800	[thread overview]
Message-ID: <20161215114901.GA22625@kroah.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1612150435420.4882@ca624034.mitel.com>

On Thu, Dec 15, 2016 at 04:56:18AM -0500, Robert P. J. Day wrote:
> 
>   (Q asked by a colleague, a wee bit vague on details so i'm hoping
> i'm describing it correctly, seems like it should be easy to solve.)
> 
>   short form of question: what is the standard way of, at boot time,
> passing the kernel information to specify that a built-in driver
> should *not* be started?

Depends on the subsystem and driver, the only "standard way" is to just
not build the driver into the kernel in the first place and use modules
and load the module from userspace as-needed.

Or, use the device tree that is passed to the kernel by the bootloader
to define the hardware and if the hardware isn't defined, then no driver
will get bound to it.

good luck!

greg k-h

  reply	other threads:[~2016-12-15 11:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-15  9:56 easiest way to deactivate a driver at boot time? Robert P. J. Day
2016-12-15 11:49 ` Greg KH [this message]
2016-12-15 12:20   ` Clemens Gruber
2016-12-15 12:35     ` Daniel.
2016-12-15 12:55       ` Robert P. J. Day
2016-12-15 13:38         ` Daniel.
     [not found] ` <100DFE2D-EB21-4D9F-B46D-CBD284D4FD60@amazon.com>
2016-12-15 12:26   ` Hayward, Shaun

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=20161215114901.GA22625@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 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.