HEADSUP: RTC changes on i386
- From: Poul-Henning Kamp <phk@xxxxxxxxxxxxxxxxxx>
- Date: Sat, 12 Apr 2008 20:57:04 +0000
This heads-up is relevant only to non-PnP and non-ACPI systems,
which more or less is only older "ISA-bus" only systems and embedded
platforms such as Soekris, WRAP etc.
If you are running -current on such a system, make sure that you
copy the "hint.atrtc.*" lines from sys/i386/conf/GENERIC.hints to
/boot/device.hints.
If you have never heard of this file before, and have never edited
/boot/device.hints, just do this:
cp /sys/i386/conf/GENERIC.hints /boot/device.hints
If you fail to add these hints, and your system has no PnP or ACPI
hints either, the RTC device will not be found and the wall-clock
time will not read from, or written to, the RTC chip on the
motherboard.
If "devinfo -r" shows these lines, your system is fine:
atrtc0
Interrupt request lines:
8
I/O ports:
0x70-0x71
When you build new releases or nanoBSD images, the right thing will
automatically happen via src/etc/Makefile.
Poul-Henning
Log:
Move i386 to generic RTC handling code.
Make clock_if.m and subr_rtc.c standard on i386
Add hints for "atrtc" driver, for non-PnP, non-ACPI systems.
NB: Make sure to install GENERIC.hints into /boot/device.hints in these!
Nuke MD inittodr(), resettodr() functions.
Don't attach to PHP0B00 in the "attimer" dummy driver any more, and remove
comments that no longer apply for that reason.
Add new "atrtc" device driver, which handles IBM PC AT Real Time
Clock compatible devices using subr_rtc and clock_if.
This driver is not entirely clean: other code still fondles the
hardware to get a statclock interrupt on non-ACPI timer systems.
Wrap some overly long lines.
After it has settled in -current, this will be ported to amd64.
Technically this is MFC'able, but I fail to see a good reason.
Revision Changes Path
1.593 +2 -0 src/sys/conf/files.i386
1.20 +3 -0 src/sys/i386/conf/GENERIC.hints
1.246 +168 -103 src/sys/i386/isa/clock.c
------- End of Forwarded Message
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Prev by Date: Re: mlock(2), unprivileged users, and RLIMIT_MEMLOCK
- Next by Date: Re: mlock(2), unprivileged users, and RLIMIT_MEMLOCK
- Previous by thread: mlock(2), unprivileged users, and RLIMIT_MEMLOCK
- Next by thread: Build failure without options RADIX_MPATH
- Index(es):
Relevant Pages
|
