From: David Brownell <david-b@pacbell.net>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: loosen dependancy on rtc cmos
Date: Wed, 14 Feb 2007 11:55:33 -0800 [thread overview]
Message-ID: <200702141155.33970.david-b@pacbell.net> (raw)
In-Reply-To: <20070214180915.GA6412@redhat.com>
On Wednesday 14 February 2007 10:09 am, Dave Jones wrote:
> This option is useful for all of the X86 subarchs afaik (and especially X86_GENERICARCH).
You're right ... _potentially_ useful, which is the same standard used
in most of the other cases. The "X86_PC" is debris from an early version
of this patch, which limited the code to cases where it was known to work.
The X86_PC hardware standard does standardize on this particular RTC, but
non-PC platforms can use it too.
I still need to resubmit the patch, for X86_PC, which defines the platform
device in the (common) case where PNPACPI isn't defined. Other X86 boards
would need something similar, based on what chips are wired to the CPU.
> Signed-off-by: Dave Jones <davej@redhat.com>
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
> --- linux-2.6.20.noarch/drivers/rtc/Kconfig~ 2007-02-14 13:07:07.000000000 -0500
> +++ linux-2.6.20.noarch/drivers/rtc/Kconfig 2007-02-14 13:07:13.000000000 -0500
> @@ -101,7 +101,7 @@ comment "RTC drivers"
>
> config RTC_DRV_CMOS
> tristate "PC-style 'CMOS' real time clock"
> - depends on RTC_CLASS && (X86_PC || ALPHA || ARM26 || ARM \
> + depends on RTC_CLASS && (X86 || ALPHA || ARM26 || ARM \
> || M32R || ATARI || POWERPC)
> help
> Say "yes" here to get direct support for the real time clock
>
> --
> http://www.codemonkey.org.uk
>
next prev parent reply other threads:[~2007-02-14 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 18:09 loosen dependancy on rtc cmos Dave Jones
2007-02-14 19:55 ` David Brownell [this message]
2007-02-14 23:20 ` Len Brown
2007-02-14 23:47 ` David Brownell
2007-02-16 4:38 ` Len Brown
2007-02-16 5:12 ` David Brownell
2007-02-17 0: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=200702141155.33970.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=davej@redhat.com \
--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