Messages in this thread | | | From | Irfan Hamid <> | Subject | Re: Path Name to kdev_t | Date | Thu, 14 Nov 2002 22:50:48 +0000 |
| |
in all functions of the driver where you will need the kdev_t (e.g.: the VFS layer hooks) you will receive either a struct inode* and/or the struct file* of the device file. the i_rdev member of struct inode is defined as the kdev_t of the particular device.
hope this helps.
regards, irfan.
On Thursday 14 November 2002 01:49 pm, chandrasekhar.nagaraj wrote: > Hi, > > In one of the part of my driver module , I have a path name to a device > file (for eg:- /dev/hda1) .Now if I want to obtain the associated major > number and minor number i.e. device ID(kdev_t) of this file what would be > the procedure? > > Thanks and Regards > Chandrasekhar > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |