The thing that makes this happen is udev, the Linux machinery that manages devices. It all runs in user space, and it's governed by textfiles in /lib/udev/rules.d and /etc/udev/rules.d . (Remember textfiles? Before XML, when someone told you something was "human-readable," it was a textfile, which actually was.)
The ones in /etc are meant to be local, so you can add new ones. To talk to the Beaglebone, I need to add rules. The details are still magic incantations to me, but Karim gave us a pair that work: 73-beaglebone.rules and 51-android.rules.
After installing them, and getting the udev daemon to re-read its rules, with
sudo udevadm control --reload-rules
plugging in the bone makes /dev/beaglebone-serial appear.
Note: This step, together with all the other basic, beaglebone setup steps I talk about in the next few posts, are documented and implemented here. Clone the repo, then do a make in that directory, and everything should get set up.
I put things in scripts and Makefiles, not just because I'm lazy (which I am), but because doing so forces me to document every picky, little detail. It's on GitHub, so if you're ever reading this, trying it yourself, and find stuff I've missed, fork the repo, fix it, and send me a pull request.
No nit is too small to pick.
Note: This step, together with all the other basic, beaglebone setup steps I talk about in the next few posts, are documented and implemented here. Clone the repo, then do a make in that directory, and everything should get set up.
I put things in scripts and Makefiles, not just because I'm lazy (which I am), but because doing so forces me to document every picky, little detail. It's on GitHub, so if you're ever reading this, trying it yourself, and find stuff I've missed, fork the repo, fix it, and send me a pull request.
No nit is too small to pick.
No comments:
Post a Comment