jor/minor numbers were required when device files had to be created on
regular filesystem like UFS but when a devfs filesystem was implemented
for DragonFly almost a decade ago, nobody thought it was important anymore.
There have been no fixed major numbers on DragonFly since 2009 or so.
--
Fra
SDCon conferences fall on the same week-end :-(
>> I'm not sure which one I will be attending to at this point.
>
>Not sure yet if I will be attending either. But would happily
> provide any input on this either in person (if I am there), or via email.
Dri-devel seems to still be the best place for now :)
Cheers,
--
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 wh
our work
> against Dave's drm-next branch [2]
Sorry about that, this new patch is signed and based on the drm-next branch.
--
Francois Tigeot
-- next part --
A non-text attachment was scrubbed...
Name: 0001-drm.h-Handle-DragonFly-like-Linux.patch
Type: t
t; +++ b/xf86drmMode.c
> @@ -806,6 +806,8 @@ int drmCheckModesettingSupported(const char *busid)
> return -EINVAL;
> return (modesetting ? 0 : -ENOSYS);
> }
> +#elif defined(__DragonFly__)
> + return 0;
> #endif
> return -ENOSY
uot;yes" ;;
> *) LIBKMS="no" ;;
> esac
> fi
> --
> 1.8.5.2
Even though the DragonFly kernel contains a kms implementation, libdrm only
enable libkms support for Linux and FreeBSD by default.
Is anyone willing to push the above commit ?
--
Francois Tigeot
