Skip to contentSkip to conversation

replacing X Window System !

DISCUSSION Al Boldi 4 participants 5 messages May 20, 2006 – May 22, 2006

lore
Share & tools
lore

Al Boldi

author
#0 lore raw
Quoted 9 lines · Adrian Bunk
Quoted 1 line · linux cbon

I think the discussion should move to X.Org ?

The whole discussion is pointless anywhere as long as you are not writing the code to implement your proposal.

If you think you could send an idea and other people would implement it you are misunderstanding how open source software works.

Quoted 6 lines

You have your idea.

It is YOUR job to write the code implementing your proposal.

Then there's a basis for a technical discussion of the advantages and disadvantages of your ideas.

Implementing an idea before discussing it's feasibility?

Kind of stupid, don't you think?

Quoted 2 lines

Otherwise, you are only wasting your (and our) time since there's exactly a 0% probability that someone else will implement your ideas.

Maybe not 0% exactly.

Not that I would agree with the in-Kernel X idea per se, but it does raise the issue of a stable API once more, as it would allow more freedom to create a module against a version line w/o fear of being rejected.

Thanks!

--
Al

#1 lore raw
Quoted 12 lines · Al Boldi
Quoted 11 lines · Adrian Bunk
Quoted 1 line · linux cbon

I think the discussion should move to X.Org ?

The whole discussion is pointless anywhere as long as you are not writing the code to implement your proposal.

If you think you could send an idea and other people would implement it you are misunderstanding how open source software works.

You have your idea.

Quoted 8 lines
Quoted 4 lines

It is YOUR job to write the code implementing your proposal.

Then there's a basis for a technical discussion of the advantages and disadvantages of your ideas.

Implementing an idea before discussing it's feasibility?

Kind of stupid, don't you think?

Sure, it does make sense to ask for comments before starting with an implementation.

But discussing possible patches also becomes kind of stupid if you aren't willing to implement it yourself.

There have already been more than enough discussions regarding this issue - if he still considers his idea worth it HE must start with the implementation NOW.

He seems to be the kind of troll who wants to convince other people of his "great" ideas without writing a single line of code himself.

Quoted 4 lines
Quoted 2 lines

Otherwise, you are only wasting your (and our) time since there's exactly a 0% probability that someone else will implement your ideas.

Maybe not 0% exactly.

In this case, 0% exactly.

Quoted 3 lines

Not that I would agree with the in-Kernel X idea per se, but it does raise the issue of a stable API once more, as it would allow more freedom to create a module against a version line w/o fear of being rejected.

It does not raise the issue of a stable kernel API:

The solution is to work on getting the module included into the kernel. All problems with changing kernel APIs vanish as soon as your module is included. This is independent from what the module in question is doing.

Documentation/stable_api_nonsense.txt explains the advantages of not having a stable API.

Quoted 2 lines

Thanks!
Al

cu
Adrian

BTW: Don't drop people from the Cc.

Signature · 4 lines
       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed
author
#2 lore raw
Quoted 11 lines · Adrian Bunk
Quoted 4 lines · Al Boldi

Not that I would agree with the in-Kernel X idea per se, but it does raise the issue of a stable API once more, as it would allow more freedom to create a module against a version line w/o fear of being rejected.

It does not raise the issue of a stable kernel API:

The solution is to work on getting the module included into the kernel. All problems with changing kernel APIs vanish as soon as your module is included. This is independent from what the module in question is doing.

Yes, but the question is:
What's the trick to get the module into the kernel?

It seems that we are currently under the mercy of the few, who have the power to control this. And forking isn't really a solution.

With a stable API, I can just implement whatever w/o caring whether it is included into the kernel. Now that's freedom!

Thanks!

--
Al

#3 lore raw
Quoted 7 lines · On Saturday May 20, [email protected] wrote:
Quoted 6 lines · Adrian Bunk
Quoted 4 lines · Al Boldi

Not that I would agree with the in-Kernel X idea per se, but it does raise the issue of a stable API once more, as it would allow more freedom to create a module against a version line w/o fear of being rejected.

Quoted 8 lines
Quoted 5 lines

It does not raise the issue of a stable kernel API:

The solution is to work on getting the module included into the kernel. All problems with changing kernel APIs vanish as soon as your module is included. This is independent from what the module in question is doing.

Yes, but the question is:
What's the trick to get the module into the kernel?

The 'trick' is to write well designed, maintainable code, and accept all criticism with good grace. (It helps if the code works too)

By far the best approach is to incrementally improve what is already in the kernel. In this case, that probably means fbdev and/or DRI. If you get them to play nicely together and gradually enhance them to provide the functionality you need, I think you would make a lot of people happy.

Quoted 3 lines

It seems that we are currently under the mercy of the few, who have the power to control this. And forking isn't really a solution.

It is true that a thick skin helps. But if you demonstrate (with code) that you know what you are talking about, and respond intelligently to all feedback (even when you don't feel the feedback itself is intelligent) people will listen to you.

The coin of this realm is very much code. That is one of the reasons to start with small patches to existing code: it increases your credibility with less investment than creating a great big slab of code.

Quoted 4 lines

With a stable API, I can just implement whatever w/o caring whether it is included into the kernel. Now that's freedom!

That's userspace.

Improve what is in the kernel so that it presents to userspace whatever API you need, and write stuff in userspace to your hearts content. I'm sure that there is no need for the entire 'X' server to be in the kernel, and I'm equally sure that there are advantages in the kernel providing more services for an X server than it currently does. You need to find that balance. It may be hard, but there are people here who will help. You add bits of functionality - people will question them and require you to justify them. Some will make it, some won't. Bit by bit you will arrive at a workable solution.

As a sort of example: were I to start writing an NFS server for Linux today, I wouldn't put it all in the kernel. I would figure out the minimum services I needed from the kernel and add them one at a time, at each step modifying the userspace NFS server to use this functionality. Some of it would be quite tricky - particularly achieving zero-copy reads and single-copy writes. But I'm sure it is possible, and I'm sure there are people here who would help point me in the right direction.

NeilBrown

#4 lore raw

Hi!

Quoted 16 lines
Quoted 3 lines

With a stable API, I can just implement whatever w/o caring whether it is included into the kernel. Now that's freedom!

That's userspace.

Improve what is in the kernel so that it presents to userspace whatever API you need, and write stuff in userspace to your hearts content. I'm sure that there is no need for the entire 'X' server to be in the kernel, and I'm equally sure that there are advantages in the kernel providing more services for an X server than it currently does. You need to find that balance. It may be hard, but there are people here who will help. You add bits of functionality - people will question them and require you to justify them. Some will make it, some won't. Bit by bit you will arrive at a workable solution.

Quoted 8 lines

As a sort of example: were I to start writing an NFS server for Linux today, I wouldn't put it all in the kernel. I would figure out the minimum services I needed from the kernel and add them one at a time, at each step modifying the userspace NFS server to use this functionality. Some of it would be quite tricky - particularly achieving zero-copy reads and single-copy writes. But I'm sure it is possible, and I'm sure there are people here who would help point me in the right direction.

I'm sure it is still possible to rewrite knfsd into userspace :-). With splice & friends, maybe it is now easier to do 0-copy...

Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html