Re: devfs_mk_cdev question

On Tue, Dec 07, 2004 at 06:57:41PM +0100, Paul Akkermans wrote: > Where can I find this documentation? A: No. Q: Should I include quotations after my reply? Look in the kernel source tree, that is your best location to figure out what the code is doing, and to read any documentation that is prese

Re: devfs_mk_cdev question

On Tue, Dec 07, 2004 at 05:34:16PM +0100, Paul Akkermans wrote: > Can you also tell me what "class_simple_device_add() " does then? To quote the documentation (why do I write it if no one even reads it...): /** * class_simple_device_add - adds a class device to sysfs for a character driver * @c

Re: devfs_mk_cdev question

On Tue, Dec 07, 2004 at 03:16:48PM +0100, Paul Akkermans wrote: > Hi group, > > Can anybody tell me what happens in this piece of code: > > mousedev_table[minor] = mousedev; > > devfs_mk_cdev(MKDEV(INPUT_MAJOR, MOUSEDEV_MINOR_BASE + minor), >S_IFCHR|S_IRUGO|S_IWUSR, "input/mouse%d", minor);

Re: HotSync Hangs: Binding to path /dev/ttyUSB0

On Mon, Nov 11, 2002 at 12:39:52AM +1000, Jules wrote: > > >insmod usbserial vendor=0x830 product=0x3 Do NOT do this. This would cause the generic usb to serial driver to want to bind to your device, and not have the visor driver bind to it (luckily it looks like it is working properly in your k