Date: Tue, 24 May 2016 01:47:37 -0700 From: Matthew Macy <mmacy@nextbsd.org> To: "Alexander Mishurov" <alexander.m.mishurov@gmail.com> Cc: "Nils Beyer" <nbe@renzel.net>, "<freebsd-x11@freebsd.org>" <freebsd-x11@freebsd.org> Subject: Re: Update 2 the state of drm-next-4.6 and next steps Message-ID: <154e1f2ab3f.112258e51225954.5570058563350589991@nextbsd.org> In-Reply-To: <574413C0.2020306@gmail.com> References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <15449ec286e.11def424858288.297669375175006270@nextbsd.org> <1549f266cc5.ea588cba219264.3594536435079440635@nextbsd.org> <20160521231734.GM21899@ivaldir.etoilebsd.net> <CAASDrV=h7C8JjqQPcWWE4=Z6=F%2BvG1aU_YqPgLDoTM2-362PVQ@mail.gmail.com> <57436A8E.4020109@gmail.com> <154df5bc8e2.b7d4a800194520.6901257599921444588@nextbsd.org> <5743824C.6050308@gmail.com> <154dfc5f7e9.109281b7a199490.5235064548489806889@nextbsd.org> <1854718.X2I93raCOV@asbach.renzel.net> <154e1d87643.b5b82861225515.4992131373924163574@nextbsd.org> <574413C0.2020306@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
---- On Tue, 24 May 2016 01:41:26 -0700 Alexander Mishurov <alexander.m.mishurov@gmail.com> wrote ---- > 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. If it needs agp, that would explain it. I haven't reved agp support with the new drm. That's also why I don't support Arrandale yet. I thought agp was dead. But maybe not for SoCs. Thanks. -M > > On 24/05/16 11:19, Matthew Macy wrote: > > > > > > ---- On Tue, 24 May 2016 01:12:11 -0700 Nils Beyer <nbe@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@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > > > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" > > > > > > > _______________________________________________ > > freebsd-x11@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?154e1f2ab3f.112258e51225954.5570058563350589991>