Hi Kumar,
Kumar Gala writes:
> As Arnd mentioned you would have something like:
>
> pci {
> pcie@0 {
> reg = <0 0 0 0 0>;
> #interrupt-cells = <1>;
> #size-cells = <2>;
> #address-cells = <3>;
> device_ty
On Oct 7, 2014, at 6:44 PM, Kalle Valo wrote:
> Andy Lutomirski writes:
>
>> Perhaps unsurprisingly, the OpenWRT patch that enables it to work for
>> real (by shoving a file into /lib/firmware that's contains a copy of
>> data read from flash) hasn't made it upstream. I assume that the
>> pur
Andy Lutomirski writes:
> Perhaps unsurprisingly, the OpenWRT patch that enables it to work for
> real (by shoving a file into /lib/firmware that's contains a copy of
> data read from flash) hasn't made it upstream. I assume that the
> purpose of this discussion is to settle on a real solution.
As far as I'm aware there's no unique identifier in the silicon. It's
all in the OTP or flash.
The NIC comes up with a standard MAC address, the same for all NICs in
the family.
-a
___
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infrad
On Fri, Oct 3, 2014 at 9:42 AM, Arnd Bergmann wrote:
> On Friday 03 October 2014 17:25:13 Mark Rutland wrote:
>> > From a system design point, it's still horrible that you have to use
>> > DT for a device that is on a discoverable bus like PCI, but as you
>> > describe,
>> > the reality is that p
On Friday 03 October 2014 17:25:13 Mark Rutland wrote:
> > From a system design point, it's still horrible that you have to use
> > DT for a device that is on a discoverable bus like PCI, but as you describe,
> > the reality is that products are shipping that use ath10k PCI devices
> > without this
On Fri, Oct 3, 2014 at 8:29 AM, Arnd Bergmann wrote:
> On Thursday 02 October 2014 12:05:27 Andy Lutomirski wrote:
>> On 10/02/2014 06:44 AM, Kalle Valo wrote:
>> > Hi Mark,
>> >
>> > Mark Rutland writes:
>> >
>> >>> ath10k is a wireless driver for Qualcomm Atheros 802.11ac hardware and
>> >>> lo
> From a system design point, it's still horrible that you have to use
> DT for a device that is on a discoverable bus like PCI, but as you describe,
> the reality is that products are shipping that use ath10k PCI devices
> without this data in them.
I'd see any DT property for this as a workaroun
On Thursday 02 October 2014 12:05:27 Andy Lutomirski wrote:
> On 10/02/2014 06:44 AM, Kalle Valo wrote:
> > Hi Mark,
> >
> > Mark Rutland writes:
> >
> >>> ath10k is a wireless driver for Qualcomm Atheros 802.11ac hardware and
> >>> located in drivers/net/wireless/ath/ath10k/. Currently it only
On Thu, Oct 2, 2014 at 12:28 PM, Adrian Chadd wrote:
> On 2 October 2014 12:05, Andy Lutomirski wrote:
>> On 10/02/2014 06:44 AM, Kalle Valo wrote:
>>> Hi Mark,
>>>
>>> Mark Rutland writes:
>>>
> ath10k is a wireless driver for Qualcomm Atheros 802.11ac hardware and
> located in drivers/
On 2 October 2014 12:05, Andy Lutomirski wrote:
> On 10/02/2014 06:44 AM, Kalle Valo wrote:
>> Hi Mark,
>>
>> Mark Rutland writes:
>>
ath10k is a wireless driver for Qualcomm Atheros 802.11ac hardware and
located in drivers/net/wireless/ath/ath10k/. Currently it only supports
PCI d
On 10/02/2014 06:44 AM, Kalle Valo wrote:
> Hi Mark,
>
> Mark Rutland writes:
>
>>> ath10k is a wireless driver for Qualcomm Atheros 802.11ac hardware and
>>> located in drivers/net/wireless/ath/ath10k/. Currently it only supports
>>> PCI devices.
>>>
>>> Some of the devices store the calibratio
On Thursday 02 October 2014 17:55:57 Kalle Valo wrote:
>
> > I notice that there are no Qualcomm or Atheros PCI host controller drivers
> > in Linux though, so you first have to write a driver that allows probing
> > the PCI bus, and get the binding reviewed for that before you can add
> > it to t
On Thu, Oct 02, 2014 at 02:44:26PM +0100, Kalle Valo wrote:
> Hi Mark,
>
> Mark Rutland writes:
>
> >> ath10k is a wireless driver for Qualcomm Atheros 802.11ac hardware and
> >> located in drivers/net/wireless/ath/ath10k/. Currently it only supports
> >> PCI devices.
> >>
> >> Some of the devi
Arnd Bergmann writes:
> On Thursday 02 October 2014 16:47:48 Kalle Valo wrote:
>> >
>> > When you know the PCI bus/device/function ID of the device, you can put
>> > a device node in the dts file that corresponds to the PCI dev, and you
>> > can find the of_node pointer from pci_dev->dev.of_node.
On Thursday 02 October 2014 16:47:48 Kalle Valo wrote:
> >
> > When you know the PCI bus/device/function ID of the device, you can put
> > a device node in the dts file that corresponds to the PCI dev, and you
> > can find the of_node pointer from pci_dev->dev.of_node.
>
> For me that's easier sa
Arnd Bergmann writes:
> On Thursday 02 October 2014 16:14:43 Kalle Valo wrote:
>> Hi Device Tree gurus,
>>
>> ath10k is a wireless driver for Qualcomm Atheros 802.11ac hardware and
>> located in drivers/net/wireless/ath/ath10k/. Currently it only supports
>> PCI devices.
>>
>> Some of the devic
Hi Mark,
Mark Rutland writes:
>> ath10k is a wireless driver for Qualcomm Atheros 802.11ac hardware and
>> located in drivers/net/wireless/ath/ath10k/. Currently it only supports
>> PCI devices.
>>
>> Some of the devices store the calibration data to the host flash and the
>> bootloader reads t
Hi,
> ath10k is a wireless driver for Qualcomm Atheros 802.11ac hardware and
> located in drivers/net/wireless/ath/ath10k/. Currently it only supports
> PCI devices.
>
> Some of the devices store the calibration data to the host flash and the
> bootloader reads the data from the flash. And now we
On Thursday 02 October 2014 16:14:43 Kalle Valo wrote:
> Hi Device Tree gurus,
>
> ath10k is a wireless driver for Qualcomm Atheros 802.11ac hardware and
> located in drivers/net/wireless/ath/ath10k/. Currently it only supports
> PCI devices.
>
> Some of the devices store the calibration data to
Hi Device Tree gurus,
ath10k is a wireless driver for Qualcomm Atheros 802.11ac hardware and
located in drivers/net/wireless/ath/ath10k/. Currently it only supports
PCI devices.
Some of the devices store the calibration data to the host flash and the
bootloader reads the data from the flash. And
Kalle Valo writes:
> ath10k is a wireless driver for Qualcomm Atheros 802.11ac hardware and
> located in drivers/net/wireless/ath/ath10k/. Currently it only supports
> PCI devices.
Great, I used an old address:
5.1.0 - Unknown address error 550-'5.1.6 :
Recipient address rejected: User has mov
Hi Device Tree gurus,
ath10k is a wireless driver for Qualcomm Atheros 802.11ac hardware and
located in drivers/net/wireless/ath/ath10k/. Currently it only supports
PCI devices.
Some of the devices store the calibration data to the host flash and the
bootloader reads the data from the flash. And
23 matches
Mail list logo
