From: Len Brown <lenb@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Eric Piel <Eric.Piel@tremplin-utc.net>,
Tilman Schmidt <tilman@imap.cc>,
Dave Hansen <haveblue@us.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Thomas Renninger <trenn@suse.de>,
Christoph Hellwig <hch@infradead.org>,
Markus Gaugusch <dsdt@gaugusch.at>,
linux-acpi@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
Arjan van de Ven <arjanv@redhat.com>
Subject: Re: [2.6.25-rc5-mm1] BUG: spinlock bad magic early during boot
Date: Mon, 17 Mar 2008 13:59:30 -0400 [thread overview]
Message-ID: <200803171359.31298.lenb@kernel.org> (raw)
In-Reply-To: <alpine.LFD.1.00.0803151315250.3020@woody.linux-foundation.org>
> For things like DVD install images, you'd quite possibly want to have a
> few known-workaround DSDT images with the installer, and just say "ok, we
> want to fix up this ACPI crap in order to get working suspend/resume" kind
> of thing.
For a Linux distro to ship DSDT override images, they'd have to
have some licensing & support arrangement with the OEM
who actually owns that BIOS code.
While this wouldn't defy any laws of physics, it doesn't
look compatible with current industry business practices.
OEMs are more likely to simply ship a BIOS update ISO.
-Len
next prev parent reply other threads:[~2008-03-17 18:00 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080311011434.ad8c8d7d.akpm@linux-foundation.org>
2008-03-12 1:14 ` 2.6.25-rc5-mm1 Dave Young
[not found] ` <47D87238.8080305@imap.cc>
[not found] ` <20080313183439.GA12798@suse.de>
2008-03-13 19:57 ` [2.6.25-rc5-mm1] WARNING: at drivers/base/sys.c:173 Dave Jones
[not found] ` <20080313195656.GA32463@codemonkey.org.uk>
2008-03-14 0:01 ` Tilman Schmidt
2008-03-14 0:44 ` Dave Jones
2008-03-14 0:57 ` Zhao Yakui
2008-03-14 9:58 ` Tilman Schmidt
2008-03-15 12:16 ` Tilman Schmidt
[not found] ` <47D86D43.2060108@imap.cc>
[not found] ` <1205441216.4971.65.camel@nimitz.home.sr71.net>
[not found] ` <47D9C853.3040701@imap.cc>
[not found] ` <1205517802.12763.18.camel@nimitz.home.sr71.net>
2008-03-14 20:06 ` [2.6.25-rc5-mm1] BUG: spinlock bad magic early during boot Dave Hansen
2008-03-14 20:20 ` Linus Torvalds
2008-03-14 20:51 ` Eric Piel
2008-03-14 21:35 ` Dave Hansen
2008-03-14 22:50 ` Eric Piel
2008-03-14 23:29 ` Dave Hansen
2008-03-15 12:47 ` Tilman Schmidt
2008-03-15 19:21 ` Linus Torvalds
2008-03-15 19:42 ` Éric Piel
2008-03-15 20:19 ` Linus Torvalds
2008-03-16 0:15 ` Éric Piel
2008-03-17 17:27 ` Len Brown
[not found] ` <1205858252.21619.233.camel@queen.suse.de>
2008-03-18 20:32 ` Len Brown
2008-03-20 14:28 ` Thomas Renninger
2008-03-17 17:59 ` Len Brown [this message]
2008-03-21 13:17 ` Pavel Machek
2008-03-23 16:00 ` Dave Hansen
2008-03-24 16:03 ` Pavel Machek
2008-03-24 17:05 ` Eric Piel
2008-03-24 17:19 ` Pavel Machek
2008-03-24 17:23 ` Dave Hansen
2008-03-27 9:23 ` Helge Hafting
2008-03-17 18:05 ` Len Brown
2008-03-16 20:11 ` Dave Hansen
2008-03-17 12:23 ` Peter Zijlstra
2008-03-19 23:50 ` Tilman Schmidt
2008-03-17 17:48 ` Len Brown
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=200803171359.31298.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=Eric.Piel@tremplin-utc.net \
--cc=akpm@linux-foundation.org \
--cc=arjanv@redhat.com \
--cc=dsdt@gaugusch.at \
--cc=haveblue@us.ibm.com \
--cc=hch@infradead.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tilman@imap.cc \
--cc=torvalds@linux-foundation.org \
--cc=trenn@suse.de \
--cc=viro@zeniv.linux.org.uk \
/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