From: Matthew Wilcox <matthew@wil.cx>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
waldi@debian.org, dannf@dannf.org,
debian-kernel@lists.debian.org, 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: Tue, 9 Sep 2008 12:46:48 -0600 [thread overview]
Message-ID: <20080909184648.GC2772@parisc-linux.org> (raw)
In-Reply-To: <20080909184204.B3F9B4E2A@hiauly1.hia.nrc.ca>
On Tue, Sep 09, 2008 at 02:42:03PM -0400, John David Anglin wrote:
> > Um, because the architecture doesn't have an i2c bus.
>
> Don't know about rtc but some PA-RISC models definitely have an i2c bus.
> I see this message on a A500-75 model:
>
> The support bus which connects the system processors, the Guardian Service
> Processor (GSP) and the Power Monitor or Platform Monitor may have become
> hung. (The support bus can be tested by issuing the GSP command "XD", and
> selecting the I2C access test).
This I2C bus is not acessible by the operating system (as far as I know).
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-09-09 18:46 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
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 [this message]
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=20080909184648.GC2772@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dannf@dannf.org \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=debian-hppa@lists.debian.org \
--cc=debian-kernel@lists.debian.org \
--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.