Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Bastian Blank <waldi@debian.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
	debian-kernel@lists.debian.org
Cc: Parisc List <linux-parisc@vger.kernel.org>, debian-hppa@lists.debian.org
Subject: Re: Debian parisc config for 2.6.26 broke the real time clock
Date: Mon, 8 Sep 2008 18:37:04 +0200	[thread overview]
Message-ID: <20080908163703.GA3218@wavehammer.waldi.eu.org> (raw)
In-Reply-To: <1220713586.3430.14.camel@localhost.localdomain>

On Sat, Sep 06, 2008 at 10:06:26AM -0500, James Bottomley wrote:
> Parisc is a CONFIG_GEN_RTC architecture (we use the generic real time
> clock driver).

Well.

>                 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.

Yes. Most arches already needs it anyway.

> 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.

Apparently hppa uses its special rtc type.  I propose that you take a
look at drivers/rtc/rtc-ppc.c and write a wrapper rtc module.

>                                        I'd suggest checking the debian
> kernel configs against the in-tree default files to see if there are any
> other cockups like this.

If there are, this are bugs in the kernel themself. I'm no hppa
developer so I won't waste my time with such.

Bastian

-- 
Those who hate and fight must stop themselves -- otherwise it is not stopped.
		-- Spock, "Day of the Dove", stardate unknown

  parent reply	other threads:[~2008-09-08 16:37 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
2008-09-08 16:37 ` Bastian Blank [this message]
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=20080908163703.GA3218@wavehammer.waldi.eu.org \
    --to=waldi@debian.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=debian-hppa@lists.debian.org \
    --cc=debian-kernel@lists.debian.org \
    --cc=linux-parisc@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