<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/"><channel><title>Cloud_Apex的专栏</title><link>http://blog.csdn.net/cloud_apex/</link><description>希望同样喜欢编写OS的网友多多评论,并留下联系方式</description><dc:language>zh-CN</dc:language><lastUpdateTime>Thu, 04 Jan 2007 17:25:22 GMT</lastUpdateTime><ttl>60</ttl><item><dc:creator>Cloud_Apex</dc:creator><title>Low byte reference in intel 64</title><link>http://blog.csdn.net/Cloud_Apex/archive/2007/01/04/1474067.aspx</link><pubDate>Thu, 04 Jan 2007 17:25:00 GMT</pubDate><guid>http://blog.csdn.net/Cloud_Apex/archive/2007/01/04/1474067.aspx</guid><wfw:comment>http://blog.csdn.net/cloud_apex/comments/1474067.aspx</wfw:comment><comments>http://blog.csdn.net/Cloud_Apex/archive/2007/01/04/1474067.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://blog.csdn.net/cloud_apex/comments/commentRss/1474067.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=1474067</trackback:ping><description> In 64-bit mode, there are limitations on accessing byte registers. An instruction cannot reference legacy high-bytes (for example: AH, BH, CH, DH) and one of the new byte registers at the same time (for example: the low byte of the RAX register). However, instructions may reference legacy low-bytes (for example: AL, BL, CL or
DL) and new byte registers at the same time (for example: the low byte of the R8 register, or RBP). The architecture enforces this limitation by changing high-byte refere&lt;img src ="http://blog.csdn.net/cloud_apex/aggbug/1474067.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Cloud_Apex</dc:creator><title>Canonical Addressing</title><link>http://blog.csdn.net/Cloud_Apex/archive/2007/01/04/1473975.aspx</link><pubDate>Thu, 04 Jan 2007 16:09:00 GMT</pubDate><guid>http://blog.csdn.net/Cloud_Apex/archive/2007/01/04/1473975.aspx</guid><wfw:comment>http://blog.csdn.net/cloud_apex/comments/1473975.aspx</wfw:comment><comments>http://blog.csdn.net/Cloud_Apex/archive/2007/01/04/1473975.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://blog.csdn.net/cloud_apex/comments/commentRss/1473975.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=1473975</trackback:ping><description>3.3.7.1 Canonical Addressing
In 64-bit mode, an address is considered to be in canonical form if address bits 63
through to the most-significant implemented bit by the microarchitecture are set to
either all ones or all zeros.
Intel 64 architecture defines a 64-bit linear address. Implementations can support
less. The first implementation of IA-32 processors with Intel 64 architecture supports
a 48-bit linear address. This means a canonical address must have bits 63 through 48
set to zero&lt;img src ="http://blog.csdn.net/cloud_apex/aggbug/1473975.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Cloud_Apex</dc:creator><title>块设备 驱动 缓存 记要</title><link>http://blog.csdn.net/Cloud_Apex/archive/2006/07/06/884226.aspx</link><pubDate>Thu, 06 Jul 2006 11:16:00 GMT</pubDate><guid>http://blog.csdn.net/Cloud_Apex/archive/2006/07/06/884226.aspx</guid><wfw:comment>http://blog.csdn.net/cloud_apex/comments/884226.aspx</wfw:comment><comments>http://blog.csdn.net/Cloud_Apex/archive/2006/07/06/884226.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://blog.csdn.net/cloud_apex/comments/commentRss/884226.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=884226</trackback:ping><description>关于缓存，应该将其放在块设备底层读写驱动中，而非上层文件系统层， 并分配固定大小的缓存， 文件系统无需考虑缓存问题，而将问题集中在文件存储结构上。 &lt;img src ="http://blog.csdn.net/cloud_apex/aggbug/884226.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Cloud_Apex</dc:creator><title>我喜欢现在的工作，喜欢我的同事，还有还有我们的小小老板^_^</title><link>http://blog.csdn.net/Cloud_Apex/archive/2006/06/28/847356.aspx</link><pubDate>Wed, 28 Jun 2006 22:18:00 GMT</pubDate><guid>http://blog.csdn.net/Cloud_Apex/archive/2006/06/28/847356.aspx</guid><wfw:comment>http://blog.csdn.net/cloud_apex/comments/847356.aspx</wfw:comment><comments>http://blog.csdn.net/Cloud_Apex/archive/2006/06/28/847356.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://blog.csdn.net/cloud_apex/comments/commentRss/847356.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=847356</trackback:ping><description>我喜欢现在的工作，喜欢我的同事，还有还有我们的小小老板^_^&lt;img src ="http://blog.csdn.net/cloud_apex/aggbug/847356.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Cloud_Apex</dc:creator><title>工作了，以后写Apex的时间少了</title><link>http://blog.csdn.net/Cloud_Apex/archive/2006/06/07/779080.aspx</link><pubDate>Wed, 07 Jun 2006 21:31:00 GMT</pubDate><guid>http://blog.csdn.net/Cloud_Apex/archive/2006/06/07/779080.aspx</guid><wfw:comment>http://blog.csdn.net/cloud_apex/comments/779080.aspx</wfw:comment><comments>http://blog.csdn.net/Cloud_Apex/archive/2006/06/07/779080.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://blog.csdn.net/cloud_apex/comments/commentRss/779080.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=779080</trackback:ping><description>工作了，以后写Apex的时间少了，不过我还会尽量多写些的，更希望曾经与我共同写Apex的朋友，和想加入Apex编写的朋友与我联系，我会尽快为大家分配编写任务，通过大家的努力加速Apex的编写。&lt;img src ="http://blog.csdn.net/cloud_apex/aggbug/779080.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Cloud_Apex</dc:creator><title>Apex OS 走向开源化</title><link>http://blog.csdn.net/Cloud_Apex/archive/2006/05/25/755585.aspx</link><pubDate>Thu, 25 May 2006 23:10:00 GMT</pubDate><guid>http://blog.csdn.net/Cloud_Apex/archive/2006/05/25/755585.aspx</guid><wfw:comment>http://blog.csdn.net/cloud_apex/comments/755585.aspx</wfw:comment><comments>http://blog.csdn.net/Cloud_Apex/archive/2006/05/25/755585.aspx#Feedback</comments><slash:comments>13</slash:comments><wfw:commentRss>http://blog.csdn.net/cloud_apex/comments/commentRss/755585.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=755585</trackback:ping><description>Apex OS 走向开源化
我是Apex的设计者与开发者，Apex在初步运行启动后，我计划将Apex OS开源化，并长期从事Apex OS 的开发，希望通过我的努力和社会各界人士的帮助，在中国，这个原创开源社区不是很繁荣的国家，与各种企业，组织，每位学者，工作者共同在Apex OS的基础上建立一个交流学习的地方，更希望与国外著名的开源社区建立联系，不分国界不分民族不分阶级的交流与学习。在此我希望有志之士能给予Apex帮助和关爱。
Apex 开源组织计划向政府部门申请非盈利性组织（开源组织），通过其他企业，组织或个人的资助得到发展，而开源组织将为赞助者提供Apex所涉及的技术范围内的技术帮助，包括各种源码及文档，与赞助者的技术人员进行技术交流，提供程序源码，共同解决技术问题，技术范围是PC机硬件驱动，操作系统，以及网络协议以及提供各种测试报告，我们将长期无偿的为赞助者提供这样的帮助，而我们所希望的仅仅是赞助者为Apex组织提供的少量资金，以维持开源组织各方面的财政支出，维持Apex的生存。
我们为各个赞助者提供的程序及其他技术帮助不但可以促进各企业之间的交流，减少企业在这些方面的资&lt;img src ="http://blog.csdn.net/cloud_apex/aggbug/755585.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Cloud_Apex</dc:creator><title>Apex OS Start Beta 0.1 Edition Picture</title><link>http://blog.csdn.net/Cloud_Apex/archive/2006/05/22/750091.aspx</link><pubDate>Mon, 22 May 2006 21:41:00 GMT</pubDate><guid>http://blog.csdn.net/Cloud_Apex/archive/2006/05/22/750091.aspx</guid><wfw:comment>http://blog.csdn.net/cloud_apex/comments/750091.aspx</wfw:comment><comments>http://blog.csdn.net/Cloud_Apex/archive/2006/05/22/750091.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://blog.csdn.net/cloud_apex/comments/commentRss/750091.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=750091</trackback:ping><description>Apex 在Bochs 2.2.6上的运行图：

