On Fri, Jun 08, 2012 at 12:16:41PM +0300, Jani Nikula wrote:
>
> Hi Daniel -
>
> On Thu, 07 Jun 2012, Daniel Vetter wrote:
> > I've done an audit of everything which is being set up between the
> > place where drm_pci_agp_init is called currently and where the
> > driver's ->load function is cal
Hi Daniel -
On Thu, 07 Jun 2012, Daniel Vetter wrote:
> I've done an audit of everything which is being set up between the
> place where drm_pci_agp_init is called currently and where the
> driver's ->load function is called. Nothing seems to depend upon
> dev->agp being set up correctly.
>
> Th
On Fri, Jun 08, 2012 at 12:16:41PM +0300, Jani Nikula wrote:
>
> Hi Daniel -
>
> On Thu, 07 Jun 2012, Daniel Vetter wrote:
> > I've done an audit of everything which is being set up between the
> > place where drm_pci_agp_init is called currently and where the
> > driver's ->load function is cal
Hi Daniel -
On Thu, 07 Jun 2012, Daniel Vetter wrote:
> I've done an audit of everything which is being set up between the
> place where drm_pci_agp_init is called currently and where the
> driver's ->load function is called. Nothing seems to depend upon
> dev->agp being set up correctly.
>
> Th
I've done an audit of everything which is being set up between the
place where drm_pci_agp_init is called currently and where the
driver's ->load function is called. Nothing seems to depend upon
dev->agp being set up correctly.
This is one big step into squashing this giant midlayer mistaken.
Thou
I've done an audit of everything which is being set up between the
place where drm_pci_agp_init is called currently and where the
driver's ->load function is called. Nothing seems to depend upon
dev->agp being set up correctly.
This is one big step into squashing this giant midlayer mistaken.
Thou
