Update 2 the state of drm-next-4.6 and next steps

[Alexander Mishurov]

It's a SoC, actually. It doesn't even use a dedicated PCI address for 
"dev_priv->bridge_dev", I set the same address for bridge_dev as for 
video device itself in order to get some data from regs when I tried to 
rev my video.

Also, I included device id, 0x0f31, to agp_i810.c which had a valleyvew 
driver in 3.8 update in order to load agp driver first. I don't know 
whether it is necessary in the newest versions, just in case.

On 24/05/16 11:19, Matthew Macy wrote:
>
>
>   ---- On Tue, 24 May 2016 01:12:11 -0700 Nils Beyer <nbe at renzel.net> wrote ----
>   > Hi Matthew,
>   >
>   > first of all, thank you very much for your work on this.
>   >
>   > I'm using the same ValleyView/BayTrail chipset (0x0f31) as Alexander and nearly
>   > having the same issue kldloading the kernel module.
>   >
>   > "kldload" hangs at the "vmwait" state (checked via CTRL+T). On a second console,
>   > I can enter a username; but after entering the username "root" and pressing
>   > enter, the login process hangs at the "pfault" state.
>   >
>   > Hopefully, this information helps you a little bit...
>
> That actually gives me more to go on. Running "procstat -kk <kldload pid>" would help even more. Thanks.
>
> -M
>
>   >
>   >
>   >
>   > Regards,
>   > Nils
>   > _______________________________________________
>   > freebsd-x11 at freebsd.org mailing list
>   > https://lists.freebsd.org/mailman/listinfo/freebsd-x11
>   > To unsubscribe, send any mail to "freebsd-x11-unsubscribe at freebsd.org"
>   >
>
> _______________________________________________
> freebsd-x11 at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-x11
> To unsubscribe, send any mail to "freebsd-x11-unsubscribe at freebsd.org"