白色物体为鼠标：
&lt;img src ="http://blog.csdn.net/cloud_apex/aggbug/750091.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Cloud_Apex</dc:creator><title>Apex 调试 初成成果</title><link>http://blog.csdn.net/Cloud_Apex/archive/2006/05/20/747233.aspx</link><pubDate>Sat, 20 May 2006 23:50:00 GMT</pubDate><guid>http://blog.csdn.net/Cloud_Apex/archive/2006/05/20/747233.aspx</guid><wfw:comment>http://blog.csdn.net/cloud_apex/comments/747233.aspx</wfw:comment><comments>http://blog.csdn.net/Cloud_Apex/archive/2006/05/20/747233.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://blog.csdn.net/cloud_apex/comments/commentRss/747233.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=747233</trackback:ping><description>启动，vesa 图形模式下字符界面，鼠标&lt;img src ="http://blog.csdn.net/cloud_apex/aggbug/747233.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Cloud_Apex</dc:creator><title>工作日志：这几天在找图形界面的解决方法,现在基本上确定了，准备编写图形界面代码了</title><link>http://blog.csdn.net/Cloud_Apex/archive/2006/03/24/637871.aspx</link><pubDate>Fri, 24 Mar 2006 21:28:00 GMT</pubDate><guid>http://blog.csdn.net/Cloud_Apex/archive/2006/03/24/637871.aspx</guid><wfw:comment>http://blog.csdn.net/cloud_apex/comments/637871.aspx</wfw:comment><comments>http://blog.csdn.net/Cloud_Apex/archive/2006/03/24/637871.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://blog.csdn.net/cloud_apex/comments/commentRss/637871.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=637871</trackback:ping><description>工作日志：这几天在找图形界面的解决方法,现在基本上确定了，准备编写图形界面代码了&lt;img src ="http://blog.csdn.net/cloud_apex/aggbug/637871.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Cloud_Apex</dc:creator><title>scanline</title><link>http://blog.csdn.net/Cloud_Apex/archive/2006/03/09/619843.aspx</link><pubDate>Thu, 09 Mar 2006 15:50:00 GMT</pubDate><guid>http://blog.csdn.net/Cloud_Apex/archive/2006/03/09/619843.aspx</guid><wfw:comment>http://blog.csdn.net/cloud_apex/comments/619843.aspx</wfw:comment><comments>http://blog.csdn.net/Cloud_Apex/archive/2006/03/09/619843.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://blog.csdn.net/cloud_apex/comments/commentRss/619843.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=619843</trackback:ping><description>'Scanlines' 
The word 'Scanline' has a slightly different meaning these days to the one I'm used to 
I always took the word 'Scanline' to describe 1 physical horizontal display line on a monitor,
more often these days, when someone talks about a 'Scanline' they are referring to the 
'Horizontal Retrace Interval',
or (in the case of emulators) faking a low scanrate horizontal retrace interval on a high scanrate monitor

