From: David Brownell <david-b@pacbell.net>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: RTC_DRV_CMOS can break userspace interface
Date: Fri, 1 Jun 2007 10:11:44 -0700 [thread overview]
Message-ID: <200706011011.44607.david-b@pacbell.net> (raw)
In-Reply-To: <20070601125422.GA12204@srcf.ucam.org>
On Friday 01 June 2007, Matthew Garrett wrote:
> The code for checking for a platform device only gets included if
> CONFIG_PNP isn't set! David, surely this should be a runtime thing
> rather than a compile-time one? Right now building a kernel with PNP
> support will break horribly if it's then run on a non-PNP system...
Maybe it should be a runtime thing. But then, on x86 there's
nothing to create the platform device for this driver either...
I had posted code to create that platform device at one point,
adjacent to what creates the pcspeaker device, but after ACPI
changed to require PNPACPI it wasn't needed on any system I
could test with. There are probably a bunch of platform_device
nodes that should be created automagically on old PNP-less PCs.
- Dave
next prev parent reply other threads:[~2007-06-01 17:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8pwhX-46n-3@gated-at.bofh.it>
[not found] ` <8pCQo-5QL-7@gated-at.bofh.it>
[not found] ` <87abvogbdp.fsf@buer.dfakt.de>
2007-05-28 21:06 ` RTC_DRV_CMOS can break userspace interface David Brownell
2007-05-31 4:32 ` Tino Keitel
2007-05-31 10:26 ` Matthew Garrett
2007-06-01 7:46 ` Tino Keitel
2007-06-01 12:54 ` Matthew Garrett
2007-06-01 17:11 ` David Brownell [this message]
2007-06-04 9:35 ` Tino Keitel
2007-06-04 12:14 ` Matthew Garrett
2007-06-12 18:17 ` Tino Keitel
2007-05-27 19:03 Matthew Garrett
2007-05-27 23:39 ` Matthew Garrett
2007-05-28 0:38 ` Matthew Garrett
2007-05-28 1:44 ` David Brownell
2007-05-28 2:16 ` Matthew Garrett
2007-05-28 1:36 ` David Brownell
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=200706011011.44607.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox