From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 4 Nov 2008 15:25:41 +0000 From: Eris Discordia To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <1CF8271E0E449545D858FAB3@[192.168.1.2]> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: [9fans] punched cards live Topicbox-Message-UUID: 2f42cbfe-ead4-11e9-9d60-3106f5b1d025 > i think it's a tradition at this point to use 0x20 and not 0x00 to > fill a fixed-with signature. ata identify device uses 0x20 to fill > out fixed-width fields like the serial number. i'd be interested > where this tradition popped up. 0 would make more sense. I risk being wrong--as always--and say it must have popped up in a normal ASCII environment. 0x20 = 32, the ASCII code point for a simple whitespace. BIOS routines know how to display a whitespace, or any ASCII character, in text mode. I remember somewhere back in time I could load AL with an ASCII character, call interrupt 0x0A service 0x0E, and have the character printed on the screen and the cursor moved one character to the right. This was (is?) fairly standard and time-proven. And it worked (works?) everywhere, at least in the PC world. --On Monday, November 03, 2008 7:06 AM -0500 erik quanstrom wrote: >> This courtesy of the ACPI spec: ""RSD PTR " (Notice that this >> signature must contain a trailing >> blank character.)" >> >> So where do we get the guys who design this stuff? Can we send them >> back? Or put them in an infinite loop in a time machine (oh wait see >> the subject). > > i think it's a tradition at this point to use 0x20 and not 0x00 to > fill a fixed-with signature. ata identify device uses 0x20 to fill > out fixed-width fields like the serial number. i'd be interested > where this tradition popped up. 0 would make more sense. > > - erik > >