Re: Hardware rendered Wayland client up and running

2016-08-13 Thread Adrian Chadd 
w!

ok, what has to be committed to -head?



-a


On 13 August 2016 at 19:12, Lundberg, Johannes
 wrote:
> Hi FreeBSD hackers!
>
> Today we reached a big milestone. For the first time, we could render
> Wayland clients, backed by hardware, not shm (shared memory), on Intel Atom
> Cherryview.
>
> Please see attached image of my setup.
>
> UP board (Intel Cherryview)
> OS running on on-board eMMC (need sdhci and mmc patches to function)
> Ports: https://github.com/freebsd/freebsd-ports-graphics/tree/wayland
> Base: https://github.com/FreeBSDDesktop/freebsd-base-graphics/tree/drm-next
> (from today, evdev enabled kernel)
>
> Mouse and keyboard available using libinput.
> Device detection by libudev-devd.
>
> Only one thing, we needed to disable PRIME in drm to get the Wayland
> clients to properly allocate image buffers. Working on getting that fixed!
>
> This opens up for the next big task, getting XWayland working that enable
> use of unmodified X clients as well as testing Wayland enabled libraries
> like Enlightenment, QT5, GTK3, etc. That however is not high priority for
> me so I will probably not work on that.
>
> [image: Inline image 1]
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> 秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。
> もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、
> 複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。
> ---
> CONFIDENTIALITY NOTE: The information in this email is confidential
> and intended solely for the addressee.
> Disclosure, copying, distribution or any other action of use of this
> email by person other than intended recipient, is prohibited.
> If you are not the intended recipient and have received this email in
> error, please destroy the original message.
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: FreeBSD 11.0-RC1 Now Available

2016-08-13 Thread Peter Wemm 
On Saturday, August 13, 2016 08:47:52 PM Glen Barber wrote:
> On Sat, Aug 13, 2016 at 07:35:45PM +0200, Jan Beich wrote:
> > Glen Barber  writes:
> > > The first RC build of the 11.0-RELEASE release cycle is now available.
> > > 
> > > Installation images are available for:
> > > 
> > > o 11.0-RC1 amd64 GENERIC
> > > o 11.0-RC1 i386 GENERIC
> > > o 11.0-RC1 powerpc GENERIC
> > > o 11.0-RC1 powerpc64 GENERIC64
> > > o 11.0-RC1 sparc64 GENERIC
> > > o 11.0-RC1 armv6 BANANAPI
> > > o 11.0-RC1 armv6 BEAGLEBONE
> > > o 11.0-RC1 armv6 CUBIEBOARD
> > > o 11.0-RC1 armv6 CUBIEBOARD2
> > > o 11.0-RC1 armv6 CUBOX-HUMMINGBOARD
> > > o 11.0-RC1 armv6 GUMSTIX
> > > o 11.0-RC1 armv6 RPI-B
> > > o 11.0-RC1 armv6 RPI2
> > > o 11.0-RC1 armv6 PANDABOARD
> > > o 11.0-RC1 armv6 WANDBOARD
> > > o 11.0-RC1 aarch64 GENERIC
> > 
> > What about granular sets? sparc64 is N/A while amd64 is missing
> > lib32.txz, src.txz, ports.txz, tests.txz. Regressed since 11.0-BETA4.
> > I've waited a day to see if the issue would disappear after mirrors
> > catch up but no joy, even via Tor.
> > 
> > [...]
> 
> Thanks for letting us know.  This isn't an re@ issue, it's an admins@
> issue, and we thought this was fixed.  Give me a bit to investigate.
> 
> Glen

If this isn't fixed now, please yell.

It seems we found a bug in the syncthing-inotify tool.  chmod events were 
being missed.  In theory this is worked around now.

-- 
Peter Wemm - pe...@wemm.org; pe...@freebsd.org; pe...@yahoo-inc.com; KI6FJV
UTF-8: for when a ' or ... just won\342\200\231t do\342\200\246

signature.asc
Description: This is a digitally signed message part.

drm-4.7-final tagged - CFT for drm-next was Re: drm-4.7-rc1 tagged

