From: Hubert Tonneau <hubert.tonneau@fullpliant.org>
To: linux-kernel@vger.kernel.org
Subject: Desparately wanted: intelfb modesetting in mainline
Date: Sun, 03 Feb 2008 01:58:16 GMT [thread overview]
Message-ID: <081P9H411@briare1.fullpliant.org> (raw)
As a probable result of Intel opening specifications,
it is now fairly easy to buy a business computer that will run Linux
without loosing weeks hacking to get it up and running:
just go with an intel graphic board since Intel X11 driver now works just fine.
Well, this apply only if you run mainstream Linux, that is X11 for the
graphics, because if your application relies on the framebuffer,
we are still at far west time.
Now that Linux is getting more professional with plenty of hackers paid to do
so, it would be nice to include active minimal completeness of the system goal,
as opposed to just passive filtering of preposed patches,
because without it, small more inovative projects (that sit on top of the
kernel instead of beeing kernel rated projects) have a hard time,
so that Linux behaviour is not that different from closed one:
favor the mainstream and ignore small players at the expense of inovation.
Same applies for user land part of some drivers. The current situation is
complete lack of consistency so that getting a working kernel (which nowdays
means kernel + many user land helpers) get's more and more complicated year
after year, as opposed to early days where user land was just achieving a
fiew simple IOCTLs to configure.
It is very understandable to reject many part of drivers to user land to avoid
too much code (with nasty well known side effects) in the kernel, but just
saying that since it is user land it does not have to follow any rule (such as
beeing part of the kernel source and linking only to kernel source provided
libraries) just means lot of work to distributions (so death of small ones
that are not just a recent fork of a big one)
reply other threads:[~2008-02-03 0:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=081P9H411@briare1.fullpliant.org \
--to=hubert.tonneau@fullpliant.org \
--cc=linux-kernel@vger.kernel.org \
/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