lkml.org 
[lkml]   [2008]   [Jun]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [rtc-linux] Re: [Bug 10866] /dev/rtc was missing until I disabled CONFIG_RTC_CLASS
On Sat, 14 Jun 2008 14:18:06 +0300
Adrian Bunk <bunk@kernel.org> wrote:

>
> If Lior's problem was due to something like CONFIG_RTC_CLASS=y,
> CONFIG_RTC_DRV_CMOS=n that's a kernel configuration that would
> anyway break when the old driver gets removed, and it just broke
> earlier.

I haven't seen the .config, but CONFIG_RTC_CLASS=y
and CONFIG_RTC_DRV_CMOS=n is perfectly legal.

It just don't have to be put in the default x86 config maybe,
but it's legal..

> Everyone seems to focus on this kconfig related case, what about my
> point of no /dev/rtc with a static /dev ? When talking about existing
> setups and embedded systems that's a real issue for some systems.

the device node creation is yet another option of the
rtc class. it should be on by default in any defconfig, I'd guess.

But then you'll get /dev/rtc0 without any specific device node.

As I said in the past, I'd accept a patch to handle this special
case of having /dev/rtc with a specific major and minor, but I'm against
it.

It would be better to upgrade your userspace when such big changes
happens in the kernel. In fact, it the first time that the rtc
has been touched in the last.. 10 year? I think it's not unreasonable to
ask to upgrade userspace.

wrto embedded systems, having worked with them for years, you are expected
to check every detail of every new kernel you want to use before releasing
it or, say, uploading it to your lander on the moon :)




--

Best regards,

Alessandro Zummo,
Tower Technologies - Torino, Italy

http://www.towertech.it



\
 
 \ /
  Last update: 2008-06-14 13:37    [W:0.365 / U:0.112 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site