Messages in this thread | | | Subject | Re: [OOPS/HACK] atmel_cs and the latest changes in sysfs/symlink.c | From | Marcel Holtmann <> | Date | Fri, 23 Apr 2004 16:26:52 +0200 |
| |
Hi Dmitry,
> > I haven't tested it yet, but the same problem should apply to the > > bt3c_cs driver for the 3Com Bluetooth card. Are there any patches > > available that integrates the PCMCIA subsystem into the driver model, so > > we don't have to hack around it if a firmware download is needed? > > > I do not know. But the problem seems to be somewhat widespread - I just got > oops with the following trace: > > [<c0182f99>] sysfs_create_link+0x29/0x140 > [<c01ac578>] kobject_hotplug+0x58/0x60 > [<c0211490>] class_device_dev_link+0x30/0x40 > [<c02117ad>] class_device_add+0xed/0x130 > [<e185ffab>] usb_register_dev+0x12b/0x170 [usbcore] > [<e1b2bf2a>] hiddev_connect+0x7a/0x120 [usbhid] > > I think we should not oops, just complain loudly, when we come across a > kobject which has never beek kobject_add()ed, like in patch below.
I can't tell you anything about the hiddev problem, but for the PCMCIA subsystem we have the problem that right now it is not integrated into the driver model. Maybe a dummy integration for PCMCIA would be nice or can we get a device_simple like we have class_simple?
Regards
Marcel
- 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/
| |