From: Fabio Giovagnini <fgiovag@tin.it>
To: linuxsh-dev@lists.sourceforge.net
Cc: "Linux-SH (m17n)" <linux-sh@m17n.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RTC (real time clock) question about sh4 7760
Date: Thu, 7 Oct 2004 10:29:56 +0000 [thread overview]
Message-ID: <200410071029.56911.fgiovag@tin.it> (raw)
In-Reply-To: <41642CBA.7030709@redhat.com>
Hi All,
I'm porting linux sh onLogic PD lsh7760-10 board.
The sh4 7760 doesn't have an on chip RTC (while other sh4 processors does),
and the board I'm working on seems to have no RTC (maybe I2C bus connected).
So in such application I think there is no RTC available; what is the best way
to describe this? I think to write rtc.c rtc.h modules and write the related
funcions doing nothing.
Is it correct?
Thanks a lot
Fabio
prev parent reply other threads:[~2004-10-07 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 16:37 [PATCH] RFC. User space backtrace on segv Alex Bennee
2004-10-06 16:39 ` Alex Bennee
2004-10-06 17:17 ` Arnd Bergmann
2004-10-06 17:34 ` Neil Horman
2004-10-07 9:48 ` P
2004-10-07 10:29 ` Fabio Giovagnini [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=200410071029.56911.fgiovag@tin.it \
--to=fgiovag@tin.it \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@m17n.org \
--cc=linuxsh-dev@lists.sourceforge.net \
/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