public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Kars de Jong <jongk@linux-m68k.org>
Cc: Linux/m68k mailing list <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH] RTC updates for Amiga
Date: Wed, 18 Mar 2009 15:29:20 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0903181521590.9249@anakin> (raw)
In-Reply-To: <1046634024.1620.22.camel@kars.perseus.home>

	Hi Kars,

On Sun, 2 Mar 2003 (yeah, that's a long time ago), Kars de Jong wrote:
> I got tired of my Amiga locking up every time when hwclock got run (see
> http://lists.linux-m68k.org/pipermail/linux-m68k/2002-January/000730.html for details) even with CONFIG_GEN_RTC_X=y in my .config, so I decided to look at the OKI website for the datasheet of the MSM6242RS clock (the one used in A2000 / A1200).

While looking into creating separate rtc-msm6242 (`A2000 RTC') and rtc-rp5c01
(`A3000 RTC') drivers, as per current RTC policy, I browsed through the various
Amiga schematics to identify RTC chips.

Surprisingly, I discovered a Ricoh RP5C01 (not an Oki MSM6242) on the A1200
schematics:
http://www.symbolengine.com/index.php/2007/04/21/amiga-1200-schematics-in-pdf-format/
Hence does arch/m68k/amiga/config.c:amiga_identify() handle the A1200
incorrectly?

It also seems the CDTV has a builtin MSM6242, while the CD32 hasn't any RTC,
like A1000/A500/A600. So ideally, we have to probe for RTC presence. I guess
for the MSM6242 we can use the existing loop (timeout = no MSM6242). What about
the RP5C01?

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

           reply	other threads:[~2009-03-18 14:29 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1046634024.1620.22.camel@kars.perseus.home>]

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=Pine.LNX.4.64.0903181521590.9249@anakin \
    --to=geert@linux-m68k.org \
    --cc=jongk@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.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