2016-08-13 Thread Matthew Macy 
I have merged up through v4.7 and fixed a number of issues.  I've also added 
kevent support to drm and merged in evdev, so all the kernel dependencies for 
Wayland are enabled by default in GENERIC. I've tagged the last commit as 
drm-v4.7-final as following that I will start merging v4.8-rc1 changes.

With the final change Wayland now works on post-Haswell hardware:
https://twitter.com/Yohanesu75Tweet/status/764640489429540864

Unfortunately I still see corruption when playing multiple videos on chrome 
(chrome has hardware accelerated video playback). FF (not offloaded) does not 
show corruption, but requires the use of a compositor to avoid tearing to keep 
frame updates in sync with screen refresh.

The scope of my personal testing is limited so please report any regressions 
with respect to drm-next-4.6.


  On Fri, 12 Aug 2016 00:21:02 -0700 Matthew Macy  wrote 
 
 >  
 > A few days ago I branched drm-next-4.6 in to drm-next and synced it with 
 > Torvalds' tree as of the v4.6 tag. I then integrated the ~800 commits to drm 
 > / i915 / radeon / amdgpu , testing periodically along the way and updating 
 > the linuxkpi as needed. I've just tagged the drm-next branch with 
 > drm-4.7-rc1 to indicate that it is in sync with 4.7-rc1 upstream.  
 >  
 > If any of you are feeling adventurous I would appreciate it if you would try 
 > it and report any regressions with respect to drm-next-4.6. I'm aware that 
 > there are a number of issues with drm-next-4.6 so I'm only really interested 
 > in _new_ issues.  
 >  
 > If you're feeling really adventurous - run the piglit test suite from the 
 > ports' xserver-next branch and do a root cause analysis on test failures.   
 >  
 > As always the repo is at: 
 > https://github.com/FreeBSDDesktop/freebsd-base-graphics 
 >  
 > Look through the existing open issues before filing a report and check the 
 > wiki first to address any problems. 
 >  
 > Cheers. 
 >  
 > -M 
 >  
 > ___ 
 > freebsd-current@freebsd.org mailing list 
 > https://lists.freebsd.org/mailman/listinfo/freebsd-current 
 > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" 
 > 

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

Hardware rendered Wayland client up and running

2016-08-13 Thread Lundberg, Johannes 
​Hi FreeBSD hackers!
​
​Today we reached a big milestone. For the first time, we could render
Wayland clients, backed by hardware, not shm (shared memory), on Intel Atom
Cherryview.

Please see attached image of my setup.

UP board (Intel Cherryview)
OS running on on-board eMMC (need sdhci and mmc patches to function)
Ports: https://github.com/freebsd/freebsd-ports-graphics/tree/wayland
Base: https://github.com/FreeBSDDesktop/freebsd-base-graphics/tree/drm-next
(from today, evdev enabled kernel)

Mouse and keyboard available using libinput.
Device detection by libudev-devd.

Only one thing, we needed to disable PRIME in drm to get the Wayland
clients to properly allocate image buffers. Working on getting that fixed!

This opens up for the next big task, getting XWayland working that enable
use of unmodified X clients as well as testing Wayland enabled libraries
like Enlightenment, QT5, GTK3, etc. That however is not high priority for
me so I will probably not work on that.

[image: Inline image 1]​

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。
もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、
複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。
---
CONFIDENTIALITY NOTE: The information in this email is confidential
and intended solely for the addressee.
Disclosure, copying, distribution or any other action of use of this
email by person other than intended recipient, is prohibited.
If you are not the intended recipient and have received this email in
error, please destroy the original message.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: FreeBSD 11.0-RC1 Now Available

2016-08-13 Thread Glen Barber 
On Sat, Aug 13, 2016 at 09:30:10PM +, Glen Barber wrote:
> On Sat, Aug 13, 2016 at 08:47:52PM +, Glen Barber wrote:
> > On Sat, Aug 13, 2016 at 07:35:45PM +0200, Jan Beich wrote:
> > > Glen Barber  writes:
> > > 
> > > > The first RC build of the 11.0-RELEASE release cycle is now available.
> > > 
> > > What about granular sets? sparc64 is N/A while amd64 is missing
> > > lib32.txz, src.txz, ports.txz, tests.txz. Regressed since 11.0-BETA4.
> > > I've waited a day to see if the issue would disappear after mirrors
> > > catch up but no joy, even via Tor.
> > > 
> > > [...]
> > 
> > Thanks for letting us know.  This isn't an re@ issue, it's an admins@
> > issue, and we thought this was fixed.  Give me a bit to investigate.
> > 
> 
> I forced the mirrors to re-sync from the master.  My initial test (amd64
> lib32.txz) seems to have worked.  We need to investigate this further,
> as the issues we've seen with this in the past should have been fixed.
> 
> Give it about an hour or so to be sure, but I think everything will be
> fine this time.
> 
> Sorry about that, and thank you again for bringing it to our attention.
> 

