On Sun, Nov 05, 2006 at 01:27:49PM -0800, David Miller wrote: > > This should be easy to fix, thanks for the report. I'll take > a look. > No problem. I'm happy to test patches, etc. > > Only in 2.6.18 do these drivers even have MODULE loading device > ID information, and nobody has done the userland components yet. > > Ubuntu and Debian use a hack'ish script that automatically finds the > correct SBUS modules by dumping the firmware device tree and looking > for certain node names. They have a simple file that has firmware > node name to kernel module name mappings, which the bootup and > installer infrastructure make use of. I forget where all of this is, > but I've tested it and it does work. > Thanks for the info. I'll take a look at edgy and see what they have done. Is anybody else running a pure 64bit distro? I am finding two of my favourite tools, xemacs and gdb to be a tad flakey. Haven't done any serious investigating yet, or reported any bugs. Just wondered if anyone else has experienced this? Andrew Walrond - To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
