From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Cc: david-b@pacbell.net
Subject: Re: RTC_DRV_CMOS can break userspace interface
Date: Fri, 1 Jun 2007 13:54:23 +0100 [thread overview]
Message-ID: <20070601125422.GA12204@srcf.ucam.org> (raw)
In-Reply-To: <20070601074606.GA6060@dose.home.local>
On Fri, Jun 01, 2007 at 09:46:06AM +0200, Tino Keitel wrote:
> Yes, you are right. I think this issue should be covered by Kconfig.
>
> However:
>
> $ cat wakealarm
> cat: wakealarm: Input/output error
>
> It worked with /proc/acpi/alarm before.
Can you do
for i in /sys/bus/pnp/devices/*; do if [ "$(cat $i/id)" = PNP0b00 ];
then cat $i/resources; echo options; cat $i/options; fi; done
and provide the output? It sounds like you have the same problem I do,
that is that you have no IRQ listed in the PNP table.
Though, actually, on reading the code:
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...
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2007-06-01 12:54 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 [this message]
2007-06-01 17:11 ` David Brownell
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=20070601125422.GA12204@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.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