re: CVS commit: [riastradh-drm2] src/sys/external/bsd/drm2/i915drm

[matthew green <mrg%eterna.com.au@localhost>]

>    > Defer i915drm_attach_framebuffer until interrupts are running.
>    > 
>    > The i915 code initialization relies on counting hardclock ticks for a
>    > delay (ugh).
>    > 
>    > Not an issue for modules, but it will matter when we build drm2 into
>    > the kernel proper.
> 
>    not sure why this is a problem generally.  there have been
>    defer for interrupts primatives in our kernel for almost
>    2 deacdes now.
> 
> Yes, that is exactly what I used:
> 
> -       i915drm_attach_framebuffer(self);
> +       /* Attach a framebuffer, but not until interrupts work.  */
> +       config_interrupts(self, &i915drm_attach_framebuffer);
> 
> What is the problem you're referring to?

i mean your comment about builtin driver.

ah, i see.  you've fixed the problem, now.  good :-)