The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: viro@ZenIV.linux.org.uk
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Kconfig fix (GEN_RTC dependencies)
Date: Mon, 05 Sep 2005 18:51:41 -0700 (PDT)	[thread overview]
Message-ID: <20050905.185141.44096788.davem@davemloft.net> (raw)
In-Reply-To: <20050906005645.GQ5155@ZenIV.linux.org.uk>

From: viro@ZenIV.linux.org.uk
Date: Tue, 6 Sep 2005 01:56:45 +0100

> 	Yet another architecture not coverd by GEN_RTC - sparc64 never
> picked it until now and it doesn't have asm/rtc.h to go with it, so
> it wouldn't compile anyway (or have these ioctls in the user-visible
> headers, for that matter).
> 
> 	FWIW, I'm very tempted to introduce ARCH_HAS_GEN_RTC and have
> it set in arch/*/Kconfig for architectures that know what to do with this
> stuff - for something supposedly generic the list of architectures where
> it doesn't work is getting too long...
> 
> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

I'll add this patch to my sparc tree, thanks Al.

Admittedly, the whole RTC situation is quite a mess I have to
agree.

To make the problem worse, we have two sets of RTC ioctls
which userland makes use of on Sparc.  The older ones which
the SBUS RTC driver exported and supported, and the normal
ones the rest of the world uses.  Because the normal RTC driver
gets used as well, userland actually tries both ioctl sets.
Therefore, it probably would work to completely do away with
the SBUS RTC ioctl support, and only use the normal ones.

This would make using the generic RTC driver much easier, I
would think.

Anyways, I've added this to my sparc64 TODO list at:

	 http://vger.kernel.org/~davem/sparc64_todo.html

so that I can get to dealing with this at some point.

  reply	other threads:[~2005-09-06  1:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06  0:56 [PATCH] Kconfig fix (GEN_RTC dependencies) viro
2005-09-06  1:51 ` David S. Miller [this message]
2005-09-06  2:24   ` viro
2005-09-06 14:40     ` Maciej W. Rozycki
2005-09-06 17:48       ` Tom Rini
2005-09-07 18:06         ` Maciej W. Rozycki
2005-09-07 19:42           ` Tom Rini

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=20050905.185141.44096788.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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