Re: [XFree86] Help writing a accelerator X driver

2003-03-26 Thread dave
- Original Message - 
From: Mark Vojkovich [EMAIL PROTECTED]
To: dave [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, March 25, 2003 12:44 PM
Subject: Re: [XFree86] Help writing a accelerator X driver


 
You are being naive.  You don't have enough information to
 do such a thing.
 
 Mark.
 

Hi I think I do and in fact I am doing it the LNVRM part is working
Their is a lot to add to it yet but the basics are working
Like NV04_CHANNEL_DMA is up and running that is how my 
X client is sending data and commands to the chip .  
Just now I am adding more accelerator classs to LNVRM
then the fun of linking them into X
I say my LNVRM is already up and running allocating classs and free them
and controlling the chip and DMA  mappings and interrupts
my X client is already using NV04_REANDER_SOLID_RECTANGLE
thou DMA channel I also have made my own software class
NV04_NVXF_DISPLAY in steed of NV04_VIDEO_LUT_CURSOR_DAC
For controlling the screen


 On Tue, 25 Mar 2003, dave wrote:
 
  Help I am writing a X-4.2.x fully accelerator driver
  For NVIDIA video cards .
  
  It consisted of 2 parts 
   1. kernel LNVRM (LINUX NVIDIA RESOURCE MANAGER)
   2. XNVXF (NVIDIA X FREE)
  
  The kernel part controls the hardware 
  and the X part talks to the kernel part using  (ioctl)
  and the USER part of the hardware using DMA and MMIO  
  
  All data 2D ,3D ,IMAGE ,VIDEO ,  MPEG , OVERLAY to and from 
  screen MUST Go thou the accelerator and their can 
  be NO! direct access to screen memory can X function
  in this way?? (Complete accelerator driver)
  
  
  
  
  
  
  ___
  XFree86 mailing list
  [EMAIL PROTECTED]
  http://XFree86.Org/mailman/listinfo/xfree86
  
 
 

___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


http://www.xfree86.org/devel/ is gone?

2003-03-26 Thread Juliusz Chroboczek
 Not Found
 The requested URL /devel/ was not found on this server.

 Apache/1.3.26 Server at www.xfree86.org Port 80
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: http://www.xfree86.org/devel/ is gone?

2003-03-26 Thread David Dawes
On Wed, Mar 26, 2003 at 08:19:30PM +0100, Juliusz Chroboczek wrote:
 Not Found
 The requested URL /devel/ was not found on this server.

 Apache/1.3.26 Server at www.xfree86.org Port 80

That is correct.  Since this is a resource that contained information
that cannot be made publicly available, it has been removed.

David
-- 
David Dawes
Founder/committer/developer The XFree86 Project
www.XFree86.org/~dawes
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


XFree86 host.def file questions

2003-03-26 Thread Kendall Bennett
Hi Guys,

One area that appears to be severely lacking for the 'new' developer is 
guidance on how to set up the host.def file properly so that you can 
build XFree86 successfully on your system. The default xf86site.def is a 
good start, but it doesn't really explain things since everything is 
essentially commented out. You don't really know what stuff you *should* 
define to get a standard build on different systems.

Perhaps a good start would be to have a directory with sample host.def 
files in it, especially a good 'default' file that can be used to build a 
complete XFree86 system on Linux and FreeBSD for instance. That is where 
a lot of developers could really use a default they can just copy to 
host.def and then do a 'make World'.

Which brings me to my question. Do I need to uncomment the 
XF86CardDrivers section in the host.def file in order to build the driver 
modules? The comments would seem to indicate you need to do this, but 
IMHO that would be kind of silly (too error prone). I *think* in reality 
if you do not define this that the default set of all drivers will be 
built, and you can use this define to change which drivers actually get 
built. Is that correct?

Thanks!

---
Kendall Bennett
Chief Executive Officer
SciTech Software, Inc.
Phone: (530) 894 8400
http://www.scitechsoft.com

~ SciTech SNAP - The future of device driver technology! ~

___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: XFree86 host.def file questions

2003-03-26 Thread Mark Vojkovich
On Wed, 26 Mar 2003, Kendall Bennett wrote:

 Hi Guys,
 
 One area that appears to be severely lacking for the 'new' developer is 
 guidance on how to set up the host.def file properly so that you can 
 build XFree86 successfully on your system. The default xf86site.def is a 
 good start, but it doesn't really explain things since everything is 
 essentially commented out. You don't really know what stuff you *should* 
 define to get a standard build on different systems.
 
 Perhaps a good start would be to have a directory with sample host.def 
 files in it, especially a good 'default' file that can be used to build a 
 complete XFree86 system on Linux and FreeBSD for instance. That is where 
 a lot of developers could really use a default they can just copy to 
 host.def and then do a 'make World'.

  The xf86site.def IS the sample host.def.   You don't need the
host.def.  It merely overrides the xf86site.def and provides
a way to edit a file that doesn't get clobbered by CVS.  If 'make World'
doesn't just build without any editing at all, that is a bug.


 
 Which brings me to my question. Do I need to uncomment the 
 XF86CardDrivers section in the host.def file in order to build the driver 
 modules? The comments would seem to indicate you need to do this, but 
 IMHO that would be kind of silly (too error prone). I *think* in reality 
 if you do not define this that the default set of all drivers will be 
 built, and you can use this define to change which drivers actually get 
 built. Is that correct?

   All drivers get built unless you uncomment and edit the XF86CardDrivers.
The point of doing that in a separate file (the host.def) is so you
don't prevent the sample (the xf86site.def) from patching properly.


Mark.

___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: http://www.xfree86.org/devel/ is gone?

2003-03-26 Thread David Dawes
On Wed, Mar 26, 2003 at 08:50:32PM +0100, Juliusz Chroboczek wrote:
DD That is correct.  Since this is a resource that contained
DD information that cannot be made publicly available, it has been
DD removed.

Which means that we no longer have access to the patches@ and
cvs-commit@ list archives?  It doesn't make life much earlier.

Patches are now submitted via bugzilla, which is accessible to
everyone.  Once someone can tell me how we automatically forward
any further submissions to those addresses to bugzilla, we'll do
so.  cvs-commit has been a public list for a long time, and I'd be
surprised if one of the usual mailing list archives sites doesn't
carry it.

David
-- 
David Dawes
Founder/committer/developer The XFree86 Project
www.XFree86.org/~dawes
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: XFree86 host.def file questions

2003-03-26 Thread David Dawes
On Wed, Mar 26, 2003 at 12:42:03PM -0800, Kendall Bennett wrote:
Hi Guys,

One area that appears to be severely lacking for the 'new' developer is 
guidance on how to set up the host.def file properly so that you can 
build XFree86 successfully on your system. The default xf86site.def is a 
good start, but it doesn't really explain things since everything is 
essentially commented out. You don't really know what stuff you *should* 
define to get a standard build on different systems.

Perhaps a good start would be to have a directory with sample host.def 
files in it, especially a good 'default' file that can be used to build a 
complete XFree86 system on Linux and FreeBSD for instance. That is where 
a lot of developers could really use a default they can just copy to 
host.def and then do a 'make World'.

The general rule is don't create a host.def file unless you find
you need to.  It follows from this that a good default file is
an empty one, hence the empty collection of sample host.def files :-).
If the build fails without one, it's usually a bug.

