<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>1073</bug_id>
          
          <creation_ts>2011-05-15 02:30:17 +0000</creation_ts>
          <short_desc>beagle-xm: random MAC address</short_desc>
          <delta_ts>2012-04-10 05:02:30 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>Meta-yocto</product>
          <component>configuration</component>
          <version>1.0</version>
          <rep_platform>Beagleboard</rep_platform>
          <op_sys>arm</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard>RFC out to meta-ti (29/Jun/2011)</status_whiteboard>
          <keywords></keywords>
          <priority>Low</priority>
          <bug_severity>enhancement</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Robert Berger">pokylinux</reporter>
          <assigned_to name="Bruce Ashfield">bruce.ashfield</assigned_to>
          <cc>poky.bs.watcher</cc>
    
    <cc>poky.watcher</cc>
    
    <cc>yang.shi</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>13839</commentid>
    <comment_count>0</comment_count>
    <who name="Robert Berger">pokylinux</who>
    <bug_when>2011-05-15 02:30:17 +0000</bug_when>
    <thetext>The beagle-xm issues a random MAC address with each reboot, which makes it a bit &quot;non standard&quot; to work with DHCP.

I don&apos;t know if that&apos;s the right way to go, but one possible solution is here:
http://maxgalemin.blogspot.com/2010/11/patch-for-fixing-random-mac-address-on.html</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>13906</commentid>
    <comment_count>1</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2011-05-19 13:27:22 +0000</bug_when>
    <thetext>Hi Robert, has this kernel patch been pushed upstream?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>13921</commentid>
    <comment_count>2</comment_count>
    <who name="Robert Berger">pokylinux</who>
    <bug_when>2011-05-19 22:43:29 +0000</bug_when>
    <thetext>(In reply to comment #1)
&gt; Hi Robert, has this kernel patch been pushed upstream?

Hi Darren,

Frankly I don&apos;t know. Let me ask around on the various mailing lists. It might be something you should not do in the kernel.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>13922</commentid>
    <comment_count>3</comment_count>
    <who name="Robert Berger">pokylinux</who>
    <bug_when>2011-05-19 22:55:15 +0000</bug_when>
    <thetext>It looks like there is/was something upstream from the Linaro team:

https://bugs.launchpad.net/ubuntu/+source/linux-linaro/+bug/687396

There is also something on openembedded which uses the OMAP&apos;s die ID as a MAC (which I find a neat idea)

http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-October/026240.html</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>14478</commentid>
    <comment_count>4</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2011-06-29 14:23:39 +0000</bug_when>
    <thetext>Sent a mail to oe-core and the meta-ti maintainers for their preference on a solution to this as we don&apos;t want to deviate from where they go with this.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>14479</commentid>
    <comment_count>5</comment_count>
    <who name="Robert Berger">pokylinux</who>
    <bug_when>2011-06-29 14:57:44 +0000</bug_when>
    <thetext>Hi Darren,

Assuming the MAC address comes from u-boot it might be possible to get away without a kernel patch.

I did not try it out on the beagle-xm, but in general u-boot variables can be read from user space - see u-boot/tools/env.

Afterwards a script could be cooked, which patches this u-boot variable into the network config: hwaddress ether &lt;something&gt;

Just a thought at 1:00 am so I might also just be too tired for anything more creative.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>14480</commentid>
    <comment_count>6</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2011-06-29 16:12:06 +0000</bug_when>
    <thetext>There is some debate on how to best resolve this. We will wait for meta-ti to decide on an approach, and then follow that.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>14533</commentid>
    <comment_count>7</comment_count>
    <who name="Robert Berger">pokylinux</who>
    <bug_when>2011-07-04 10:57:39 +0000</bug_when>
    <thetext>Just stumbled across this: 

http://www.electronsonradio.com/2011/07/angstrom-on-the-beagleboard-fixing-your-mac-address/

https://patchwork.kernel.org/patch/263861/ is supposed to be upstream

explanation:

http://fossplanet.com/f10/%5Bmaverick-sru%5D%5Bmaster%5D%5Bti-omap4%5D-%5Bpatch%5D-smsc95xx-generaterandom-mac-address-once-not-every-ifup-73702/

I did not test it, but it looks promising.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>20023</commentid>
    <comment_count>8</comment_count>
    <who name="Darren Hart">dvhart</who>
    <bug_when>2012-04-06 22:12:56 +0000</bug_when>
    <thetext>Bruce, can you (or a delegate) pick this one up - or close it as will not fix?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>20078</commentid>
    <comment_count>9</comment_count>
    <who name="Yang Shi">yang.shi</who>
    <bug_when>2012-04-09 18:40:26 +0000</bug_when>
    <thetext>Checked https://patchwork.kernel.org/patch/263861/, it&apos;s commit f4e8ab7cc4e819011ca6325e54383b3da7a5d130 in mainline. It sounds this commit has been there since 2.6.x.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>20102</commentid>
    <comment_count>10</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2012-04-10 05:02:30 +0000</bug_when>
    <thetext>This one is resolved in the 3.0 and 3.2 kernels, so we can mark this as fixed.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>