Sponsored links

Valid XHTML 1.0!
Valid CSS!

Product: Book - Paperback
Title: Linux Device Drivers, 3rd Edition
Publisher: O'Reilly
Authors: Jonathan Corbet, Alessandro Rubini, Greg Kroah-Hartman
Rating: 1/5
Customer opinion - 1 stars out of 5
OK reference. Bad tutorial ...

Before starting let me assure you that I had written SCSI drivers for SVR4 and 4.2. I had also done some proprietary drivers for *BSDs earlier during undergrad/grad years.
After reading all the reviews and all the ravings about this book, I made the mistake of spending my money on it! Alas! What a waste. Its like one gigantic piece of mish-mash-mess. All the information might be in there (who knows). But, finding out the correct info is almost impossible! The scull driver is a joke.
Another irritating thing about the book is that it attempts to throw all sorts of info at you, all at the same time! Guys, take a break. Present information, one at a time, and only when needed.
Essentially, I was trying to write a driver to read information off my Nikon F100 onto my TP600 running Mandrake 8.0. And life was miserable till I finally started digging through some other driver code that you get with the kernel sources. Gosh, that made life so simple.
But, when I first read this book, I was almost ready to give up writing Linux drivers. I didn't know where to start and where I would end up! I was lost, confused, and felt utterly hopeless.
Also, I wondered if the other guys who had raved about this book were:1. the authors and their friends?2. guys who had no clue what they were talking/writing about?3. guys who were happy to see that there was a book on Linux drivers, but neither bought nor read it!
So, don't trust these reviews. This is one heck of a horrible book that you should most definitely stay away from. Cause if you read, you would never be able to write any useful drivers.
Read the source.

Product: Book - Paperback
Title: Programming .NET Components
Publisher: O'Reilly
Authors: Juval Lowy
Rating: 5/5
Customer opinion - 5 stars out of 5
A real gem of a book

After a very long time I have come across a book that is really fabulous. Most of the programming books are too bulky and they waste all the pages in explaining only the documentation rather than the architecture. Most of this documentaion can be obtained on the web. This book explains the principles and the architecture behind all the commonly used .net concepts. I highly recommend this book. However, do not buy this book if you are planning to learn .net and have never used it before. This book caters to programmers who have had at least some programming experience in .net previously.

Product: Book - Hardcover
Title: Discrete-Time Signal Processing (2nd Edition)
Publisher: Prentice Hall
Authors: Alan V. Oppenheim, Ronald W. Schafer, John R. Buck
Rating: 4/5
Customer opinion - 4 stars out of 5
The DSP Bible

As others have said, this is the DSP bible. I have worked in the field of DSP as a post-grad student, lecturer ("professor") and an R&D engineer for over 10 years now and this book is in my "must-have" collection. It is the book I learnt my DSP from; it is the book I have taught DSP from; it is a very good reference book for the practicioner.
Having said that, I should also point out what I believe this book is not (and why it gets only 4 stars) : it is not a good book for self-learning. If this is what you are after, I recommend Rick Lyons' book "Understanding Digital Signal Processing" (five stars from me).
If you are a mechanical engineer learning DSP, I suggest asking your local Bruel & Kjaer representative if he'll give you a copy of Bob Randall's "Frequency Analysis" published by B&K (ISBN 87 87355 07 8; "only" 3.5 stars, but 4.5 stars if you're a mechanical engineer).

Product: Book - Paperback
Title: C++ Primer (4th Edition)
Publisher: Addison-Wesley Professional
Authors: Stanley B. Lippman, Josée Lajoie, Barbara E. Moo
Rating: 5/5
Customer opinion - 5 stars out of 5
Good book, not for dummies

When I was first using C++, I figured, "This book isn't working for me because I lack knowledge of C and overall programming rules." However, now that I know enough C++ to get me by, I realize that this book couldn't have worked for me at any point. It's 1300 pages long, so forget reading it sequentially, so one is left using the thing as a reference guide. But the amount of time I have spent wading through, for example, its abysmally bad section on class inheritance ("This, boys and girls, is a subclass. We'll just draw a fancy picture, but not tell you how to use them; we'll leave that as an exercise for the student") is enough for me to have authored a better work. And I don't believe I have encountered a worse index in any reference work ever: indiscriminate when it's not just plain wrong, finding an entry on a subject you're interested in is cause for celebration, while finding actual information on that topic within the book proper should merit a trip to Vegas. This book, unsatisfied with making me hate itself, made me hate the entire C++ language. Do not buy this book; buying a reference guide on maintaining your muffler is likely to teach you more about the language.