ماهى مدى الاستفاده التى تعود علينا من هذه المشاريع
ومن يستطيع ان يقيمها فى مجال hardware
http://opensparc.sunsource.net
1.Q: What is the OpenSPARC Project?
A: OpenSPARC project is making the hardware source code of the recently announced UltraSPARC T1 processor available under an Open Source license.
This technology offers a wide range of innovative opportunities not yet explored. By lowering the costs of entry to leverage a current hardware design, more developers can engage in the process, and more specialized implementations can be pursued.
2.Q: What parts to the chip design are you "Open Sourcing?"
A: Today we are announcing our intent to open source the design point for the UltraSPARC T1 chip in 2006. We are targeting the March timeframe. The initial publications should include: the source of the design in Verilog, a verification suite and simulation models, ISA specification (UltraSPARC Architecture 2005), and a Solaris port. We expect to announce additional details during the first quarter of calendar 2006.
3.Q: Why are you opening the source code for the UltraSPARC T1?
A: Sun's 64-bit UltraSPARC processors have been an industry standard for more than a decade. Our goal is to expand the SPARC community and lay the groundwork for a new generation of 64-bit hardware and multi-threaded software products. Sun has a long history of being associated with open standards and specifications and opening up the UltraSPARC-T1 design point is part of our overall open source strategy.
4.Q: Why would Sun "open" its current hardware chip design?
A: We also believe the open source model can help solve some serious issues created by more traditional licensing terms in a rapidly-changing semiconductor industry. In particular, we think it can be a key enabler for the increasingly important "System On a Chip" (SOC) design business.
5.Q: How does the OpenSPARC project model differ from other models for processor cores?
A: We are not aware of any other major company that posts 64-bit, multi-threaded processor core IP on a Web site where anyone can download it under an OSI-Approved open source license.
6.Q: What are the benefits to Sun?
A: We expect this open source strategy will help create new markets for the 64-bit, multithreading features offered by UltraSPARC T1 and its derivatives. As in software, innovation happens everywhere, and the hardware community can make huge strides with current, accessible, low-cost technology at their fingertips.
With added "eyes" addressing the challenges and opportunities around multithreading and 64-bit processes, Sun's products - along with new products by other companies - can evolve more quickly and attract more customers.
7.Q: What are the benefits to developers?
A: Opening the UltraSPARC T1 source code lets developers create innovative software applications faster, and with a higher degree of hardware integration than ever before. Software developers will now be able to create highly optimized applications that are tightly integrated with the hardware, creating unique, high-value solutions for specific markets.
8.Q: What are the benefits to the user?
A: We realize from existing projects using the Open Source development model that while we can make some predictions, the most exciting results occur unexpectedly. The creation of a vibrant community built around a 64-bit, thread-rich implementation will bring more choices and applications to the market faster.
9.Q: How does this introduction help solve some of the deterrents to designing a "System on a Chip (SOC)?
A: The SOC design movement involves integrating functional units onto a single chip that, even just a few years ago, would have been spread across several chips or even a whole system. SOC designs are increasingly important because they can lower product costs while improving both performance and reliability. They also can speed up product design cycles.
The SOC design movement currently faces two intractable problems. First, it's very difficult to get access to the wide range of IP potentially of interest in the various different single chip designs now feasible. Secondly, it's very hard to acquire the separate pieces selected for integration on a given chip in a compatible form that lets them all interconnect and interoperate as required. If similar license models were adopted widely across the semiconductor industry, it would solve both these problems. Designers not only would have free and immediate access to all the IP of possible interest to them, but all IP would be available in a "soft" format that facilities both easy customization and ready integration.
10.Q: Who do you expect to be key contributors to this project?
A: We have received a tremendous amount of interest from universities, small design companies, embedded device manufacturers, and network specialists in understanding the 64-bit processor environment and multithreading capabilities. We expect now that the RTL is made available, the interest level among these groups and others will grow significantly.
11.Q: What role does SPARC International play in this?
A: SPARC International was created in 1989 as an independent, non-profit organization. The Corporation's purpose is to promote the design, development, and application of SPARC (Scalable Processor ARChitecture) to computer and related products, and to control, maintain, and enforce SPARC trademarks. Sun has open-sourced an implementation of the SPARC architecture; the open-source implementation is independent of the oversight provided by SPARC International. SPARC International continues to provide SPARC compliance test suites to developers who wish to certify and brand their own implementation based on SPARC architectures. To become a SPARC International member, obtain information for compliance test suites, or to get answers to trademark questions contact: karen@sparc.org
12.Q: What license are you going to use for the code?
A: We expect to choose an Open Source Initiative- (OSI) approved model. Our intent is to choose the option that will provide the community with the greatest freedom to innovate.
13.Q: Is there any cost to using the code?
A: No. There are no fees associated with downloading the code from this site.
14.Q: What is "Open Source" Hardware?
A: The term "Open Source" today most often refers to "Free/Libre or Open Source Software, (FL/OSS)." While it is not a perfect term in the hardware space, we consider "Open Source" as a reference to the development process, where we are providing free and open tools that are essential components to developing a new chip.
Our goal to encourage an open, collaborative process around developing new chips. Until now, chip design and development has almost exclusively been a closely guarded, proprietary event.
15.Q: Who do I contact at Sun if I have additional questions?
A: If you have a general question whose answer would benefit the community, post it to the General forum. If your question is more specific to your own development needs, send an email to opensparc-interest@sun.com.
Back to top
--------------------------------------------------------------------------------
16.Q: What is the Contributors Agreement for?
A: The Contributor Agreement (CA) gives Sun and the contributor joint copyright interests in the code: the contributor retains copyrights while also granting those rights to Sun as the open source project sponsor. This enables Sun to represent the aggregated code base (and the community) as a whole in order to enforce licensing restrictions, and/or other legal concerns.
17.Q: If I sign this once, does it apply to source code on all projects on the site?
A: Yes. This agreement covers not only all projects on this site, but also applies to any project sponsored by Sun that requires this agreement. Please retain a copy for your records, and to send to another project if you are asked.
18.Q: Where do I send the Contributor Agreement to?
A: US copyright law requires that we retain a signed copy of the agreement. To execute the Contributor Agreement, please fax the signed, completed Sun Contributor Agreement to OpenSPARC Administrator: (408) 774-8589 or email a scanned, signed copy to opensparc_CA@sun.com. You will receive a reference number confirming that the document has been received. Please provide this reference number when making contributions to the OpenSPARC project.
Back to top
--------------------------------------------------------------------------------
19. Q: Why was the GPLv2 chosen as the license for the T1 processor Register Transfer Language (RTL)?
A: Sun wanted to release T1 processor RTL under the GPLv2 so that the community would have access to processor technology under an open source license. The GPLv2 gives user the freedom to run, copy, distribute, study, change and improve the technology. More precisely, it refers to four kinds of freedom, for the users of the technology:
The freedom to use the technology for any purpose.
The freedom to study how the technology works, and adapt it to your needs.
The freedom to redistribute copies so you can help others in the community.
The freedom to improve the technology, and release your improvements to the public, so that the whole community benefits.
The GPLv2 license is viewable here. Unofficial translations can also be found there at Translations. The GPLv2 meets the requirements of the Open Source Definition and has been approved as an open source license by the Open Source Initiative.
20. Q: Will all of the T1 processor RTL technology be released under the GPLv2?
A: We plan to release the T1 processor RTL under the GPLv2. In order to promote compatibility with a variety of communities (Linux, FreeBSD and OpenSolaris), some technology and tools will be made available under a BSD license. Other technology (particularly code contributed by third parties and certain tools) will only be available as binaries will only be available under a binary Software License Agreement. Finally, some components may be based on existing open source projects and these will be made available on the OpenSPARC website under their current licenses.
21. Q: Can I license my modified OpenSPARC technology under the GPLv2, as well as under another license?
A: You should carefully review the terms of the GPLv2 with respect to your licensing obligations, but generally if you choose to distribute your modifications to others it must be released under the same terms as the original technology. So, the modifications you choose to distribute must be licensed under the GPLv2.
22. Q: If I distribute OpenSPARC technology licensed under the GPLv2 in my proprietary product, will I have to share my RTL?
A: Yes, for any technology licensed under the GPLv2 and any modifications you make you must share. Review the terms of the GPLv2 to determine if you have additional obligations. will I be asked to do as far as licensing is concerned?
23. Q: If I contribute technology which was licensed under the GPLv2 to the OpenSPARC project, what will I be asked to do as far as licensing is concerned?
A: Technology licensed under the GPLv2 which you contribute to the OpenSPARC project must be made available under the GPLv2. We're working out the details of the code submission process. In addition, you must have submitted a contributor agreement. The contributor agreement policy can be found at: http://opensparc.sunsource.net/nonav/ca_policy.html
24. Q: May I take portions of the OpenSPARC technology licensed under the GPLv2 and use it in another project?
A: You can only do so if you comply with the terms of the GPLv2.
25. Q: Can I redistribute or sell the OpenSPARC technology licensed under the GPLv2 with my modifications?
A: Yes, you can modify and redistribute technology, including charging a fee for the distribution. However, you will need to meet the terms of the GPLv2, including making the RTL of your modified technology available under the GPLv2.
26. Q: Can Sun ever take away the OpenSPARC technology licensed under the GPLv2?
A: No, once technology is licensed under the GPLv2, the technology remains licensed under the terms of the GPLv2.
27. Q: I want to get credit for my work and for people to know what I wrote - can I still get credit if I use the GPLv2?
A: You can certainly get credit for your work. Part of releasing a program under the GPL is writing a copyright notice in your own name (assuming you are the copyright holder). The GPL require's all copies to carry an appropriate copyright notice, however you should not remove any copyright notices already embedded in the technology.
28. Q: Why was the BSD license chosen for some of the OpenSPARC technology?
A: Sun chose the BSD for certain technologies in order to make them more broadly available to multiple open source communities such as FreeBSD and OpenSolaris.
29. Q: Does Sun intend to use GPLv3 as the license for the RTL when GPlv3 is released?
A: It is anticipated that the GPLv3 will be available in about a year, but the terms are still under discussion, so we are using GPLv2 for the RTL. We will evaluate GPLv3, and consider its appropriateness for OpenSPARC, when GPLv3 is finalized.
Disclaimer:
These FAQs are not legal advice. You should consult a lawyer experienced in copyright, licensing and intellectual property issues for legal advice with respect to the GPLv2 or any other license used on the OpenSPARC website.
Back to top
--------------------------------------------------------------------------------
30. Q: What are the differences between OpenSPARC T1 and UltraSPARC T1? A: OpenSPARC T1 source code is modified from the original source code of UltraSPARC T1. Every attempt is made to keep the OpenSPARC T1 source as close to the original UltraSPARC T1 in the process of preparing it for release in a standalone environment and preparing it to comply with the legal requirements.
31. Q: What is included in the OpenSPARC T1 download?
A: OpenSPARC T1 Download for the Chip Design and Verification includes:
Chip Design source code in Verilog language.
Verification test benches source code in Verilog, Vera®, PLI code in C and C++.
Verification tests source code in SPARC assembly language.
Scripts needed to assemble and run tests on the design using verification test benches.
Synthesis scripts for Synopsys Design Compiler®.
SPARC Architecture Simulator (SAS).
Documentation.
OpenSPARC T1 Download for Architecture and Performance modeling includes:
SAM - SPARC Architecture Model
Legion - Fast instruction accurate simulator for software developers
SPARC Architecture Simulator (SAS).
Solaris image for simulation.
Documentation.
32. Q: What are the system requirements to use OpenSPARC T1 source code?
A: Once you download the source code, you can run Verilog simulation, RTL synthesis, Architecture and Performance modeling tools on any SPARC system with Solaris 9 or Solaris 10 operating system.
33. Q: What are the commercial EDA tools needed to use the OpenSPARC T1 source code?
A: Once you download the source code, to run simulations of the OpenSPARC T1 you will need the following:
A Verilog Simulator - VCS® from Synopsys or NC-Verilog® from Cadence.
Optionally, Vera® compiler and run time libraries from Synopsys.
Optionally, Debussy® debug system from Novas for simulation debugging.
To run Synthesis of OpenSPARC T1, you will need:
Design Compiler® from Synopsys.
Your silicon fab vendor's synthesis libraries.
34. Q: Can I use Verilog simulator other than VCS or NC-Verilog ?
A: Yes, you can use any Verilog Simulator, but please make sure to follow instructions to compile and link PLI C/C++ code, and specify correct parameters to the Simulation script.
Design Compiler®, VCS®, Vera® are registered trademarks of Synopsys, Inc.
NC-Verilog® is registered trademark of Cadence, Inc.
Debussy® is registered trademark of Novas, Inc.
Back to top
