Linux - Embedded & Single-board computerThis forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
i have the following custom board:
Freescale ColdFire MCF5307
4MB Flash, with 2.6.36 main line kernel
dm9000e ethernet chip.
I succesfully slightly modified the dm9000.c driver to work with this big endian cpu, ping (in and out) and telnet server are working fine now.
My issue now is that, once launched httpd with a simple index page, refreshing continuosly the page from a browser cause a kind of kernel trap error:
Seems some splinlock issue, issued from inside the dm9000_interrupt routine, the kernel then continue to work, the packet sending also seems to works still, but the network packet receiving is not working anymore. Looking with an oscilloscope, the interrupt signal receving packet is still issued from the dm9000 chip, the /proc/interrupts is showing that the interrupt count still increasing, but the kernel seems not handling it anymore.
I tried to get some help in the kernel mailing list, but there is too much patch/development jub there and i couldn't get any help.