Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
AT&T Hobbit
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{Use mdy dates|date=November 2023}} {{Short description|1990s microprocessor design}} {{more citations needed|date=October 2014}} The '''AT&T Hobbit''' is a [[microprocessor]] design developed by [[AT&T Corporation]] in the early 1990s. It was based on the company's CRISP (C-language Reduced Instruction Set Processor) design resembling the [[classic RISC pipeline]], and which in turn grew out of the C Machine design by [[Bell Labs]] of the late 1980s. All were optimized for running code compiled from the [[C programming language]]. The design concentrates on fast instruction decoding, indexed array access, and [[Subroutine|procedure call]]s. The project was ended in March 1994<ref>{{Cite book |last=Dominic Giampaolo |url=http://archive.org/details/practical-file-system-design |title=Practical File System Design |date=2008}}</ref> because the Hobbit failed to achieve commercially viable sales. ==History== The C Machine Project at Bell Labs had been underway since 1975 to develop computer architectures to run C programming language programs efficiently, aiming for a design that would offer an order of magnitude performance improvement over commercially available computers while remaining competitive in terms of cost. The design methodology for the C Machine architecture involved an iterative development approach informed by measurements of C program characteristics, involving the formulation and implementation of new computer architecture revisions, the development of a compiler to target each new revision, the compilation of "a large body of UNIX software", and the analysis of the compiled software. The results from such measurements then informed subsequent architecture revisions.<ref name="ditzel1987_hardware">{{ Cite book | chapter-url=https://dl.acm.org/doi/abs/10.1145/30350.30385 | isbn=0818607769 | doi=10.1145/30350.30385 | last1=Ditzel | first1=David R. | last2=McLellan | first2=Hubert R. | last3=Berenbaum | first3=Alan D. | title=Proceedings of the 14th annual international symposium on Computer architecture - ISCA '87 | chapter=The hardware architecture of the CRISP microprocessor | date=1987 | access-date=March 28, 2023 | pages=309–319 | s2cid=14954824 }}</ref> Following on from the stabilization of the C Machine architecture in 1981 for an uncompleted [[Emitter-coupled logic|ECL]] implementation, a design team was formed for CRISP in April 1983, and CRISP was first produced in a silicon implementation in 1986. The performance objectives were largely met by the fabricated processor, running at 16 MHz and delivering a Dhrystone benchmark score over 13 times greater than the VAX-11/750, achieving approximately 7.7 [[VAX Unit of Performance|VAX MIPS]]. This was competitive with the [[MIPS R2000]] as delivered in the MIPS M/500 Development System (an 8 MHz device delivering around 7.4 VAX MIPS<ref name="mips1988">{{ cite tech report | url=http://www.bitsavers.org/pdf/dec/prism/memos/880530_Cutler_PRISM_vs_MIPS.pdf | title=Performance Brief Part 1: CPU Benchmarks | publisher=MIPS Computer Systems Inc. | date=May 1988 | access-date=September 28, 2021 | pages=12 }}</ref>) although some benchmarks showed somewhat stronger performance by the CRISP processor. Compared to the R2000 which required numerous support chips when incorporated into a computer system, the CRISP was a "complete" processor incorporating on-chip caches and had "substantially" reduced board area requirements.<ref name="ditzel1987_hardware"/> It was subsequently reoriented toward low-power applications and commercialized, resulting in the Hobbit.<ref name="byte199302_hobbit">{{ cite magazine | url=https://archive.org/details/BYTE-1993-02/page/n188/mode/1up | title=Communications Gets Personal | magazine=Byte | last1=Ryan | first1=Bob | date=February 1993 | access-date=March 27, 2023 | pages=169–170, 172, 174, 176 }}</ref> It was introduced in 1992 in the form of the 92010 and aimed at the personal communicator market. Operating at 3.3V, its reported performance is up to 13.5 VAX MIPS. Initial pricing in multiples of 10,000 units was given as $35 per unit, with the full chipset below $100.<ref name="computerworld19921102_hobbit">{{ cite magazine | url=https://archive.org/details/sim_computerworld_1992-11-02_26_44/page/n50/mode/1up | title=AT&T announces line of personal communicators | magazine=Computerworld | date=November 2, 1992 | access-date=March 26, 2023 | last1=Booker | first1=Ellis | pages=41 }}</ref> Several support chips were produced:<ref name="eo_block_diagram">{{ cite web | url = http://www.utexas.edu/ftp/microlib/eo/html/ATT.Block.Diagram.html | title = EO Block Diagram | first = Michael | last = Cerda | access-date = May 15, 2009 | url-status = dead | archive-url = https://web.archive.org/web/20030330042024/http://www.utexas.edu/ftp/microlib/eo/html/ATT.Block.Diagram.html | archive-date = March 30, 2003 }}</ref> * AT&T 92011 System Management Unit * AT&T 92012 PCMCIA Controller * AT&T 92013 Peripheral Controller * AT&T 92014 Display Controller AT&T followed in 1993 with the 92020 family of processors, introducing new support chipsets targeting different applications. These devices can run at 3.3V or at 5V with an elevated clock frequency. The 92020S is pin-compatible with the 92010, has a larger 6 KB instruction cache (as opposed to the 3 KB cache of the 92010<ref name="byte199401_hobbit"/>), and performs the equivalent of 16 VAX MIPS with a typical power consumption of 210 mW.<ref name="electronicnews19931018_hobbit">{{ cite magazine | url=https://archive.org/details/sim_electronic-news_1993-10-18_39_1985/page/n3/mode/1up | title=AT&T Micro Unveils Fastest Hobbit MPU | magazine=Electronic News | date=October 18, 1993 | access-date=March 26, 2023 | pages=4 }}</ref> The 92020S was intended to be used in conjunction with most of the original 92010 chipset, excluding the 92013 peripheral controller. Meanwhile, the 92020M and 92020MX processors were intended for use with the new support chips, also employing a multiplexed address and data bus for reduced pin count, and offering lower levels of performance, with the 92020M also utilizing a 6 KB cache and achieving similar performance to the original 92010. The updated support chips are as follows:<ref name="byte199401_hobbit">{{ cite magazine | url=https://archive.org/details/eu_BYTE-1994-01_OCR/page/n134/mode/1up | title=The AT&T Hobbit Enters Its Second Generation | magazine=Byte | last1=Statt | first1=Paul | date=January 1994 | access-date=March 26, 2023 | pages=105 }}</ref> * AT&T 92021M System Management Unit * AT&T 92021MX System Management Unit * AT&T 92024M Display Controller The most highly integrated processor, the 92020MX, preserved the 3 KB cache of the 92010 but has a single-channel PCMCIA interface and a display controller supporting resolutions of up to {{nowrap|640 x 480}}. Costing $32 per unit in 10,000 unit quantities, it presented opportunities for cost reduction with certain devices when compared to the original Hobbit chipset.<ref name="electronicnews19931018_hobbit"/> [[Apple Computer]] approached AT&T and paid it to develop a newer version of the CRISP suitable for low-power use in the [[Apple Newton|Newton]] handheld computer. The Hobbit-based Newton was never produced. According to [[Larry Tesler]], "The Hobbit was rife with bugs, ill-suited for our purposes, and overpriced. We balked after AT&T demanded not one but several million more dollars in development fees."<ref name="lt">{{ cite web | first = Larry | last = Tesler | date = April 11, 1999 | url = http://www.nomodes.com/LinzmayerBook.html | title = 'The Fallen Apple' Corrections | url-status = dead | archive-url = https://web.archive.org/web/20160304012108/http://www.nomodes.com/LinzmayerBook.html | archive-date = March 4, 2016 | access-date = August 21, 2020 }}</ref> Apple rejected the Hobbit and adopted the ARM610 for the Newton,<ref name="byte199207_apple">{{ cite magazine | url=https://archive.org/details/byte-magazine-1992-07/page/n143/mode/1up | title=Apple ARMs Itself | magazine=Byte | last1=Redfern | first1=Andy | date=July 1992 | access-date=October 10, 2022 | pages=134 }}</ref> also partnering with [[Acorn Computers]] and [[VLSI Technology]] to form [[Advanced RISC Machines]] (ARM) in late 1990 with a $2.5 million investment. Apple sold its stake in ARM years later for a net $800 million.<ref name="lt" /> The Active Book Company (founded by [[Hermann Hauser]], who also founded Acorn Computers), which had been using an ARM in its Active Book [[personal digital assistant]] (PDA),<ref name="acornuser199008_abc">{{ cite news | url=https://archive.org/details/AcornUser097-Aug90/page/n8/mode/1up | title=Xmas Launch for Active Books | work=Acorn User | date=August 1990 | access-date=May 6, 2021 | pages=7 }}</ref> was later purchased by AT&T and was subsumed by AT&T's Eo subsidiary,<ref name="Kirkpatrick">{{ cite news | url = https://money.cnn.com/magazines/fortune/fortune_archive/1993/05/17/77857/index.htm | title = COULD AT&T RULE THE WORLD? | last = Kirkpatrick | first = David | date = May 17, 1993 | access-date = June 10, 2008 | work = CNN }}</ref> which produced an early PDA, the [[EO Personal Communicator]], running [[PenPoint OS]] from the [[GO Corporation]].<ref name="pcworld199212_eo">{{ cite magazine | url=https://archive.org/details/pcworld1012unse/page/62/mode/1up | title=Eo Communicator: Lord of the Roads | magazine=PC World | last1=Glitman | first1=Russell | date=December 1992 | access-date=March 30, 2023 | pages=58 }}</ref> AT&T made early announcements in 1992 of broad vendor adoption.<ref name="att19921116_hobbit">{{ cite press release | url=http://www.att.com/press/1192/921116.mea.html | title=Wide hardware and applications support for AT&T Hobbit chips | publisher=AT&T | date=November 16, 1992 | archive-url=https://web.archive.org/web/19961226013700/http://www.att.com/press/1192/921116.mea.html | access-date=March 30, 2023 | archive-date=December 26, 1996 }}</ref> Hobbit was used in the earliest prototypes of the [[BeBox]] until in 1993, AT&T announced discontinuation of Hobbit.<ref>{{Cite web|last=Gassée|first=Jean-Louis|date=January 31, 2019|title=50 Years In Tech Part 15. Be: From Concept To Near Death|url=https://mondaynote.com/50-years-in-tech-part-15-be-from-concept-to-near-death-f69c64d8725e|access-date=August 31, 2020|website=Medium|language=en}}</ref> AT&T closed its Eo operations which were responsible for the only commercially released product using the Hobbit,<ref name="input20200103_fax">{{Cite web|last=Smith|first=Ernie|date=January 3, 2020|title=Fax on the beach: The story of the audacious, totally calamitous iPad of the '90s|url=https://www.inputmag.com/features/fax-on-the-beach-the-story-of-atts-eo-communicator-90s-ipad-flop|access-date=November 1, 2020|website=Input|language=en}}</ref> and finally discontinued the Hobbit in 1994.<ref name="hacker1999">{{ cite book | url=https://archive.org/details/the-beos-bible/page/34/mode/1up | title=The BeOS Bible | publisher=Peachpit Press | last1=Hacker | first1=Scot | last2=Bortman | first2=Henry | last3=Herborth | first3=Chris | date=1999 | access-date=March 30, 2023 | isbn=0201353776 | pages=34 }}</ref> ==Design== In a traditional [[RISC]] design implementing a [[load–store architecture]], memory is accessed through instructions that explicitly load data into [[Processor register|registers]] and store data back to memory, with instructions that manipulate data working solely on the registers. By seeking to limit the data processing operations to a single clock cycle, a simpler control mechanism can be employed to dispatch instructions, making it easier to tune the [[instruction pipeline]]s,<ref name="patterson1985">{{ cite journal | url=https://archive.org/details/tutorialsoftware0000unse_s5q2/page/76/mode/2up | title=Reduced Instruction Set Computers | journal=Communications of the ACM | publisher=Association for Computing Machinery | last1=Patterson | first1=David A. | date=January 1985 | access-date=April 3, 2023 | volume=28 | issue=1 | pages=8–21 | doi=10.1145/2465.214917 | s2cid=1493886 | doi-access=free }}</ref> and add [[superscalar]] support. However, programming languages do not actually operate in this fashion. Generally they use a [[stack (data structure)|stack]] containing local variables and other information for subroutines known as a [[stack frame]] or activation record. The [[compiler]] writes code to create activation records using the underlying processor's load-store design. The C Machine in its CRISP implementation, and the Hobbit that followed directly, both aim to support the types of memory access that programming languages use, with the [[C (programming language)|C programming language]] being a particular consideration.<ref name="byte199401_hobbit"/> Instructions can access memory directly, referencing values in structures and arrays held within memory and updating memory with computation results. Although this memory-to-memory model is typical of the earlier [[Complex instruction set computer|CISC]] designs, the C Machine as implemented by CRISP differs from both CISC and RISC designs, including the earlier [[Bellmac 32]], by providing no directly accessible registers. Instead, a "stack cache" of 32-bit register entries is provided, 32 entries in CRISP but extended to 64 entries in Hobbit,<ref name="hobbit199212_ds">{{ cite book | url=https://archive.org/details/bitsavers_atthobbitArocessorDataSheetDec92_5104422/mode/2up | title=ATT92010 Hobbit Microprocessor | publisher=AT&T Microelectronics | date=December 1992 | access-date=April 7, 2023 }}</ref>{{rp|30}} mapped to the address space corresponding to the top of the program stack, these being purely accessible using a stack-relative addressing mode. The CRISP architecture was described as a "2½ address memory-to-memory machine", where instructions can employ zero, one, or two memory addresses and can employ a stack entry called the accumulator for computation results. Reminiscent of the Bellmac 32 architecture, various instructions designed to support procedure calling are provided by the CRISP architecture: ''call'' saves the return address and branches to a routine; ''enter'' allocates a stack frame for a routine, flushing stack cache entries if necessary; ''return'' deallocates the stack frame and branches to the caller's return address; ''catch'' restores stack entries from memory.<ref name="ditzel1987_hardware"/> One side effect of the Hobbit design is that it inspired designers of the [[Dis virtual machine]] (an offshoot of [[Plan 9 from Bell Labs]]) to use a memory-to-memory-based system that more closely matches the internal [[register machine|register-based]] workings of real-world processors. They found, as RISC designers would have expected, that without a load-store design it was difficult to improve the [[instruction pipeline]] and thereby operate at higher speeds. They decided that all future processors would thus move to a load-store design, and built [[Inferno (operating system)|Inferno]] to reflect this. In contrast, [[Java (programming language)|Java]] and [[Microsoft .NET|.NET]] virtual machines are stack-based, a side effect of being designed by language programmers as opposed to chip designers. Translating from a stack-based language to a register-based [[assembly language]] is a "heavyweight" operation; Java's [[virtual machine]] (VM) and compiler are many times larger and slower than the Dis VM and the [[Limbo programming language|Limbo]] (the most common language compiled for Dis) compiler.<ref>{{ cite web | url = http://herpolhode.com/rob/hotchips.html | archive-url = https://web.archive.org/web/20130422020155/http://herpolhode.com/rob/hotchips.html | archive-date = April 22, 2013 | title = The design of the Inferno virtual machine | date = April 22, 2013 }}</ref> The VMs for [[Android (operating system)|Android]] ([[Dalvik (software)|Dalvik]]), [[Parrot virtual machine|Parrot]], and [[Lua (programming language)#Internals|Lua]] are also register-based.{{citation needed|date=August 2020}} ==See also== * [[Jazelle]] ==References== {{Reflist}} ==External links== * [https://web.archive.org/web/20110806044928/http://www.bebox.nu/images.php?s=images%2Fhobbit The BeBox Zone - ''Prototype Hobbit BeBox'' Gallery] (archived version) * [http://findarticles.com/p/articles/mi_m3311/is_n3-4_v28/ai_13604566 Computer Industry Report 1992 article - ''Hobbit - AT&T Microelectronics' most visible new product - takes on Intel, ARM, Motorola, Microsoft - Intel Corp.; Motorola Inc.; Microsoft Corp''] * [http://lowendmac.com/2013/the-story-behind-apples-newton/ ''Sculley's Dream: The Story Behind the Newton'', by Tom Hormby, Low End Mac] {{RISC-based processor architectures}} {{Portal bar|1990s}} {{DEFAULTSORT:ATandT Hobbit}} [[Category:AT&T computers|Hobbit]] [[Category:Inferno (operating system)]] [[Category:Plan 9 from Bell Labs]] [[Category:32-bit microprocessors]]
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)
Pages transcluded onto the current version of this page
(
help
)
:
Template:Citation needed
(
edit
)
Template:Cite book
(
edit
)
Template:Cite journal
(
edit
)
Template:Cite magazine
(
edit
)
Template:Cite news
(
edit
)
Template:Cite press release
(
edit
)
Template:Cite tech report
(
edit
)
Template:Cite web
(
edit
)
Template:More citations needed
(
edit
)
Template:Nowrap
(
edit
)
Template:Portal bar
(
edit
)
Template:RISC-based processor architectures
(
edit
)
Template:Reflist
(
edit
)
Template:Rp
(
edit
)
Template:Short description
(
edit
)
Template:Use mdy dates
(
edit
)