From: Kay Sievers <kay.sievers@vrfy.org>
To: Bill Nottingham <notting@redhat.com>
Cc: Chuck Ebbert <cebbert@redhat.com>, Jeff Garzik <jeff@garzik.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Dmitry Torokhov <dtor@insightbb.com>, Greg KH <greg@kroah.com>
Subject: Re: 2.6.22: pcspkr driver no longer loads automatically
Date: Wed, 08 Aug 2007 22:02:07 +0200 [thread overview]
Message-ID: <1186603327.3584.12.camel@lov.localdomain> (raw)
In-Reply-To: <20070808193220.GB5001@nostromo.devel.redhat.com>
On Wed, 2007-08-08 at 15:32 -0400, 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'.)
Ah, ok, makes sense. Yeah, that weird "platform devices loads itself by
the name" thing got disabled in the platform subsystem. It caused
modprobe loops for other devices.
The whole idea of issuing MODALIAS with plain module names instead of
aliases can't really work, but the platform maintainer didn't like to
use the usual aliases and the matches in the modules, for a reason I
didn't understand while we talked about the problem last time.
Kay
next prev parent reply other threads:[~2007-08-08 19:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 19:33 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 [this message]
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
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=1186603327.3584.12.camel@lov.localdomain \
--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
all inboxes | Powered by JetHome®