[PATCH] drm.h: Handle DragonFly like Linux

2016-05-17 Thread Ed Maste
On 17 May 2016 at 01:26, Francois Tigeot wrote: > > FreeBSD and NetBSD even have two different drm.h kernel headers. For some > reason they think it is a good idea to keep a separate drm implementation > from ~= 10 years ago or so. No, we (FreeBSD) don't think it's a good idea. It's an unfortunat

[PATCH] drm.h: Handle DragonFly like Linux

2016-05-17 Thread Francois Tigeot
Hi Randy, randyf at sibernet.com wrote: > >If you are interested in the primary Solaris source, you will really > want to looking at: > > https://java.net/projects/solaris-x11/sources/x-s12-clone/show/open-src/kernel Thanks. This doesn't look like a git repository though. How can I clone it ?

[PATCH] drm.h: Handle DragonFly like Linux

2016-05-17 Thread Francois Tigeot
On Mon, May 16, 2016 at 11:02:33PM +0100, Emil Velikov wrote: > On 16 May 2016 at 17:24, Francois Tigeot wrote: > > > > The #else code path is not being used on DragonFly and actually breaks > > kernel compilation. > > > I guess what I'm wondering here is where they working at some point in > the

[PATCH] drm.h: Handle DragonFly like Linux

2016-05-17 Thread ran...@sibernet.com
On Tue, 17 May 2016, Francois Tigeot wrote: > Hi Randy, > > randyf at sibernet.com wrote: >> >>If you are interested in the primary Solaris source, you will really >> want to looking at: >> >> https://java.net/projects/solaris-x11/sources/x-s12-clone/show/open-src/kernel > > Thanks. This do

[PATCH] drm.h: Handle DragonFly like Linux

2016-05-16 Thread ran...@sibernet.com
On Tue, 17 May 2016, Francois Tigeot wrote: > >>> On the other hand, the non-Linux code path really is unused. I didn't want >>> to be too intrusive in my patch but it's probably best to just remove it. >>> >> There is more to this world than Linux and BSD, there's Solaris as >> well. Even though

[PATCH] drm.h: Handle DragonFly like Linux

2016-05-16 Thread Emil Velikov
On 16 May 2016 at 17:24, Francois Tigeot wrote: > Hi Emil, > > Emil Velikov wrote: >> >> >> On 14 May 2016 at 08:13, François Tigeot wrote: >>> >>> The drm code in DragonFly uses a local Linux implementation which doesn't >>> define the __linux__ macro. >>> >>> Use __DragonFly__ instead in order

[PATCH] drm.h: Handle DragonFly like Linux

2016-05-16 Thread Francois Tigeot
Hi Emil, Emil Velikov wrote: > > On 14 May 2016 at 08:13, François Tigeot wrote: >> The drm code in DragonFly uses a local Linux implementation which doesn't >> define the __linux__ macro. >> >> Use __DragonFly__ instead in order to not try to compile non-Linux code. > Does that meant that the w

[PATCH] drm.h: Handle DragonFly like Linux

2016-05-14 Thread Emil Velikov
Hi François, On 14 May 2016 at 08:13, François Tigeot wrote: > The drm code in DragonFly uses a local Linux implementation which doesn't > define the __linux__ macro. > > Use __DragonFly__ instead in order to not try to compile non-Linux code. Does that meant that the workarounds in the else st

[PATCH] drm.h: Handle DragonFly like Linux

2016-05-14 Thread François Tigeot
The drm code in DragonFly uses a local Linux implementation which doesn't define the __linux__ macro. Use __DragonFly__ instead in order to not try to compile non-Linux code. --- include/uapi/drm/drm.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/uapi/drm/drm.h b/in