From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] smbus RTC as misc device
Date: Thu, 16 Jun 2005 19:47:09 +0000 [thread overview]
Message-ID: <20050616194558.402b7253.khali@linux-fr.org> (raw)
Hi Olav,
Sorry for the delay.
> I hope this is the right list for my question. If not,
> please point me to a better list.
>
> Sometime at 2.6.8-2.6.9 kernel I needed a driver for the
> m41t11 RTC smbus chip. As there was none in the kernel at
> that time, I wrote it myself and made it available for user
> space as a misc device /dev/rtc (character dev 10 135). This
> way unmodified hwclock could access it.
>
> Now I noticed that latest kernels already contain the
> m41t00.c, which may well be able to drive my m41t11 RTC
> unmodified. However, it does not make the device available
> through /dev/rtc. Neither do that other few i2c RTCs
> currently in the kernel. They all seem to define their own
> ioctls each.
>
> What about making i2c RTCs available through /dev/rtc
> supporting its ioctls? If this would be OK then I can
> propose a patch for m41t00.c.
You are probably right. There have been quite a few discussions lately
about how to standardize the kernel interface to RTC drivers, the same
question may hold for the user-space interface.
However, this is neither related to hardware monitoring, nor to i2c, so
there's not much advice we can give to you - it's something we don't
know anything about ourselves. Better try to contact the various authors
of RTC drivers and/or the LKML, and see what they think about the idea.
--
Jean Delvare
next reply other threads:[~2005-06-16 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 19:47 Jean Delvare [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-20 10:24 [lm-sensors] smbus RTC as misc device Olav Kongas
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=20050616194558.402b7253.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=lm-sensors@vger.kernel.org \
/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.