David
-- 
David Dawes
Founder/committer/developer The XFree86 Project
www.XFree86.org/~dawes
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: XFree86 host.def file questions

2003-03-26 Thread David Dawes
On Wed, Mar 26, 2003 at 02:51:13PM -0800, Kendall Bennett wrote:
Mark Vojkovich [EMAIL PROTECTED] wrote:

  One area that appears to be severely lacking for the 'new' developer is 
  guidance on how to set up the host.def file properly so that you can 
  build XFree86 successfully on your system. The default xf86site.def is a 
  good start, but it doesn't really explain things since everything is 
  essentially commented out. You don't really know what stuff you *should* 
  define to get a standard build on different systems.
  
  Perhaps a good start would be to have a directory with sample host.def 
  files in it, especially a good 'default' file that can be used to build a 
  complete XFree86 system on Linux and FreeBSD for instance. That is where 
  a lot of developers could really use a default they can just copy to 
  host.def and then do a 'make World'.
 
   The xf86site.def IS the sample host.def.   You don't need the
 host.def.  It merely overrides the xf86site.def and provides a way
 to edit a file that doesn't get clobbered by CVS.  If 'make World'
 doesn't just build without any editing at all, that is a bug. 

Well if you don't actually need a host.def file, then that needs to be 
*much* more clearly explained in the build documentation. I just went 

Quoting from http://www.xfree86.org/current/BUILD2.html:

  2. Configuring the source before building

  In most cases it shouldn't be necessary to configure anything
  before building.

  If you do want to make configuration changes, it is recommended
  that you start by going to ...

David
-- 
David Dawes
Founder/committer/developer The XFree86 Project
www.XFree86.org/~dawes
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: http://www.xfree86.org/devel/ is gone?

2003-03-26 Thread Leif Delgass
On Wed, 26 Mar 2003, Thomas Dickey wrote:

 On Wed, Mar 26, 2003 at 05:58:54PM -0500, David Dawes wrote:
  On Wed, Mar 26, 2003 at 08:50:32PM +0100, Juliusz Chroboczek wrote:
  DD That is correct.  Since this is a resource that contained
  DD information that cannot be made publicly available, it has been
  DD removed.
  
  Which means that we no longer have access to the patches@ and
  cvs-commit@ list archives?  It doesn't make life much earlier.
  
  Patches are now submitted via bugzilla, which is accessible to
  everyone.  Once someone can tell me how we automatically forward
  any further submissions to those addresses to bugzilla, we'll do
  so.  cvs-commit has been a public list for a long time, and I'd be
  surprised if one of the usual mailing list archives sites doesn't
  carry it.
 
 I haven't noticed it on google (not that google is omniscient...)

