dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Gray <jsg@jsg.id.au>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH libdrm 2/5] xf86drm: implement drmParseSubsystemType for OpenBSD
Date: Wed, 30 Nov 2016 11:23:33 +1100	[thread overview]
Message-ID: <20161130002333.GC12128@largo.jsg.id.au> (raw)
In-Reply-To: <CACvgo51w4c4UP3jwQwB2qett-1-5Zm6aErBTzYJ_WmSCkwC-Qg@mail.gmail.com>

On Tue, Nov 29, 2016 at 07:46:31PM +0000, Emil Velikov wrote:
> On 26 November 2016 at 00:40, Jonathan Gray <jsg@jsg.id.au> wrote:
> > Implement drmParseSubsystemType for OpenBSD by always returning
> > DRM_BUS_PCI.  No non-pci drm drivers are in the kernel and this is
> > unlikely to change anytime soon as the existing ones aren't permissively
> > licensed.
> >
> A few noticeable X11 MIT style licensed drivers include qxl, vgem and
> virtio. Two of which PCI ones and vgem in it's own unique category ;-)
> 
> There was a question about re-licensing [some] drivers a few years ago
> at XDC in France. IIRC devs were fine with it, yet it doesn't seem
> like things changed much.
> Have you/fellow BSD developers considered reaching out [as a group] to
> interested drivers/developers ? Pardon if I've already
> mentioned/already asked about this.
> 
> Thanks
> Emil

There is no particular driver, cirrus, gma500 etc might be nice but
really what limited spare time we have that involves drm is dealt
dealing with the constant churn of i915.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-11-30  0:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-26  0:40 [PATCH libdrm 1/5] xf86drm: implement drmGetMinorNameForFD for non-sysfs Jonathan Gray
2016-11-26  0:40 ` [PATCH libdrm 2/5] xf86drm: implement drmParseSubsystemType for OpenBSD Jonathan Gray
2016-11-29 19:46   ` Emil Velikov
2016-11-30  0:23     ` Jonathan Gray [this message]
2016-11-30 16:23       ` Emil Velikov
2016-11-26  0:40 ` [PATCH libdrm 3/5] xf86drm: implement drmParsePciDeviceInfo " Jonathan Gray
2016-11-29 19:55   ` Emil Velikov
2016-11-30  0:38     ` Jonathan Gray
2016-11-30 16:11       ` Emil Velikov
2016-11-26  0:40 ` [PATCH libdrm 4/5] xf86drm: implement drmParsePciBusInfo " Jonathan Gray
2016-11-26  0:40 ` [PATCH libdrm 5/5] xf86drm: implement an OpenBSD specific drmGetDevice Jonathan Gray
2016-11-29 20:03   ` Emil Velikov
2016-11-30  0:00     ` Jonathan Gray
2016-11-30 16:32       ` Emil Velikov
2016-11-29 19:22 ` [PATCH libdrm 1/5] xf86drm: implement drmGetMinorNameForFD for non-sysfs Emil Velikov
2016-11-30  0:15   ` Jonathan Gray
2016-11-30 16:16     ` Emil Velikov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161130002333.GC12128@largo.jsg.id.au \
    --to=jsg@jsg.id.au \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox