From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: rtc-linux@googlegroups.com
Cc: david-b@pacbell.net, rol@as2917.net,
"'Adrian Bunk'" <bunk@stusta.de>,
linux-kernel@vger.kernel.org, a.zummo@towertech.it
Subject: Re: [rtc-linux] Re: 2.6.21-rc2 : Oops in rtc_cmos...
Date: Tue, 6 Mar 2007 21:50:23 +0100 [thread overview]
Message-ID: <20070306215023.1ec0a4d7@inspiron> (raw)
In-Reply-To: <200703061132.29331.david-b@pacbell.net>
On Tue, 6 Mar 2007 11:32:28 -0800
David Brownell <david-b@pacbell.net> wrote:
> > on then... My dmesg says, related to rtc :
> >
> > ...
> > rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
>
> I think the RTC core shouldn't emit this message; I'll send
> a patch. It's just confusing on error paths; and on success
> paths it's less informative than a message from the driver
> itself could be.
I would like a way to have a common "welcome" message among
all the drivers. Please take this into account if you want
to send a patch ;)
> > What does this all mean ? I thought an RTC Cmos was always there on a
> > standard PC motherboard... (that's why I had activated the option in the
> > first time).
>
> You enabled CONFIG_RTC (under char drivers, "Enhanced Real Time Clock Support")
> so that driver has claimed the CMOS RTC instead of "rtc-cmos.c". Disable it.
> Then you'll be able to use this driver with no little surprises.
maybe we should consider this in the Kconfig.
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
next prev parent reply other threads:[~2007-03-06 20:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 18:43 2.6.21-rc2 : Oops in rtc_cmos Paul Rolland
2007-03-04 23:48 ` Adrian Bunk
2007-03-06 7:29 ` Paul Rolland
2007-03-06 19:32 ` David Brownell
2007-03-06 20:50 ` Alessandro Zummo [this message]
2007-03-06 22:23 ` [rtc-linux] " David Brownell
2007-03-07 4:42 ` Paul Rolland
2007-03-07 5:26 ` David Brownell
2007-03-07 8:16 ` Alessandro Zummo
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=20070306215023.1ec0a4d7@inspiron \
--to=alessandro.zummo@towertech.it \
--cc=a.zummo@towertech.it \
--cc=bunk@stusta.de \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rol@as2917.net \
--cc=rtc-linux@googlegroups.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