From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: nvram and generic_nvram modules are problematic, was Re: [PATCH] arch: m68k: mac: misc.c: Remove some unused functions
Date: Sun, 1 Feb 2015 08:42:45 +0000 [thread overview]
Message-ID: <20150201084245.GF26493@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.LNX.2.00.1502011230150.32582@nippy.intranet>
On Sun, Feb 01, 2015 at 02:39:42PM +1100, Finn Thain wrote:
> I find the ARM support in drivers/char/nvram to be surprising, not to say
> questionable. The /proc/driver/nvram implementation, given
> defined(__arm__), decodes the NVRAM contents in exactly the same format as
> when defined(__i386__) || defined(__x86_64__).
That's because it's used on the Netwinder and EBSA285 platforms, which
are PCI-like, complete with a southbridge which makes them look like a
PC.
> Whereas, only MIPS and
> PowerPC defconfigs set CONFIG_RTC_DRV_CMOS at all, and without that symbol
> the driver will never be built for ARM. This raises the question, does
> /proc/driver/nvram do anything useful on any ARM platforms?
Yes.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-02-01 8:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1420131732-31039-1-git-send-email-rickard_strandqvist@spectrumdigital.se>
[not found] ` <alpine.LNX.2.00.1501041045020.15927@nippy.intranet>
[not found] ` <CAMuHMdXFu3n4d0dMZop186UF+QG=MtLHV=oQr+VszftpEA1kFQ@mail.gmail.com>
2015-02-01 3:39 ` nvram and generic_nvram modules are problematic, was Re: [PATCH] arch: m68k: mac: misc.c: Remove some unused functions Finn Thain
2015-02-01 8:42 ` Russell King - ARM Linux [this message]
2015-02-03 6:11 ` Finn Thain
2015-02-01 9:11 ` Geert Uytterhoeven
2015-02-03 3:22 ` Finn Thain
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=20150201084245.GF26493@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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