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 still don't understand the connection between uboot and kernel when you give it a "console=ttySMX0,115200n8" kernel argument ..
I know that the kernel when it sees that uses the argument as the console instead of the default tty1. But how does it know what serial port on the imx to use?
uboot will use its own independent driver, and this vanishes when the kernel in launched. You were correct about the functionality of the serial hardware earlier when you noted that the bootloader uses that hardware correctly. Your kernel commandline specifies which port to use as the console: 'console=ttySMX0,115200n8'.
I asked earlier whether there is a possibilty to specify, to the driver via kernel commandline arguments, details of the hardware. Did you explore this?