As you said in a e-mail before, and also mentioned in the very
interesting book "Linux Device Drivers" By Alessandro Rubini & Jonathan
Corbet , things should be done in the most simplest way. The reasons are
both avoid rewriting of code in order to optimize it, and also when
things are small you can control them better and therefore your
hardware is better accesed.
Sorry about this little note from a kernel newbie to all the developers
out there if it makes you feel offended in some way.
> Submitting dprintk() seems like a great starting point. I've also got
> some patches in the archive someone sent that allows you to configure
> out the #! exec stuff
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Oct 07 2002 - 22:01:02 EST