To show you what I mean, here's a simplified diagram of how an image i&lt;img src ="http://blog.csdn.net/cloud_apex/aggbug/619843.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Cloud_Apex</dc:creator><title>summaries of keyboard</title><link>http://blog.csdn.net/Cloud_Apex/archive/2006/02/24/608860.aspx</link><pubDate>Fri, 24 Feb 2006 23:26:00 GMT</pubDate><guid>http://blog.csdn.net/Cloud_Apex/archive/2006/02/24/608860.aspx</guid><wfw:comment>http://blog.csdn.net/cloud_apex/comments/608860.aspx</wfw:comment><comments>http://blog.csdn.net/Cloud_Apex/archive/2006/02/24/608860.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://blog.csdn.net/cloud_apex/comments/commentRss/608860.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=608860</trackback:ping><description>i8048

Although most set two make codes are only one-byte wide, there are a handfull of "extended keys" whose make codes are two or four bytes wide.  These make codes can be identified by the fact that their first byte is E0h.  

you won't always have to use lookup tables to figure out a key's break code--certain relationships do exist between make codes and break codes.  Most set two break codes are two bytes long where the first byte is F0h and the second byte is the make code for that key&lt;img src ="http://blog.csdn.net/cloud_apex/aggbug/608860.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Cloud_Apex</dc:creator><title>mouse  keboard</title><link>http://blog.csdn.net/Cloud_Apex/archive/2006/02/24/608489.aspx</link><pubDate>Fri, 24 Feb 2006 16:23:00 GMT</pubDate><guid>http://blog.csdn.net/Cloud_Apex/archive/2006/02/24/608489.aspx</guid><wfw:comment>http://blog.csdn.net/cloud_apex/comments/608489.aspx</wfw:comment><comments>http://blog.csdn.net/Cloud_Apex/archive/2006/02/24/608489.aspx#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://blog.csdn.net/cloud_apex/comments/commentRss/608489.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=608489</trackback:ping><description>mouse:

