Re: CFT: ndis(4) testers needed! - on 11.0-RELESE

2017-01-03 Thread Yoshihiro Ota
Hi Gleb, Are you still accepting a bug report on this? I have a laptop that I need to use NDIS driver. This change impacted and causes kernel panic. I haven't used this laptop for a quite while and didn't realize it had stopped working. When I setup a wlan0 device with NDIS in wepmode, "ifconfig

Re: ACPI Error on HP ProBook 430 G2

2017-01-03 Thread Jung-uk Kim
On 01/03/2017 11:22, Hans Petter Selasky wrote: > On 01/03/17 16:26, Moore, Robert wrote: >> Not sure I understand. The fix has been committed, and is part of >> version 20161222. >> >> > > Hi Robert, > > From what I can see that patches have been pushed to the following > branch,

RE: ACPI Error on HP ProBook 430 G2

2017-01-03 Thread Moore, Robert
> -Original Message- > From: Hans Petter Selasky [mailto:h...@selasky.org] > Sent: Tuesday, January 3, 2017 8:23 AM > To: Moore, Robert ; Edward Tomasz Napierala > ; O. Hartmann > Cc: freebsd-a...@freebsd.org;

RE: ACPI Error on HP ProBook 430 G2

2017-01-03 Thread Moore, Robert
Not sure I understand. The fix has been committed, and is part of version 20161222. > -Original Message- > From: Hans Petter Selasky [mailto:h...@selasky.org] > Sent: Monday, January 2, 2017 12:30 AM > To: Moore, Robert ; Edward Tomasz Napierala >

Re: ACPI Error on HP ProBook 430 G2

2017-01-03 Thread Hans Petter Selasky
On 01/03/17 16:26, Moore, Robert wrote: Not sure I understand. The fix has been committed, and is part of version 20161222. Hi Robert, From what I can see that patches have been pushed to the following branch, vendor-sys/acpica/20161222/, see:

Re: current freebsd graphics stack

2017-01-03 Thread blubee blubeeme
I haven't looked at dragonfly I saw a few talks from the FreeBSD guys and it seemed like the main reason for dragonfly was misguided. I am interested in solving the problem within the constraints set fourth by FreeBSD so I won't be forking anything. I might look at that project though. I think

Re: current freebsd graphics stack

2017-01-03 Thread Johannes Lundberg
Isn't that the way it was done before and is done on DragonFly? Don't forget, linuxkpi also supports AMD and Gallium drivers It is a complex subject.. in a perfect world we'd have unlimited time and resources and FreeBSD would be in every man's hand :) Good luck! On Tue, Jan 3, 2017 at

Re: current freebsd graphics stack

2017-01-03 Thread blubee blubeeme
It's understandable and I actually came across your twitter account a long time ago before I joined this list. I did look at intels open source gpu drivers. I will be attempting after a smaller project to get it up and running on BSD without using the linux wrappers. Crazy, I know but nothing

Re: current freebsd graphics stack

2017-01-03 Thread Johannes Lundberg
Hi Not sure about the other graphics drivers but porting a driver like drm/i915 for Intel graphics is a massive undertaking (look at the source code from Intel!). Intel develops their open source driver for Linux and having linuxkpi reduces porting efforts for us from a full time job to a few

Re: current freebsd graphics stack

2017-01-03 Thread blubee blubeeme
Hi Johannes I was asking about the current state of those three main items. I just looked at the linuxkpi thing and it's a wrapper around the linux version of DRM but isn't DRM a open standard, if we keep chasing down linux the more they move their stuff into their kernel the harder it will

Re: current freebsd graphics stack

2017-01-03 Thread Johannes Lundberg
Hi Owen I've been helping out with drm, i915, linuxkpi and evdev in the kernel. For userland I'm working on Wayland-related stuff. You can check my twitter (@johalun) or this mailing list for my earlier posts about how to use this work. Sorry for asking but exactly what is your question now

current freebsd graphics stack

2017-01-03 Thread blubee blubeeme
Howdy Is there anyone on this list that works on the graphics stack for FreeBSD? Watching this video: https://www.youtube.com/watch?v=dZI4pAvK_RY=5 from a few years ago and what I've gathered so far the new x is getting a major redesign and a lot of code is moving into the kernel. You can take