bare metal
I write my programs on bare metal by flipping switches in time to the processor's 100MHz bus clock.
So you know.
Ads
Monday, May 12, 2008
Subscribe to:
Post Comments (Atom)
skip to main |
skip to sidebar
About Me
Labels
- alarm_clock (5)
- Atlanta (1)
- boat (12)
- cats humor (1)
- comcast (3)
- Congress (5)
- emacs (1)
- food (1)
- garden (9)
- Grammar (1)
- Iran (2)
- moped (10)
- NCW (1)
- OODA (2)
- radish (1)
- robot_overlords (2)
- running (3)
- shave (1)
- squeaky shoes (1)
- squirrel (10)
- systems of systems (1)
- Thought_of_Day (2)
- trampoline (1)
- Venezuela (4)
- voting (1)
- wine (1)
3 comments:
But someone else *implements* the processor and bus though?
I have no idea it means, but I love the way that sentence sounds (the first one).
I've been meaning to ask what you actually meant by this.
This reminds me of a lab in highschool electronics with Dr. Wilkes. An 80386 was mounted on a development board with a monitor program and keypad. x86 CPUs have a single-step mode in which they only execute a single instruction then call an interrupt which jumps back into the monitor program. We could actually set breakpoints and halt programs on the fly, examine register states, edit the data with the monitor program [where data could mean actual data or program instruction "data"], then resume.
Good fun.
Now that I think about it, x86 as an architecture was largely suppressed as a feasible target of study in both undergrad and grad at GT. Sure, it's more complicated than your favorite RISC architecture, but it seems like a kludge that's important enough to spend some time on. Making your CPUs execute x86[-64] fast is rather useful, I'd say.
Post a Comment