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.
This question deals with device mounting - mapping a mount point 'back' to a device driver.
I have a running Beagleboard utilizing Angstrom distribution RFS via NFS on my Slackware (12.1) based laptop. I can access the 'data' partition (1) of an on-board SD via /media/card mount point. My goal is to pare down the RFS (from the ~280MB), making it as small as possible with the minimum drivers installed to get at key HW, such as the SD.
I successfully created a new 'teeny' RFS with minimum capability & hit a road block trying to install SD support. Going back to the Angstrom RFS, I could not determine a mount point in (/dev) and which kernel driver(s) are required. Since the SD can be removed, I'm assuming it is a 'hotplug' device thus handled by UDEV? I found SD references in UDEV related scripts but could not find mention of a specific device driver.
I'm able to build the kernel (2.6.29)/drivers & thus observe diagnostics when the drivers are installed; I did this for the SD/MMC related drivers that are built-in to the kernel. I did not see any diagnostic output - even though I can get at the card as mentioned above.
I'm able to wade thru /proc & /sys & observe SD/MMC references but I'm not expert make the mount point linkage - my goal is to find (and install) the required driver for SD access. I can even bypass the hot-plug capability for my environment.