Re: Plans for mISDN? Was: [PATCH 00/14] [ISDN] ...

From: Marcel Holtmann
Date: Thu Feb 21 2008 - 14:46:22 EST


Hi Simon,

mISDN has two problems, which are of course interrelated:

mISDN has one problem that is even bigger than these: the kernel oopses if modules aren't loaded in the right order. misdn-init works around that, but if it doesn't work for some reason (and I can think of multiple here), the user is left with a kernel that oopses during hardware discovery and never gets to a stage where this can be rectified, as almost all distributions now have hardware discovery before the first opportunity to get a shell. At least these were my experiences the last time I tried it on my test box.

that is not a big problem at all. If you have to enforce a specific module load order then create some dummy exports like misdn_load() and use them from the module that depends on it. It is not beautiful, but sometimes you have to do it this way. So if that is stopping mainline inclusion it is a lame excuse.

Regards

Marcel

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/