From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: PowerPC dev list <Linuxppc-dev@ozlabs.org>
Subject: Re: pcspkr device, pnpPNP,100
Date: Mon, 12 Nov 2007 12:07:26 +1100 [thread overview]
Message-ID: <1194829646.18185.8.camel@pasglop> (raw)
In-Reply-To: <9e4733910711111618l5190dee3jd8e0aa8f9b78ebf4@mail.gmail.com>
On Sun, 2007-11-11 at 19:18 -0500, Jon Smirl wrote:
> Using this scheme, which platforms should select the pcspkr hardware?
Run a poll :-) I suppose at least chrp/prep/pegasos
Ben.
next prev parent reply other threads:[~2007-11-12 1:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 23:35 pcspkr device, pnpPNP,100 Jon Smirl
2007-11-12 0:03 ` Benjamin Herrenschmidt
2007-11-12 0:07 ` Jon Smirl
2007-11-12 0:09 ` Benjamin Herrenschmidt
2007-11-12 0:18 ` Jon Smirl
2007-11-12 1:07 ` Benjamin Herrenschmidt [this message]
2007-11-12 10:48 ` Geert Uytterhoeven
2007-11-12 13:51 ` Jon Smirl
2007-11-12 13:57 ` Geert Uytterhoeven
2007-11-12 14:50 ` Gerhard Pircher
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=1194829646.18185.8.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Linuxppc-dev@ozlabs.org \
--cc=jonsmirl@gmail.com \
/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).