From: Jeff Garzik <jeff@garzik.org>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: discuss@x86-64.org, linux-input@atrey.karlin.mff.cuni.cz,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC] make PC Speaker driver work on x86-64
Date: Sat, 29 Apr 2006 16:36:07 -0400 [thread overview]
Message-ID: <4453CE37.8010705@garzik.org> (raw)
In-Reply-To: <200604291830.k3TIUA23009336@harpo.it.uu.se>
Mikael Pettersson wrote:
> I have a pair of Athlon64 machines that dual-boot 32-bit and
> 64-bit kernels. One annoying difference between the kernels
> is that the PC Speaker driver (CONFIG_INPUT_PCSPKR=y) only
> works in the 32-bit kernels. In the 64-bit kernels it remains
> inactive and doesn't even generate any boot-time initialisation
> or error messages.
>
> Today I debugged that issue, and found that the PC Speaker
> driver's ->probe() routine doesn't even get called in the
> 64-bit kernels. The reason for that is that the arch code
> apparently has to explictly add a "pcspkr" platform device
> in order for the driver core to call the ->probe() routine.
> arch/i386/kernel/setup.c unconditionally adds a "pcspkr"
> device, but the x86_64 kernel has no code at all related to
> the PC Speaker.
Wow, thanks.
I was wondering why my PC speaker didn't seem to work. And here I was,
blaming Fedora...
Jeff
next prev parent reply other threads:[~2006-04-29 20:36 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 [this message]
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
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=4453CE37.8010705@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=discuss@x86-64.org \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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.