Thank you so much 
All this in answer to the following question so I dont get taken wrong: “who
would you hire especially in a fast moving chip company”, someone that knows
a lil bit about some kernel API having written *a few* drivers or a thorough
OS/ comp arch expert that understands the *whys* and not necessarily the
*hows* of *a particular OS* and has a good understanding of software
engineering. I m not trying to answer this question:)
As a --sidenote–, parallel programming doesnt start with pNp management in
some driver code. There is volumes of research that takes place on parallel
programming including special languages that are tailored for them. But I
guess end of day it is an individuals choice:
“would you want to sit and code using pthread in a monotonous language like
C” or “research how to better split an incoming serial algorithm at runtime
into a parallel algorithm”. For the former 30 years of experience will do
you wonders.
banks
wrote in message news:xxxxx@ntdev…
> Don,
>
>> I will add you to my list of people who I ask to please tell me the
>> products that you work on, so I > can be sure to avoid them and tell my
>> customers to.
>
> I am almost sure that this stupid post was made by someone who has not
> written a SINGLE driver in his entire life, so that I could not even be
> bothered to reply to it - anyone who ever wrote drivers knows that it is
> so much more than “picking up an API” , so that it just does not even make
> sense to explain to this guy what kernel-mode programming is all about.
> After all, he is unaware even of the fact that, in actuality, there are
> not that many drivers that deal directly with IO registers
> (i.e. only the lowest-level drivers on their respective stacks), which
> makes me believe that the whole concept of driver stacks is a mystery for
> him…
>
> Anton Bassov
>