From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: Clemens Koller <clemens.koller@anagramm.de>
Cc: rtc-linux@googlegroups.com, linuxppc-embedded@ozlabs.org
Subject: Re: DS1337 RTC on I2C broken.
Date: Wed, 28 Nov 2007 19:43:21 +0100 [thread overview]
Message-ID: <20071128194321.0804b3aa@i1501.lan.towertech.it> (raw)
In-Reply-To: <474DB27C.7020909@anagramm.de>
On Wed, 28 Nov 2007 19:25:00 +0100
Clemens Koller <clemens.koller@anagramm.de> wrote:
> Well, as already mentioned, I have problems to get my DS1337 RTC on I2C
> on my MPC8540(ads like) PowerPC working properly on
> latest 2.6.24-rc2-ge6a5c27f kernels. A paulus.git 2.6.21-rc5-g9a5ee4cc
> as well as a 2.6.22-rc6-gb75ae860 is working fine.
> (mainstream's console is broken, so cannot test these, yet.)
>
>
> My guess is that the new rtc-lib's RTC_DRV_DS1307 support is still broken
> and it also breaks the deprecated SENSORS_DS1337. :-(
mmm. I've been told it should work ;)
> Here is a snippet from my .config which is similar among my kernels.
> CONFIG_GEN_RTC=y
this one must be deselected.
> CONFIG_SENSORS_DS1337=y
> CONFIG_SENSORS_DS1374=y
ditto.
> DEV: registering device: ID = '0-0068'
> bus i2c: add device 0-0068
> bound device '0-0068' to driver 'ds1337'
maybe the wrong driver is kicking in here.
the fact that there is no rtc class
related output in dmesg should and that
there is no /dev/rtc0 could be a sign that the whole class
is not going in.
do you have full dmesg?
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
next prev parent reply other threads:[~2007-11-28 18:51 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 18:25 DS1337 RTC on I2C broken Clemens Koller
2007-11-28 18:43 ` Alessandro Zummo [this message]
2007-11-28 19:20 ` Clemens Koller
2007-11-28 19:36 ` Clemens Koller
2007-11-28 20:34 ` [rtc-linux] " Alessandro Zummo
2007-11-29 11:24 ` Clemens Koller
2007-11-29 11:34 ` raul.moreno
2007-11-29 12:43 ` Clemens Koller
2007-11-29 20:03 ` Clemens Koller
2007-11-29 20:19 ` Alessandro Zummo
2007-11-30 11:04 ` Clemens Koller
2007-11-30 11:20 ` [rtc-linux] " Alessandro Zummo
2007-11-30 14:12 ` Clemens Koller
2007-12-01 12:24 ` Alessandro Zummo
2007-12-02 20:25 ` Olof Johansson
2007-11-30 18:12 ` Clemens Koller
2007-12-01 12:16 ` Alessandro Zummo
2007-12-03 15:14 ` Clemens Koller
2007-12-03 16:07 ` Bartlomiej Sieka
2007-12-03 16:38 ` Clemens Koller
2007-12-03 16:09 ` solved: " Clemens Koller
2007-12-03 16:48 ` Scott Wood
2007-12-03 17:41 ` OT: " Clemens Koller
2007-12-03 18:07 ` Scott Wood
2007-12-03 19:35 ` Clemens Koller
2007-12-03 20:05 ` Grant Likely
2007-12-03 20:46 ` Scott Wood
2007-12-04 11:42 ` Clemens Koller
2007-12-04 13:08 ` Scott Wood
2007-12-04 15:32 ` Clemens Koller
2007-12-04 16:08 ` Scott Wood
2007-12-05 10:27 ` Clemens Koller
2007-12-04 17:19 ` Jon Smirl
2007-12-05 10:30 ` Clemens Koller
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=20071128194321.0804b3aa@i1501.lan.towertech.it \
--to=alessandro.zummo@towertech.it \
--cc=clemens.koller@anagramm.de \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rtc-linux@googlegroups.com \
/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.