public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: <benh@kernel.crashing.org>
To: <linux-kernel@vger.kernel.org>, Lukas Geyer <geyer@ml.kva.se>
Subject: Re: Two issues with 2.4.18pre3 on PPC
Date: Wed, 16 Jan 2002 17:37:37 +0100	[thread overview]
Message-ID: <20020116163737.29030@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0201161417540.6868-100000@cauchy.ml.kva.se>
In-Reply-To: <Pine.LNX.4.33.0201161417540.6868-100000@cauchy.ml.kva.se>

>- The generic RTC driver in drivers/char/rtc.c does not work for this
>  iBook. The driver in drivers/macintosh/rtc.c does work, but it only
>  implements the two ioctls RTC_RD_TIME and RTC_SET_TIME. (Is this due to
>  hardware limitations?) Anyway, it is confusing to have both drivers
>  configurable for PPC, maybe the corresponding Config.in files should be
>  adjusted. (In addition, this is complicated by the fact that both
>  configuration options appear in different submenus and if you select
>  both as modules, then the generic driver will "shadow" the macintosh
>  one.)

That's a weirdness we haven't solved yet. Part of the problem is
that a common kernel can boot pmac, chrp and prep, and the later
ones can use the drivers/char/rtc.c driver. Actually, the
drivers/macintosh/rtc.c one may work on these too as it's just
a wrapper on some platform code selected at runtime depending on
the machine class.

Now, regarding the support of only GET/SET ioctls, it's normal.
Some of these machines don't have the legacy PC hardware RTC with
alarm support etc... That's the case of macs where the RTC hardware
is purely a real time clock. (It has other features, like scheduled
power up, but these aren't implemented yet and could be done entirely
in userland using /dev/adb anyway).

So the driver in drivers/macintosh/rtc.c is just a wrapper on the
get/set time functions provided by each type of machine.

Ben.




  parent reply	other threads:[~2002-01-16 16:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-16 13:47 Two issues with 2.4.18pre3 on PPC Lukas Geyer
2002-01-16 15:24 ` Ed Sweetman
2002-01-16 18:56   ` Lukas Geyer
2002-01-16 16:37 ` benh [this message]
2002-01-16 16:55   ` Automatic reboot on PPC (was: Re: Two issues with 2.4.18pre3 on PPC) Thomas Capricelli
2002-01-16 17:55     ` Benjamin Herrenschmidt
2002-01-16 17:05   ` Two issues with 2.4.18pre3 on PPC Tom Rini
2002-01-16 17:10     ` Eric S. Raymond
2002-01-16 17:31       ` Tom Rini
2002-01-16 17:25         ` Eric S. Raymond
2002-01-16 17:54           ` Tom Rini
2002-01-17  0:08       ` Horst von Brand

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=20020116163737.29030@mailhost.mipsys.com \
    --to=benh@kernel.crashing.org \
    --cc=geyer@ml.kva.se \
    --cc=linux-kernel@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