On Fri, Jun 15, 2007 at 04:05:05PM -0700, [EMAIL PROTECTED] wrote:
>
>
> Ooh, cool. This is crucial when you want to do a persistent 'failed'
> state for cheap machines with memory errors that you are using as
> appliances. Can you MFC these?
Yeah it sounds like there are some interesting uses
Ooh, cool. This is crucial when you want to do a persistent 'failed'
state for cheap machines with memory errors that you are using as
appliances. Can you MFC these?
peter 2007-06-15 22:58:14 UTC
FreeBSD src repository
Modified files:
sys/i386/isa clock.c
sys/amd64/i
peter 2007-06-15 22:58:14 UTC
FreeBSD src repository
Modified files:
sys/i386/isa clock.c
sys/amd64/isaclock.c
Log:
Prototype (but functional) Linux-ish /dev/nvram interface to the extra
114 bytes of cmos ram in the PC clock chip. The big difference betw
On Wed, 6 Dec 2006, Suleiman Souhlal wrote:
Bruce Evans wrote:
bde 2006-12-03 03:49:28 UTC
FreeBSD src repository
Modified files:
sys/i386/isa clock.c sys/amd64/isaclock.c Log:
Optimized RTC accesses by avoiding null writes to the index register
and b
Bruce Evans wrote:
bde 2006-12-03 03:49:28 UTC
FreeBSD src repository
Modified files:
sys/i386/isa clock.c
sys/amd64/isaclock.c
Log:
Optimized RTC accesses by avoiding null writes to the index register
and by only delaying when an RTC register is wri
bde 2006-12-03 03:49:28 UTC
FreeBSD src repository
Modified files:
sys/i386/isa clock.c
sys/amd64/isaclock.c
Log:
Optimized RTC accesses by avoiding null writes to the index register
and by only delaying when an RTC register is written to. The delay