Try this:
http://marc.theaimsgroup.com/?l=xfree-cvs

-- 
Leif Delgass 
http://www.retinalburn.net

___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: XFree86 host.def file questions

2003-03-26 Thread Kendall Bennett
David Dawes [EMAIL PROTECTED] wrote:

 The general rule is don't create a host.def file unless you find
 you need to.  It follows from this that a good default file is
 an empty one, hence the empty collection of sample host.def files
 :-). If the build fails without one, it's usually a bug. 

I can see that now, but when I was starting trying to build this stuff 
not long ago that was not at all clear to me. Seems to me that the 
barrier to entry for new developers with XFree86 is the lack of 
documentation and a simple 'getting started' guide. It helps immensely 
with projects if developers can download and do a successful compile 
within the first 10 minutes of unpacking the source code IMHO. Any longer 
and they start to lose interest fast ;-)

Regards,

---
Kendall Bennett
Chief Executive Officer
SciTech Software, Inc.
Phone: (530) 894 8400
http://www.scitechsoft.com

~ SciTech SNAP - The future of device driver technology! ~

___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: XFree86 host.def file questions

2003-03-26 Thread David Dawes
On Wed, Mar 26, 2003 at 05:11:36PM -0800, Kendall Bennett wrote:
David Dawes [EMAIL PROTECTED] wrote:

 The general rule is don't create a host.def file unless you find
 you need to.  It follows from this that a good default file is
 an empty one, hence the empty collection of sample host.def files
 :-). If the build fails without one, it's usually a bug. 

I can see that now, but when I was starting trying to build this stuff 
not long ago that was not at all clear to me. Seems to me that the 
barrier to entry for new developers with XFree86 is the lack of 
documentation and a simple 'getting started' guide. It helps immensely 
with projects if developers can download and do a successful compile 
within the first 10 minutes of unpacking the source code IMHO. Any longer 
and they start to lose interest fast ;-)

I guess you must have read something to even know about the existence
of a host.def file.  I presume that it was misleading, and so should
be fixed.

I think that http://www.xfree86.org/current/BUILD.html is a
reasonable introduction to building XFree86, but suggestions for
improving that document are most welcome.  The best starting point
for documentation in general is is http://www.xfree86.org/current/,
which is an index of the online documentation that we have available
for the most recent release.

I wish there was as much information available when I got started. :-)
I can understand that you're pretty busy and have a lot to do.  If
the typical would-be developer is put off by not being able to
build within 10 minutes of unpacking, then they're probably not
going to make much progress with any real development challenges.
I'll spare everyone my when I was a lad stories :-)

David
--
David Dawes
Founder/committer/developer The XFree86 Project
www.XFree86.org/~dawes
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: http://www.xfree86.org/devel/ is gone?

2003-03-26 Thread Alan Coopersmith
David Dawes wrote:
On Wed, Mar 26, 2003 at 08:50:32PM +0100, Juliusz Chroboczek wrote:

DD That is correct.  Since this is a resource that contained
DD information that cannot be made publicly available, it has been
DD removed.
Which means that we no longer have access to the patches@ and
cvs-commit@ list archives?  It doesn't make life much earlier.
Patches are now submitted via bugzilla, which is accessible to
everyone. 
If we had previously submitted bugs/fixes to the patches mailing list
that haven't been integrated yet, do we need to resubmit via bugzilla?
Or is someone still working through the old backlog the old fashioned
way?
--
-Alan Coopersmith-  [EMAIL PROTECTED]
 Sun Microsystems, Inc.   -   Sun Software Group
 Quality, Integration,  Customer Success (QICS)
 Platform Globalization Engin. - X11 Engineering
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: http://www.xfree86.org/devel/ is gone?

2003-03-26 Thread David Dawes
On Wed, Mar 26, 2003 at 07:41:18PM -0800, Alan Coopersmith wrote:
David Dawes wrote:
 On Wed, Mar 26, 2003 at 08:50:32PM +0100, Juliusz Chroboczek wrote:
 
DD That is correct.  Since this is a resource that contained
DD information that cannot be made publicly available, it has been
DD removed.

Which means that we no longer have access to the patches@ and
cvs-commit@ list archives?  It doesn't make life much earlier.
 
 Patches are now submitted via bugzilla, which is accessible to
 everyone. 

If we had previously submitted bugs/fixes to the patches mailing list
that haven't been integrated yet, do we need to resubmit via bugzilla?
Or is someone still working through the old backlog the old fashioned
way?

There's no need to resubmit anything that has already been submitted
through the old mechanism.

David
-- 
David Dawes
Release Engineer/Architect  The XFree86 Project
www.XFree86.org/~dawes
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel