Linux PARISC architecture development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Bastian Blank <waldi@debian.org>
Cc: dann frazier <dannf@dannf.org>,
	debian-kernel@lists.debian.org,
	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: Tue, 09 Sep 2008 13:12:01 -0500	[thread overview]
Message-ID: <1220983921.3334.36.camel@localhost.localdomain> (raw)
In-Reply-To: <20080909180127.GA2712@wavehammer.waldi.eu.org>

On Tue, 2008-09-09 at 20:01 +0200, Bastian Blank wrote:
> On Tue, Sep 09, 2008 at 12:48:35PM -0500, James Bottomley wrote:
> > They certainly have to be inessential to the parisc ABI ... they don't
> > work if anything's actually trying to use them.
> 
> Really? Which sort of "don't work" is this? Why should a I2C rtc device
> (some dallas chip) not work?

Um, because the architecture doesn't have an i2c bus.

James



  reply	other threads:[~2008-09-09 18:12 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 [this message]
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=1220983921.3334.36.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=dannf@dannf.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox