On 03/21/2017 10:59 AM, Frans van Berckel wrote: >> Are you talking about the driver or the firmware? > > The driver (including the sparc kernel, true).
Ok. Then it's a bug that will need some git-bisecting. >> No, we have to fix the actual bug. Jamming an old, unsupported kernel >> into a sparc64 package is a workaround, not a fix. > > True, but nobody is listing. So being happy with a workaround :-) It happens. People are busy with work and there is sometimes lots of traffic on the lists. I also didn't learn about this issue until today and I'm on both the debian-sparc and the sparclinux mailing lists. >> You should add some SPARC kernel people to the CC of this bug report >> and also post this to the sparclinux kernel mailing list so you get >> some attention. > > Sorry, but I did at least five sparclinux mailing list posts on this > topic, as well. With one of them pointing to the open bug report. Yes, then you need to keep pinging. Sometimes these things can take a bit longer. I made the same experiences often enough. As I said, you have the guy who worked on the endianness issue and it's probably not a bad idea to ping him directly. Don't give up :). Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - [email protected] `. `' Freie Universitaet Berlin - [email protected] `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
