All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Alessandro Zummo <a.zummo@towertech.it>,
	Arno Griffioen <arno.griffioen@ieee.org>
Cc: "Linux/m68k" <linux-m68k@vger.kernel.org>,
	rtc-linux@googlegroups.com,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rtc: rp5c01 - Add NVRAM support
Date: Wed, 23 Jun 2010 21:55:27 +0200	[thread overview]
Message-ID: <AANLkTikdDZf1zvgtu3DjuMoabHBo43zY6H_AUKn0Q5Qz@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1006131208470.18415@ayla.of.borg>

On Sun, Jun 13, 2010 at 12:12, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> The Ricoh RP5C01 RTC contains 26 x 4 bits of NVRAM.
> Provide access to it via a sysfs "nvram" attribute file.

I also created a small tool to correct NVRAM checksums, interprete the
contents, and
modify individual NVRAM fields on Amiga 3000/4000.
You can find it at
git://git.kernel.org/pub/scm/linux/kernel/git/geert/amiga-nvram.git.

BTW, does anyone (Arno?) know the meaning of the AMIX-specific bits (32-63)?
battmembitsamix.h just says "See Amix documentation for these bit definitions".
I also couldn't find anything about it at http://www.amigaunix.com/.

Thx!

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

  parent reply	other threads:[~2010-06-23 19:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-13 10:12 [PATCH] rtc: rp5c01 - Add NVRAM support Geert Uytterhoeven
2010-06-13 10:12 ` Geert Uytterhoeven
2010-06-13 13:41 ` [rtc-linux] " Wan ZongShun
2010-06-13 17:44   ` Geert Uytterhoeven
2010-06-13 13:41 ` Wan ZongShun
2010-06-23 19:55 ` Geert Uytterhoeven [this message]
2010-07-18 18:32 ` 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=AANLkTikdDZf1zvgtu3DjuMoabHBo43zY6H_AUKn0Q5Qz@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=a.zummo@towertech.it \
    --cc=arno.griffioen@ieee.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=rtc-linux@googlegroups.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.