<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Monitoring gadget events or g_ether events to run custom ifup script in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Monitoring-gadget-events-or-g-ether-events-to-run-custom-ifup/m-p/300673#M37787</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Kevin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What board are you using?, because&amp;nbsp; I have seen in the schematics of the i.MX6Solo EVK that the USB OTG share pins with the USB&amp;nbsp; Host so you always begin with the device down, to avoid a hardware issue. If this is the case we can test in a WandBoard. to see if the problem persist.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Jaime&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 06 May 2014 14:30:42 GMT</pubDate>
    <dc:creator>jamesbone</dc:creator>
    <dc:date>2014-05-06T14:30:42Z</dc:date>
    <item>
      <title>Monitoring gadget events or g_ether events to run custom ifup script</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Monitoring-gadget-events-or-g-ether-events-to-run-custom-ifup/m-p/300671#M37785</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm trying to find where in linux i would be able to setup the network interface for g_ether. Basically I want to run avahi-autoipd and dhcpd on the usb0 interface when it comes up. The problem is that linux isn't as transparent about how all this things are supposed to work. I worked with wince previously and what I want to do was really simple registry options...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So in my /etc/network/interfaces I have set usb0 as manual with custom scripts for up/down.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;allow-howplug usb0&lt;/P&gt;&lt;P&gt;iface usb0 inet manual&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; up /path/to/script&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; down /path/to/script&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I plug in my device to a host pc, neither is run. I guess i don't really understand how g_ether acts as a network interface since it doesn't seem to know its available, and doesn't run ifup for it. If i run ifup usb0 the scripts will run.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm thinking i can create a udev rule, when the usb is plugged in, to run ifup usb0 and ifdown usb0 depending on the state.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help would be much appreciated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Apr 2014 15:58:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Monitoring-gadget-events-or-g-ether-events-to-run-custom-ifup/m-p/300671#M37785</guid>
      <dc:creator>kevin_chaves</dc:creator>
      <dc:date>2014-04-21T15:58:42Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring gadget events or g_ether events to run custom ifup script</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Monitoring-gadget-events-or-g-ether-events-to-run-custom-ifup/m-p/300672#M37786</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There might be an issue with our otg driver, or board... I'm not sure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It seems regardless of whether or not I've plugged the usb in, the device is always down. That might be why allow-hotplug doesn't work?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;# cat carrier &lt;/P&gt;&lt;P&gt;cat: read error: Invalid argument&lt;/P&gt;&lt;P&gt;# cat operstate &lt;/P&gt;&lt;P&gt;down&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Apr 2014 22:01:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Monitoring-gadget-events-or-g-ether-events-to-run-custom-ifup/m-p/300672#M37786</guid>
      <dc:creator>kevin_chaves</dc:creator>
      <dc:date>2014-04-21T22:01:39Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring gadget events or g_ether events to run custom ifup script</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Monitoring-gadget-events-or-g-ether-events-to-run-custom-ifup/m-p/300673#M37787</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Kevin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What board are you using?, because&amp;nbsp; I have seen in the schematics of the i.MX6Solo EVK that the USB OTG share pins with the USB&amp;nbsp; Host so you always begin with the device down, to avoid a hardware issue. If this is the case we can test in a WandBoard. to see if the problem persist.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Jaime&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 May 2014 14:30:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Monitoring-gadget-events-or-g-ether-events-to-run-custom-ifup/m-p/300673#M37787</guid>
      <dc:creator>jamesbone</dc:creator>
      <dc:date>2014-05-06T14:30:42Z</dc:date>
    </item>
  </channel>
</rss>

