Prev: [patch 1/7] [patch] DT3155: Use pci_get_device
Next: [patch] hamradio: avoid null deref
From: Robert P. J. Day on 23 Dec 2009 06:30

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
========================================================================
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [patch 1/7] [patch] DT3155: Use pci_get_device
Next: [patch] hamradio: avoid null deref