Re: CVS: cvs.openbsd.org: src - kms
Kevin Chadwick [ma1l1i...@yahoo.co.uk] wrote: > Made my day. > > So does this mean machdep can be turned off for some hardware and is > the best way to find out, simply to try? > If inteldrm attaches, the aperture now appears to work at 1 (instead of 2) but not yet 0.
Re: CVS: cvs.openbsd.org: src - kms
On Mon, Mar 18, 2013 at 9:48 PM, Kevin Chadwick wrote: >> > Log message: >> > Significantly increase the wordlist for ddb hangman, >> > and update our device independent DRM code and the Intel DRM code >> > to be mostly in sync with Linux 3.8.3. Among other things this >> > brings support for kernel modesetting and enables use of >> > the rings on gen6+ Intel hardware. >> > >> > Based on some earlier work from matthieu@ with some hints from FreeBSD >> > and with lots of help from kettenis@ (including a beautiful accelerated >> > wscons framebuffer console!) >> > >> > Thanks to M:Tier and the OpenBSD Foundation for sponsoring this work. >> >> Wow guys, hats off, thanks for the work and thanks for the sponsors for >> making this available for us. > > Made my day. > > So does this mean machdep can be turned off for some hardware and is > the best way to find out, simply to try? I think you meant machdep.allowaperture
Re: CVS: cvs.openbsd.org: src - kms
> > Log message: > > Significantly increase the wordlist for ddb hangman, > > and update our device independent DRM code and the Intel DRM code > > to be mostly in sync with Linux 3.8.3. Among other things this > > brings support for kernel modesetting and enables use of > > the rings on gen6+ Intel hardware. > > > > Based on some earlier work from matthieu@ with some hints from FreeBSD > > and with lots of help from kettenis@ (including a beautiful accelerated > > wscons framebuffer console!) > > > > Thanks to M:Tier and the OpenBSD Foundation for sponsoring this work. > > Wow guys, hats off, thanks for the work and thanks for the sponsors for > making this available for us. Made my day. So does this mean machdep can be turned off for some hardware and is the best way to find out, simply to try? -- ___ 'Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface' (Doug McIlroy) ___
Re: CVS: cvs.openbsd.org: src - kms
On Mon, Mar 18, 2013 at 02:13:20PM +0100, LEVAI Daniel wrote: > On h, márc 18, 2013 at 06:36:52 -0600, Jonathan Gray wrote: > [...] > > Log message: > > Significantly increase the wordlist for ddb hangman, > > and update our device independent DRM code and the Intel DRM code > > to be mostly in sync with Linux 3.8.3. Among other things this > > brings support for kernel modesetting and enables use of > > the rings on gen6+ Intel hardware. > > [...] Just to get this clear though, the 'gen6+ only' bit is meant for _both_ KMS and rings, right? -- Gregor Best
Re: CVS: cvs.openbsd.org: src - kms
On h, márc 18, 2013 at 06:36:52 -0600, Jonathan Gray wrote: [...] > Log message: > Significantly increase the wordlist for ddb hangman, > and update our device independent DRM code and the Intel DRM code > to be mostly in sync with Linux 3.8.3. Among other things this > brings support for kernel modesetting and enables use of > the rings on gen6+ Intel hardware. > > Based on some earlier work from matthieu@ with some hints from FreeBSD > and with lots of help from kettenis@ (including a beautiful accelerated > wscons framebuffer console!) > > Thanks to M:Tier and the OpenBSD Foundation for sponsoring this work. Wow guys, hats off, thanks for the work and thanks for the sponsors for making this available for us. Daniel
