From: Kay Sievers <kay.sievers@vrfy.org>
To: Dmitry Torokhov <dtor@insightbb.com>
Cc: Bill Nottingham <notting@redhat.com>,
Chuck Ebbert <cebbert@redhat.com>, Jeff Garzik <jeff@garzik.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>
Subject: Re: 2.6.22: pcspkr driver no longer loads automatically
Date: Sun, 04 Nov 2007 09:30:43 +0100 [thread overview]
Message-ID: <1194165043.2132.5.camel@lov.site> (raw)
In-Reply-To: <200711040120.12640.dtor@insightbb.com>
On Sun, 2007-11-04 at 01:20 -0400, Dmitry Torokhov wrote:
> On Wednesday 08 August 2007 15:32, Bill Nottingham wrote:
> > Kay Sievers (kay.sievers@vrfy.org) said:
> > > It doesn't have any aliases, so seems it was never autoloaded.
> >
> > It was - prior kernels loaded it via the uevent generated from
> > /devices/platform/pcspkr. Newer kernels seem to never actually
> > trigger a uevent from that (tested with a combination of
> > udevmonitor and 'udevtrigger --subsystem-match=platform'.)
> >
>
> The patch below should restore generation of uevents for pcspkr devices.
> Since devices are not created in pcspkr module but rather in arch setup
> code it is right (and safe) thing to do.
This is not needed. The global disablement of platform device creation
events has been reverted in 2.6.24, it broke more than pcsprkr, and
modules that should be auto-loaded just get an alias as usual:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=43cc71eed1250755986da4c0f9898f9a635cb3bf
Thanks,
Kay
prev parent reply other threads:[~2007-11-04 8:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 19:33 2.6.22: pcspkr driver no longer loads automatically Chuck Ebbert
2007-08-07 20:43 ` Jeff Garzik
2007-08-07 21:43 ` Chuck Ebbert
2007-08-07 22:23 ` Kay Sievers
2007-08-08 19:32 ` Bill Nottingham
2007-08-08 20:02 ` Kay Sievers
2007-08-08 22:22 ` Bill Nottingham
2007-08-08 22:39 ` Kay Sievers
2007-11-04 5:20 ` Dmitry Torokhov
2007-11-04 8:30 ` Kay Sievers [this message]
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=1194165043.2132.5.camel@lov.site \
--to=kay.sievers@vrfy.org \
--cc=cebbert@redhat.com \
--cc=dtor@insightbb.com \
--cc=greg@kroah.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=notting@redhat.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