From: Torben N. <tr...@bi...> - 2004-04-17 07:43:40
|
I wrote a driver for the gamecube real time clock. It works fine for me, so I wonder if it is possible to contribute the code to the project. Or is everyone else just running NTP? |
From: JockyW <joc...@ho...> - 2004-04-26 18:39:06
|
"Torben Nielsen" <tr...@bi...> wrote in message news:1082187695.1177.19.camel@hannibal... > I wrote a driver for the gamecube real time clock. It works fine for me, > so I wonder if it is possible to contribute the code to the project. > Or is everyone else just running NTP? > I'm interested! I use NTP, but it doesn't work properly. I always get this: "Jan 1 01:03:32 cube ntpd[191]: time correction of 1083004124 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time." I'd be happy to test your RTC driver. |
From: Michael S. <st...@in...> - 2004-04-26 18:47:08
|
The RTC driver has been put into the CVS. Checkout the kernel from there to test it. :-) Michael On Apr 26, 2004, at 8:39 PM, JockyW wrote: > > "Torben Nielsen" <tr...@bi...> wrote in message > news:1082187695.1177.19.camel@hannibal... >> I wrote a driver for the gamecube real time clock. It works fine for >> me, >> so I wonder if it is possible to contribute the code to the project. >> Or is everyone else just running NTP? >> > > I'm interested! > > I use NTP, but it doesn't work properly. I always get this: > "Jan 1 01:03:32 cube ntpd[191]: time correction of 1083004124 seconds > exceeds sanity limit (1000); set clock manually to the correct UTC > time." > > I'd be happy to test your RTC driver. > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek > For a limited time only, get FREE Ground shipping on all orders of $35 > or more. Hurry up and shop folks, this offer expires April 30th! > http://www.thinkgeek.com/freeshipping/?cpg=12297 > _______________________________________________ > Gc-linux-devel mailing list > Gc-...@li... > https://lists.sourceforge.net/lists/listinfo/gc-linux-devel > |
From: JockyW <joc...@ho...> - 2004-04-26 21:41:23
|
"Michael Steil" <st...@in...> wrote in message news:C69...@in...... > The RTC driver has been put into the CVS. Checkout the kernel from > there to test it. :-) > > Michael > Thanks Michael:) I'm now building 2.6.5 and noticed that gamecubefb.c and fbmem.c need a #define __powerpc__ in order to build the kernel. W/o these there is a missing reference to fb_writel_real() Everything works as usual (also the RTC, thanks Torben!), except that the screen is very green and not very clear. It seems to me that the __powerpc__ definitions that I added also have a negative impact :( PS: I still have an unanswered question related to a dvd driver which I developed: Do you know to what memory the virtual address 0xc2004048 is mapped? When I convert it to a bus or phys address it doesn't seem to be a physical address. JockyW |
From: <a.o...@bl...> - 2004-04-26 23:08:59
|
On Mon, Apr 26, 2004 at 11:41:12PM +0200, JockyW wrote: > I'm now building 2.6.5 and noticed that gamecubefb.c and fbmem.c need a > #define __powerpc__ in order to build the kernel. W/o these there is a > missing reference to fb_writel_real() Sounds like your setup (probably toolchain) might be up to some funkiness - I can't seem to reproduce that here. Taken from 2.6.5, wrapped for legibility: include/linux/fb.h:554:#elif defined(__i386__) || defined(__alpha__) || \ defined(__x86_64__) || defined(__hppa__) || \ defined(__sh__) || defined(__powerpc__) > Everything works as usual (also the RTC, thanks Torben!), except that the > screen is very green and not very clear. It seems to me that the __powerpc__ > definitions that I added also have a negative impact :( Sounds like you're crashing before the framebuffer console kicks in. You could either enable the debug console to see the call trace (if any), or start with the default config (`make gamecube_defconfig') and play the fun game of elimination. Arthur |
From: JockyW <joc...@ho...> - 2004-04-27 15:11:05
|
"Arthur Othieno" <a.o...@bl...> wrote in message news:20040426230746.GA1966@mars... > On Mon, Apr 26, 2004 at 11:41:12PM +0200, JockyW wrote: > > I'm now building 2.6.5 and noticed that gamecubefb.c and fbmem.c need a > > #define __powerpc__ in order to build the kernel. W/o these there is a > > missing reference to fb_writel_real() > > Sounds like your setup (probably toolchain) might be up to some > funkiness - I can't seem to reproduce that here. > Yes, you are absolutely right. I used the PPC gcc 3.3 cross-compiler for Linux (by Wintermute). This has always worked fine for building kernelversions 2.6.3 and 2.6.4. I have now built a perfectly working 2.6.5 kernel directly on the cube :) It only takes a bit longer ... Thanks for your help! JockyW |
From: Adam T. <ad...@io...> - 2004-04-26 19:35:15
|
On Mon, 2004-04-26 at 13:39, JockyW wrote: > I use NTP, but it doesn't work properly. I always get this: > "Jan 1 01:03:32 cube ntpd[191]: time correction of 1083004124 seconds > exceeds sanity limit (1000); set clock manually to the correct UTC time." > > I'd be happy to test your RTC driver. NTP works OK, but a) you probably need a bigger sanity limit (like ten million), and b) you do need to get it closer than the start of the epoch. What I do is to manually set the date to 1/1/04 in one of the init.d scripts before running ntpdate. Adam |
From: JockyW <joc...@ho...> - 2004-04-26 21:20:14
|
> > NTP works OK, but a) you probably need a bigger sanity limit (like ten > million), and b) you do need to get it closer than the start of the > epoch. What I do is to manually set the date to 1/1/04 in one of the > init.d scripts before running ntpdate. > > Adam > I just solved that issue by starting ntpd with -g argument. Appr. 3 minutes after ntpd is started time is synchronized. Thx anyway for the alt solution JockyW |