From: Bhavana N. <Bha...@3d...> - 2003-03-17 20:29:43
|
> On Fre, 2003-03-14 at 17:42, Bhavana Nagendra wrote:=20 > > I have a DRI based DRM driver and wanted to know if it needs a=20 > > major device number assigned by the linux community, like any=20 > > standalone driver. =20 >=20 > >From linux/Documentation/devices.txt: >=20 > 226 char Direct Rendering Infrastructure (DRI) > 0 =3D /dev/dri/card0 First graphics card > 1 =3D /dev/dri/card1 Second graphics = card > ... >=20 > So it looks to me like char major 226 is reserved for the DRM. >=20 Right. > > Since the driver opens /dev/dri/card0 as it boots up,=20 > > I'd like to know how exactly does it use the DRIVER_MAJOR,=20 > > DRIVER_MINOR macros? Are these macros required? >=20 > They denote the API version of the specific DRM, not the=20 > major and minor > of the device. You probably don't need them if you don't use our DRM > templates. >=20 >=20 Thanks for your reply. I'm using the DRM templates. =20 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=20 the DRM I'm using? The DRM I'm using is from CVS, ~July 2002.=20 > Hope this helps, >=20 >=20 > --=20 > Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux=20 > (powerpc) developer > XFree86 and DRI project member / CS student, Free Software=20 > enthusiast >=20 |
From: Michel <mi...@da...> - 2003-03-17 21:52:59
|
On Mon, 2003-03-17 at 21:29, Bhavana Nagendra wrote: > > On Fre, 2003-03-14 at 17:42, Bhavana Nagendra wrote: > > > > 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. These days, the DRM prints it on initialization, e.g. [drm] Initialized radeon 1.8.0 20020828 on minor 0 but I don't know if that was always the case. Then, if there has been a backwards compatible change in the interface of the DRM to user space, you need to bump the minor; if there has been an incompatible change (strongly discouraged), you need to bump the major. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast |