From: David Brownell <david-b@pacbell.net>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: David Miller <davem@davemloft.net>,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org
Subject: Re: [PATCH] fix RTC_CLASS regression with PARISC
Date: Mon, 8 Sep 2008 16:32:25 -0700 [thread overview]
Message-ID: <200809081632.26166.david-b@pacbell.net> (raw)
In-Reply-To: <1220916186.8074.84.camel@localhost.localdomain>
On Monday 08 September 2008, James Bottomley wrote:
>=20
> > All the powerpc folks are doing is providing a dummy shim into the
> > RTC layer using their machine description vector, and not really us=
ing
> > the RTC layer drivers at all.
>=20
> But realistically that's all we need. =A0Our RTC is controlled by two
> calls into firmware: a get and a set; nothing else. =A0We don't have =
the
> docs to get at the clock without the firmware calls.
True for PARISC ... but not for PowerPC. Lots of PowerPC
system boards use off-the-shelf RTCs with more capabilities
than the machine description vector acknowledges.
- Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc"=
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: David Brownell <david-b@pacbell.net>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: David Miller <davem@davemloft.net>,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org
Subject: Re: [PATCH] fix RTC_CLASS regression with PARISC
Date: Mon, 8 Sep 2008 16:32:25 -0700 [thread overview]
Message-ID: <200809081632.26166.david-b@pacbell.net> (raw)
In-Reply-To: <1220916186.8074.84.camel@localhost.localdomain>
On Monday 08 September 2008, James Bottomley wrote:
>
> > All the powerpc folks are doing is providing a dummy shim into the
> > RTC layer using their machine description vector, and not really using
> > the RTC layer drivers at all.
>
> But realistically that's all we need. Our RTC is controlled by two
> calls into firmware: a get and a set; nothing else. We don't have the
> docs to get at the clock without the firmware calls.
True for PARISC ... but not for PowerPC. Lots of PowerPC
system boards use off-the-shelf RTCs with more capabilities
than the machine description vector acknowledges.
- Dave
next prev parent reply other threads:[~2008-09-08 23:32 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 15:53 [PATCH] fix RTC_CLASS regression with PARISC James Bottomley
2008-09-08 18:19 ` David Brownell
2008-09-08 18:39 ` James Bottomley
2008-09-08 19:13 ` David Brownell
2008-09-08 20:28 ` James Bottomley
2008-09-08 21:29 ` David Brownell
2008-09-08 21:29 ` David Brownell
2008-09-08 21:35 ` David Miller
2008-09-08 23:00 ` James Bottomley
2008-09-08 23:04 ` David Miller
2008-09-08 23:23 ` James Bottomley
2008-09-08 23:32 ` David Brownell [this message]
2008-09-08 23:32 ` David Brownell
2008-09-08 23:43 ` David Miller
2008-09-08 23:29 ` David Brownell
2008-09-08 23:44 ` David Miller
2008-09-09 0:55 ` David Brownell
2008-09-09 2:52 ` David Miller
2008-09-09 3:17 ` David Brownell
2008-09-09 3:17 ` David Brownell
2008-09-09 3:51 ` David Miller
2008-09-09 3:51 ` David Miller
2008-09-09 4:14 ` David Brownell
2008-09-09 4:14 ` David Brownell
2008-09-10 21:04 ` Andrew Morton
2008-09-10 21:09 ` Randy.Dunlap
2008-09-10 21:19 ` David Brownell
2008-09-10 21:19 ` David Brownell
2008-09-10 21:20 ` David Miller
2008-09-10 21:20 ` David Miller
2008-09-10 21:36 ` David Brownell
2008-09-10 21:36 ` David Brownell
2008-09-10 21:40 ` David Miller
2008-09-09 1:22 ` Paul Mackerras
2008-09-08 21:37 ` James Bottomley
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=200809081632.26166.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=torvalds@linux-foundation.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.