From: Clemens Koller <clemens.koller@anagramm•de>
To: Marc LeFevre <lfx@cypress•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: RTC woes
Date: Tue, 19 Feb 2008 23:30:54 +0100 [thread overview]
Message-ID: <47BB589E.4040201@anagramm.de> (raw)
In-Reply-To: <06cb01c87315$5dad6010$f30213ac@isd.cypress.com>
Marc LeFevre schrieb:
> I’m new to the list.
Welcome! :-)
> I have an e500-based embedded Linux system running
> a 2.6.22 kernel. I have a PCF8563T i2c based RTC chip attached to the
> PPC i2c bus. In my kernel config file I have selected
> CONFIG_RTC_INTF_DEV=y and CONFIG_RTC_DRV_PCF8563=y. I do a mknod for
> /dev/rtc as c 10 135 (standard Linux) and link /dev/rtc0 to it.
>
> When I boot, get the following message:
>
> drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
2.6.22.x and 2.6.23.x i2c rtc code was quite messy around PCF8563.
> 3) Does the PPC have some quirks regarding i2c operation that are
> at the root of this problem?
The RTC subsystem was improved quite a bit lately. Try 2.6.24' powerpc
architecture with a proper device tree instead. It works over here on
mpc8540 / mpc8548 whereas the older ones were just a waste of time.
Regards,
Clemens
prev parent reply other threads:[~2008-02-19 22:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 16:34 RTC woes Marc LeFevre
2008-02-19 22:30 ` Clemens Koller [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=47BB589E.4040201@anagramm.de \
--to=clemens.koller@anagramm$(echo .)de \
--cc=lfx@cypress$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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