Re: what is the status of KMS support in newcons?

2013-09-21 Thread symbolics
On Fri, Sep 20, 2013 at 02:23:07AM +0300, Aleksandr Rybalko wrote:
 On Wed, 18 Sep 2013 21:46:50 -0700
 John Reynolds john...@reynoldsnet.org wrote:
 
  Hello all,
  
  I was just wondering what the status of KMS support with newcons is? 
  About 6 weeks ago I got some help on x11@ and much was said about KMS 
  (and the lack of support for the 'newer' Haswell graphics). somebody 
  mentioned that one of the problems where the console goes away once 
  you fire up X was that the console driver didn't support KMS, so you 
  could never really successfully alt-Ctrl-bksp and kill X (or exit 
  cleanly) and get back to your VT. Word was said that this problem was 
  being worked on and hopefully would get brought in towards the tail
  end of august.
  
  So, am just wondering what the status of that project is?
  
  thanks,
  
  -Jr
  
  ___
  freebsd-current@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-current
  To unsubscribe, send any mail to
  freebsd-current-unsubscr...@freebsd.org
 
 Hello John!
 
 I can't say anything about Haswell support, but newcons works,
 sometimes :) Just not now.
 I've currently doing some redesign, so it is broken last week.
 Hope I will done something for wide testing in a week or so, but I'm
 afraid it will not be fully done to be shipped with 10.0.
 
 I will let you and others to know when something will happen :)

Hi,

From the code in the user/ed/newcons branch it seems that there is no
support for 256 colors at the moment. Is this planned? I have moved to
only using a console from X11 and I miss the additional colours. 

Thanks!
-sym
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: what is the status of KMS support in newcons?

2013-09-19 Thread Aleksandr Rybalko
On Wed, 18 Sep 2013 21:46:50 -0700
John Reynolds john...@reynoldsnet.org wrote:

 Hello all,
 
 I was just wondering what the status of KMS support with newcons is? 
 About 6 weeks ago I got some help on x11@ and much was said about KMS 
 (and the lack of support for the 'newer' Haswell graphics). somebody 
 mentioned that one of the problems where the console goes away once 
 you fire up X was that the console driver didn't support KMS, so you 
 could never really successfully alt-Ctrl-bksp and kill X (or exit 
 cleanly) and get back to your VT. Word was said that this problem was 
 being worked on and hopefully would get brought in towards the tail
 end of august.
 
 So, am just wondering what the status of that project is?
 
 thanks,
 
 -Jr
 
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to
 freebsd-current-unsubscr...@freebsd.org

Hello John!

I can't say anything about Haswell support, but newcons works,
sometimes :) Just not now.
I've currently doing some redesign, so it is broken last week.
Hope I will done something for wide testing in a week or so, but I'm
afraid it will not be fully done to be shipped with 10.0.

I will let you and others to know when something will happen :)

Thanks!
-- 
Aleksandr Rybalko r...@freebsd.org
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: what is the status of KMS support in newcons?

2013-09-19 Thread Michael Schnell


On Fri, 20 Sep 2013, Aleksandr Rybalko wrote:


On Wed, 18 Sep 2013 21:46:50 -0700
John Reynolds john...@reynoldsnet.org wrote:


Hello all,

I was just wondering what the status of KMS support with newcons is?
About 6 weeks ago I got some help on x11@ and much was said about KMS
(and the lack of support for the 'newer' Haswell graphics). somebody
mentioned that one of the problems where the console goes away once
you fire up X was that the console driver didn't support KMS, so you
could never really successfully alt-Ctrl-bksp and kill X (or exit
cleanly) and get back to your VT. Word was said that this problem was
being worked on and hopefully would get brought in towards the tail
end of august.

So, am just wondering what the status of that project is?

thanks,

-Jr

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
freebsd-current-unsubscr...@freebsd.org


Hello John!

I can't say anything about Haswell support, but newcons works,
sometimes :) Just not now.

There is currently no Haswell graphic support in Current. I've a new
Dell Latitude E7240 with a Core i5 4200 and i915kms didn't attach to it.
I added then support and managed to start the X server, but there were
quite some changes necessary, e.g adding the ID and feature set to agp,
i915 and drm2, plus some changes in registers etc.

Perhaps it's better to directly import the latest version from the linux
kernel? I also suffered some problems now with this version like I
cannot shutdown the machine anymore. The display freezes (with my
desktop background, not going black as expected without newcons) and
what is worse there is no dump.


I've currently doing some redesign, so it is broken last week.
Hope I will done something for wide testing in a week or so, but I'm
afraid it will not be fully done to be shipped with 10.0.

I will let you and others to know when something will happen :)

That sounds great.


Greetings
Michael
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: what is the status of KMS support in newcons?

2013-09-19 Thread John Reynolds

On 09/19/13 16:23, Aleksandr Rybalko wrote:
Hello John! I can't say anything about Haswell support, but newcons 
works, sometimes :) Just not now. I've currently doing some redesign, 
so it is broken last week. Hope I will done something for wide testing 
in a week or so, but I'm afraid it will not be fully done to be 
shipped with 10.0. I will let you and others to know when something 
will happen :) Thanks! 
I'm currently running 9.x and have no plans (at the moment) to run 
-current or move to 10.0. I assume this will be MFC'ed (or whatever the 
current term is these days :) into 9x? Also for anybody in the know 
out there, I thought I'd understood from a thread about 6 weeks ago that 
fixed KMS support was going to be integral for getting haswell 
graphics to work with the intel X driver. Is there anybody out there 
(yet) that is running on a haswell system that has gotten the native 
driver to work? Right now I'm still stuck using the VESA driver. Is 
anybody working on it? I bought the system figuring that it was SO new 
that things wouldn't work so it wasn't much of a shock, but we're 3+ 
months into the life of the new hardware . just figured that there 
was probably work going on to make things supported, and if so can 
somebody share the progress made?


Thanks,

-JR

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


what is the status of KMS support in newcons?

2013-09-18 Thread John Reynolds

Hello all,

I was just wondering what the status of KMS support with newcons is? 
About 6 weeks ago I got some help on x11@ and much was said about KMS 
(and the lack of support for the 'newer' Haswell graphics). somebody 
mentioned that one of the problems where the console goes away once 
you fire up X was that the console driver didn't support KMS, so you 
could never really successfully alt-Ctrl-bksp and kill X (or exit 
cleanly) and get back to your VT. Word was said that this problem was 
being worked on and hopefully would get brought in towards the tail end 
of august.


So, am just wondering what the status of that project is?

thanks,

-Jr

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org