Re: [PATCH bluetooth-next 15/18] at86rf230: generate random perm extended address

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Varka,

On Sat, Dec 13, 2014 at 10:28:24AM +0530, Varka Bhadram wrote:
> For CC2520 the extended address is software defined.
> So the default case is possible for CC2520.
> 
> We may need to add ieee802154_random_extended_addr().
> 

ok, this sounds good.

I think if the transceiver chip doesn't support such function it could
be that some board designer for the transceiver place some eeprom on it.



What I mean is somebody builds a CC2520 transceiver board with an
eeprom. The eeprom contains the EUI-64 address. Then we need some
mechanism to connect them (I think the common way is devicetree) to
readout the eeprom and set the perm address.

I think this should not touch the driver layer, so random extended addr
should be fine. The same is for an eeprom which is placed on the dev
board and contains the necessary EUI-64 address information.

This is for some further 802.15.4 work.

- Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-wpan" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux