> On Fre, 2003-03-14 at 17:42, Bhavana Nagendra wrote: 
> > I have a DRI based DRM driver and wanted to know if it needs a 
> > major device number assigned by the linux community, like any 
> > standalone driver.  
> 
> >From linux/Documentation/devices.txt:
> 
> 226 char        Direct Rendering Infrastructure (DRI)
>                   0 = /dev/dri/card0            First graphics card
>                   1 = /dev/dri/card1            Second graphics card
>                     ...
> 
> So it looks to me like char major 226 is reserved for the DRM.
> 
Right.

> > Since the driver opens /dev/dri/card0 as it boots up, 
> > I'd like to know how exactly does it use the DRIVER_MAJOR, 
> > DRIVER_MINOR macros?   Are these macros required?
> 
> They denote the API version of the specific DRM, not the 
> major and minor
> of the device. You probably don't need them if you don't use our DRM
> templates.
> 
> 

Thanks for your reply.  I'm using the DRM templates.  
These are the values I have, I must have got them from an
example.
DRIVER_MAJOR 1
DRIVER_MINOR 0
DRIVER_PATCHLEVEL 0

How do I find out what's the major, minor and patch level for 
the DRM I'm using?  The DRM I'm using is from CVS, ~July 2002. 

> Hope this helps,
> 
> 
> -- 
> Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux 
> (powerpc) developer
> XFree86 and DRI project member   /  CS student, Free Software 
> enthusiast
> 


-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to