Things should be fine now, thanks to Peter.  Moving forward, there
should not be any propagation issues, but please let us know if you see
anything like this during the duration of 11.0-RELEASE.

Glen



signature.asc
Description: PGP signature

Re: build fails post SVN r304026

2016-08-13 Thread Navdeep Parhar 
On Sat, Aug 13, 2016 at 08:30:09PM +, Rick Macklem wrote:
> Lev Serebryakov wrote:
> >On 13.08.2016 16:54, Michael Butler wrote:
> >
> >> Is anyone else seeing this?
> >  Yes, I've posted message to fs@, as it is r304026 for sure (and author
> >was CC:ed too).
> Should be fixed now. Sorry about the breakage. I didn't realize the old
> nfsstat.c wouldn't build with the kernel source patch. (The old nfsstat
> binary does still work, as required to avoid a POLA violation.)
> 
> Anyhow, the changes to nfsstat.c are now committed to head.

I still see errors in nfsstat during buildworld (this is r304065):

Building /usr/obj/usr/src/usr.bin/nfsstat/nfsstat.full
nfsstat.o: In function `compute_new_stats':
/usr/src/usr.bin/nfsstat/nfsstat.c:506: undefined reference to
`devstat_compute_etime'
/usr/src/usr.bin/nfsstat/nfsstat.c:532: undefined reference to
`devstat_compute_etime'
/usr/src/usr.bin/nfsstat/nfsstat.c:506: undefined reference to
`devstat_compute_etime'
/usr/src/usr.bin/nfsstat/nfsstat.c:532: undefined reference to
`devstat_compute_etime'
cc: error: linker command failed with exit code 1 (use -v to see invocation)
*** Error code 1

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

Re: build fails post SVN r304026

2016-08-13 Thread Rick Macklem 
Lev Serebryakov wrote:
>On 13.08.2016 16:54, Michael Butler wrote:
>
>> Is anyone else seeing this?
>  Yes, I've posted message to fs@, as it is r304026 for sure (and author
>was CC:ed too).
Should be fixed now. Sorry about the breakage. I didn't realize the old
nfsstat.c wouldn't build with the kernel source patch. (The old nfsstat
binary does still work, as required to avoid a POLA violation.)

Anyhow, the changes to nfsstat.c are now committed to head.

Sorry about the breakage, rick

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

kevent support to drm

2016-08-13 Thread Lundberg, Johannes 
​Hi

I've just posted a patch that adds kevent to drm 3.8 branch. This is needed
for Wayland (along with evdev).

I posted it on phabricator for now.

https://reviews.freebsd.org/D7496


Phabricator gave me a horrible username because I used an old email, is
there anyway to change it?

Best regards

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。
もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、
複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。
---
CONFIDENTIALITY NOTE: The information in this email is confidential
and intended solely for the addressee.
Disclosure, copying, distribution or any other action of use of this
email by person other than intended recipient, is prohibited.
If you are not the intended recipient and have received this email in
error, please destroy the original message.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: FreeBSD 11.0-RC1 Now Available

2016-08-13 Thread Glen Barber 
On Sat, Aug 13, 2016 at 08:47:52PM +, Glen Barber wrote:
> On Sat, Aug 13, 2016 at 07:35:45PM +0200, Jan Beich wrote:
> > Glen Barber  writes:
> > 
> > > The first RC build of the 11.0-RELEASE release cycle is now available.
> > >
> > > Installation images are available for:
> > >
> > > o 11.0-RC1 amd64 GENERIC
> > > o 11.0-RC1 i386 GENERIC
> > > o 11.0-RC1 powerpc GENERIC
> > > o 11.0-RC1 powerpc64 GENERIC64
> > > o 11.0-RC1 sparc64 GENERIC
> > > o 11.0-RC1 armv6 BANANAPI
> > > o 11.0-RC1 armv6 BEAGLEBONE
> > > o 11.0-RC1 armv6 CUBIEBOARD
> > > o 11.0-RC1 armv6 CUBIEBOARD2
> > > o 11.0-RC1 armv6 CUBOX-HUMMINGBOARD
> > > o 11.0-RC1 armv6 GUMSTIX
> > > o 11.0-RC1 armv6 RPI-B
> > > o 11.0-RC1 armv6 RPI2
> > > o 11.0-RC1 armv6 PANDABOARD
> > > o 11.0-RC1 armv6 WANDBOARD
> > > o 11.0-RC1 aarch64 GENERIC
> > 
> > What about granular sets? sparc64 is N/A while amd64 is missing
> > lib32.txz, src.txz, ports.txz, tests.txz. Regressed since 11.0-BETA4.
> > I've waited a day to see if the issue would disappear after mirrors
> > catch up but no joy, even via Tor.
> > 
> > [...]
> 
> Thanks for letting us know.  This isn't an re@ issue, it's an admins@
> issue, and we thought this was fixed.  Give me a bit to investigate.
> 

I forced the mirrors to re-sync from the master.  My initial test (amd64
lib32.txz) seems to have worked.  We need to investigate this further,
as the issues we've seen with this in the past should have been fixed.

Give it about an hour or so to be sure, but I think everything will be
fine this time.

Sorry about that, and thank you again for bringing it to our attention.

Glen



signature.asc
Description: PGP signature

Re: FreeBSD 11.0-RC1 Now Available

2016-08-13 Thread Glen Barber 
On Sat, Aug 13, 2016 at 07:35:45PM +0200, Jan Beich wrote:
> Glen Barber  writes:
> 
> > The first RC build of the 11.0-RELEASE release cycle is now available.
> >
> > Installation images are available for:
> >
> > o 11.0-RC1 amd64 GENERIC
> > o 11.0-RC1 i386 GENERIC
> > o 11.0-RC1 powerpc GENERIC
> > o 11.0-RC1 powerpc64 GENERIC64
> > o 11.0-RC1 sparc64 GENERIC
> > o 11.0-RC1 armv6 BANANAPI
> > o 11.0-RC1 armv6 BEAGLEBONE
> > o 11.0-RC1 armv6 CUBIEBOARD
> > o 11.0-RC1 armv6 CUBIEBOARD2
> > o 11.0-RC1 armv6 CUBOX-HUMMINGBOARD
> > o 11.0-RC1 armv6 GUMSTIX
> > o 11.0-RC1 armv6 RPI-B
> > o 11.0-RC1 armv6 RPI2
> > o 11.0-RC1 armv6 PANDABOARD
> > o 11.0-RC1 armv6 WANDBOARD
> > o 11.0-RC1 aarch64 GENERIC
> 
> What about granular sets? sparc64 is N/A while amd64 is missing
> lib32.txz, src.txz, ports.txz, tests.txz. Regressed since 11.0-BETA4.
> I've waited a day to see if the issue would disappear after mirrors
> catch up but no joy, even via Tor.
> 
> [...]

Thanks for letting us know.  This isn't an re@ issue, it's an admins@
issue, and we thought this was fixed.  Give me a bit to investigate.

Glen



signature.asc
Description: PGP signature

Re: FreeBSD 11.0-RC1 Now Available

2016-08-13 Thread Jan Beich 
Glen Barber  writes:

> The first RC build of the 11.0-RELEASE release cycle is now available.
>
> Installation images are available for:
>
> o 11.0-RC1 amd64 GENERIC
> o 11.0-RC1 i386 GENERIC
> o 11.0-RC1 powerpc GENERIC
> o 11.0-RC1 powerpc64 GENERIC64
> o 11.0-RC1 sparc64 GENERIC
> o 11.0-RC1 armv6 BANANAPI
> o 11.0-RC1 armv6 BEAGLEBONE
> o 11.0-RC1 armv6 CUBIEBOARD
> o 11.0-RC1 armv6 CUBIEBOARD2
> o 11.0-RC1 armv6 CUBOX-HUMMINGBOARD
> o 11.0-RC1 armv6 GUMSTIX
> o 11.0-RC1 armv6 RPI-B
> o 11.0-RC1 armv6 RPI2
> o 11.0-RC1 armv6 PANDABOARD
> o 11.0-RC1 armv6 WANDBOARD
> o 11.0-RC1 aarch64 GENERIC

What about granular sets? sparc64 is N/A while amd64 is missing
lib32.txz, src.txz, ports.txz, tests.txz. Regressed since 11.0-BETA4.
I've waited a day to see if the issue would disappear after mirrors
catch up but no joy, even via Tor.

$ poudriere jail -cj 110amd64 -a amd64 -v 11.0-RC1
[00:00:01] >> Creating 110amd64 fs... done
[00:00:01] >> Fetching MANIFEST for FreeBSD 11.0-RC1 amd64
/poudriere/jails/110amd64/fromftp/MANIFEST100% of 1157  B   21 MBps 00m00s
[00:00:02] >> Fetching base.txz for FreeBSD 11.0-RC1 amd64
/poudriere/jails/110amd64/fromftp/base.txz100% of   95 MB 3554 kBps 00m27s
[00:00:30] >> Extracting base.txz... done
[00:00:37] >> Fetching src.txz for FreeBSD 11.0-RC1 amd64
fetch: https://download.FreeBSD.org/ftp/releases/amd64/amd64/11.0-RC1/src.txz: 
Not Found
fetch: https://download.FreeBSD.org/ftp/releases/amd64/amd64/11.0-RC1/src.txz: 
Not Found
[00:00:37] >> Error: Failed to fetch from 
https://download.FreeBSD.org/ftp/releases/amd64/amd64/11.0-RC1/src.txz
[00:00:37] >> Error while creating jail, cleaning up.
[00:00:37] >> Removing 110amd64 jail... done

$ poudriere jail -cj 110sparc64 -a sparc64 -v 11.0-RC1
[00:00:00] >> Creating 110sparc64 fs... done
[00:00:00] >> Fetching MANIFEST for FreeBSD 11.0-RC1 sparc64
fetch: 
https://download.FreeBSD.org/ftp/releases/sparc64/sparc64/11.0-RC1/MANIFEST: 
Forbidden
fetch: 
https://download.FreeBSD.org/ftp/releases/sparc64/sparc64/11.0-RC1/MANIFEST: 
Forbidden
[00:00:00] >> Error: Failed to fetch from 
https://download.FreeBSD.org/ftp/releases/sparc64/sparc64/11.0-RC1/MANIFEST
[00:00:00] >> Error while creating jail, cleaning up.
[00:00:00] >> Removing 110sparc64 jail... done


signature.asc
Description: PGP signature

Re: Wayland work status

2016-08-13 Thread Lundberg, Johannes 
Thanks for the help Matthew..
Yeah, I can't believe it was working all along and a stupid copy/paste
error gave us so much trouble...

On Sat, Aug 13, 2016 at 12:26 AM, Matthew Macy  wrote:

>
>  >
>  > ​Wayland relies on kqueue which is not implemented in drm's 3.8 or 4.6
>  > branches. I'm working on this now for drm-next-4.6 and it is almost
>  > complete.
>  > I will probably implement it also in the 3.8 ​branch to be able to run
>  > Wayland on both to compare and find bugs in linuxkpi more easily. Will
>  > share patch for 3.8 branch when done.
>  >
>
> drm-next has working kevent support following shortly after the drm-v4.7
> tag. Your kqfilter implementation would be ideal for 3.8 but is not
> suitable for drm-next as it substantially modifies vendor code. I think
> your implementation does in fact work or is very close. Your apparent
> problem stemmed from an index overwrite in your modified kmscube.c test
> case.
>
> A working kmscube.c can be found at:
>
> https://github.com/FreeBSDDesktop/kmscube
>
> With no arguments it will use select. If you pass -k it will use kevent.
> -M
>
>

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。
もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、
複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。
---
CONFIDENTIALITY NOTE: The information in this email is confidential
and intended solely for the addressee.
Disclosure, copying, distribution or any other action of use of this
email by person other than intended recipient, is prohibited.
If you are not the intended recipient and have received this email in
error, please destroy the original message.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: build fails post SVN r304026

2016-08-13 Thread Lev Serebryakov 
On 13.08.2016 16:54, Michael Butler wrote:

> Is anyone else seeing this?
  Yes, I've posted message to fs@, as it is r304026 for sure (and author
was CC:ed too).


-- 
// Lev Serebryakov AKA Black Lion



signature.asc
Description: OpenPGP digital signature

Re: build fails post SVN r304026

2016-08-13 Thread David Wolfskill 
On Sat, Aug 13, 2016 at 09:54:02AM -0400, Michael Butler wrote:
> Is anyone else seeing this?
> 
> ===> usr.bin/nfsstat (all)
> Building /usr/obj/usr/src/usr.bin/nfsstat/nfsstat.o
> /usr/src/usr.bin/nfsstat/nfsstat.c:301:4: error: array index 72 is past
> the end of the array (which contains 49 elements) [-Werror,-Warray-bounds]
> ext_nfsstats.srvrpccnt[NFSV4OP_SYMLINK],
> 

I am, as of r304040 (src upgrading from r304004), yes.

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Those who would murder in the name of God or prophet are blasphemous cowards.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

build fails post SVN r304026

2016-08-13 Thread Michael Butler 
Is anyone else seeing this?

===> usr.bin/nfsstat (all)
Building /usr/obj/usr/src/usr.bin/nfsstat/nfsstat.o
/usr/src/usr.bin/nfsstat/nfsstat.c:301:4: error: array index 72 is past
the end of the array (which contains 49 elements) [-Werror,-Warray-bounds]
ext_nfsstats.srvrpccnt[NFSV4OP_SYMLINK],
^  ~~~
/usr/obj/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array
'srvrpccnt' declared here
int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS];
^
/usr/src/usr.bin/nfsstat/nfsstat.c:302:4: error: array index 73 is past
the end of the array (which contains 49 elements) [-Werror,-Warray-bounds]
ext_nfsstats.srvrpccnt[NFSV4OP_MKDIR],
^  ~
/usr/obj/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array
'srvrpccnt' declared here
int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS];
^
/usr/src/usr.bin/nfsstat/nfsstat.c:303:4: error: array index 74 is past
the end of the array (which contains 49 elements) [-Werror,-Warray-bounds]
ext_nfsstats.srvrpccnt[NFSV4OP_RMDIR],
^  ~
/usr/obj/usr/src/tmp/usr/include/fs/nfs/nfsport.h:457:2: note: array
'srvrpccnt' declared here
int srvrpccnt[NFSV4OP_NOPS + NFSV4OP_FAKENOPS];

 [ .. ]

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

Re: Wayland work status

2016-08-13 Thread Matthew Macy 

 > 
 > ​Wayland relies on kqueue which is not implemented in drm's 3.8 or 4.6
 > branches. I'm working on this now for drm-next-4.6 and it is almost
 > complete.
 > I will probably implement it also in the 3.8 ​branch to be able to run
 > Wayland on both to compare and find bugs in linuxkpi more easily. Will
 > share patch for 3.8 branch when done.
 > 

drm-next has working kevent support following shortly after the drm-v4.7 tag. 
Your kqfilter implementation would be ideal for 3.8 but is not suitable for 
drm-next as it substantially modifies vendor code. I think your implementation 
does in fact work or is very close. Your apparent problem stemmed from an index 
overwrite in your modified kmscube.c test case.

A working kmscube.c can be found at:

https://github.com/FreeBSDDesktop/kmscube

With no arguments it will use select. If you pass -k it will use kevent.
-M

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

[REVISED] Re: FreeBSD 11.0-RC1 Now Available

2016-08-13 Thread Glen Barber 
On Sat, Aug 13, 2016 at 01:30:56AM +, Glen Barber wrote:
> o OpenSSH DSA keys have been disabled by default.  Users upgrading from
>   prior FreeBSD versions are urged to update their SSH keys to DSA or
>   ECDSA keys before upgrading to 11.0-RC1.
> 

Note, this should have suggested to update SSH keys to RSA or ECDSA, not
DSA or ECDSA.  Apologies for any confusion.

Glen



signature.asc
Description: PGP signature