lkml.org 
[lkml]   [2009]   [Dec]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
Date
From
Subjectany value in /proc/devices showing baseminor and minorct?

once upon a time, i tweaked fs/char_dev.c so that /proc/devices
would display not only the major number and device name, but the
baseminor and minorct values as well, thusly:

=====

diff --git a/fs/char_dev.c b/fs/char_dev.c
index a173551..57022d1 100644
--- a/fs/char_dev.c
+++ b/fs/char_dev.c
@@ -70,7 +70,8 @@ void chrdev_show(struct seq_file *f, off_t offset)
if (offset < CHRDEV_MAJOR_HASH_SIZE) {
mutex_lock(&chrdevs_lock);
for (cd = chrdevs[offset]; cd; cd = cd->next)
- seq_printf(f, "%3d %s\n", cd->major, cd->name);
+ seq_printf(f, "%3d %s [%d, %d]\n", cd->major, cd->name,
+ cd->baseminor, cd->minorct);
mutex_unlock(&chrdevs_lock);
}
}
=====
is there any value in an enhancement like that? i dreamed it up
based on one of the early examples from LDD3, where one has to use
"mknod" in user space to create the appropriate dev files based on the
kernel-space registration. the major number is accessible, of course,
but the minor numbers were simply *assumed* to be 0->3.

would printing out that extra info have any value? or even making
it user-configurable? or perhaps part of a debugging setting?

rday
--

========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.

Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================

\
 
 \ /
  Last update: 2009-12-23 12:27    [W:0.071 / U:0.820 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site