Searched hist:168013 (Results 1 - 4 of 4) sorted by relevance
/freebsd-10.3-release/sys/boot/arm/at91/libat91/ | ||
H A D | getc.c | diff 168013 Wed Mar 28 22:40:37 MDT 2007 imp RTC_TIMR's RTC_SEC field is BCD. That makes it unsuitable for GetSeconds(). Instead, use CRTR register shifted right 15. This gives us a range of 32 seconds we can do for timeout. Shift to using == rather than < or > for calculating the timeout, since if we can't read the ST_CTRT register twice in a second we have even bigger problems to worry about, and == deals with the 'wrap' issue. This lets me type at the boot2 prompt again! Woo Hoo! Bogusness noticed by: tisco Pointy Hat to: That silly imp guy |
H A D | at91rm9200_lowlevel.h | diff 168013 Wed Mar 28 22:40:37 MDT 2007 imp RTC_TIMR's RTC_SEC field is BCD. That makes it unsuitable for GetSeconds(). Instead, use CRTR register shifted right 15. This gives us a range of 32 seconds we can do for timeout. Shift to using == rather than < or > for calculating the timeout, since if we can't read the ST_CTRT register twice in a second we have even bigger problems to worry about, and == deals with the 'wrap' issue. This lets me type at the boot2 prompt again! Woo Hoo! Bogusness noticed by: tisco Pointy Hat to: That silly imp guy |
H A D | at91rm9200_lowlevel.c | diff 168013 Wed Mar 28 22:40:37 MDT 2007 imp RTC_TIMR's RTC_SEC field is BCD. That makes it unsuitable for GetSeconds(). Instead, use CRTR register shifted right 15. This gives us a range of 32 seconds we can do for timeout. Shift to using == rather than < or > for calculating the timeout, since if we can't read the ST_CTRT register twice in a second we have even bigger problems to worry about, and == deals with the 'wrap' issue. This lets me type at the boot2 prompt again! Woo Hoo! Bogusness noticed by: tisco Pointy Hat to: That silly imp guy |
H A D | emac.c | diff 168013 Wed Mar 28 22:40:37 MDT 2007 imp RTC_TIMR's RTC_SEC field is BCD. That makes it unsuitable for GetSeconds(). Instead, use CRTR register shifted right 15. This gives us a range of 32 seconds we can do for timeout. Shift to using == rather than < or > for calculating the timeout, since if we can't read the ST_CTRT register twice in a second we have even bigger problems to worry about, and == deals with the 'wrap' issue. This lets me type at the boot2 prompt again! Woo Hoo! Bogusness noticed by: tisco Pointy Hat to: That silly imp guy |
Completed in 104 milliseconds