[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46D0BD22.2020200@imap.cc>
Date: Sun, 26 Aug 2007 01:37:06 +0200
From: Tilman Schmidt <tilman@...p.cc>
To: Paul Rolland <rol@...917.net>
CC: Dave Jones <davej@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
john stultz <johnstul@...ibm.com>, Andi Kleen <ak@...e.de>,
Len Brown <lenb@...nel.org>, linux-acpi@...r.kernel.org,
Dave Jones <davej@...emonkey.org.uk>,
Thomas Renninger <trenn@...e.de>,
Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>,
rol@...be.net
Subject: Re: 2.6.23-rc3-mm1
Am 25.08.2007 09:55 schrieb Paul Rolland:
> On Sat, 25 Aug 2007 00:28:09 -0400
> Dave Jones <davej@...hat.com> wrote:
>
>> On Fri, Aug 24, 2007 at 08:30:00PM -0700, Andrew Morton wrote:
>>
>> > > -<6>rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
>> > > -<4>rtc_cmos: probe of 00:03 failed with error -16
>> >
>> > I wonder if that was supposed to happen. It's also happening in
>> > 2.6.23-rc3 base.
>>
>> EBUSY. I've seen this happen when you have both CONFIG_RTC and
>> CONFIG_RTC_DRV_CMOS set.
>
> This one is becoming quite worth an entry in a FAQ, it pops up one every
> month ;)
> There was a discussion about preventing both being set at the same time
> when configuring, but I don't remember how it ends...
I must have missed that discussion. I have:
CONFIG_RTC=y
CONFIG_RTC_DRV_CMOS=m
because both of these options claim in their help texts that you
should select them if you want to access the PC RTC.
--
Tilman Schmidt E-Mail: tilman@...p.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
Download attachment "signature.asc" of type "application/pgp-signature" (254 bytes)
Powered by blists - more mailing lists