Global Sales Div. - presents your targeted list of customers
Aquire a perfect list of prospects for your business... y tnzvk vlmcn yhvlo myn Through World Data Corporation you have access to the largest demographic database of potential consumers and businesses in the WORLD. We make it easy for you. Simply define your target market with highly descriptive key words and phrases and we will build you the perfect targeted email list. Experience has proven a truly targeted email list of prospects can be up to 1000 times more responsive to your campaign compared to an untargeted list. Our lists are exclusive to our clients and are not available through any other source. Our lists are filtered through a national remove list (Do not mail list) then verified for deliverability. You will always be assured a fresh clean list. If you lack the resources or technology to send your list you are in luck. At World Data Corporation you have options. Additional services are as follows: Email List sending services Email List deliverability verification List Management services National remove list cleaning Unsubscribe and complainer removal service Bounce-back sorting and categorizing Auto-replies (filed separately) Non-existent domains (removed) Suspended mailboxes (removed) Over quota mailboxes (filed separately) Note: If you do not wish to advertise a website we can provide you with an automated toll free telephone message center to go with your email campaign. You canspeak with a representativeabout all of our available service packagesby calling the following toll-free number: 1.866.662.3388 WE LOOK FORWARD TO TURBO-CHARGING YOUR SALES. To unsubscribe simply reply to this email with the subject "unsubscribe"n sbtvqhmjd vjrrhimkf or call: 1-866-457-8755 World Data Corporationf cprvz wzdsm ymsju gzwb Sun Towers Building, 1st Floor, Office #39l fzwbt yhlqz hlhhg ox Betania, Panama City, Zona 6, Rep.Of Panamam kenmgslf atkxj Legal Department Telephone: +54-11-4032-1008e ujzgvbj image/jpegimage/jpegimage/jpegimage/jpegimage/jpegimage/jpeg
About Xwrapper
Hi, i am searching a way the Xwrapper to connect to kdm and not xdm. Any ideas? Regards, Teo. Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail! http://login.mail.lycos.com/r/referral?aid=27005 ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Manufacturers who fully disclosed specifications for agp cards?
Ryan Underwood wrote: Your request for free publication is undeniably idealistic. I think it is a perfectly reasonable compromise to provide specs under NDA to developers who have shown themselves to be productive and trustworthy in the past, e.g. by contributing to XFree86 or producing and supporting an own 3rd-party driver like Tungsten Graphics. It is a much less risky investment for the chip manufacturer than freely publishing documentation for all. The manufacturer will rarely reach any individuals who would not have qualified for a NDA anyway, and will most likely end up giving their competitors ideas they may not have had otherwise. The problem is that none of the NDAs I have seen (which is not that many) explicitly give you the rights to release source code based on documentation on NDA. If you happen to work for a company that is extremely cautious about such legal issues, that means you don't get to sign any NDAs. Personally (i.e., not speaking for my employer in any way) agree that it's reasonable for hardware vendors to release documentation under NDA. However, if they're releasing NDA documentation to developers for the purpose of creating open-source drivers, the NDA should explicitly give the developers that right. Again, that's just this developer's personal opinion. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: help new Developer
On Mon, Feb 02, 2004 at 06:34:40PM +1300, dave wrote: Hi I have just go my computers up and running and am ready to Start my X11 driver I have downloaded the latest dev-4.3.99.902 The drivers directory name will be nvxf So can some one give a quick start help about how to enter my driver In the tree and get it started ? What hardware does nvxf support Dave ? Alan. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: help new Developer
- Original Message - From: Alan Hourihane [EMAIL PROTECTED] To: dave [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, February 02, 2004 10:50 PM Subject: Re: help new Developer On Mon, Feb 02, 2004 at 06:34:40PM +1300, dave wrote: Hi I have just go my computers up and running and am ready to Start my X11 driver I have downloaded the latest dev-4.3.99.902 The drivers directory name will be nvxf So can some one give a quick start help about how to enter my driver In the tree and get it started ? What hardware does nvxf support Dave ? Alan. its a DMA based driver for NVIDIA cards NV04 - NVxx and also has a kernel module (resource manager) ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: help new Developer
On Mon, Feb 02, 2004 at 11:35:23PM +1300, dave wrote: - Original Message - From: Alan Hourihane [EMAIL PROTECTED] To: dave [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, February 02, 2004 10:50 PM Subject: Re: help new Developer On Mon, Feb 02, 2004 at 06:34:40PM +1300, dave wrote: Hi I have just go my computers up and running and am ready to Start my X11 driver I have downloaded the latest dev-4.3.99.902 The drivers directory name will be nvxf So can some one give a quick start help about how to enter my driver In the tree and get it started ? What hardware does nvxf support Dave ? Alan. its a DMA based driver for NVIDIA cards NV04 - NVxx and also has a kernel module (resource manager) Does it provide any benefit over the current 'nv' driver ? Speed ? Linux-only ? Alan. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Manufacturers who fully disclosed specifications for agp cards?
On Sat, Jan 31, 2004 at 04:55:29PM -0600, Ryan Underwood wrote: Your request for free publication is undeniably idealistic. I think it is a perfectly reasonable compromise to provide specs under NDA to developers who have shown themselves to be productive and trustworthy in the past, e.g. by contributing to XFree86 or producing and supporting an own 3rd-party driver like Tungsten Graphics. It is a much less risky investment for the chip manufacturer than freely publishing documentation for all. The manufacturer will rarely reach any individuals who would not have qualified for a NDA anyway, and will most likely end up giving their competitors ideas they may not have had otherwise. What about freely publish the documentation for older chips? That should help both the beginner developer to find his way around and the chip manufacturer push the terms he is using and his general way of doing things. As for the claim that some people might give up on buying new hardware, creating a secondary market for his old hardware should compensate for it because it should give him a bigger share of the market for new hardware too. I think that freely publish the documentation for the common features and only hiding the more advance ones is also reasonable. As an aside, some one wrote here some time ago that the best way to get started is by learning from a book. What books are there that have substantial part on the lower level of the interface to the hardware? -- If you have an apple and I have an apple and we exchange apples then you and I will still each have one apple. But if you have an idea and I have an idea and we exchange these ideas, then each of us will have two ideas. -- George Bernard Shaw (sent by shaulk @ actcom . net . il) ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
link xfree86-server statically
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello , i'm running mandrake 9.2 on their secure-kernel which is patched with grsecurity.I saw a thread in the grsecurity forum that smowhat explained howto run xfree86 on a grsecurity (with pax) patched kernel.The only for me suitable option would be to statically link the xfree86 server. I'm quite a noob and started just 6 month's ago to seriously work with linux ,how could i statically link the xfree86 server on a allready running mandrake linux 9.2 box ( mandrake 9.2 box comes with normal secure enterprise kernels. kind regards, Peter Harmsen -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAHkO4HioDLONIjLARAnR2AJ41ZA5d9lutIbarnt44o59Wbz2USACguijs qadjFnxOQ2BYcSvzxrD964c= =+2Y/ -END PGP SIGNATURE- ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: help new Developer
- Original Message - From: Alan Hourihane [EMAIL PROTECTED] To: dave [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, February 02, 2004 11:39 PM Subject: Re: help new Developer On Mon, Feb 02, 2004 at 11:35:23PM +1300, dave wrote: - Original Message - From: Alan Hourihane [EMAIL PROTECTED] To: dave [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, February 02, 2004 10:50 PM Subject: Re: help new Developer On Mon, Feb 02, 2004 at 06:34:40PM +1300, dave wrote: Hi I have just go my computers up and running and am ready to Start my X11 driver I have downloaded the latest dev-4.3.99.902 The drivers directory name will be nvxf So can some one give a quick start help about how to enter my driver In the tree and get it started ? What hardware does nvxf support Dave ? Alan. its a DMA based driver for NVIDIA cards NV04 - NVxx and also has a kernel module (resource manager) Does it provide any benefit over the current 'nv' driver ? Speed ? Linux-only ? yes Using DMA for GR commands and all data transfers will be a lot faster and more efficient The driver fully utilizes the NV architecture I will be doing the 3D OpenGl part and VIDEO in Also it works in a completely deferent way The client (NVXF) sends commands to the NV chip thou channel's DMA or PIO these Channel are allocated by the kernel module amd are protected by the NV chip its self So a local error will not bring down the whole system Also functions like sleep process until commands is are finished using NOTIFY can be used Grate for compatibility, as the client only needs to concern its self with NV commands and not the chip IO so NVXF for NV04 will work on a NV15 And it is something I really won't to do :) Alan. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [Linux-fbdev-devel] Re: [forum] Re: Announcement: Modification to the base XFree86(TM) license.
On Sat, Jan 31, 2004 at 01:06:23PM +, Andrew C Aitchison wrote:
On Sat, 31 Jan 2004, Sven Luther wrote:
On Sat, Jan 31, 2004 at 09:10:22AM +, Andrew C Aitchison wrote:
For several years the mga fb kernel driver has supported dual head and/or
dvi on cards which aren't supported by the XFree86 driver (unless you
use the mga_hal). I've wanted to use kernel code to add this support to
XFree86, but been put off by the licence problem.
And, have you asked the mgafb driver author about this ?
You can hardly complain about lack of back traffic if you didn't ask him
about it, and if you did, it would be interesting to this discussion to
know what the problems where.
The Author ?
This is open source code; there may be 27 authors of the relevant file.
In XFree86 code I wouldn't know how to find the author of a file without
looking at that file. My {limited ,mis}understanding of clean room coding
makes me wary of reading any source unless I know that its licence will
allow me to do what I wish.
This is not acceptable. You are making wild accusations, and didn't even
try to contact the relevant people. To my knowledge, Petr is the sole
author of matroxfb, and there should not have been any problem in at
least asking him about this.
OK. So I've probably been paranoid and lazy, but if the fbdev licence
had been compatible with the XFree86 one, I would have done the work.
As it is the bar was raised high enough to stop me.
Yeah, whatever, but with you asking that the fbdev drivers change their
licence, it is the same thing as the GPL zealots not liking the new
XFree86 licence.
The way to solve this is by cooperation, not by staying aloft and
pointing the finger to the opposite side.
So, for one developer at least, the reason there has been no traffic
from fbdev to XFree86 is *directly* because of the licence issue.
Yeah, but again, was it so because of a definite will on the fbdev
authors part, or because you didn't ask him ?
Isn't the aim of open source licences is to allow people to use the code
without tracking down the author and obtaining permission ?
Yes. But the aim of GPLed code is that those author give you the
permission, but also force you to give back the changes you do under the
same licence. And altough i contribute to project with the licence the
project choose, i would never choose something else as the GPL for my
own projects. If someone else wants access to the code, they can ask me
for it, and we can discuss stuff and arrive to an arrangement.
I can do that with closed source.
Well, the only reason you need to contact the author is because you want
some additional right from him, if your project was GPLed, it was no
problem.
Friendly,
Sven Luther
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
Re: help new Developer
On Tue, Feb 03, 2004 at 12:38:16AM +1300, dave wrote: - Original Message - From: Alan Hourihane [EMAIL PROTECTED] To: dave [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, February 02, 2004 11:39 PM Subject: Re: help new Developer On Mon, Feb 02, 2004 at 11:35:23PM +1300, dave wrote: - Original Message - From: Alan Hourihane [EMAIL PROTECTED] To: dave [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, February 02, 2004 10:50 PM Subject: Re: help new Developer On Mon, Feb 02, 2004 at 06:34:40PM +1300, dave wrote: Hi I have just go my computers up and running and am ready to Start my X11 driver I have downloaded the latest dev-4.3.99.902 The drivers directory name will be nvxf So can some one give a quick start help about how to enter my driver In the tree and get it started ? What hardware does nvxf support Dave ? Alan. its a DMA based driver for NVIDIA cards NV04 - NVxx and also has a kernel module (resource manager) Does it provide any benefit over the current 'nv' driver ? Speed ? Linux-only ? yes Using DMA for GR commands and all data transfers will be a lot faster and more efficient The driver fully utilizes the NV architecture I will be doing the 3D OpenGl part and VIDEO in Also it works in a completely deferent way The client (NVXF) sends commands to the NV chip thou channel's DMA or PIO these Channel are allocated by the kernel module amd are protected by the NV chip its self So a local error will not bring down the whole system Also functions like sleep process until commands is are finished using NOTIFY can be used Grate for compatibility, as the client only needs to concern its self with NV commands and not the chip IO so NVXF for NV04 will work on a NV15 And it is something I really won't to do :) Is it something that could be integrated with the current 'nv' driver as this would be the third driver to support NVIDIA cards. i.e. NVIDIA's own binary driver, the 'nv' driver and now this. If your going to support the DRI (for 3D) then it'd be great to integrate that code into the existing 'nv' driver. If that's the case, then getting your driver modifications into the DRI project would be wise. I suggest subscribing to the dri-devel lists at sourceforge. Also, utilizing the DRM kernel module layer would also be good for the kernel module. And if you are doing something more in your kernel module, it might be possible to fold your changes into other driver modules to benefit. Alan. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [Linux-fbdev-devel] Re: [forum] Re: Announcement: Modification to the base XFree86(TM) license.
On Sat, Jan 31, 2004 at 09:10:22AM +, Andrew C Aitchison wrote:
On Fri, 30 Jan 2004, Sven Luther wrote:
Yeah, that would be rather problematic, but anyway, most of the things
move from the XFree86 code to fbdev code, and most often, it is not code
that is copied, but the register information and such. It is always
easier to get specs if you are working for XFree86 than if you plan to
do some kernel driver work.
On Sat, 31 Jan 2004, Benjamin Herrenschmidt wrote:
The fact that it is mostly a one way is mostly due to the fact that the
main problem here is seeking for HW informations.
For several years the mga fb kernel driver has supported dual head and/or
dvi on cards which aren't supported by the XFree86 driver (unless you
use the mga_hal). I've wanted to use kernel code to add this support to
XFree86, but been put off by the licence problem.
On Sat, 31 Jan 2004, Sven Luther wrote:
And, have you asked the mgafb driver author about this ?
You can hardly complain about lack of back traffic if you didn't ask him
about it, and if you did, it would be interesting to this discussion to
know what the problems where.
On Sat, Jan 31, 2004 at 01:06:23PM +, Andrew C Aitchison wrote:
The Author ?
This is open source code; there may be 27 authors of the relevant file.
In XFree86 code I wouldn't know how to find the author of a file without
looking at that file. My {limited ,mis}understanding of clean room coding
makes me wary of reading any source unless I know that its licence will
allow me to do what I wish.
On Mon, 2 Feb 2004, Sven Luther wrote:
This is not acceptable. You are making wild accusations, and didn't even
try to contact the relevant people. To my knowledge, Petr is the sole
author of matroxfb, and there should not have been any problem in at
least asking him about this.
I didn't intend to make *any* accusations, and don't understand what
accusations I'm supposed to have made.
I clearly have to explain my starting position more clearly;
it is probably wrong, and almost certainly the cause of most of the
confusion, however it is how I came into this arguement, and maybe seeing
how I'm thinking will let you see that I wasn't making accusations.
My understanding of copyright/patents/plagarism (I'm vague and confused
about which this covers) is that merely by reading your document,
I am allowing the possibility that I may use that information in something
which I later write.
This is the principle behind cleanroom development, see
http://en.wikipedia.org/wiki/Cleanroom,
meaning 2.
If my licence to use your document doesn't allow me to do what I wish,
it is therefore better for me not to read your document.
My understanding about fbdev was that it was GPL-licenced, and that
it is *not* OK to incorporate GPL-ed code into XFree86.
Since I can't read the source code, I can't see who owns the bit I'm
interested in and can't therefore ask permission to use it under a
different licence.
I merely wished to point out that the GPL-licence *had* affected my
decision not to copy anything from fdbdev into XFree86.
Call me lazy, mis-informed, confused and paranoid, but I resent the
suggestion that I've been making accusations, wild or tame.
OK. So I've probably been paranoid and lazy, but if the fbdev licence
had been compatible with the XFree86 one, I would have done the work.
As it is the bar was raised high enough to stop me.
Yeah, whatever, but with you asking that the fbdev drivers change their
licence, it is the same thing as the GPL zealots not liking the new
XFree86 licence.
The way to solve this is by cooperation, not by staying aloft and
pointing the finger to the opposite side.
I didn't intend to ask that fbdev change their licence (although I wish
they would). I merely intended to point out that, however much the fault
was mine, the perception of the licence conflict had blocked transfer
from fbdev to XFree86.
Since Sven and Benjamin both suggested that transfer from fbdev to
XFree86 wasn't important, I thought it reasonable to relate my
experience showing that transfer in that direction was desirable and
that the GPL-licence was a hinderance.
I also realize that I have a habit of using complex and precise English.
As many people in this discussion are not native English speakers,
that is not smart, and may be why some of my intended meaning has
not got through. I apologize for this.
--
Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge
[EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
Regarding: www.doc.cs.univ-paris8.fr/mirrors/XFree86/xnews/
Hello, This e-mail has been sent to inform you that your web site URL has been submitted to our search engine database. This is the URL that will be added. URL : www.doc.cs.univ-paris8.fr/mirrors/XFree86/xnews/ DATE : 02/2/2004 9:52:29 IP ADDR : Unknown IP. User had used an automated software for url submission In order to complete this request we require that you click on the web site link below. This will confirm that you do wish to be added to our search engine. http://www.global-submit.com/confirm.cgi?T687452R213337 If you feel that you received this message in error or you did not have your web site submitted to our search engine, please click on the link below. We will make every effort to make sure that you are no longer bothered by this automated system. http://www.global-submit.com/clipout.cgi?T687452R213337 Thank you and please have a nice day Global-Submit.com tech Staff www.global-submit.com 1 819 571 4943 ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [Linux-fbdev-devel] Re: [forum] Re: Announcement: Modification to the base XFree86(TM) license.
On Mon, Feb 02, 2004 at 08:13:45AM -0500, Harold L Hunt II wrote:
Sven Luther wrote:
On Sat, Jan 31, 2004 at 01:06:23PM +, Andrew C Aitchison wrote:
On Sat, 31 Jan 2004, Sven Luther wrote:
On Sat, Jan 31, 2004 at 09:10:22AM +, Andrew C Aitchison wrote:
For several years the mga fb kernel driver has supported dual head
and/or
dvi on cards which aren't supported by the XFree86 driver (unless you
use the mga_hal). I've wanted to use kernel code to add this support to
XFree86, but been put off by the licence problem.
And, have you asked the mgafb driver author about this ?
You can hardly complain about lack of back traffic if you didn't ask him
about it, and if you did, it would be interesting to this discussion to
know what the problems where.
The Author ?
This is open source code; there may be 27 authors of the relevant file.
In XFree86 code I wouldn't know how to find the author of a file without
looking at that file. My {limited ,mis}understanding of clean room coding
makes me wary of reading any source unless I know that its licence will
allow me to do what I wish.
This is not acceptable. You are making wild accusations, and didn't even
try to contact the relevant people. To my knowledge, Petr is the sole
author of matroxfb, and there should not have been any problem in at
least asking him about this.
Wild accusations? How do you get wild accusations from pointing out
that there may be 27 authors of the relevant file? If anyone is
making wild accusations, it is you. Andrew simply stated the point that
Ok, sorry, shouldn't have said it so, maybe it was a bit exagerated.
Still this is degenerating in GPL bashing, which will bring us nowhere.
And if you didn't make the effort to ask at least once, where will we
go. I am sure that a post to the linux-fbdev mailing list would have
solved everything, or maybe the main maintainer of the matroxfb driver ?
this is not an issue about proving whether *one* file doesn't have
issues; rather, it is the issue of having to prove that *all* files do
not have issues, and many of these files may be just as messy in
authorship as Andrew is suggesting.
Still, there is a mailing list where all linux fbdev authors are, or at
least most of them, and bitkeeper will mostly give us full history, so i
doubt it is as bad as you say.
Also, most fbdev authors have also been XFree86 contributors in the
past, so i don't really know what the problem is here.
Friendly,
Sven Luther
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
Re: [Linux-fbdev-devel] Re: [forum] Re: Announcement: Modification to the base XFree86(TM) license.
On Mon, Feb 02, 2004 at 01:59:54PM +, Dr Andrew C Aitchison wrote:
On Sat, Jan 31, 2004 at 09:10:22AM +, Andrew C Aitchison wrote:
On Fri, 30 Jan 2004, Sven Luther wrote:
Yeah, that would be rather problematic, but anyway, most of the things
move from the XFree86 code to fbdev code, and most often, it is not code
that is copied, but the register information and such. It is always
easier to get specs if you are working for XFree86 than if you plan to
do some kernel driver work.
On Sat, 31 Jan 2004, Benjamin Herrenschmidt wrote:
The fact that it is mostly a one way is mostly due to the fact that the
main problem here is seeking for HW informations.
For several years the mga fb kernel driver has supported dual head and/or
dvi on cards which aren't supported by the XFree86 driver (unless you
use the mga_hal). I've wanted to use kernel code to add this support to
XFree86, but been put off by the licence problem.
On Sat, 31 Jan 2004, Sven Luther wrote:
And, have you asked the mgafb driver author about this ?
You can hardly complain about lack of back traffic if you didn't ask him
about it, and if you did, it would be interesting to this discussion to
know what the problems where.
On Sat, Jan 31, 2004 at 01:06:23PM +, Andrew C Aitchison wrote:
The Author ?
This is open source code; there may be 27 authors of the relevant file.
In XFree86 code I wouldn't know how to find the author of a file without
looking at that file. My {limited ,mis}understanding of clean room coding
makes me wary of reading any source unless I know that its licence will
allow me to do what I wish.
On Mon, 2 Feb 2004, Sven Luther wrote:
This is not acceptable. You are making wild accusations, and didn't even
try to contact the relevant people. To my knowledge, Petr is the sole
author of matroxfb, and there should not have been any problem in at
least asking him about this.
I didn't intend to make *any* accusations, and don't understand what
accusations I'm supposed to have made.
I clearly have to explain my starting position more clearly;
it is probably wrong, and almost certainly the cause of most of the
confusion, however it is how I came into this arguement, and maybe seeing
how I'm thinking will let you see that I wasn't making accusations.
My understanding of copyright/patents/plagarism (I'm vague and confused
about which this covers) is that merely by reading your document,
I am allowing the possibility that I may use that information in something
which I later write.
This is the principle behind cleanroom development, see
http://en.wikipedia.org/wiki/Cleanroom,
meaning 2.
If my licence to use your document doesn't allow me to do what I wish,
it is therefore better for me not to read your document.
My understanding about fbdev was that it was GPL-licenced, and that
it is *not* OK to incorporate GPL-ed code into XFree86.
Since I can't read the source code, I can't see who owns the bit I'm
interested in and can't therefore ask permission to use it under a
different licence.
I merely wished to point out that the GPL-licence *had* affected my
decision not to copy anything from fdbdev into XFree86.
Call me lazy, mis-informed, confused and paranoid, but I resent the
suggestion that I've been making accusations, wild or tame.
Well, i seriously doubt that reading the first lines of a file would
contaminate you, after all you could use head to look at them or
something. Also, you could have written to linux-fbdev mailing list if
you were interested, or even have asked on [EMAIL PROTECTED], and those
with interest in fbdev matters would have responded to you.
OK. So I've probably been paranoid and lazy, but if the fbdev licence
had been compatible with the XFree86 one, I would have done the work.
As it is the bar was raised high enough to stop me.
Yeah, whatever, but with you asking that the fbdev drivers change their
licence, it is the same thing as the GPL zealots not liking the new
XFree86 licence.
The way to solve this is by cooperation, not by staying aloft and
pointing the finger to the opposite side.
I didn't intend to ask that fbdev change their licence (although I wish
they would). I merely intended to point out that, however much the fault
was mine, the perception of the licence conflict had blocked transfer
from fbdev to XFree86.
Well, i believe this was not the only issue involved. And i guess that
if the XFree86 Project was asking the fbdev people that they move to a
dual licence or something such, in order to better share information and
code between the fbdev drivers and the XFree86 drivers, then
undoubtfully this would have happened, with the natural problem of
searching for non-active authors of past code. I believe that Benjaming
Herrenschmidt raising its concern about driver code consecutive to the
announcement of the XFree86 licence could be
Re: 4.4.0-RC2 and ATI R280 - success
On Sat, 2004-01-31 at 15:30 +0100, Torsten Duwe wrote: Hi all, being a developer myself I know what it's like to only hear from people with problems and working setups being taken for granted. So instead I want to drop you this quick note. I was looking for the fastest (fanless :) 3D graphics supported by free software, and if they haven't changed the specs, http://www.sapphiretech.com/dev/vga/9200.asp is exactly what I've gotten now. XFree-4.3 doesn't recognize it; with CVS head (?) of wednesday or so it works perfectly. GLXgears [EMAIL PROTECTED] fps, linux-2.6.2-rc1 beneath, in case someone cares. How many FPS do you get in Enemy Territory? That's what counts for me.. -- Torgeir Veimo [EMAIL PROTECTED] ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Manufacturers who fully disclosed specifications for agp cards?
On Mon, Feb 02, 2004 at 01:05:28AM -0800, Ian Romanick wrote: The problem is that none of the NDAs I have seen (which is not that many) explicitly give you the rights to release source code based on documentation on NDA. If you happen to work for a company that is extremely cautious about such legal issues, that means you don't get to sign any NDAs. Personally (i.e., not speaking for my employer in any way) agree that it's reasonable for hardware vendors to release documentation under NDA. However, if they're releasing NDA documentation to developers for the purpose of creating open-source drivers, the NDA should explicitly give the developers that right. I agree. To illuminate that point, a friend of mine applied for a NDA with Xerox to develop a Ghostscript filter for some of their inkjet printers. Upon receiving the NDA document, he realized that it specifically barred him from releasing any source code that he would develop based on their documentation. Xerox would not negotiate, so he gave up on it and bought a new printer from a different company. It is possible that NDAs that do not explicitly outline terms under which you can release source code could be even more dangerous than NDAs that come right out and say you can't publish source. The latter stops you from going any further right at the beginning, but the former could waste a lot of time and money and ruin your day if the company got the wrong attitude down the road. -- Ryan Underwood, [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: Manufacturers who fully disclosed specifications for agp cards?
On Mon, Feb 02, 2004 at 01:19:01PM +0200, Shaul Karl wrote: What about freely publish the documentation for older chips? That should help both the beginner developer to find his way around and the chip manufacturer push the terms he is using and his general way of doing things. Oh, I'd love it if they did this. Unfortunately, the decision is left up to the bean counters. So far, it's been a difficult case to prove that publishing hardware documentation openly results in more profit for consumer peripheral vendors. As for the claim that some people might give up on buying new hardware, creating a secondary market for his old hardware should compensate for it because it should give him a bigger share of the market for new hardware too. How? As I understand it, that is one of the presiding reasons why *not* to publish documentation for your older stuff; doing so might cause someone to keep using an old piece of hardware rather than upgrading to your newest model. Of course, that theory could be turned on its head if you include the possibility of buying from a competitor instead. But what it comes down to is sale or no sale; I think the majority opinion goes something like this: let support for older hardware die = sale support older hardware = no sale. Ignoring of course the cases where the mfg supports an older hardware and thus wins a loyal customer, or where the cust was going to upgrade anyway, and the mfg's lack of support causes them to seek a competitor. But we have to show that these cases have a noticeable impact on their bottom line if we want them to listen. I think that freely publish the documentation for the common features and only hiding the more advance ones is also reasonable. I'd like nothing more than to have register level documentation of every piece of hardware I own. Unfortunately, the market is not making that a reality right now. Will it ever? As an aside, some one wrote here some time ago that the best way to get started is by learning from a book. What books are there that have substantial part on the lower level of the interface to the hardware? I've never read a hardware programming book. The information in vendor databooks and driver source code are amazingly enlightening to a competent programmer; at least when they happen to be describing the same hardware. :) 3Dfx databooks Voodoo1-Voodoo3 are all available online and would be good reading material if you have never seen one before. There are some 3dlabs and mga databooks floating around on the net but I don't know if they are legal to obtain/link to. -- Ryan Underwood, [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: Manufacturers who fully disclosed specifications for agp cards?
Ryan Underwood wrote: I agree. To illuminate that point, a friend of mine applied for a NDA with Xerox to develop a Ghostscript filter for some of their inkjet printers. Upon receiving the NDA document, he realized that it specifically barred him from releasing any source code that he would develop based on their documentation. Xerox would not negotiate, so he gave up on it and bought a new printer from a different company. It is possible that NDAs that do not explicitly outline terms under which you can release source code could be even more dangerous than NDAs that come right out and say you can't publish source. The latter stops you from going any further right at the beginning, but the former could waste a lot of time and money and ruin your day if the company got the wrong attitude down the road. When S3 contracted with me to do the Savage driver way back when (3.3.4!), I put explicit language in the proposal stating that the resulting driver would be open source, and would be released to the XFree86 team on a periodic basis. I mentioned it several times during the negotiation process, just to make sure everyone understood what I was saying. It raises an interesting question, since you can actually glean more information from the source than you can from the confidential chip specs (which are extremely terse), but they had no problem with it. -- - Tim Roberts, [EMAIL PROTECTED] Providenza Boekelheide, Inc. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
howto greeke keyb layout
Hi, i have a suse8.0 installation and i want to change my keyboard layout in order to write in greek alphabet. Any ideas howto step by step? Regards, Teo. Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail! http://login.mail.lycos.com/r/referral?aid=27005 ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
http://www.lncrew.com
Hello, Thank you for registration on our board - http://www.lncrew.com Welcome to our underground Site! http://www.lncrew.com In our site you will find: Spam Hosting - from 20$ per mounth. Fraud Hosting - from 30$ per mounth. Stoln Credit Cards, Fake ID, DL's. Spam For free only from 1.02.2004 to 5.02.2004. Welcome - http://www.lncrew.com and http://forum.lncrew.com --- Best Hosting. e-mail: [EMAIL PROTECTED] abuse e-mail: [EMAIL PROTECTED] http://www.netua.com --- cock quadriceps macmillan coco carolingian derogatory didn't waller fungi morphology dangerous crucify dust bill cassius bessel automaton skin temerity sectoral nighthawk
Re: link xfree86-server statically
On Mon, 2 Feb 2004, netpython wrote: I'm quite a noob and started just 6 month's ago to seriously work with linux ,how could i statically link the xfree86 server on a allready running mandrake linux 9.2 box ( mandrake 9.2 box comes with normal secure enterprise kernels. You can compile the server with #define DoLoadableServer NO in site.def (I do this on a few Linux's to check that the server still works for me without wiping out the other parts of whatever distribution I'm using). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
compile error 4.3.0
Title: compile error 4.3.0 hi folks, i had a xf86sym compile error using the 4.1.0 sources that i patched with the 4.2.0 and 4.3.0 diff files. i also compiled and installed atk and pango before running make worldopts did i do it right? should i instead download the 4.3.0 sources? thanks and regards, carlos
Why the OS hang when I transfer from graphic mode to text mode
Hi , All After I start my machine in graphic mode as default in X-window (Redhat9) I found my linux os hang when I execute the following script: while true do init 3 sleep 10 init 5 sleep 10 done I have traced the source code of graphic driver XFree86 (I use the 9880 card of trident) and found that the system hang in the following functions: 1.InitAndStartDevices-EnableDevice 2.vbedoEdid 3.vgaHWSave The hang issue can only be duplicated randomly , often after the above script has been run for 30 minutes. Can anybody give me some ideas about this? Thanx. bst.,rgds Yukun ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
hi there
What's up, Feel younger and stonger and last longer, let me show you how. a href=http://olw.cleaxs.us/hgh/?hpsales;show you now ref/a/font http://kcj.cleaxs.us/hgh/?hpsales a href=http://azh.cleaxs.us/hgh/o.html;stop offerz/a ixf pbj gvj puh icv pgo tuy ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Estude e passe em alguns dos mais disputados.
Title: concursos publicos Respeitamos sua privacidade. Caso queira ser removido de nossa lista de e-mails, siga as instrues do rodap desta mensagem. CD-ROM com tudo o que voc precisa para estudar e passar em alguns dos principais concursos pblicos do Brasil. Material didtico e informativo. Contedo voltado para concursos pblicos da: - Polcia Civil, Militar e Federal - Secretaria da Educao - Receita Federal - Sade - Fiscal do INSS Quer saber mais informaes? Clique aqui! Caso no queira mais receber nossos e-mails informativos clique aqui!
Re: Why the OS hang when I transfer from graphic mode to text mode
--- Yukun Chen [EMAIL PROTECTED] wrote: Hi , All After I start my machine in graphic mode as default in X-window (Redhat9) I found my linux os hang when I execute the following script: while true do init 3 sleep 10 init 5 sleep 10 done I have traced the source code of graphic driver XFree86 (I use the 9880 card of trident) and found that the system hang in the following functions: 1.InitAndStartDevices-EnableDevice 2.vbedoEdid 3.vgaHWSave The hang issue can only be duplicated randomly , often after the above script has been run for 30 minutes. Can anybody give me some ideas about this? On some chips the VBE/DDC/i2c code causes lockups for various reasons. some seem to have to do with how the generic xfree86 i2c code works, others are due to weird quirks on chips that are not known to the driver writers, changing i2c addresses between chip revisions, monitors that return improperly formatted DDC info, etc. Alex Thanx. bst.,rgds Yukun __ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: compile error 4.3.0
you shud download 4.3.0, change host.def(may be), do make World -jassi On Tue, 03 Feb 2004 [EMAIL PROTECTED] wrote : hi folks, i had a xf86sym compile error using the 4.1.0 sources that i patched with the 4.2.0 and 4.3.0 diff files. i also compiled and installed atk and pango before running make worldopts did i do it right? should i instead download the 4.3.0 sources? thanks and regards, carlos
