Re: lspci memory behind bridge reporting

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

 



Hi!

> I attach a patch with behaviour similar to what you describe. It is based on
> the current master branch of pciutils (hash
> 4a190235224ff6dfe44adbb07ac929afea612acd).

I like the idea, but not much the ifdeffery in your implementation.
I wrote something similar in a little bit more systematic way, please
see commit 41d883cb97f94e844e96b4631a99c3da557cf162.

> I have not altered anything in the tests folder yet as I am not sure about how to run them.

The tests are not automated yet. Just add a configuration space
dump together with the expected output.

				Have a nice fortnight
-- 
Martin `MJ' Mares                          <mj@xxxxxx>   http://mj.ucw.cz/
Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth
Power corrupts; Powerpoint corrupts absolutely.  -- Vint Cerf
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux