On Saturday, November 20, 2010, Venkatram Tummala <venkatram867@xxxxxxxxx> wrote: > On Fri, Nov 19, 2010 at 11:55 PM, Bond <jamesbond.2k.g@xxxxxxxxx> wrote: > > > On Sat, Nov 20, 2010 at 1:14 AM, John Mahoney <jmahoney@xxxxxxxx> wrote: >> >> Bond I think you are a prime example of someone who walks the line >> between asking legit questions and asking dubious questions. I think >> your intentions are good and you really are trying to learn, but you >> ask far too many questions far too quickly. Also, I think you should > I read that book of device drivers which is ............and read it > for at least many years > and not once many many times.I could not write a single driver out of it. > Which I recently wrote by writing some other "recent docs" and then > with the understanding developed from them. > If there is some thing like my previous question for a structure in > super IO chips such things I do not see commonly being used. > I looked at a similar code in vlc media player and found that such a > structure was not known to many many experienced kernel level > programmers and > they found it difficult to understand. > I think Robert JUST mentioned something about thread hijacking in the previous mail. Sorry to say this guys - i don't see how the docs can help people understand the rules. Even this thread about guidelines is not being followed according to the guidelines. Recursion??? Recursion is just a setup for stack overflow and yes this may be turning into overkill, yet i thicken for the most part this thread has been useful! I guess I will take blame for that one. I should not have used a negative and personal example! I do like Robert's list. If people can follow that list 80 percent of the time we are doing well, there are going to be mistakes, but as long as people are improving I do not see the issue. I think everyone just wants to see this remain a friendly environment, but not a jungle gym slashdot thread. John > > If some one is asking a question via a typedef in a function pointer > or structure initialization which he never found any where else on > this planet other than the kernel then what wrong is he doing.That > book does not covers such things.See it is very good to give lecture > to any one who asked question to do blah blah but to understand his > problem and give a solution to some thing specific is not an easy > thing. > Recent example was my character device question where the driver was > dropping characters out of it. I could not understand the reason > behind it some one even blocked me from his mails and one guy actually > solved that problem. > When you are learning some thing then asking questions even the > silliest ones is not wrong. > At least some one who is asking is attempting his level best( upon his > understanding) to understand irrespective of the fact that community > does not appreciates that. > I did read K R after getting busted here and I do not see any one else > other than me asking such C questions and to the best of my knowledge > I did not found any thing the people who suggest to read K R > themselves do not read that book but will give suggestion to read. > KR was written for C in very old times to help people beginning with > programming or what ever reason it does not cover often the way Data > structures are initialized in kernel specific areas.Or some other > relevant stuff.My point is rather than giving some one such a lecture > it will be better to just make a doc with relevant structs,typedefs > and such other tricks which are used in kernel many a times which > might not be commonly found on the wiki and give a link to that may be > if such a thing is present some one whose questions appear silly would > before asking read that doc and will get his answers from there. > -- > Most of the free documentation and kernel books are not worth reading. > > -- > To unsubscribe from this list: send an email with > "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx > Please read the FAQ at http://kernelnewbies.org/FAQ > > > -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