当前位置: 首页 > news >正文

HalpInitializeClock函数分析之CMOS_WRITE宏定义和CMOS_CONTROL_PORT=0x70和CMOS_DATA_PORT=0x71

HalpInitializeClock函数分析之CMOS_WRITE宏定义和CMOS_CONTROL_PORT=0x70和CMOS_DATA_PORT=0x71

F:\srv03rtm\base\hals/halmps/i386/mpclock.asm:279:cPublicProc _HalpInitializeClock ,0
F:\srv03rtm\base\hals/halmps/i386/mpclock.asm:366: stdRET _HalpInitializeClock
F:\srv03rtm\base\hals/halmps/i386/mpclock.asm:368:stdENDP _HalpInitializeClock

第一部分:
;
; Set the interrupt rate to what is actually needed
;
stdCall _HalpAcquireCmosSpinLock ; intr disabled

mov eax, _HalpCurrentRTCRegisterA
shl ax, 8
mov al, 0AH ; Register A
CMOS_WRITE ; Initialize it
;
; Don't clobber the Daylight Savings Time bit in register B, because we
; stash the LastKnownGood "environment variable" there.
;
mov ax, 0bh
CMOS_READ
and al, 1
mov ah, al
or ah, REGISTER_B_ENABLE_PERIODIC_INTERRUPT
mov al, 0bh
CMOS_WRITE ; Initialize it
mov al,0CH ; Register C
CMOS_READ ; Read to initialize
mov al,0DH ; Register D
CMOS_READ ; Read to initialize

stdCall _HalpReleaseCmosSpinLock


第二部分:
;
; CMOS_READ
;
; Description: This macro reads a byte from the CMOS register specified
; in (AL).
;
; Parameter: (AL) = address/register to read
; Returns: (AL) = data
;

CMOS_READ MACRO
OUT CMOS_CONTROL_PORT,AL ; ADDRESS LOCATION AND DISABLE NMI
IODelay ; I/O DELAY
IN AL,CMOS_DATA_PORT ; READ IN REQUESTED CMOS DATA
IODelay ; I/O DELAY
ENDM

;
; CMOS_WRITE
;
; Description: This macro reads a byte from the CMOS register specified
; in (AL).
;
; Parameter: (AL) = address/register to read
; (AH) = data to be written
;
; Return: None
;

CMOS_WRITE MACRO
OUT CMOS_CONTROL_PORT,AL ; ADDRESS LOCATION AND DISABLE NMI
IODelay ; I/O DELAY
MOV AL,AH ; (AL) = DATA
OUT CMOS_DATA_PORT,AL ; PLACE IN REQUESTED CMOS LOCATION
IODelay ; I/O DELAY
ENDM

第三部分:
//
// CMOS related definitions and macros
//

#define CMOS_CONTROL_PORT 0x70 // cmos command port
#define CMOS_DATA_PORT 0x71 // cmos data port
#define CMOS_FLOPPY_CONFIG_BYTE 0x10

http://www.cnnetsun.cn/news/164050.html

相关文章:

  • Open-AutoGLM脚本如何做到零故障运行?3个关键编写标准揭晓
  • Open-AutoGLM集成难题全解析:5步打通CI/CD流水线瓶颈
  • 价值投资中的宏观经济考量:全局视野
  • Open-AutoGLM收费模式全解析:5种主流定制开发计费方式及企业选型建议
  • 【大模型开发新范式】:Open-AutoGLM 如何让AI研发效率提升300%?
  • Open-AutoGLM调试实战(90%工程师忽略的隐藏问题)
  • Linly-Talker支持自定义服装与背景,数字人形象更丰富
  • Open-AutoGLM测试自动化落地全记录(从0到1的突破性实践)
  • Linly-Talker部署常见问题汇总及解决方案大全
  • Linux 进程深度解析(四):环境变量 —— 进程的“环境 DNA”
  • Linly-Talker支持RESTful API调用,便于前后端分离架构集成
  • 如何用Open-AutoGLM打造企业级AI中台?4大接口调用秘诀首次公开
  • 从开发到部署:Open-AutoGLM应用适配全流程拆解(仅限资深工程师查看)
  • Linly-Talker支持LoRa远距离低功耗通信
  • Linly-Talker支持语音克隆,打造个性化虚拟主播不是梦
  • 为什么你的Open-AutoGLM集成总失败?6大常见坑点全面解析
  • Linly-Talker支持多人协作编辑,团队共创数字人内容
  • P6365 [传智杯 #2 初赛] 众数出现的次数(C++)
  • Open-AutoGLM脚本编写全攻略(专家级编码规范曝光)
  • Linly-Talker模型压缩技术揭秘:在消费级显卡上流畅运行
  • 揭秘Open-AutoGLM自定义脚本编写难点:5大关键规范你必须知道
  • Linly-Talker支持MQTT协议用于物联网通信
  • Linly-Talker语音活跃度检测避免无效唤醒
  • Linly-Talker结合SLAM技术实现空间定位交互
  • 2025-12-20 全国各地响应最快的 BT Tracker 服务器(电信版)
  • Linly-Talker在养老院陪伴机器人的落地案例
  • php.ini的庖丁解牛
  • Linly-Talker与主流大模型对比:优势在哪里?
  • Linly-Talker语音中断检测机制提升交互自然度
  • Linly-Talker支持API调用,便于系统集成