Re: [PATCH libpciaccess 1/2] linux sysfs: retrieve vendor, device... info via separate sysfs files

2017-01-11 Thread Emil Velikov
On 11 January 2017 at 15:59, Adam Jackson wrote: > On Wed, 2017-01-11 at 11:16 +, Emil Velikov wrote: >> Anyone ? > > Merged 1/2: > > remote: I: patch #125069 updated using rev > 73db249c4b1eb91e0df27a1045bea344371dd2ca. > remote: I: 1 patch(es) updated to state Accepted. > To ssh://git.freed

Re: [PATCH libpciaccess 1/2] linux sysfs: retrieve vendor, device... info via separate sysfs files

2017-01-11 Thread Adam Jackson
On Wed, 2017-01-11 at 11:16 +, Emil Velikov wrote: > Anyone ? Merged 1/2: remote: I: patch #125069 updated using rev 73db249c4b1eb91e0df27a1045bea344371dd2ca. remote: I: 1 patch(es) updated to state Accepted. To ssh://git.freedesktop.org/git/xorg/lib/libpciaccess 099489b..73db249 master

Re: [PATCH libpciaccess 1/2] linux sysfs: retrieve vendor, device... info via separate sysfs files

2017-01-11 Thread Emil Velikov
On 16 December 2016 at 19:10, Emil Velikov wrote: > On 1 December 2016 at 18:17, Emil Velikov wrote: >> From: Emil Velikov >> >> Currently the kernel does not expose the revision file. With that about >> to change (due in 4.10) we can read all the information required from >> separate files and

Re: [PATCH libpciaccess 1/2] linux sysfs: retrieve vendor, device... info via separate sysfs files

2016-12-16 Thread Emil Velikov
On 1 December 2016 at 18:17, Emil Velikov wrote: > From: Emil Velikov > > Currently the kernel does not expose the revision file. With that about > to change (due in 4.10) we can read all the information required from > separate files and avoid opening the config one. > > The latter has the [nega

[PATCH libpciaccess 1/2] linux sysfs: retrieve vendor, device... info via separate sysfs files

2016-12-01 Thread Emil Velikov
From: Emil Velikov Currently the kernel does not expose the revision file. With that about to change (due in 4.10) we can read all the information required from separate files and avoid opening the config one. The latter has the [negative] side effect of waking up the device, which in some cases