Why do some embedded projects shun cross-compiling?
As I’ve been getting into embedded systems I’ve noticed that some projects (Arch Arm and OpenBSD for example) frown upon cross compiling. What is the reasoning for this? Is a cross-compiled binary somehow different from a natively compiled one?
Why do some embedded projects shun cross-compiling?
As I’ve been getting into embedded systems I’ve noticed that some projects (Arch Arm and OpenBSD for example) frown upon cross compiling. What is the reasoning for this? Is a cross-compiled binary somehow different from a natively compiled one?
How would one implement communication between an input device and a PC?
I’m trying to get started on a side project using a mobile device (tablet or smartphone) as an input device to a PC. In its most simplest form, I envision using the mobile device touchscreen to control cursor movement and clicks on the PC. So far I’m targeting Windows machines and either Android or iOS devices (using Xamarin).
How does a user program access a device?
In Linux, from http://www.mulix.org/lectures/intro_to_linux_device_drivers/intro_linux_device_drivers.pdf
What does “host” mean in “… host driver” and “… host adapter”?
From How Linux Works, by Brian Ward, I saw “SCSI Host Adapter”, “SATA Host Driver”, “Disk Driver (sd)”, “CD/DVD Driver (sr)”, “USB Host Driver”, and “USB Storage Driver”.
What does “host” mean in “… host driver” and “… host adapter”?
From How Linux Works, by Brian Ward, I saw “SCSI Host Adapter”, “SATA Host Driver”, “Disk Driver (sd)”, “CD/DVD Driver (sr)”, “USB Host Driver”, and “USB Storage Driver”.
Can a driver running in kernel mode access a port directly?
Based on what I know so far, if I want to create a driver, and want the driver to send data on some port (for example: serial/parallel/USB), my driver will communicate with the port driver, and the port driver is the one that will access the port directly.