diff options
author | David Brownell <david-b@pacbell.net> | 2008-02-06 12:38:43 +0300 |
---|---|---|
committer | Linus Torvalds <torvalds@woody.linux-foundation.org> | 2008-02-06 21:41:13 +0300 |
commit | e07e232cd96ef0092b2bddc72f9b7caf284633cb (patch) | |
tree | 442ff1cc6f2548e27315ee6c8ad5252132e5d416 /include/asm-x86/user_32.h | |
parent | 9974b6ea7b85a32f34f824443f47aa501c85ee8f (diff) | |
download | linux-e07e232cd96ef0092b2bddc72f9b7caf284633cb.tar.xz |
rtc-cmos: export nvram in sysfs
This makes rtc-cmos export its NVRAM, like several other RTC drivers.
It still works within the limits of the current CMOS_READ/CMOS_WRITE calls,
which don't understand how to access multiple register banks. The primary
impact of that limitation is that Linux can't access the uppermost 128
bytes of NVRAM on many systems.
Note that this isn't aiming to be a drop-in replacement for the legacy
/dev/nvram support. (Presumably that has real users, and isn't just
getting carried forward automatically?) Userspace handles more work:
- When userspace code updates NVRAM, that will need to include
updating any platform-specific checksums that may apply.
- No /proc/driver/nvram file will parse and display NVRAM data
according to whichever boot firmware your board expects.
Also minor pnp-related updates: update a comment, remove dead code.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Alessandro Zummo <a.zummo@towertech.it>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/asm-x86/user_32.h')
0 files changed, 0 insertions, 0 deletions