<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> I have two EV4 or 45 alphas that I use. The AS500/166 I use for regression testing. When I hit significant milestones in some of my play projects I'll do regression testing on the alpha to make sure that I haven't introduced any portability issues. Getting X working on the AlphaStation hasn't been high on my priority list, but I've been halfway planning to some day. Truthfully, someday hasn't gotten any closer in the last 5 years, so I can't exactly complain that this would hurt me. I have been wanting somthing faster, however. If faster more modern systems are cheap and plentiful, what should I look for and where? The other is an alphabook 1 that I use when I feel like beating my head against the wall. I've managed to build two kinds of kernels. The first kind recognizes the scsi controler and disk. I can build kenels and play adventure with this one all week except it does not recognize the PCMCIA bridge. The other kind of kernel seems to recognize the PCMCIA bridge but breaks the SCSI controler. Not being able to find the root file system, it dies. Anybody out there have a kernel that supports both SCSI and PCMCIA on the alphabook 1, or better yet .configure and patches so I can build my own? I have found references to netbooting an alphabook. It appears to require a specific 3com nic. Does it boot from BOOTP or MOP? What device do I specify on the boot command line? Dialup Jon Norstog wrote: <blockquote cite="mid20090917050135.M48504@allidaho.com" type="cite"> <pre wrap="">Todd, are you maintaining for the Alpha "community?" Where do you live? I've done just what you suggest for people who were deeply involved inthe Alpha core project. jn ---------- Original Message ----------- From: "Smith, Todd" <a class="moz-txt-link-rfc2396E" href="mailto:Todd.Smith@camc.org"><Todd.Smith@camc.org></a> To: "Linux on Alpha processors" <a class="moz-txt-link-rfc2396E" href="mailto:axp-list@redhat.com"><axp-list@redhat.com></a> Sent: Wed, 16 Sep 2009 17:10:25 -0400 Subject: RE: [RFC] Dropping Alpha sparse mapping support from X </pre> <blockquote type="cite"> <pre wrap="">I don't use X on EV4 but I do have a 21066 UDB machine that I still run. I hope that dropping total support for EV4 isn't on the table unless someone has a better Alpha that they will ship me for the cost of shipping. Todd Smith -----Original Message----- From: <a class="moz-txt-link-abbreviated" href="mailto:axp-list-bounces@redhat.com">axp-list-bounces@redhat.com</a> [<a class="moz-txt-link-freetext" href="mailto:axp-list">mailto:axp-list</a>- <a class="moz-txt-link-abbreviated" href="mailto:bounces@redhat.com">bounces@redhat.com</a>] On Behalf Of Matt Turner Sent: Thursday, September 03, 2009 17:08 To: <a class="moz-txt-link-abbreviated" href="mailto:xorg-devel@lists.freedesktop.org">xorg-devel@lists.freedesktop.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:debian-alpha@lists.debian.org">debian-alpha@lists.debian.org</a>; Linux on Alpha processors Subject: [RFC] Dropping Alpha sparse mapping support from X Hi, I'd like to drop support for non-BWX Alphas (EV4 and original EV5) from X. These machines can't load/store to single bytes and require special sparse memory mappings. The code required to select which functions (sparse, dense) is convoluted, adds an extra layer of indirection, probably gets close to zero usage, and even less testing. Does anyone use X on EV4 or EV5 (not EV56, EV56 has BWX)? Thanks, Matt Turner _______________________________________________ axp-list mailing list <a class="moz-txt-link-abbreviated" href="mailto:axp-list@redhat.com">axp-list@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/axp-list">https://www.redhat.com/mailman/listinfo/axp-list</a> Confidentiality Note: The information contained in this message may be privileged and confidential. If this e-mail contains protected health information, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited,except as permitted by law. If you have received this communication in error, please notify the sender immediately by replying to this message and deleting it from your computer. Thank you. _______________________________________________ axp-list mailing list <a class="moz-txt-link-abbreviated" href="mailto:axp-list@redhat.com">axp-list@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/axp-list">https://www.redhat.com/mailman/listinfo/axp-list</a> -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. </pre> </blockquote> <pre wrap="">------- End of Original Message ------- _______________________________________________ axp-list mailing list <a class="moz-txt-link-abbreviated" href="mailto:axp-list@redhat.com">axp-list@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/axp-list">https://www.redhat.com/mailman/listinfo/axp-list</a> </pre> </blockquote> </body> </html>