From: Alan <alan@lxorguk.ukuu.org.uk>
To: Arkadiusz Miskiewicz <arekm@maven.pl>
Cc: Ben Collins <ben.collins@ubuntu.com>,
linux-kernel@vger.kernel.org, Eric Piel <eric.piel@tremplin-utc>
Subject: Re: [RFC] Include ACPI DSDT from INITRD patch into mainline
Date: Fri, 1 Dec 2006 22:17:45 +0000 [thread overview]
Message-ID: <20061201221745.7bea6e72@localhost.localdomain> (raw)
In-Reply-To: <200612012301.20086.arekm@maven.pl>
On Fri, 1 Dec 2006 23:01:20 +0100
Arkadiusz Miskiewicz <arekm@maven.pl> wrote:
> Acer notebook users here dump DSDT from their own machine, fix it and then
> load via initrd.
Under EU law thats two copies without permission and modification without
permission of the rights holder....
> > and if they do does it have to be
> > an ugly hack in the mainstream kernel.
>
> Can it be done without hacks somehow (in the way that adding fixed DSDT is
> easy for user)?
Arjan - can you explain the linking dsdt one in more detail ?
next prev parent reply other threads:[~2006-12-01 22:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 18:36 [RFC] Include ACPI DSDT from INITRD patch into mainline Ben Collins
2006-12-01 18:56 ` Alan
2006-12-01 19:35 ` Ben Collins
2006-12-01 19:45 ` Arjan van de Ven
2006-12-01 21:01 ` Ben Collins
2006-12-01 21:49 ` Arjan van de Ven
2006-12-01 22:35 ` Ben Collins
2006-12-02 7:45 ` Arjan van de Ven
2006-12-04 10:58 ` Stefan Seyfried
2006-12-01 19:53 ` Alan
2006-12-01 20:58 ` Ben Collins
2006-12-01 21:55 ` Alan
2006-12-01 22:01 ` Arkadiusz Miskiewicz
2006-12-01 22:17 ` Alan [this message]
2006-12-02 10:28 ` Arjan van de Ven
2006-12-02 12:50 ` Acer smart battery (was Re: [RFC] Include ACPI DSDT from INITRD patch into mainline) Pavel Machek
2006-12-02 17:34 ` Arkadiusz Miskiewicz
2006-12-02 18:58 ` Pavel Machek
2006-12-02 0:21 ` [RFC] Include ACPI DSDT from INITRD patch into mainline Dave Jones
2006-12-02 10:25 ` Arjan van de Ven
2006-12-02 10:30 ` Arjan van de Ven
2006-12-02 11:11 ` Jan Engelhardt
2006-12-02 16:15 ` Sergey Vlasov
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=20061201221745.7bea6e72@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=arekm@maven.pl \
--cc=ben.collins@ubuntu.com \
--cc=eric.piel@tremplin-utc \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.