http://www.computer-engineering.org/ps2mouse/

http://www.ardent-tool.org.uk/ohland/mouse.html

keboard:

http://www.computer-engineering.org/ps2keyboard/

http://www.beyondlogic.org/keyboard/keybrd.htm
&lt;img src ="http://blog.csdn.net/cloud_apex/aggbug/608489.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Cloud_Apex</dc:creator><title>寻求pci 文档</title><link>http://blog.csdn.net/Cloud_Apex/archive/2006/02/20/603719.aspx</link><pubDate>Mon, 20 Feb 2006 18:39:00 GMT</pubDate><guid>http://blog.csdn.net/Cloud_Apex/archive/2006/02/20/603719.aspx</guid><wfw:comment>http://blog.csdn.net/cloud_apex/comments/603719.aspx</wfw:comment><comments>http://blog.csdn.net/Cloud_Apex/archive/2006/02/20/603719.aspx#Feedback</comments><slash:comments>4</slash:comments><wfw:commentRss>http://blog.csdn.net/cloud_apex/comments/commentRss/603719.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=603719</trackback:ping><description>请问各位谁有有关pci总线的文档，是比较详细介绍pci总线及其编程的文档，我在网上找过一段时间，没找到什么好的，求救啊！

或者哪位熟悉pci编程的，能否传授些知识来，我将感激不尽啊
&lt;img src ="http://blog.csdn.net/cloud_apex/aggbug/603719.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Cloud_Apex</dc:creator><title>关于IDE DMA的简单说明.</title><link>http://blog.csdn.net/Cloud_Apex/archive/2006/02/20/603640.aspx</link><pubDate>Mon, 20 Feb 2006 16:48:00 GMT</pubDate><guid>http://blog.csdn.net/Cloud_Apex/archive/2006/02/20/603640.aspx</guid><wfw:comment>http://blog.csdn.net/cloud_apex/comments/603640.aspx</wfw:comment><comments>http://blog.csdn.net/Cloud_Apex/archive/2006/02/20/603640.aspx#Feedback</comments><slash:comments>2</slash:comments><wfw:commentRss>http://blog.csdn.net/cloud_apex/comments/commentRss/603640.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=603640</trackback:ping><description>关于IDE DMA的简单说明.&lt;img src ="http://blog.csdn.net/cloud_apex/aggbug/603640.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Cloud_Apex</dc:creator><title>Apex中DMA的代码.代码主要来自LINUX.:)其实这些代码已经都比较成熟了.</title><link>http://blog.csdn.net/Cloud_Apex/archive/2006/02/18/602314.aspx</link><pubDate>Sat, 18 Feb 2006 23:02:00 GMT</pubDate><guid>http://blog.csdn.net/Cloud_Apex/archive/2006/02/18/602314.aspx</guid><wfw:comment>http://blog.csdn.net/cloud_apex/comments/602314.aspx</wfw:comment><comments>http://blog.csdn.net/Cloud_Apex/archive/2006/02/18/602314.aspx#Feedback</comments><slash:comments>3</slash:comments><wfw:commentRss>http://blog.csdn.net/cloud_apex/comments/commentRss/602314.aspx</wfw:commentRss><trackback:ping>http://tb.blog.csdn.net/TrackBack.aspx?PostId=602314</trackback:ping><description>DMA代码.&lt;img src ="http://blog.csdn.net/cloud_apex/aggbug/602314.aspx" width = "1" height = "1" /&gt;</description></item></channel></rss>