public inbox for kernelnewbies@kernelnewbies.org
 help / color / mirror / Atom feed
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: noloader@gmail.com
Cc: Greg KH <greg@kroah.com>,
	kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Disable EISA and probes
Date: Sat, 05 Sep 2020 16:25:45 -0400	[thread overview]
Message-ID: <111722.1599337545@turing-police> (raw)
In-Reply-To: <CAH8yC8k1DYaKAgs7cvf9T+8C07hdMwA7F=o3f6oC0QOARRDQKA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1200 bytes --]

On Sat, 05 Sep 2020 11:11:27 -0400, Jeffrey Walton said:
> On Sat, Sep 5, 2020 at 10:52 AM Greg KH <greg@kroah.com> wrote:

> > > Modern distros and their minimum requirements preclude EISA. One
> > > cannot meet a distros minimum requirements and have EISA.
> >
> > Then file a bug with your distro to have it removed from their kernel
> > images.
>
> Thanks.
>
> So does that mean it is not possible to disable EISA and its probes?

16:18:21 0 [~] uname -a
Linux turing-police 5.9.0-rc2-next-20200827-dirty #779 SMP Sun Aug 30 04:22:57 EDT 2020 x86_64 x86_64 x86_64 GNU/Linux
16:19:38 0 [~] grep EISA /boot/config-`uname -r`
CONFIG_HAVE_EISA=y
# CONFIG_EISA is not set
16:19:55 0 [~]

It's possible, because I'm positive this laptop isn't about to suddenly sprout
an EISA bus that needs supporting. (That, and it's fun to watch a kernel build
blow up because I have an oddball .config for the build :)

Convincing a distro to remove it is a different question.  And I'm sure they
won't be interested in doing so unless you can prove "can't meet minimum
requirements and have EISA". Can you name-and-shame some distros, and
point at a minimum requirement that can't be met by a box that has EISA?



[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      reply	other threads:[~2020-09-05 20:26 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
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 [this message]

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=111722.1599337545@turing-police \
    --to=valdis.kletnieks@vt.edu \
    --cc=greg@kroah.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=noloader@gmail.com \
    /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