|
|
| (22 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| '''Work is in progress to write a feature request for FEL'''
| | #REDIRECT [[Electronic Lab]] |
| | |
| | |
| = Feature Name =
| |
| | |
| Fedora Electronic Lab
| |
| | |
| == Summary ==
| |
| | |
| Fedora Electronic Lab is Fedora with extensive hardware design and simulations tools following the industry's current trend.
| |
| | |
| This page is a feature request to FESCo with respect to the work done on the Fedora Electronic Lab. Below entails the highlights of the major development items :
| |
| * Perl modules to extend vhdl and verilog support
| |
| | |
| == Definitions ==
| |
| | |
| Below are terms used in this page which has other meanings in a normal opensource software community. These definitions are to prevent any misunderstandings from any side.
| |
| | |
| * Software : a design or simulation tool that can be compiled into a RPM package
| |
| * Package : Mechanical body that envelops a chip
| |
| | |
| | |
| == Owner ==
| |
| | |
| * Name: [[User:chitlesh| Chitlesh Goorah]]
| |
| * email: < chitlesh [AT] fedoraproject DOT org>
| |
| | |
| == Current status ==
| |
| * Targeted release: [[Releases/{{FedoraVersion||next}} | {{FedoraVersion|long|next}} ]]
| |
| * Last updated: 19 January 2009
| |
| * Percentage of completion: 60%
| |
| | |
| == Detailed Description ==
| |
| | |
| Below entails the highlights of the major development item :
| |
| * Perl modules to extend vhdl and verilog support. These perl modules together with rawhide's gtkwave improves chip testing support.
| |
| * Introduction of Verilog-AMS modeling into ngspice
| |
| * Improved VHDL debugging support with gcov.
| |
| * Improved support for re-usable HDL packages as IP core
| |
| * Improved PLI support on both iverilog and ghdl
| |
| * Introduction of C-based methodologies for HDL testbenches and models.
| |
| | |
| == Benefit to Fedora ==
| |
| | |
| Fedora benefits from FEL in various ways as FEL extends Fedora's commitments for opensource content in the hardware design community.
| |
| | |
| The Fedora Project during the last 3 Fedora releases has established its roots deep into the opensource EDA community as a robust and successful opensource EDA provider.
| |
| | |
| FEL is not a --package-only-EDA-tools-- community, but a clear goal to strengthen the opensource EDA community, in terms of marketing, methodologies, design flows,..
| |
| | |
| FEL brings something unique that is missing in the opensource software community : direc
| |
| | |
| == Scope ==
| |
| | |
| FEL
| |
| | |
| == How To Test ==
| |
| <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.
| |
| | |
| Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
| |
| | |
| A good "how to test" should answer these four questions:
| |
| | |
| 0. What special hardware / data / etc. is needed (if any)?
| |
| 1. How do I prepare my system to test this feature? What packages
| |
| need to be installed, config files edited, etc.?
| |
| 2. What specific actions do I perform to check that the feature is
| |
| working like it's supposed to?
| |
| 3. What are the expected results of those actions?
| |
| | |
| -->
| |
| | |
| == User Experience ==
| |
| <!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. -->
| |
| | |
| == Dependencies ==
| |
| <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? -->
| |
| | |
| == Contingency Plan ==
| |
| | |
| There is no need for backup plan as the work done behind FEL-11 is only to improve hardware design experience and expand FEL targeted userbase to Test & Verification Engineers.
| |
| | |
| == Documentation ==
| |
| <!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. -->
| |
| | |
| | |
| == Release Notes ==
| |
| | |
| <!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
| |
| <!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
| |
| | |
| == Comments and Discussion ==
| |
| | |
| * See [[Talk:Features/YourFeatureName]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
| |
| | |
| | |
| ----
| |
| | |
| [[Category:FeaturePageIncomplete]]
| |
| <!-- When your feature page is completed and ready for review -->
| |
| <!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
| |
| <!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
| |
| <!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
| |
