From: "Hanno Böck" <mail@hboeck.de>
To: torvalds@osdl.org, Andrew Morton <akpm@osdl.org>,
"Brown, Len" <len.brown@intel.com>
Cc: acpi-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
Karol Kozimor <sziwan@hell.org.pl>,
Christian Aichinger <Greek0@gmx.net>
Subject: asus_acpi still broken on Samsung P30/P35
Date: Wed, 21 Dec 2005 16:11:49 +0100 [thread overview]
Message-ID: <200512211611.51977.mail@hboeck.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
Hi,
Since several kernel-versions now the asus_acpi module is broken on several
Samsung notebooks, it causes an oops when loading and a kernelpanic when
compiled into the kernel.
This is known for ages. There was a patch by Karol Kozimor shortly after the
bug became public that was ignored.
The code was changed so the patch failed. Christian Aichinger again made a
patch. It was ignored as well.
Now, finally the patch is in the mm-source, I asked Andrew Morton to push it
to Linus so 2.6.15 will be fixed, Andrew said this is up to Len Brown. No
Reply from him.
Now it seems that 2.6.15 is going to be released soon, the patch still has not
made it into linus tree.
This is not "some minor issue", this completely breaks the usage of current
vanilla-kernels on certain Hardware. Can please, please, please anyone in the
position to do this take care that this patch get's accepted before 2.6.15?
The patch is available inside mm-sources or here:
http://www.int21.de/samsung/p30-2.6.14.diff
If I should send it to anyone else or if there's anything I can do to help
fixing this, I'm glad to help.
cu,
--
Hanno Böck Blog: http://www.hboeck.de/
GPG: 3DBD3B20 Jabber: jabber@hboeck.de
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-12-21 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 15:11 Hanno Böck [this message]
2005-12-21 18:37 ` asus_acpi still broken on Samsung P30/P35 Linus Torvalds
2005-12-21 19:22 ` [ACPI] " Carl-Daniel Hailfinger
2005-12-21 19:06 Brown, Len
2005-12-22 10:53 ` Karol Kozimor
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=200512211611.51977.mail@hboeck.de \
--to=mail@hboeck.de \
--cc=Greek0@gmx.net \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sziwan@hell.org.pl \
--cc=torvalds@osdl.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).