Good books?

[Tilman Baumann]

Same with the stupid book 'Messen Steuern und Regeln mit ARM- 
Mikorontrollern' from Franzis.
They concentrate on Linux describe in detail how to connect to the  
linux Telnet port (WTF!?) how to write IP servers and how to use the  
build system.
Or how to write 'hello world' in c and perl. And how to use ifconfig...

Not a single word how to connect any hardware, sensors or whatsoever!
Really disappointing. Some platform have more or less generic  
interfaces to use GPIO pins from userspace (like AVR32 Linux). But  
they are far from standard and do not look like a particular bright  
idea to me. :)

Really disappointing. A book that describes these topic for the  
typical arm7 or xscale platforms would interest me very much. If  
someone has ever seen one...

Am 27.06.2008 um 17:34 schrieb Joe Pfeiffer:

> Crane, Matthew writes:
>> "building embedded Linux systems" o'rielly.
>>
>> I think embedded is really just the code that is close to the
>> hardware.  Daemons, services, aren't embedded.  Modules if they're
>> interacting with the hardware.  Not all will.
>
> If that's the definition the O'Reilly book is using (I haven't read
> it), it's *really* idiosyncratic.  Normally, an "embedded" system is
> one in which the computer is being used as the control of some device,
> but the computer isn't the "point" of the device.  So, for instance,
> the engine management computer in an automobile is embedded; a modern
> stereo with digital tuning has a computer driving its display that's
> embedded; the computer driving your microwave oven is embedded.  A PC
> isn't an embedded system, but the CPU in the keyboard is.
>
> What you're describing sounds a lot more like device drivers.
>
>> Maybe you want to look more at a kernel book.  I expect the hardware
>> level code is battlescared enough that one would expect a bit of a
>> learning curve to get into the details.  I dunno though..
>
> The O'Reilly books on Linux device drivers, and on the kernel, are
> both outstanding.
>