ÈçºÎ¿ªÊ¼Ñ§Ï° Linux ÄÚºË [ת] - C/C++ / ·Ç¼¼ÊõÇø

> Message: 1
> Date: Sat, 24 Apr 2010 11:31:02 +1000
> from: Crossfire <xfire@xware.cx>
> Subject: Re: [coders] New to Kernel programming and device drivers
> To: coders@slug.org.au
> Message-ID: <4BD249D6.7030508@xware.cx>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 21/04/2010 11:14 AM, Tharanga Abeyseela wrote:
>> Thanks Nick. I thought to write a characther driver or a block driver
>> first, then i can move to another level. how about Linux device
>> drivers , understanding the linux kernel book (Orielly), and wrox
>> professional Linux kernel architecture ? iam looking for a book which
>> suits for learner..(step by step guide kind of a document, which
>> explains from the beginning). i wanna right it my own..iam doing this
>> as a pet project.
>
> That's all nice and fine, but you really do need to have a goal when
> trying to do this sort of stuff, and most of the easy targets have
> already been dealt with.
>
> Likewise, assess if what you want to achieve can be in in userspace
> first - coding in userspace is far easier to do, far easier to debug,
> and teaches you a lot about what it is you're trying to achieve in the
> first place without the associated headaches of trying to develop for a
> moving target. A