public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Finn Thain <fthain@telegraphics.com.au>
To: Thorsten Glaser <tg@mirbsd.de>
Cc: linux-m68k@vger.kernel.org
Subject: Re: [PATCH 1/1] m68k: add missing I/O macros {in,out}{w,l}_p() for !CONFIG_ISA
Date: Thu, 7 Oct 2010 01:15:15 +1100 (EST)	[thread overview]
Message-ID: <alpine.OSX.2.00.1010070044520.278@localhost> (raw)
In-Reply-To: <Pine.BSM.4.64L.1010060924250.21623@herc.mirbsd.org>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 878 bytes --]


On Wed, 6 Oct 2010, Thorsten Glaser wrote:

> the ARAnyM RTC driver added after my last “report” probably vanished too 
> (hwclock still says it can’t access it).

I gather that atari uses CONFIG_RTC_DRV_CMOS which needs CONFIG_RTC_CLASS. 
The Debian 2.6.32-23 configs lack these:

linux-2.6-2.6.32$ grep -r RTC_CLASS debian/config/
debian/config/config:CONFIG_RTC_CLASS=y
debian/config/m68k/config.atari:# CONFIG_RTC_CLASS is not set
debian/config/sh4/config.sh7785lcr:CONFIG_RTC_CLASS=y
debian/config/sh4/config.sh7751r:CONFIG_RTC_CLASS=y
debian/config/hppa/config:# CONFIG_RTC_CLASS is not set
linux-2.6-2.6.32$ 

That's about all I can tell from looking at the sources. Hopefully someone 
who knows something about atari/aranym can say more. This link might jog 
some memories: 
http://permalink.gmane.org/gmane.linux.debian.ports.68k/9157

Finn

  parent reply	other threads:[~2010-10-06 14:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-03 18:38 [PATCH 0/1] m68k: add missing I/O macros {in,out}{w,l}_p() for !CONFIG_ISA Thorsten Glaser
2010-10-03 18:48 ` [PATCH 1/1] " Thorsten Glaser
2010-10-04  0:51   ` Finn Thain
2010-10-04  7:40     ` Thorsten Glaser
2010-10-04  8:47       ` Finn Thain
2010-10-04  9:10         ` Thorsten Glaser
2010-10-04 10:22           ` Finn Thain
2010-10-04 11:30             ` Thorsten Glaser
2010-10-04 13:18             ` Geert Uytterhoeven
2010-10-04 13:33               ` Finn Thain
2010-10-04 13:40               ` Thorsten Glaser
2010-10-04 14:01                 ` Geert Uytterhoeven
2010-10-04 14:13                   ` Thorsten Glaser
2010-10-04 19:20                   ` Thorsten Glaser
2010-10-13 20:17                   ` Thorsten Glaser
2010-10-05 12:56                 ` Stephen R. Marenka
2010-10-05 14:10                   ` debian kernel config, was " Finn Thain
2010-10-06  0:57                   ` Stephen R. Marenka
2010-10-06  9:26                   ` Thorsten Glaser
2010-10-06 13:09                     ` Stephen R. Marenka
2010-10-06 14:15                     ` Finn Thain [this message]
2010-10-04  7:57   ` Michael Schmitz
2010-10-04  8:13     ` Thorsten Glaser
2010-10-04  9:08       ` Finn Thain
2010-10-04 10:18         ` Thorsten Glaser
2010-10-04 10:51           ` Finn Thain
2010-10-04 11:37             ` Thorsten Glaser
2010-10-04 12:45               ` Finn Thain
2010-10-16 17:12   ` 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=alpine.OSX.2.00.1010070044520.278@localhost \
    --to=fthain@telegraphics.com.au \
    --cc=linux-m68k@vger.kernel.org \
    --cc=tg@mirbsd.de \
    /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