--- In "fabianmejia" <>
wrote:
> After your suggestion and some reading, I made the following.
>
> make 7200_config
> make oldonfig
>
> Neither make dep or make bzImage worked. I always get this error:
> "... include/linux/rbtree.h:11:24: #if with no expression"
> And a lot more.
Not sure what is wrong here. Maybe start with a clean unpacked
kernel source and post all the commands that you give and output
that you get and we may be able to help??
> So I used your adc driver as a timer. I suggest if somebody is
> facing the same issue with the time resolution this driver can be
> helpful. In about 15 minutes I took the code from the example you
> provided and created a timer each 5msec.
After thinking about this some more, this probably not a good thing
to with an unmodified driver. The driver does some coalescing of the
sampled data with higher samplerates that will not give the results
that you are after. Also, Linux sceduling will have a big effect on
this. If the timing is critical, there is no substitute for doing it
properly in the kernel. So disregard what I said about that!! :)
> As a homework, I tried to use the code to create my own timer using
> request_irq, writel, readl, etc with no luck.
> Again, I get a lot of errors, starting with this:
> "include/asm/system.h:43: error: parse error before string
> constant"
Did you use the main part of the Makefile that came with the driver,
and just modified as little as necessary to use it with your code.
The error message looks like a symptom of the compiler using the
userland headers instead of the kernel headers. The Makefile has all
the options setup to reference the correct headers, etc. (Note that
I didn't even attempt to set up my own Makefile, the one with the
adc driver was just shamelessly copied from other driver example
from this group)
> Another post helped me with the services question. Thanks for that
> tip. I will start reading about deamons (I hope I can compile
> them).
As mentioned before, there is nothing really special about daemon
programs (as opposed to kernel code whcih needs the above setup). If
you can compile a simple c program, like a "Hello World" or similar,
then you can compile daemon programs aswell. The only main
difference is that daemon programs don't normally exit, they wait
for something, do something and then go back and wait again.
Cheers
Phil
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|