From: Stas Sergeev <stsp@aknet.ru>
To: dbrownell@users.sourceforge.net
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [patch] provide rtc_cmos platform device
Date: Thu, 22 May 2008 23:05:02 +0400 [thread overview]
Message-ID: <4835C3DE.8070209@aknet.ru> (raw)
In-Reply-To: <20080521153223.e989cb88.akpm@linux-foundation.org>
Hello.
David, please CC me the replies.
David Brownell wrote:
> Well, "regression" is the wrong phrase. You've switched
> drivers (from the legacy RTC to the new one), so this is
> not the thing which worked for you before.
I am not sure how could that happen.
I am always just taking an old kernel
config and never change the options
that are not supposed to be changed.
Was the old RTC driver removed by any
chance?
>> This may also help running the
>> PNP-enabled kernel on an older PCs.
> As in, pre-PNP. That's pretty darn old!
But... I think they should still be
supported, unless it is too difficult.
> (1) On an ARM build (with no PNP configured):
OK, but unfortunately I can't help
with that. I won't touch any non-x86
arch code, so I'll simply go for
the #ifdef here, or someone else
should make the patch instead. :)
> You shouldn't define those symbols; the right values are already
> defined in <asm/mc146818rtc.h>. RTC_PORT(0) and RTC_PORT(1) are
> the symbolss to use; RTC_IRQ is already defined. All this stuff
> is used in the <asm-generic/rtc.h> code ...
OK, thanks.
I'll update the patch, in todo for
the week-end.
next prev parent reply other threads:[~2008-05-22 19:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 18:25 [patch] provide rtc_cmos platform device Stas Sergeev
2008-05-21 22:32 ` Andrew Morton
2008-05-22 19:05 ` Stas Sergeev [this message]
2008-05-22 19:56 ` David Brownell
2008-05-23 5:12 ` Stas Sergeev
2008-05-21 23:05 ` 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=4835C3DE.8070209@aknet.ru \
--to=stsp@aknet.ru \
--cc=akpm@linux-foundation.org \
--cc=dbrownell@users.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.