Just a short update on this bug if somebody has more time to work on this. I will be only partly available until the begining of august. I will be able to respond to mail, but most likely not be able to work on the package.
* The current version of mol in testing and unstable works with the patches from SuSE. So no update to mol or the driver packages is needed to fix the RC bug on mol-source. * The fix needed to be able to build mol kernel modules with the current Debian kernel was rejected by the kernel team. They only accept pachtes also accepted upstream and upstream does not like the patch. The longterm way forward is to integrate the mol modules into the upstream kernel. See #486798. * So the only short term option I see is to update mol-source based on the SuSE patches and to advise user to build their own kernel with the handl_mm_fault patch if they want to run mol. > The SuSE patches can be found here: > http://bb.zhang.free.fr/suse-mol-patch-for-2.6.25/ > I used all pachtes except suse-ppc32-mol-handle-mm-fault plus the > attached mol-mm.patch. > > diff --git a/arch/powerpc/kernel/ppc_ksyms.c b/arch/powerpc/kernel/ppc_ksyms.c > index c6b1aa3..455fb38 100644 > --- a/arch/powerpc/kernel/ppc_ksyms.c > +++ b/arch/powerpc/kernel/ppc_ksyms.c > @@ -189,6 +189,7 @@ EXPORT_SYMBOL(set_context); > extern long mol_trampoline; > EXPORT_SYMBOL(mol_trampoline); /* For MOL */ > EXPORT_SYMBOL(flush_hash_pages); /* For MOL */ > +EXPORT_SYMBOL(handle_mm_fault); /* For MOL */ > #ifdef CONFIG_SMP > extern int mmu_hash_lock; > EXPORT_SYMBOL(mmu_hash_lock); /* For MOL */ Gaudenz -- Ever tried. Ever failed. No matter. Try again. Fail again. Fail better. ~ Samuel Beckett ~ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
