On 15 Jun 2003, Klaasjan Brand wrote: > On Sun, 2003-06-15 at 12:16, Robert P. J. Day wrote: > > > i don't know why this has never been fixed, but that #&^%@#&^($ > > riscom8 code has generated compile problems for as long as i can > > remember. > > > > deselect it and see what happens. and maybe someday, somebody > > will fix it. > > Please! file it in the kernel 2.5 bug database so that it's at least > known the driver fails. And if you really need it try to lend a hand in > fixing it. Kernel debugging is not that difficult ;) i don't know the procedure for logging a bug in the 2.5 kernel database, but i know for a fact that every module in each 2.5.XX release is tested. if you go to www.osdl.org/archive/cherry/stability, you can see the compile stability of all versions up to 2.5.70 (2.5.71 just became available so expect some new data shortly). if you check out "Modules (allmodconfig)", you'll see the output from the build and, sure enough, partway down, the riscom8 driver fails to compile. so it's not like no one is aware of this. it just seems no one is all that interested in fixing it at the moment. i remember this specific code being a problem so long ago, i just reflexively make sure it's deselected in every kernel i build. rday
