LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: rtc-linux@googlegroups.com
Cc: woodys@xandros.com, galak@kernel.crashing.org,
	LKML Kernel <linux-kernel@vger.kernel.org>,
	linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	rz@linux-m68k.org
Subject: Re: [rtc-linux] Re: state of GEN_RTC vs rtc subsystem
Date: Thu, 21 Feb 2008 01:14:25 +0100	[thread overview]
Message-ID: <20080221011425.2f8ad363@i1501.lan.towertech.it> (raw)
In-Reply-To: <47BC8F88.80502@xandros.com>

On Wed, 20 Feb 2008 15:37:28 -0500
woodys <woodys@xandros.com> wrote:

> On ARM genrtc has been arbitrary disabled in Kconfig circa 2.6.19 and 
> the change to rtc_cmos it is not 100% transparent (ARM Netwinder, Debian).
> If I want to use a current (Etch) hwclock binary - I need genrtc with 
> /dev/rtc at 10,135, however new rtc_cmos creates /dev/rtc0 at 254,0.
> As a result on new kernels hwclock claims that it is not able to access 
> hardware.
> 
> However upgrading the util-linux package will (sometime in the 
> "unstable" future) solve it, so it is not completely broken... Still, at 
> the moment - genrtc seems to be a better solution...

 Strange that it has been disabled, I used to keep an eye to avoid touching
 anything outside of drivers/rtc .

 the rtc subsystem creates the device dynamically, you shouldn't count
 on having 254,0. I would eventually ack a patch that adds
 /dev/rtc at 10,135 as an alias for /dev/rtc0.

 however the best solution would be to upgrade hwclock.


-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it


  reply	other threads:[~2008-02-21  0:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 16:11 Kumar Gala
2008-02-20 17:03 ` [rtc-linux] " Alessandro Zummo
2008-02-20 20:37   ` woodys
2008-02-21  0:14     ` Alessandro Zummo [this message]
2008-02-22  7:47   ` J.A. Magallón
2008-05-30 22:45   ` Geoff Levand
2008-06-02 22:27     ` Geoff Levand
2008-06-07  6:38       ` Rogério Brito
2008-06-07  9:46       ` [rtc-linux] " David Woodhouse
2008-02-21  9:26 ` Richard Zidlicky

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=20080221011425.2f8ad363@i1501.lan.towertech.it \
    --to=alessandro.zummo@towertech.it \
    --cc=galak@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=rtc-linux@googlegroups.com \
    --cc=rz@linux-m68k.org \
    --cc=woodys@xandros.com \
    --subject='Re: [rtc-linux] Re: state of GEN_RTC vs rtc subsystem' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).