Programming from the Ground Up Book - Patches: patch #2591, Data Bus Clarifications
You are not allowed to post comments on this tracker with your current authentication level.
patch #2591: Data Bus Clarifications
Submitter: | None | ||
Submitted: | Thu 05 Feb 2004 09:48:17 PM UTC | ||
Category: | None | Priority: | 1 - Later |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Email: | -email is unavailable- |
Open/Closed: | Open |
Sat 20 Mar 2004 06:45:23 PM UTC, comment #1: |
Matt Robineau <vexer> |
Thu 05 Feb 2004 09:48:17 PM UTC, original submission:
There was a couple of things in chapter 2 I think it would be worth to
(page7, 2nd paragrapgh). Right before, however, it is said that the CPU
and CPU. But because of that the sentence "On x86 processors, a byte is
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Powered by Savane 3.13-758e.
Corresponding source code
Quoted:
-------------
It made me wonder why the
processor, which until now was something kind of independent,
determines the size of the cells and not, say, the memory manufacturer.
-------------
The reason for this, IMO, is that they need a standard. Think of how much extra work the cpu would have to do to figure out how big the memory sizes are. Mixing different memory stick manufacturers would create havoc on the cpu. So instead, the cpu decides that a byte is 0 to 255 then it knows for certain that when it checks memory, regardless of the manufacturer, it knows where and how much.