So sounds as though *maybe* you're saying if "we" edit /etc/modules, and add "g_serial" or "g_ether" or "g_multi". The respective service would start ?
On Mon, May 18, 2015 at 9:31 AM, William Hermans <yyrk...@gmail.com> wrote: > @Robert, ah cool, but the idea was to help this person enable one of the > USB gadget devices via his / her dev machine. As it does not seem as though > he/she has access to a serial debug cable. > > With sysv, I've done this, and know how to go about it, but with systemd . > . . yeah no idea. > > On Mon, May 18, 2015 at 9:27 AM, William Hermans <yyrk...@gmail.com> > wrote: > >> err, wow just realized my noted are riddled with mistakes . . . paths >> are wrong, etc. >> >> On Mon, May 18, 2015 at 9:23 AM, Robert Nelson <robertcnel...@gmail.com> >> wrote: >> >>> On Mon, May 18, 2015 at 11:17 AM, William Hermans <yyrk...@gmail.com> >>> wrote: >>> > Better yet, enable g_serial, or g_ether. >>> > >>> > @Robert, does systemd get in the way when trying to enable either of >>> those >>> > gadget drivers ? I know for me it was pretty easy, but don't think I >>> dd'd >>> > over a Jessie image. Wheezy 7.8 I'm thinking, and all I did in >>> preparation >>> > was comment out the systemd init line in uEnv.txt >>> >>> systemd actually does the right thing, even when it has to wait for us >>> to decide g_multi vs g_ether.... >>> >>> btw, here's how the systemd serial-getty service was enabled for >>> ttyGS0 (without systemctr).. (when we modprobe g_multi and the >>> usb-slave device starts: usb flash, usb ether, & usb serial) >>> >>> cp /lib/systemd/system/serial-getty@.service >>> /etc/systemd/system/serial-getty@ttyGS0.service >>> ln -s /etc/systemd/system/serial-getty@ttyGS0.service >>> /etc/systemd/system/getty.target.wants/serial-getty@ttyGS0.service >>> >>> after g_multi is loaded, systemd correctly fires up the getty service >>> for usb serial... >>> >>> Regards, >>> >>> -- >>> Robert Nelson >>> https://rcn-ee.com/ >>> >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "BeagleBoard" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to beagleboard+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
