From: Andi Kleen <ak@suse.de>
To: matthieu castet <castet.matthieu@free.fr>
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: [discuss] Re: [RFC] make PC Speaker driver work on x86-64
Date: Tue, 2 May 2006 22:35:09 +0200 [thread overview]
Message-ID: <200605022235.09381.ak@suse.de> (raw)
In-Reply-To: <4457C228.9050209@free.fr>
On Tuesday 02 May 2006 22:33, matthieu castet wrote:
> Andi Kleen wrote:
>
> > Does it work?
> >
> of course (at least on x86) !
>
> > Also I have no idea if all x86 systems report the PC speaker in ACPI - a small
> > survey of that would be probably a good idea. I guess just most of them reporting it would be
> > reasonable.
> That's why I keep the platform driver :
> the logic is try with ACPI in order to discover if there is a speaker.
> If we failed, let's try the platform driver.
Ok - you mean just keeping the old code for that as fallback That makes sense.
> Matthieu
>
> PS : even system without ACPI should report the speaker with pnpbios.
PNP BIOS doesn't work on 64bit.
-Andi
next prev parent reply other threads:[~2006-05-02 20:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-29 18:30 [RFC] make PC Speaker driver work on x86-64 Mikael Pettersson
2006-04-29 20:36 ` Jeff Garzik
2006-04-29 21:00 ` Matthieu CASTET
2006-04-30 8:50 ` [discuss] " Andi Kleen
2006-04-30 8:50 ` Andi Kleen
2006-05-02 17:37 ` matthieu castet
2006-05-02 17:50 ` Andi Kleen
2006-05-02 17:50 ` Andi Kleen
2006-05-02 20:33 ` matthieu castet
2006-05-02 20:35 ` Andi Kleen [this message]
2006-05-02 20:54 ` Andi Kleen
2006-04-30 8:46 ` [discuss] " Andi Kleen
2006-04-30 14:32 ` Goswin von Brederlow
2006-04-30 16:29 ` Alistair John Strachan
2006-05-01 7:09 ` Jan Engelhardt
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=200605022235.09381.ak@suse.de \
--to=ak@suse.de \
--cc=castet.matthieu@free.fr \
--cc=discuss@x86-64.org \
--cc=linux-acpi@vger.kernel.org \
--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.