<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for BrassTacks (wpc)</title>
	<atom:link href="http://jaoswald.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://jaoswald.wordpress.com</link>
	<description>Joe Oswald's Project/Hacking Blog</description>
	<lastBuildDate>Sun, 07 Dec 2008 17:27:44 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Linux/BSD with &#8220;Lisp personality&#8221;? by ajzimm3rman</title>
		<link>http://jaoswald.wordpress.com/2007/03/13/linuxbsd-with-lisp-personality/#comment-299</link>
		<dc:creator>ajzimm3rman</dc:creator>
		<pubDate>Sun, 07 Dec 2008 17:27:44 +0000</pubDate>
		<guid isPermaLink="false">http://jaoswald.wordpress.com/2007/03/13/linuxbsd-with-lisp-personality/#comment-299</guid>
		<description>Sounds very interesting, and something I would go along with completely.</description>
		<content:encoded><![CDATA[<p>Sounds very interesting, and something I would go along with completely.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Symbolics Rev. C Keyboard Secrets by asciilifeform</title>
		<link>http://jaoswald.wordpress.com/2007/09/26/symbolics-rev-c-keyboard-secrets/#comment-281</link>
		<dc:creator>asciilifeform</dc:creator>
		<pubDate>Tue, 13 Nov 2007 15:51:54 +0000</pubDate>
		<guid isPermaLink="false">http://jaoswald.wordpress.com/2007/09/26/symbolics-rev-c-keyboard-secrets/#comment-281</guid>
		<description>Argh, I suppose I should have actually read your post - you have already read my code. Sorry about the confusion.</description>
		<content:encoded><![CDATA[<p>Argh, I suppose I should have actually read your post &#8211; you have already read my code. Sorry about the confusion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on MacIvory Keyboard Support Software by asciilifeform</title>
		<link>http://jaoswald.wordpress.com/2007/10/09/macivory-keyboard-support-software/#comment-280</link>
		<dc:creator>asciilifeform</dc:creator>
		<pubDate>Tue, 13 Nov 2007 15:50:10 +0000</pubDate>
		<guid isPermaLink="false">http://jaoswald.wordpress.com/2007/10/09/macivory-keyboard-support-software/#comment-280</guid>
		<description>Just a moment ago I commented on one of your older entries, but here goes.

Having no Lisp Machine, I have entirely reverse-engineered the keyboard protocol &quot;with my bare hands&quot; (oscilloscope.) Here (http://lmkbd.googlecode.com/svn/trunk/symkeys.asm) is the table of keycodes for the Old Style Keyboard (new style is probably identical.) If you look at the schematics (http://www.asciilifeform.com/images/3.png) and PIC16F84 code in the rest of my project, you will see how to connect the device and what the protocol looks like: you simply toggle the clock line to increment a counter, and the keyboard will toggle a data line if the key corresponding to that counter value is pressed. My current code simply lights an LED if any key is pressed, but it should be easy to extend it to transmit PS/2 keycodes (unfortunately, I have not had the time to finish this project.)

Good luck!</description>
		<content:encoded><![CDATA[<p>Just a moment ago I commented on one of your older entries, but here goes.</p>
<p>Having no Lisp Machine, I have entirely reverse-engineered the keyboard protocol &#8220;with my bare hands&#8221; (oscilloscope.) Here (<a href="http://lmkbd.googlecode.com/svn/trunk/symkeys.asm" rel="nofollow">http://lmkbd.googlecode.com/svn/trunk/symkeys.asm</a>) is the table of keycodes for the Old Style Keyboard (new style is probably identical.) If you look at the schematics (<a href="http://www.asciilifeform.com/images/3.png" rel="nofollow">http://www.asciilifeform.com/images/3.png</a>) and PIC16F84 code in the rest of my project, you will see how to connect the device and what the protocol looks like: you simply toggle the clock line to increment a counter, and the keyboard will toggle a data line if the key corresponding to that counter value is pressed. My current code simply lights an LED if any key is pressed, but it should be easy to extend it to transmit PS/2 keycodes (unfortunately, I have not had the time to finish this project.)</p>
<p>Good luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Symbolics keyboard to PIC, step 1 by asciilifeform</title>
		<link>http://jaoswald.wordpress.com/2007/09/04/symbolics-keyboard-to-pic-step-1/#comment-279</link>
		<dc:creator>asciilifeform</dc:creator>
		<pubDate>Tue, 13 Nov 2007 15:43:11 +0000</pubDate>
		<guid isPermaLink="false">http://jaoswald.wordpress.com/2007/09/04/symbolics-keyboard-to-pic-step-1/#comment-279</guid>
		<description>These pieces of my half-completed project may help you:

http://www.asciilifeform.com/images/3.png

http://lmkbd.googlecode.com/svn/trunk/</description>
		<content:encoded><![CDATA[<p>These pieces of my half-completed project may help you:</p>
<p><a href="http://www.asciilifeform.com/images/3.png" rel="nofollow">http://www.asciilifeform.com/images/3.png</a></p>
<p><a href="http://lmkbd.googlecode.com/svn/trunk/" rel="nofollow">http://lmkbd.googlecode.com/svn/trunk/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ordering a Lisp machine by thekevinmackay</title>
		<link>http://jaoswald.wordpress.com/2007/07/11/ordering-a-lisp-machine/#comment-253</link>
		<dc:creator>thekevinmackay</dc:creator>
		<pubDate>Thu, 02 Aug 2007 00:39:25 +0000</pubDate>
		<guid isPermaLink="false">http://jaoswald.wordpress.com/2007/07/11/ordering-a-lisp-machine/#comment-253</guid>
		<description>Cool. I just Wikipedia&#039;d MacIvory to guess what you might be doing with one. Looks like dead technology. Are you self-training as a computer architect?</description>
		<content:encoded><![CDATA[<p>Cool. I just Wikipedia&#8217;d MacIvory to guess what you might be doing with one. Looks like dead technology. Are you self-training as a computer architect?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ordering a Lisp machine by jaoswald</title>
		<link>http://jaoswald.wordpress.com/2007/07/11/ordering-a-lisp-machine/#comment-252</link>
		<dc:creator>jaoswald</dc:creator>
		<pubDate>Wed, 01 Aug 2007 20:45:38 +0000</pubDate>
		<guid isPermaLink="false">http://jaoswald.wordpress.com/2007/07/11/ordering-a-lisp-machine/#comment-252</guid>
		<description>MW is a &quot;megaword&quot;: the MacIvory uses a 40-bit word. The Lisp machines don&#039;t address memory at the byte level; some of the bits were used to distinguish between address pointers, integers, machine instructions, and other data types. That allows the machine to automatically detect illegal array accesses and automatically manage dynamic memory allocation. Another 8 bits per word are used for ECC (error correction coding) to allow correction of single-bit errors. So a 8 megabyte memory board is 1.3 MW of MacIvory memory.

I haven&#039;t seen any compromising pictures of you on the web, yet. </description>
		<content:encoded><![CDATA[<p>MW is a &#8220;megaword&#8221;: the MacIvory uses a 40-bit word. The Lisp machines don&#8217;t address memory at the byte level; some of the bits were used to distinguish between address pointers, integers, machine instructions, and other data types. That allows the machine to automatically detect illegal array accesses and automatically manage dynamic memory allocation. Another 8 bits per word are used for ECC (error correction coding) to allow correction of single-bit errors. So a 8 megabyte memory board is 1.3 MW of MacIvory memory.</p>
<p>I haven&#8217;t seen any compromising pictures of you on the web, yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ordering a Lisp machine by thekevinmackay</title>
		<link>http://jaoswald.wordpress.com/2007/07/11/ordering-a-lisp-machine/#comment-251</link>
		<dc:creator>thekevinmackay</dc:creator>
		<pubDate>Wed, 01 Aug 2007 15:54:33 +0000</pubDate>
		<guid isPermaLink="false">http://jaoswald.wordpress.com/2007/07/11/ordering-a-lisp-machine/#comment-251</guid>
		<description>Oh, and whats a MW of memory?
Sounds very powerful.</description>
		<content:encoded><![CDATA[<p>Oh, and whats a MW of memory?<br />
Sounds very powerful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ordering a Lisp machine by thekevinmackay</title>
		<link>http://jaoswald.wordpress.com/2007/07/11/ordering-a-lisp-machine/#comment-250</link>
		<dc:creator>thekevinmackay</dc:creator>
		<pubDate>Wed, 01 Aug 2007 15:52:57 +0000</pubDate>
		<guid isPermaLink="false">http://jaoswald.wordpress.com/2007/07/11/ordering-a-lisp-machine/#comment-250</guid>
		<description>Joe,

I google searched &quot;communicating with GPIB synthesizer example code&quot; and your blog came up on page 1. You must be prominent in the field. I envy your PhD.

On a separate note, both my full name and e-mail address were &quot;already in use&quot; when I set up an account to leave this comment. Somebody has apparently set up a me blog behind my back. I hope there are not pictures...

BR,
Kevin
kevin_mackay@ltx.com</description>
		<content:encoded><![CDATA[<p>Joe,</p>
<p>I google searched &#8220;communicating with GPIB synthesizer example code&#8221; and your blog came up on page 1. You must be prominent in the field. I envy your PhD.</p>
<p>On a separate note, both my full name and e-mail address were &#8220;already in use&#8221; when I set up an account to leave this comment. Somebody has apparently set up a me blog behind my back. I hope there are not pictures&#8230;</p>
<p>BR,<br />
Kevin<br />
<a href="mailto:kevin_mackay@ltx.com">kevin_mackay@ltx.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dell 2007FP and xorg.conf by jkayser</title>
		<link>http://jaoswald.wordpress.com/2006/08/07/dell-2007fp-and-xorgconf/#comment-232</link>
		<dc:creator>jkayser</dc:creator>
		<pubDate>Mon, 15 Jan 2007 03:49:26 +0000</pubDate>
		<guid isPermaLink="false">http://jaoswald.wordpress.com/2006/08/07/dell-2007fp-and-xorgconf/#comment-232</guid>
		<description>Thank you for posting your &quot;xorg.conf&quot; file.  Windows clearly has Linux beat when it comes to hooking up new display hardware.  Don&#039;t get me wrong; I have worked on UNIX machines for 25 years, and I really love UNIX.  However, hooking up the 2007FP to CentOS was a real struggle.  Hooking it up to Windows Server 2003 was trivial -- load the 2007FP drivers (which were shipped with the monitor) and run.

I tried using your &quot;xorg.conf&quot; file, and discovered that some of the settings depended on the video card.  I have a different video card (ATI Mach64 3D Rage IIC) with 4MB of video RAM.  Since I have less video RAM, the 1600x1200@60 mode would not work with 24-bit color, but only with 16-bit color.  As a result, I had to tweak both the DEVICE section and the SCREEN section as well.

If any of your other readers want to try this, be forwarned that you should probably figure out which resolutions and color depths your video card will support (I used Windows Server 2003 to figure this out), and then modify BOTH the DEVICE section (for your video card), and the SCREEN section (for which color depths and screen resolutions your video card will support).

Thanks again for your initial post and &quot;xorg.conf&quot; file.  It was a huge help!</description>
		<content:encoded><![CDATA[<p>Thank you for posting your &#8220;xorg.conf&#8221; file.  Windows clearly has Linux beat when it comes to hooking up new display hardware.  Don&#8217;t get me wrong; I have worked on UNIX machines for 25 years, and I really love UNIX.  However, hooking up the 2007FP to CentOS was a real struggle.  Hooking it up to Windows Server 2003 was trivial &#8212; load the 2007FP drivers (which were shipped with the monitor) and run.</p>
<p>I tried using your &#8220;xorg.conf&#8221; file, and discovered that some of the settings depended on the video card.  I have a different video card (ATI Mach64 3D Rage IIC) with 4MB of video RAM.  Since I have less video RAM, the 1600&#215;1200@60 mode would not work with 24-bit color, but only with 16-bit color.  As a result, I had to tweak both the DEVICE section and the SCREEN section as well.</p>
<p>If any of your other readers want to try this, be forwarned that you should probably figure out which resolutions and color depths your video card will support (I used Windows Server 2003 to figure this out), and then modify BOTH the DEVICE section (for your video card), and the SCREEN section (for which color depths and screen resolutions your video card will support).</p>
<p>Thanks again for your initial post and &#8220;xorg.conf&#8221; file.  It was a huge help!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Venting about Linux by josephoswald</title>
		<link>http://jaoswald.wordpress.com/2006/08/02/venting-about-linux/#comment-228</link>
		<dc:creator>josephoswald</dc:creator>
		<pubDate>Fri, 13 Oct 2006 21:14:23 +0000</pubDate>
		<guid isPermaLink="false">http://jaoswald.wordpress.com/2006/08/02/venting-about-linux/#comment-228</guid>
		<description>I suppose Binford is right; Slackware does aspire to be a distribution for UNIX purists, and not necessarily the ready-for-the-desktop distribution.  Perhaps I need to get around to downloading an Ubuntu ISO and installing that instead. Or, follow your example of Fedora Core.</description>
		<content:encoded><![CDATA[<p>I suppose Binford is right; Slackware does aspire to be a distribution for UNIX purists, and not necessarily the ready-for-the-desktop distribution.  Perhaps I need to get around to downloading an Ubuntu ISO and installing that instead. Or, follow your example of Fedora Core.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
