>>
>> Hi Bjorn,
>>I'm reworking this patch, but found some strange info about vpd serial
>> number.
>> I have two x86 machines, they almost have the same hardware topology. But by
>> lspci,
>> I found two different Broadcom BCM5709 NIC in different machine have the
>> same vpd serial
>> numb
On Mon, Jul 29, 2013 at 9:46 PM, Yijing Wang wrote:
>> I'm not sure this is implemented at the correct place. The idea of
>> using the serial number to detect card swaps is not really specific to
>> pciehp. I know the Device Serial Number capability is defined in the
>> PCIe spec, but it doesn't
> I'm not sure this is implemented at the correct place. The idea of
> using the serial number to detect card swaps is not really specific to
> pciehp. I know the Device Serial Number capability is defined in the
> PCIe spec, but it doesn't *require* any PCIe functionality, and
> there's no reaso
Hi Bjorn,
Thanks for your review and comments!
>
> I'm not sure this is implemented at the correct place. The idea of
> using the serial number to detect card swaps is not really specific to
> pciehp. I know the Device Serial Number capability is defined in the
> PCIe spec, but it doesn't *r
On Fri, Jul 12, 2013 at 3:32 AM, Yijing Wang wrote:
> If device was removed from slot and reinsert a new device during
> suspend, pciehp can not identify the physical device change now.
> So the old driver .resume() method will be called for the new device,
> this is bad. If device support device
If device was removed from slot and reinsert a new device during
suspend, pciehp can not identify the physical device change now.
So the old driver .resume() method will be called for the new device,
this is bad. If device support device serial number capability,
we can identify this by DSN. So the
6 matches
Mail list logo
