On 22/01/14 00:46, Jordan Justen wrote:
> On Sat, Jan 11, 2014 at 8:54 AM, Emil Velikov
> wrote:
>> All the various window system integration layers duplicate roughly the
>> same code for figuring out device and driver name, pci-id's, etc. Which
>> is sad. So extract it out into a loader util l
On Sat, Jan 11, 2014 at 8:54 AM, Emil Velikov wrote:
> All the various window system integration layers duplicate roughly the
> same code for figuring out device and driver name, pci-id's, etc. Which
> is sad. So extract it out into a loader util lib.
>
> Signed-off-by: Rob Clark
>
> v2 (Emil)
On Mon, Jan 13, 2014 at 12:01:03AM +, Emil Velikov wrote:
> All the various window system integration layers duplicate roughly the
> same code for figuring out device and driver name, pci-id's, etc. Which
> is sad. So extract it out into a loader util lib.
>
> Signed-off-by: Rob Clark
>
>
All the various window system integration layers duplicate roughly the
same code for figuring out device and driver name, pci-id's, etc. Which
is sad. So extract it out into a loader util lib.
Signed-off-by: Rob Clark
v2 (Emil)
* Separate the introduction of libloader from the code de-duplicat
All the various window system integration layers duplicate roughly the
same code for figuring out device and driver name, pci-id's, etc. Which
is sad. So extract it out into a loader util lib.
Signed-off-by: Rob Clark
v2 (Emil)
* Separate the introduction of libloader from the code de-duplicat
