From: Jani Nikula <jani.nikula@linux.intel.com>
To: Scott Long <scottl@netflix.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: Ed Maste <emaste@freebsdfoundation.org>, K Macy <kmacy@freebsd.org>
Subject: Re: FreeBSD i915 driver update
Date: Fri, 13 May 2016 10:34:59 +0300 [thread overview]
Message-ID: <871t56h0m4.fsf@intel.com> (raw)
In-Reply-To: <946F24C0-6419-4C15-ACAB-0CD6E247D082@netflix.com>
On Fri, 13 May 2016, Scott Long <scottl@netflix.com> wrote:
> Jean-Sébastien and other developers have been discussing a new approach
> for post-3.8.13 updates. Instead of maintaining a large set of changes,
> the plan is to keep the driver as close as possible to the upstream Linux
> version, and use straightforward shims to adapt to interfaces provided by
> FreeBSD where possible.
FWIW, I think this is likely the only viable option.
The i915 driver is a fast moving target, and I have witnessed the
struggles of full time paid developers backporting and forward porting
drm and i915 features from Linux kernel version to another. It is not a
trivial task. Last I checked, the Linux driver backports project has
also given up backporting latest drm drivers to stable kernel versions.
I don't have any FreeBSD experience and I don't know what kind of team
of developers you have, but it is my educated guess that you'll have
plenty of more productive things to do than trying to maintain a
significant amount of delta with upstream while also trying to stay
up-to-date.
> Our ultimate goal is to align closely with the Linux graphics
> development community and collaborate with Intel, ATI, and others on
> keeping FreeBSD up to date in their product development efforts.
The focus and priority of the i915 driver is obviously Linux, but I
don't see us rejecting patches that help FreeBSD if the patches
generally make sense and don't interfere with the main priority.
Good luck with your efforts!
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-05-13 7:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 21:12 FreeBSD i915 driver update Scott Long
2016-05-13 7:34 ` Jani Nikula [this message]
2016-05-13 7:43 ` K. Macy
2016-05-17 7:20 ` Jani Nikula
2016-05-17 7:38 ` K. Macy
2016-05-13 8:39 ` Scott Long
2016-05-13 14:00 ` Ed Maste
2016-05-17 10:23 ` Daniel Vetter
2016-05-17 15:09 ` K. Macy
2016-05-18 8:11 ` Daniel Vetter
2016-05-18 8:50 ` K. Macy
2016-05-18 1:10 ` randyf
-- strict thread matches above, loose matches on Subject: below --
2016-05-12 20:18 Scott Long
2016-05-13 13:27 ` Jani Nikula
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=871t56h0m4.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=emaste@freebsdfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kmacy@freebsd.org \
--cc=scottl@netflix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.