public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Patrick Bottelberger <patrick.bottelberger@sigon.net>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Thorsten Glaser <tg@debian.org>, linux-m68k@vger.kernel.org
Subject: Re: Linux on Amiga A600, a success story (in progress, with possible patch)
Date: Mon, 20 Feb 2012 23:47:16 +0100	[thread overview]
Message-ID: <4F42CD74.5010409@sigon.net> (raw)
In-Reply-To: <m2obstgnsu.fsf@igel.home>

Hi Andreas,

yes, but after setting the clock (e.g. via "date MMDDhhmmccyy" and
"hwclock --systohc" thereafter) the date and time should be correct, as
long as the computer isn't turned off, right? That's not the case with
my A600, the date stays correct, but the time seems to have difficulties
with the first digit (e.g. jumping between 02:20, 12:20 and 22:20 in a
few seconds) and often returns an EINVAL when trying to read the time.
Trying to access the date (through /sys/class/rtc/rtc0/date for example)
curiously always works. Could it be related to the floating point
emulation? But i don't think the kernel relies on floating point
registers for getting the time from the rtc, or is it?


Regards,
Patrick

Andreas Schwab schrieb:
> Patrick Bottelberger <patrick.bottelberger@sigon.net> writes:
>
>   
>> Back to my current problems, i don't think the read errors for the RTC
>> may be connected to the fact, that i don't have a battery on my A603
>> board, or could it?
>>     
>
> The kernel rtc code rejects dates before the Unix epoch.  Typically an
> rtc that is reset reports a year before 1970.
>
> Andreas.
>
>   

  reply	other threads:[~2012-02-20 22:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-22 18:37 Linux on Amiga A600, a success story (in progress, with possible patch) Patrick Bottelberger
2012-01-23 20:42 ` Geert Uytterhoeven
2012-01-23 23:04   ` Michael Schmitz
2012-01-24  8:41     ` Geert Uytterhoeven
2012-01-24 17:56     ` Patrick Bottelberger
2012-01-24 21:19       ` Geert Uytterhoeven
2012-01-27 17:44     ` Thorsten Glaser
2012-01-28 20:24       ` Michael Schmitz
2012-01-28 20:43         ` Thorsten Glaser
2012-01-28 20:49           ` Geert Uytterhoeven
2012-01-28 21:01             ` Thorsten Glaser
2012-01-24 17:35   ` Patrick Bottelberger
2012-01-24 21:17     ` Geert Uytterhoeven
2012-01-24 21:49       ` Geert Uytterhoeven
2012-01-25 19:11       ` Patrick Bottelberger
2012-01-26 17:05         ` Patrick Bottelberger
2012-02-07 19:55           ` Patrick Bottelberger
2012-02-07 22:13             ` Thorsten Glaser
2012-02-20 21:38               ` Patrick Bottelberger
2012-02-20 22:09                 ` Andreas Schwab
2012-02-20 22:47                   ` Patrick Bottelberger [this message]
2012-02-20 23:02                     ` Andreas Schwab
2012-02-21 10:55                       ` Patrick Bottelberger
2012-01-29 21:59         ` Geert Uytterhoeven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F42CD74.5010409@sigon.net \
    --to=patrick.bottelberger@sigon.net \
    --cc=linux-m68k@vger.kernel.org \
    --cc=schwab@linux-m68k.org \
    --cc=tg@debian.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox