From: "H. Peter Anvin" <hpa@zytor.com>
To: Samuel Thibault <Samuel.Thibault@ens-lyon.org>,
Sebastien Hinderer <Sebastien.Hinderer@ens-lyon.org>,
Andreas Mohr <andi@lisas.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Len Brown <len.brown@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: EuroBraille/Iris power off
Date: Wed, 25 Aug 2010 17:06:20 -0700 [thread overview]
Message-ID: <4C75AFFC.5090601@zytor.com> (raw)
In-Reply-To: <20100825225036.GV4762@const.famille.thibault.fr>
On 08/25/2010 03:50 PM, Samuel Thibault wrote:
> H. Peter Anvin, le Wed 25 Aug 2010 14:19:55 -0700, a écrit :
>> At that point I'd almost prefer doing something like a BIOS signature
>> check if we can't do anything better.
>
> Well, there will be several versions of the BIOS signature, which the
> constructor is not likely to provide.
>
Then we'll gather them up, or something.
> Just to make sure there's no misunderstanding: it was never planned that
> this driver be loaded unless some manual intervention, like explicitly
> loadling the module or setting some parameter, so that if bad effects
> happen on the machine, the user can only get angry at himself for having
> loaded by hand a random module without reading the documentation that
> explicitly says (twice) it's only for a particular kind of hardware.
>
> I however now realize that I don't find a way to force a driver to be
> compiled only as a module. If there isn't, I guess we can just add
> a module parameter to enable/disable the driver, so that it won't be
> active by default even compiled-in?
There is, but that is hardly a reasonable solution.
What other forms of enumerable hardware is on this machine? PCI?
-hpa
next prev parent reply other threads:[~2010-08-26 0:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 9:49 [PATCH] x86: EuroBraille/Iris power off Shérab
2010-08-25 16:12 ` Andreas Mohr
2010-08-25 21:12 ` Sebastien Hinderer
2010-08-25 21:19 ` H. Peter Anvin
2010-08-25 22:50 ` Samuel Thibault
2010-08-26 0:06 ` H. Peter Anvin [this message]
2010-08-26 0:19 ` Samuel Thibault
2010-08-26 6:45 ` Sebastien Hinderer
2010-08-26 6:55 ` H. Peter Anvin
2010-08-26 7:09 ` Andreas Mohr
2010-08-26 9:29 ` Sebastien Hinderer
2010-08-26 18:11 ` Len Brown
2010-08-26 21:08 ` Shérab
2010-08-26 21:16 ` H. Peter Anvin
2010-08-27 17:35 ` Shérab
2010-08-27 18:49 ` H. Peter Anvin
2010-08-27 22:27 ` Shérab
2010-08-29 20:59 ` Shérab
2010-09-13 10:07 ` Shérab
2010-09-13 15:10 ` Valdis.Kletnieks
2010-09-13 15:22 ` Samuel Thibault
2010-09-13 16:06 ` H. Peter Anvin
2010-09-13 16:12 ` Samuel Thibault
2010-09-14 1:45 ` Valdis.Kletnieks
2010-09-14 5:16 ` Shérab
2010-09-20 8:22 ` Shérab
2010-09-26 17:54 ` Shérab
2010-10-10 16:22 ` Shérab
2010-11-13 19:22 ` Shérab
2010-09-13 15:25 ` Shérab
2010-09-13 15:48 ` H. Peter Anvin
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=4C75AFFC.5090601@zytor.com \
--to=hpa@zytor.com \
--cc=Samuel.Thibault@ens-lyon.org \
--cc=Sebastien.Hinderer@ens-lyon.org \
--cc=akpm@linux-foundation.org \
--cc=andi@lisas.de \
--cc=fweisbec@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).