| To: | Matt Turner <mattst88@gmail.com> |
|---|---|
| Subject: | Re: select() to /dev/rtc0 to wait for clock tick timed out |
| From: | john stultz <johnstul@us.ibm.com> |
| Date: | Fri, 19 Aug 2011 11:07:22 -0700 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <CAEdQ38HGfd9YWE+WLuirE4Km6UE6N26toTj=-1BuXAQUux6t5g@mail.gmail.com> |
| References: | <CAEdQ38HGfd9YWE+WLuirE4Km6UE6N26toTj=-1BuXAQUux6t5g@mail.gmail.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
On Fri, 2011-08-19 at 00:16 -0400, Matt Turner wrote: > Hi John, > > I just sent a patch series to linux-mips@ that enables the RTC on a > particular Broadcom MIPS motherboard (BCM91250A SWARM). The RTC is an > M41T80. > > When I first found the patchset (it was originally sent a a few years > ago) and applied it to 2.6.37, it worked perfectly. > > Applied to 3.x (and I think even 2.6.38) I get the following when I run > hwclock: > > # hwclock --systohc > select() to /dev/rtc0 to wait for clock tick timed out So do alarm interrupts actually work on the hardware? The rtc-m41t80.c driver looks like it should support them ok. Does the test program at the end of Documentation/rtc.txt do much? thanks -john |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Problems booting 3.0.3 kernel on Octeon CN58XX board, Guenter Roeck |
|---|---|
| Next by Date: | [PATCH] MIPS: Octeon: Select CONFIG_HOLES_IN_ZONE, David Daney |
| Previous by Thread: | Re: select() to /dev/rtc0 to wait for clock tick timed out, john stultz |
| Next by Thread: | Re: select() to /dev/rtc0 to wait for clock tick timed out, Matt Turner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |