From: James Chapman <jchapman@katalix.com>
To: David Brownell <david-b@pacbell.net>
Cc: Alessandro Zummo <alessandro.zummo@towertech.it>,
linux-kernel@vger.kernel.org,
Ladislav Michl <ladis@linux-mips.org>,
eibach@gdsys.de, stieler@gdsys.de,
Jean Delvare <khali@linux-fr.org>,
Bill Gatliff <bgat@billgatliff.com>
Subject: Re: rtc-ds1307 driver (especially for DS1337, DS1339)
Date: Mon, 04 Dec 2006 16:02:50 +0000 [thread overview]
Message-ID: <457446AA.9050001@katalix.com> (raw)
In-Reply-To: <200612021013.50425.david-b@pacbell.net>
I don't have access to my ds1337 hardware right now (working away from
my office). Is someone else able to test this?
--
James Chapman
Katalix Systems Ltd
http://www.katalix.com
Catalysts for your Embedded Linux software development
David Brownell wrote:
> On Saturday 02 December 2006 5:55 am, Alessandro Zummo wrote:
>
>> Hello,
>>
>> given the recent patch for ds1337 initialization (drivers/i2c/chips),
>> I would like to ask owners of DS1307, DS1337, DS1338, DS1339, DS1340, ST M41T00
>> to give a try the rtc-ds1307 driver (drivers/rtc).
>>
>> I need to be sure that it works (and correctly initializes)
>> all the chips that claims to support.
>
>
> Unless it's broken _recently_ we already have confirmation that rtc-1307
> works for DS1307 and M41T00, so it's the other chips that would be most
> interesting ...
>
>
>
>> Jean would be very happy if we can remove drivers from
>> i2c/chips ;)
>
>
> I think the ds1337.c driver could vanish if we had confirmation that
> the ds1307 driver also works on the DS1337 and DS1339 ... so, special
> thanks if you can confirm it with those chips. Chip docs say they
> are compatible, so far as the driver is concerned.
>
> - Dave
>
prev parent reply other threads:[~2006-12-04 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 13:55 rtc-ds1307 driver Alessandro Zummo
2006-12-02 18:13 ` rtc-ds1307 driver (especially for DS1337, DS1339) David Brownell
2006-12-04 16:02 ` James Chapman [this message]
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=457446AA.9050001@katalix.com \
--to=jchapman@katalix.com \
--cc=alessandro.zummo@towertech.it \
--cc=bgat@billgatliff.com \
--cc=david-b@pacbell.net \
--cc=eibach@gdsys.de \
--cc=khali@linux-fr.org \
--cc=ladis@linux-mips.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stieler@gdsys.de \
/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