Re: Bug#352483: link broken on http://debian.org/ports/sparc/porting
Dear Sparc porters, There is a broken link on http://www.debian.org/ports/sparc/porting as described by the bug below: On Sun, Feb 12, 2006 at 10:52:08AM +0100, Miguel Gea Milvaques wrote: Package: www.debian.org Severity: normal The link the SPARC buildd web pages that points to http://sparc.debian.org/ is broken. Could you please give us the replacement link for that ? http://buildd.debian.org/~jeroen/status/architecture.php?a=sparc ? I've attached the current wml file for this page so that you can easily provide us a patch. Thanks and best regards. -- Simon Paillard #use wml::debian::template title=Debian SPARC -- Porting Documentation NOHEADER=yes #include $(ENGLISHDIR)/ports/sparc/menu.inc h1Debian SPARC Porting Documentation/h1 h2Porting Debian Packages to SPARC/h2 p If you want to be an official porter, you must be a registered Debian developer. That is, your public key must appear in the official keyring. p The Debian SPARC porting effort is now organized around the excellent codewanna-build/code system, first used for the a href=../m68k/m68k/a port. With codewanna-build/code in place, porting boils down to locating the packages where automatic compilation failed, and then going though and determining what went wrong. p Failed build logs can be found at a href=http://sparc.debian.org/;the SPARC buildd web pages/a. Also, you can email codewanna-build/code and ask it for the failed build logs (see the file codeREADME.mail/code from the codewanna-build/code distribution). p codequinn-diff/code output, which includes a report of packages by distribution which are out of sync in for the SPARC port can be found at a href=http://buildd.debian.org/quinn-diff/output/unstable/by_priority_split-sparc.txt;\ http://buildd.debian.org/quinn-diff/output/unstable/by_priority_split-sparc.txt/a. p Serious porters should learn how to interact with codewanna-build/code via email. You'll need to ask a href=mailto:[EMAIL PROTECTED]Ben Collins lt;[EMAIL PROTECTED]gt;/a to add your public key to the known list of keys. p All Debian developers can use Debian's a href=http://db.debian.org/machines.cgi?host=auric;auric/a and a href=http://db.debian.org/machines.cgi?host=vore;vore/a machines to test their packages on the SPARC architecture. h2I'm not an official developer; can I still help?/h2 p Certainly. In fact, most of the real work in a Debian port requires not official status, just knowledge. There are a number of things you can do: ul li Track down bugs, and report them to the a href=$(HOME)/Bugs/Debian Bug Tracking System/a. li Figure out patches for known bugs. Be sure to submit the patch to the Bug Tracking System! li Help with documentation. Most documentation areas are managed under CVS, and most documentation authors can give out CVS access to non-porters who are interested in helping. /ul p So, go ahead and email a href=mailto:debian-sparc@lists.debian.orglt;debian-sparc@lists.debian.orggt;/a with a description of how you'd like to help; we're sure someone there can get you started. # !-- Keep this comment at the end of the file # Local variables: # mode: sgml # sgml-indent-data:nil # sgml-doctype:../../releases/.doctype # End: # --
Re: XVR-500 support in Lenny
On Wed, Oct 22, 2008 at 12:46:16AM +0200, Petr Vyslouzil wrote: Dave, Julien, thanks for your replies. I asked just to make sure I did not miss something obvious (like the .config file in /boot dir :)). I've been wondering why Debian on Sparc doesn't have compiled-in drivers for SUN's graphics cards. I can confirm that sunxvr500 driver works flawlessly even with XVR-600 card (although lspci shows wrong description), so at least all Sun Blade [12]500 users would benefit. And I suppose that sunxvr2500 is not any worse. So, please, could you consider to compile them in? The difference between OpenBoot ansi terminal and XVR-600 framebuffer is abysmal. [adding debian-boot since it relates to the problems with installer on Sunblade 1000 which I recently reported] Petr, can you please try the images I've built from http://www.wooyd.org/debian/kernel/ They are the same as Debian's stock kernels, except that the CONFIG_FB_XVR500 and CONFIG_FB_XVR2500 are enabled (note that it does not make sense to build framebuffer drivers as modules, because they are used early during boot). I was hoping that enabling them will fix problems with the installer (black-and-white terminal, with invisible menu highlight) on my SunBlade 1000, however there is a PCI id mismatch which makes it not work for me. The XVR-500 framebuffer driver supports PCI ID 3d3d:07a0 (vendor is 3D Labs) while my card is reported as 1901:07a0 (vendor is Intergraph). Since 3D Labs bought Intergraph at some point, there is a chance that this is the same chip, but I will have to rebuild the kernel again to test it. Cheers. regards, Petr Petr: Well, a google search turned up this page (http://merkel.debian.org/~jurij/) which has the Debian kernel configurations. The entry for 2.6.26-8 for sparc, config-2.6.26-1-sparc64.gz http://merkel.debian.org/%7Ejurij/2.6.26-8/sparc/config-2.6.26-1-sparc64.gz shows: # CONFIG_FB_XVR500 is not set # CONFIG_FB_XVR2500 is not set Does that help? [I was expecting to find information that tells me where the config file details are contained on a running system (under /proc, I thought), but I haven't found that, yet Perhaps that functionality isn't available / compiled into the sparc kernels...] Cheers, Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Jurij Smakov [EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
