On Mon, Oct 08, 2007 at 12:35:52PM -0500, David Young wrote:David, You're aware that many of the "microcoded" devices we support are actually instances of full general-purpose CPU architectures, and that their vendors call their software load "microcode" simply as a matter of convention? This has been the case for many, many years (look at "isp" as an example, or "ti" or "bge" -- noting that the only real difference with bge is that it loads a *default* software image at power-up, but the driver knows how to load a new image). Even the special-purpose CPUs like 53c8xx or the Adaptec SCSI "sequencers" are certainly as flexible as many simple microcontrollers -- and we provide toolchains for many of these in our own tree! I do not believe that it is reasonable to draw a distinction between programmable, DMA-capable devices as you are doing. Thor
| Greg Kroah-Hartman | [PATCH 002/196] Chinese: rephrase English introduction in HOWTO |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
| Linus Torvalds | Re: 2.6.25-rc2 System no longer powers off after suspend-to-disk. Screen becomes g... |
git: | |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Ray Lee | Re: [BUG] New Kernel Bugs |
