User talk:Kmcguire/Quick And Dirty Device Management

Conflicting Edits

Okay, what was wrong with my finishing of your overview? I thought it was a nice finish, since you started with the magic energy balls and stuff. Shouldn't a wiki have some humor? - Alboin

You edited it while I was editing it. I pushed edit and a few minutes later you edited, and about twenty minutes later I pushed save and it over wrote it. I only noticed it after it happened, but figured I would stick it back in on the next save if you had not. I still have a lot more to push onto the end of it. - kmcguire

Oh......sorry then.......this is why I shouldn't edit the wiki at midnight.....bad things happen..... If you have more to add to the end you can just toss mine then and do what you were planning. I wasn't aware that anyone else was working on it, so I figured it needed more than a sentence. - Alboin

Use of "Motherboard"

The document suggests that you need a driver for the motherboard (which pretends to be a bus). This is rather confusing as:

• the motherboard is actually a collection of devices and buses
• the motherboard should be transparent to the kernel (and for most x86s, it is)

The processor is hooked up to the system bus according to the intel architecture, so kernels do not need to worry about the top-level bus (or buses, if you want to include the processor's on chip buses) as it is defined. Most buses beyond that are made transparent by the bios and need no specific modifications. Hence what is referred to as 'the motherboard driver' is for one part integral to the kernel, while the second part is a collection of chip drivers (PIT, APIC, PC speaker, PCI, etc, etc). I'd recommend removing the motherboard=bus analogy as its bad for the reasons above - Combuster 06:32, 26 March 2007 (CDT)

You're recommendation is accepted by me, and as the original author I will made amendments to my local article from this copy then and push it back. - kmcguire