Morti has quit [Remote host closed the connection]
set_ has joined #beagle
<set_>
So, once these boards get ordered, the Capes, what exactly should i know to get it functioning?
<set_>
i2c or uart in .dts format?
<set_>
For instance, if I have to bypass the eeprom on the Capes, UART comm. to and from the BBBW would be correct. Right?
<set_>
10:00!
vd has quit [Ping timeout: 256 seconds]
buzzmarshall has quit [Quit: Konversation terminated!]
Shadyman has quit [Quit: Leaving.]
ikarso has joined #beagle
troth has quit [Ping timeout: 240 seconds]
troth has joined #beagle
ikarso has quit [Quit: Connection closed for inactivity]
zjason` is now known as zjason
buckket has quit [Read error: Connection reset by peer]
buckket has joined #beagle
<jfsimon1981>
Good evening, which solution do you recommand for auto mount (for usb stick) ?
jfsimon1981 has quit [Ping timeout: 256 seconds]
jfsimon1981 has joined #beagle
<jfsimon1981>
Hi
<jfsimon1981>
which solution do you recommand for auto mount (for usb stick) ?
vagrantc has joined #beagle
buzzmarshall has joined #beagle
<zmatt>
depends on what exactly the use-case is I guess
<jfsimon1981>
just mount the only usb port into one same location so a software can write a file into
<jfsimon1981>
also I'd need a mean to check a device was mounted from the c++ code, that's what i'm working on
<zmatt>
I don't see why you'd want automounting in that case, have software mount it before performing the action an unmount it afterwards (so that you know for sure it's safe to remove the usb stick afterwards)
<zmatt>
you can use udev to detect when the usb stick shows up, and use fstab to allow it to be mounted/unmounted by a specific user
<jfsimon1981>
ok thanks
<jfsimon1981>
i did'nt about udev, i'll check it.
<zmatt>
yeah, libudev or various bindings
<jfsimon1981>
thx
<zmatt>
it's also possible to have a systemd service get started when the device shows up
<zmatt>
and use a dependency on a mount unit to have systemd mount the filesystem before running the service and unmount it after it completes
<zmatt>
that's probably the solution I'd use if whatever needs to be done when the usb stick gets inserted can be put into a standalone process that runs only for the duration of that action
<zmatt>
(of course, even if writing the file can't be easily extracted from your main program, you could always just have this service send a message to your main program (e.g. using dbus) telling it that the filesystem is available for writing the file, and the wait for a reply that confirms it's done writing the file)
<zmatt>
lots of solutions exist
vd has joined #beagle
<jfsimon1981>
a simple one in this case, i'll check
<jfsimon1981>
if i can do with udev that'd be all right
<jfsimon1981>
problem is i need to learn and got a short time left in this case to make it work
<jfsimon1981>
let's go i'm on it now
<jfsimon1981>
look good with udev found out a good example, the compiled example kind of does the job
<jfsimon1981>
things are so simple under unix/linux for development
zjason` has joined #beagle
zjason has quit [Ping timeout: 245 seconds]
jfsimon1981 has quit [Remote host closed the connection]