From: Helge Hafting <helgehaf@aitel.hist.no>
To: kartikey bhatt <kartik_me@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Can't X be elemenated?
Date: Thu, 02 Oct 2003 10:57:42 +0200 [thread overview]
Message-ID: <3F7BE886.8070401@aitel.hist.no> (raw)
In-Reply-To: <Law11-F67ATnLE7P95L00001388@hotmail.com>
kartikey bhatt wrote:
> hey everyone who have joined this thread, my fundamental question have got
> out of scope. I mean to say
>
> 1. Kernel level support for graphics device drivers.
> 2. On top of that, one can develop complete lightweight GUI.
> 3. Maybe kernel can provide support for event handling.
>
> and I still stick to my opinion that graphics card is a computer resource
> that needs to be managed by OS rather than 3rd party developers.
The card is managed by the os - X has to ask the kernel nicely to get it.
(Try starting another X server inside an xterm and see how
that is refused.)
The details of drawing the windows is something the os don't
need to worry about though - that is the job of X.
Please explain whats wrong about "3rd party developers". Depending on
how you look at it, all of linux is "3rd part developers" except from Linus.
> Just feeding in patches to provide support for AGP gart and DRI
> is an adhoc solution, a stark immoral choice.
Explain the immoral part. Committing a crime is (usually) immoral.
Designing software in a way you dislike isn't.
> you don't know my frustration when i got PC and wasn't able to
> run X until i810 agp gart support was available at kernel level.
>
So?
Having graphichs in the kernel would *not* change this at all.
You would still have to wait for graphichs support for your card.
The kernel would still have to support i810 agp gart.
Linux doesn't support every graphics solution in existence. That is
a fact of life. Wheter the missing part is in kernel or somewhere
else doesn't matter at all. It either works or it don't.
> And if you feel that I am a guy heavily dependent on X that's not true.
> I just mean to say if anything is that kernel level support for graphics
> device drivers.
This sentence didn't make sense to me. Syntax error? :-)
> And X will be automatically eliminated.
Sure. Having the kernel provide graphichs would eliminate X, if the
kernel would support all the stuff X supports. But whats the
_point_ of eliminating X?
1. It wouldn't be faster
2. You wouldn't get support for more cards this way
3. It wouldn't be better in other ways either
Using X for graphichs is nice however, for several reasons:
1. Separation of kernel and graphichs system. This means
we can trivially run without graphichs if we don't need it.
And yes - there are many such uses for linux. The desktop
is merely one of many places where you find linux.
2. There would be fewer graphichs developers for linux with
the graphichs in-kernel. Today X is used not only by linux people,
it is also used by other unices like bsd, and others too.
A bsd/os2/... X developer working on X today will benefit linux
too. That won't happen with a graphichs system internal to linux.
Helge Hafting
next prev parent reply other threads:[~2003-10-02 8:48 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 4:32 kartikey bhatt
2003-10-01 5:00 ` Tupshin Harper
2003-10-01 15:12 ` Jesse Pollard
2003-10-01 18:27 ` Tomasz Rola
2003-10-02 8:57 ` Helge Hafting [this message]
2003-10-02 18:18 ` Herbert Poetzl
2003-10-03 14:30 ` Jesse Pollard
2003-10-02 18:37 ` Erik Steffl
[not found] <BGWr.3eL.7@gated-at.bofh.it>
2003-10-01 8:19 ` Ihar 'Philips' Filipau
-- strict thread matches above, loose matches on Subject: below --
2003-09-30 17:50 kartikey bhatt
2003-09-30 8:09 kartikey bhatt
2003-09-30 9:25 ` Matti Aarnio
2003-09-30 9:54 ` Paul Rolland
2003-09-30 13:34 ` Jesse Pollard
2003-09-29 19:45 kartikey bhatt
2003-09-29 14:44 kartikey bhatt
2003-09-29 14:51 ` Leonard Milcin Jr.
2003-09-29 15:05 ` Gábor Lénárt
2003-09-29 15:10 ` Erik Hensema
2003-09-29 15:11 ` Valdis.Kletnieks
2003-09-29 20:56 ` George France
2003-09-29 21:04 ` Erik Bourget
2003-09-29 21:16 ` Erik Steffl
2003-09-29 21:11 ` Diego Calleja García
2003-09-29 22:30 ` bill davidsen
2003-09-30 18:48 ` Paul Jakma
2003-09-30 19:30 ` Krishna Akella
2003-09-30 20:21 ` David Lang
2003-09-30 20:46 ` Krishna Akella
2003-09-30 20:45 ` David Lang
2003-10-07 4:04 ` Pavel Machek
2003-10-07 8:23 ` Giacomo A. Catenazzi
2003-10-07 12:18 ` Pavel Machek
2003-10-07 12:52 ` Måns Rullgård
2003-10-07 14:34 ` Valdis.Kletnieks
2003-10-07 14:47 ` Jesse Pollard
2003-10-07 15:37 ` Pavel Machek
2003-10-07 19:07 ` David Lang
2003-10-07 19:16 ` Pavel Machek
2003-10-07 20:09 ` jlnance
2003-10-07 18:52 ` David Lang
2003-09-30 21:51 ` J.A. Magallon
2003-10-01 14:54 ` Jesse Pollard
2003-10-01 8:27 ` John Bradford
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=3F7BE886.8070401@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=kartik_me@hotmail.com \
--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
Powered by JetHome