From: Daniel Vetter <daniel@ffwll.ch>
To: Thomas Richter <richter@rus.uni-stuttgart.de>
Cc: daniel.vetter@ffwll.ch, intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: VGA1 output no longer detected on IBM R31/i830
Date: Mon, 16 Jun 2014 19:59:01 +0200 [thread overview]
Message-ID: <20140616175901.GC5821@phenom.ffwll.local> (raw)
In-Reply-To: <539DF649.5060406@rus.uni-stuttgart.de>
On Sun, Jun 15, 2014 at 09:38:49PM +0200, Thomas Richter wrote:
> Am 15.06.2014 14:26, schrieb Ville Syrjälä:
>
> >We all know nightly is rather broken with 830. Nothing new here. I
> >suggest just trying my alm_fixes5 branch.
>
> Excuse my ignorance, but there is something I do not get. There are patches
> that are tested and working. Having them in an off-side repository does not
> help users at all, so what stops anyone from either applying these patches
> to the kernel, or alternatively removing the 830/845 support from the
> current i915 driver and create a separate i830 driver from the current
> sources with the patches applied?
>
> The linux i830 kernel support should be working, and not in the broken state
> it is right now - the current state of the affair is not very helpful.
>
> Thanks for keeping the repository, but that's not a solution, at least not
> for most of the remaining users of old hardware.
Repositories with patches are normal procedures until those patches are
properly tested and reviewed. I don't just merge random stuff.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-06-16 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-15 12:16 VGA1 output no longer detected on IBM R31/i830 Thomas Richter
2014-06-15 12:26 ` Ville Syrjälä
2014-06-15 19:38 ` Thomas Richter
2014-06-16 17:59 ` Daniel Vetter [this message]
2014-06-16 19:22 ` Thomas Richter
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=20140616175901.GC5821@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=richter@rus.uni-stuttgart.de \
/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