Searched hist:"0 d4d72bf" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/drivers/net/wireless/ath/ath6kl/ |
| H A D | target.h | 0d4d72bf Mon Nov 14 11:30:39 CST 2011 Kalle Valo <kvalo@qca.qualcomm.com> ath6kl: add board address to struct ath6kl_hw
This is to make it configurable by firmware IEs. Also determine if we need
to write or read the board address to the chip by checking if board address
is set or not.
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
0d4d72bf Mon Nov 14 11:30:39 CST 2011 Kalle Valo <kvalo@qca.qualcomm.com> ath6kl: add board address to struct ath6kl_hw
This is to make it configurable by firmware IEs. Also determine if we need
to write or read the board address to the chip by checking if board address
is set or not.
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
|
| H A D | init.c | 0d4d72bf Mon Nov 14 11:30:39 CST 2011 Kalle Valo <kvalo@qca.qualcomm.com> ath6kl: add board address to struct ath6kl_hw
This is to make it configurable by firmware IEs. Also determine if we need
to write or read the board address to the chip by checking if board address
is set or not.
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
0d4d72bf Mon Nov 14 11:30:39 CST 2011 Kalle Valo <kvalo@qca.qualcomm.com> ath6kl: add board address to struct ath6kl_hw
This is to make it configurable by firmware IEs. Also determine if we need
to write or read the board address to the chip by checking if board address
is set or not.
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
|
| H A D | core.h | 0d4d72bf Mon Nov 14 11:30:39 CST 2011 Kalle Valo <kvalo@qca.qualcomm.com> ath6kl: add board address to struct ath6kl_hw
This is to make it configurable by firmware IEs. Also determine if we need
to write or read the board address to the chip by checking if board address
is set or not.
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
0d4d72bf Mon Nov 14 11:30:39 CST 2011 Kalle Valo <kvalo@qca.qualcomm.com> ath6kl: add board address to struct ath6kl_hw
This is to make it configurable by firmware IEs. Also determine if we need
to write or read the board address to the chip by checking if board address
is set or not.
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
|