From: Jeffrey Walton <noloader@gmail.com>
To: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Disable EISA and probes
Date: Sat, 5 Sep 2020 07:31:13 -0400 [thread overview]
Message-ID: <CAH8yC8kBdaD2NriscXnFus6cyCuouD8MUPfeOpA-m_bzP92VFA@mail.gmail.com> (raw)
In-Reply-To: <20200905061514.GA177286@kroah.com>
On Sat, Sep 5, 2020 at 2:15 AM Greg KH <greg@kroah.com> wrote:
>
> On Fri, Sep 04, 2020 at 10:57:38PM -0400, Jeffrey Walton wrote:
> > Hi Everyone,
> >
> > I would like to disable EISA and its probes during boot. I found the
> > docs at https://www.kernel.org/doc/html/latest/driver-api/eisa.html,
> > but it does not discuss how to disable EISA or the probes.
> >
> > I also found https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543919,
> > where folks are wondering why EISA is enabled by default nowadays. And
> > one person asks about a kernel option to disable it (like I am doing).
> >
> > I'd like to add a boot param like eisa=0 or eisa=off, but I suspect
> > it's not that easy. Looking at the three documented kernel parameters,
> > they all enable EISA and probes.
> >
> > How do I disable EISA and the probes?
>
> Build a kernel without EISA in it at all? That's the simplest way as
> you must have some custom hardware that doesn't like this, so a
> custom-configuration seems like the best option.
Nothing custom. I just have modern hardware.
What's the purpose of including EISA by default? It has not been used
in 25 years.
> Did you try that and it did not work? What is the problem of EISA at
> boot anyway?
No, I did not build a custom kernel. I was looking for kernel options
to disable it.
The machine is part of a distro.
Jeff
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-09-05 11:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 2:57 Disable EISA and probes Jeffrey Walton
2020-09-05 6:15 ` Greg KH
2020-09-05 11:31 ` Jeffrey Walton [this message]
2020-09-05 11:37 ` Greg KH
2020-09-05 13:17 ` Jeffrey Walton
2020-09-05 14:52 ` Greg KH
2020-09-05 15:11 ` Jeffrey Walton
2020-09-05 20:25 ` Valdis Klētnieks
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=CAH8yC8kBdaD2NriscXnFus6cyCuouD8MUPfeOpA-m_bzP92VFA@mail.gmail.com \
--to=noloader@gmail.com \
--cc=kernelnewbies@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).