Home » forums » Software Develop » Linux4Palm

Date/Time Import

Submitted by joker556 on 10 June, 2007 - 03:18. Linux4Palm

Date/Time Import

I was wondering if there is any way for the kernel to "import" the date/time from the Palm OS. If Linux on is going to become a useable second/first OS, then switching should be seemless. If it is not possible to import, then maybe cocoboot could be modified to passthrough the date/time as a parameter. But this solution would only work when switching from Palm to Linux, not from Linux to Palm.

Is this an issue on all Palm versions or is this only a Zire 72 issue?

Thanks to all the developers!!!

» previous forum topic | next forum topic | 583 reads

It's old bug... And use

Submitted by orange on 11 June, 2007 - 06:01.

It's old bug...

And use http://trac.hackndev.com/projects/palmz72/newticket for commiting bugs. Register is needed.

» login or register to post comments

Dont use trac, it'll be

Submitted by marex on 14 June, 2007 - 23:28.

Dont use trac, it'll be wiped out soon. It is now deprecated thing. This date/time thing is problem of RTC, palm screwed it's implementation

» login or register to post comments

Is this an issue on all Palm

Submitted by joker556 on 30 July, 2007 - 04:36.

Is this an issue on all Palm versions or is this only a Zire 72 issue?

» login or register to post comments

joker556 wrote:Is this an

Submitted by Alex on 30 July, 2007 - 08:07.
joker556 wrote:
Is this an issue on all Palm versions or is this only a Zire 72 issue?

All of them. Although we had a crude stab at a workaround a while ago by adding an option to set the epoch date to menuconfig when building a kernel. There might still be problems with the date calculation though, and it may not take affect depending on whether or not you have the RTC driver compiled in etc.

The issue is simply that Palm OS uses 1904 as it's epoch while Linux uses 1970.

» login or register to post comments

Alex, 1940 or 1904?

Submitted by orange on 30 July, 2007 - 11:43.

Alex, 1940 or 1904?

» login or register to post comments

1940

Submitted by marex on 30 July, 2007 - 15:34.

1940

» login or register to post comments

1904, sorry. I corrected the

Submitted by Alex on 30 July, 2007 - 23:46.

1904, sorry. I corrected the typo.

» login or register to post comments

If changing the epoch in the

Submitted by joker556 on 9 August, 2007 - 03:52.

If changing the epoch in the kernel doesn't work, is there any way to "translate" the RTC data?

» login or register to post comments

joker556 wrote:If changing

Submitted by kEdAR on 9 August, 2007 - 06:43.
joker556 wrote:
If changing the epoch in the kernel doesn't work, is there any way to "translate" the RTC data?

on T3 partially work for me:
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
CONFIG_RTC_EPOCH=1904

» login or register to post comments

Submitted by Alex on 9 August, 2007 - 10:39.
Quote:
CONFIG_RTC_EPOCH=1904
Just to clarify, that option doesn't change the kernel's epoch (as basically everything relies on it being 1970) it changes the epoch that is used when storing to the RTC hardware. So yes it does "translate" it,

» login or register to post comments