From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: waldi@debian.org
Cc: Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: Debian parisc config for 2.6.26 broke the real time clock
Date: Mon, 08 Sep 2008 10:43:03 -0500 [thread overview]
Message-ID: <1220888583.8074.10.camel@localhost.localdomain> (raw)
In-Reply-To: <1220713586.3430.14.camel@localhost.localdomain>
On Sat, 2008-09-06 at 10:06 -0500, James Bottomley wrote:
> Parisc is a CONFIG_GEN_RTC architecture (we use the generic real time
> clock driver). Starting with 2.6.26, debian is now enabling
> CONFIG_RTC_CLASS (for platforms with specific RTC drivers) which
> disables CONFIG_GEN_RTC and means that hwclock (and ntp tracking) are
> broken on parisc with debian kernels 2.6.26 and above.
>
> All of the arch/parisc/config files get this right, so someone at debian
> must have screwed up somehow. The config option CONFIG_RTC_CLASS must
> be set to 'N' for all parisc systems. I'd suggest checking the debian
> kernel configs against the in-tree default files to see if there are any
> other cockups like this.
OK, I dug into this. The problem with debian is that CONFIG_RTC_CLASS
is set in the generic configuration and from 2.6.26 onwards
CONFIG_GEN_RTC is overridden by this (that's the reason we don't see it
on our local configs). I'm not entirely sure what the correct fix is.
It looks like GEN_RTC is being deprecated, so it might be to move to
RTC_CLASS. I think the best thing is for me to try to put an arch
override for RTC_CLASS and see what the reaction is.
In the meantime, you can get a working debian kernel here:
http://parisc-linux.org/~jejb/linux-image-2.6.26-1-parisc_2.6.26-4+b1_hppa.deb
James
next prev parent reply other threads:[~2008-09-08 15:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-06 15:06 Debian parisc config for 2.6.26 broke the real time clock James Bottomley
2008-09-08 15:43 ` James Bottomley [this message]
2008-09-08 16:37 ` Bastian Blank
2008-09-08 16:58 ` James Bottomley
2008-09-09 16:58 ` dann frazier
2008-09-09 17:38 ` Bastian Blank
2008-09-09 17:53 ` James Bottomley
2008-09-09 17:48 ` James Bottomley
2008-09-09 18:01 ` Bastian Blank
2008-09-09 18:12 ` James Bottomley
2008-09-09 18:29 ` Bastian Blank
2008-09-09 18:58 ` James Bottomley
2008-09-09 18:42 ` John David Anglin
2008-09-09 18:46 ` Matthew Wilcox
2008-09-09 19:20 ` John David Anglin
2008-09-09 19:35 ` Thibaut VARENE
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=1220888583.8074.10.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-parisc@vger.kernel.org \
--cc=waldi@debian.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.