All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Green <andy-/Zus8d0mwwtBDgjK7y7TUQ@public.gmane.org>
To: Roger Quadros <roger.quadros-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
Subject: Re: [RFC PATCH 2/5] OMAP2+: add cpu id register to MAC address helper
Date: Fri, 18 Mar 2011 09:13:04 +0000	[thread overview]
Message-ID: <4D832220.9030704@linaro.org> (raw)
In-Reply-To: <4D831D4B.8090407-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>

On 03/18/2011 08:52 AM, Somebody in the thread at some point said:

>> +	/* mark it as not multicast and outside official 80211 MAC namespace */
>> +
>> +	mac[0] = (mac[0]&  ~1) | 2;

> so here lies the answer to my question "From where do you get the MAC" :)
>
> Is there a guarantee that this MAC will work in all Ethernet setups?

Yeah it's in 80211 spec.  You have to buy the spec, I can't point you to 
it directly, but here is the wikipedia article showing the structure

http://en.wikipedia.org/wiki/MAC_address#Address_details

the random mac addresses generated by the kernel also use this scheme.

-Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: andy@warmcat.com (Andy Green)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 2/5] OMAP2+: add cpu id register to MAC address helper
Date: Fri, 18 Mar 2011 09:13:04 +0000	[thread overview]
Message-ID: <4D832220.9030704@linaro.org> (raw)
In-Reply-To: <4D831D4B.8090407@nokia.com>

On 03/18/2011 08:52 AM, Somebody in the thread at some point said:

>> +	/* mark it as not multicast and outside official 80211 MAC namespace */
>> +
>> +	mac[0] = (mac[0]&  ~1) | 2;

> so here lies the answer to my question "From where do you get the MAC" :)
>
> Is there a guarantee that this MAC will work in all Ethernet setups?

Yeah it's in 80211 spec.  You have to buy the spec, I can't point you to 
it directly, but here is the wikipedia article showing the structure

http://en.wikipedia.org/wiki/MAC_address#Address_details

the random mac addresses generated by the kernel also use this scheme.

-Andy

WARNING: multiple messages have this Message-ID (diff)
From: Andy Green <andy@warmcat.com>
To: Roger Quadros <roger.quadros@nokia.com>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	patches@linaro.org
Subject: Re: [RFC PATCH 2/5] OMAP2+: add cpu id register to MAC address helper
Date: Fri, 18 Mar 2011 09:13:04 +0000	[thread overview]
Message-ID: <4D832220.9030704@linaro.org> (raw)
In-Reply-To: <4D831D4B.8090407@nokia.com>

On 03/18/2011 08:52 AM, Somebody in the thread at some point said:

>> +	/* mark it as not multicast and outside official 80211 MAC namespace */
>> +
>> +	mac[0] = (mac[0]&  ~1) | 2;

> so here lies the answer to my question "From where do you get the MAC" :)
>
> Is there a guarantee that this MAC will work in all Ethernet setups?

Yeah it's in 80211 spec.  You have to buy the spec, I can't point you to 
it directly, but here is the wikipedia article showing the structure

http://en.wikipedia.org/wiki/MAC_address#Address_details

the random mac addresses generated by the kernel also use this scheme.

-Andy

  parent reply	other threads:[~2011-03-18  9:13 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-12 22:50 [RFC PATCH 0/5] OMAP2+ / Panda implementation for async platform_data Andy Green
2011-03-12 22:50 ` Andy Green
2011-03-12 22:50 ` [RFC PATCH 1/5] OMAP2+: Panda introduce async platform data definition Andy Green
2011-03-12 22:50   ` Andy Green
2011-03-13  1:05   ` Greg KH
2011-03-13  1:05     ` Greg KH
2011-03-12 22:50 ` [RFC PATCH 2/5] OMAP2+: add cpu id register to MAC address helper Andy Green
2011-03-12 22:50   ` Andy Green
2011-03-18  8:34   ` Arnd Bergmann
2011-03-18  8:34     ` Arnd Bergmann
2011-03-18  8:49     ` Andy Green
2011-03-18  8:49       ` Andy Green
2011-03-18 14:37     ` Premi, Sanjeev
2011-03-18 14:37       ` Premi, Sanjeev
     [not found]       ` <B85A65D85D7EB246BE421B3FB0FBB593024C3B8670-/tLxBxkBPtCIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2011-03-18 14:47         ` Andy Green
2011-03-18 14:47           ` Andy Green
2011-03-18 14:47           ` Andy Green
     [not found]   ` <20110312225047.27728.1835.stgit-MbR9/eEqKADKkTgpAXvmkg@public.gmane.org>
2011-03-18  8:52     ` Roger Quadros
2011-03-18  8:52       ` Roger Quadros
2011-03-18  8:52       ` Roger Quadros
     [not found]       ` <4D831D4B.8090407-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
2011-03-18  9:13         ` Andy Green [this message]
2011-03-18  9:13           ` Andy Green
2011-03-18  9:13           ` Andy Green
2011-03-12 22:50 ` [RFC PATCH 3/5] OMAP2+:Common CPU DIE ID reading code reads wrong registers for OMAP4430 Andy Green
2011-03-12 22:50   ` Andy Green
2011-03-14 18:12   ` Tony Lindgren
2011-03-14 18:12     ` Tony Lindgren
2011-03-12 22:51 ` [RFC PATCH 4/5] OMAP2+: Set onboard Ethernet MAC address using unique CPU ID data Andy Green
2011-03-12 22:51   ` Andy Green
     [not found] ` <20110312224440.27728.60593.stgit-MbR9/eEqKADKkTgpAXvmkg@public.gmane.org>
2011-03-12 22:51   ` [RFC PATCH 5/5] USBNET: SMSC95XX: if mac set in platform data no need for random one Andy Green
2011-03-12 22:51     ` Andy Green
2011-03-12 22:51     ` Andy Green

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D832220.9030704@linaro.org \
    --to=andy-/zus8d0mwwtbdgjk7y7tuq@public.gmane.org \
    --cc=andy.green-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=roger.quadros-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.