Search Linux Wireless

Re: [PATCH] bcma: support for PCIe Gen 2 as host platform

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

 



On 6 July 2014 14:19, Arend van Spriel <arend@xxxxxxxxxxxx> wrote:
> On 06-07-14 13:11, Rafał Miłecki wrote:
>> Signed-off-by: Rafał Miłecki <zajec5@xxxxxxxxx>
>> ---
>> I got reply from Bjorn, that we should *not* depend on PCI_EXP_LNKCAP:
>> http://marc.info/?l=linux-pci&m=140457671930896&w=2
>>
>> So the change since RFC is adding a list of PCIe 1.0 and 2.0 devices.
>> Use PCI_EXP_LNKCAP only as a fallback, in case someone tries sth like:
>> echo "14e4 4360" > /sys/bus/pci/drivers/bcma-pci-bridge/new_id
>
> Do you have to know this before or after enumerating the cores? They
> have a different core id, right?

Sure, having a list of cores would allow me to determine PCIe revision.

Unfortunately right now we have only this single bcma_bus_register
call that does both: scanning and initialization. I'd need to first
scan cores, then determine PCIe revision and finally initialize cores.

I wonder if I could try to use bcma_bus_scan_early that was developer
for SoC needs...
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux