All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Koller <clemens.koller@anagramm.de>
To: Bartlomiej Sieka <tur@semihalf.com>
Cc: Alessandro Zummo <alessandro.zummo@towertech.it>,
	rtc-linux@googlegroups.com, linuxppc-embedded@ozlabs.org
Subject: Re: [rtc-linux] Re: DS1337 RTC on I2C broken.
Date: Mon, 03 Dec 2007 17:38:05 +0100	[thread overview]
Message-ID: <475430ED.1080204@anagramm.de> (raw)
In-Reply-To: <475429DA.9060100@semihalf.com>

Hi, Bartlomiej!

Bartlomiej Sieka schrieb:
 > Do you have rtc node in your dts file (I'm assuming arch/powerpc
 > situation)? If not, you'll have to add it - for example similarly to
 > what's being done in the attached patch (68 is the I2C address of the
 > RTC chip - a DS1339 in my case).

Thank you also for your hint... that was indeed the problem here.
Simple but not really obvious.

Is it possible to have a maximum generic .dts configuration where the
kernel is told to include any device it propably finds?

I guess the failing reset since 2.6.22 is also just an entry in
my .dts... ?

Regards,
-- 
Clemens Koller
__________________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Straße 45/1
Linhof Werksgelände
D-81379 München
Tel.089-741518-50
Fax 089-741518-19
http://www.anagramm-technology.com

  reply	other threads:[~2007-12-03 16:38 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
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 [this message]
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=475430ED.1080204@anagramm.de \
    --to=clemens.koller@anagramm.de \
    --cc=alessandro.zummo@towertech.it \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=rtc-linux@googlegroups.com \
    --cc=tur@semihalf.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.