On Tue, 2008-09-09 at 20:29 +0200, Bastian Blank wrote:
> On Tue, Sep 09, 2008 at 01:12:01PM -0500, James Bottomley wrote:
> > 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.
> 
> Well, it have USB, so can also power usb-to-i2c adapters. And there is
> even the rtc test module.

Um you mean i2c_tiny_usb?  It doesn't drive any supported hardware ...
you have to build the connection yourself.  Plus only the latest revs of
PA actually supported USB ...

> Which "don't work" do you refer to?
> - Does not work because there is no binding to the hardware.
> - Does not work because a fundamental problem in the whole subsystem.
> (- Does not work because ...)

Well, like most real world systems, you can artificially construct
pathological failure cases.  If I were you I'd stop looking for the
heath robinson ones.  No-one in their right mind is going to construct a
USB to I2C interface for the purpose of running and I2C RTC; the set of
users is clearly empty.

The way you would get an external RTC is via a more credible interface
like PCI (or EISA/ISA) is from a watchdog card ... however, no-one's
apparently written a RTC interface for any of those yet.

James



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to