Re: inteldrm: add a handler for the WSDISPLAYIO_GINFO ioctl

Frederic Cambus wrote: > Hi tech@, > > Add a handler for the WSDISPLAYIO_GINFO ioctl in inteldrm, allowing > to retrieve basic information about a framebuffer display. > > When running wsconsctl on a machine with inteldrm support, this now > returns those additional fields: > > display.width=160

inteldrm: add a handler for the WSDISPLAYIO_GINFO ioctl

Hi tech@, Add a handler for the WSDISPLAYIO_GINFO ioctl in inteldrm, allowing to retrieve basic information about a framebuffer display. When running wsconsctl on a machine with inteldrm support, this now returns those additional fields: display.width=1600 display.height=900 display.depth=32 Co

csh(1): move win variable

Hi, Tiny diff, move the win variable into print_by_column() since it's the only function using it. Comments? OK? Index: file.c === RCS file: /cvs/src/bin/csh/file.c,v retrieving revision 1.23 diff -u -p -r1.23 file.c --- file.c

Re: faster timecounters for kvm/xen

On 17 June 2017 at 14:17, Jonathan Matthew wrote: > > On Fri, Jun 16, 2017 at 01:19:02PM +0200, Mike Belopuhov wrote: > > On Fri, Jun 16, 2017 at 10:25 +0200, Mike Belopuhov wrote: > > > I don't know if it's a good idea to depend on Xen's > > > definition of vcpu_time_info. I think I have factore

Re: faster timecounters for kvm/xen

On Fri, Jun 16, 2017 at 01:19:02PM +0200, Mike Belopuhov wrote: > On Fri, Jun 16, 2017 at 10:25 +0200, Mike Belopuhov wrote: > > I don't know if it's a good idea to depend on Xen's > > definition of vcpu_time_info. I think I have factored > > it out into the pvclock_time_info and put it into the >

wsfontload(8): account for the WSFONT_NAME_SIZE change

Hi tech@, Since WSFONT_NAME_SIZE was switched from 16 to 32, account for the change in wsfontload as well: tweak spacing and printf format string. Comments? OK? Index: usr.sbin/wsfontload/wsfontload.c === RCS file: /cvs/src/usr.sbin