hardware performance
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 1773
Hardware Monitor applet 1.4
The Hardware Monitor applet is a small program for the Gnome panel. more>>
Hardware Monitor applet is a small program for the Gnome panel which tries to be a beautiful all-round solution to hardware monitoring.
It also tries to be user-friendly and generally nice and sensible, integrating pleasantly with the rest of your Gnome desktop.
Main features:
- A graphical view where each monitor is represented by a (time, measurement) colored curve
- A bar-plot view with a horizontal bar per monitor
- A column view with a column (time, measurement) diagram for each monitor
- A textual view which simply lists the monitors and the currently measured values
- A flame view which produces spiffy flames, the sizes of which are determined by the values of the monitored device
And the applet supports monitoring the following hardware characteristics:
- CPU usage (all CPUs, or one at the time) - niced background processes such as SETI@home are automatically ignored
- Memory usage - cache and buffers are automatically ignored
- Swap usage
- Load average
- Disk usage (or disk space free)
- Network throughput (Ethernet, wireless, modem, serial link), either incoming or outgoing or both
- Temperatures from internal sensors (e.g. system board and CPU temperatures)
- Fan speeds from internal sensors
- To avoid eating CPU time when it is scarce, the applet lowers its priority.
<<lessIt also tries to be user-friendly and generally nice and sensible, integrating pleasantly with the rest of your Gnome desktop.
Main features:
- A graphical view where each monitor is represented by a (time, measurement) colored curve
- A bar-plot view with a horizontal bar per monitor
- A column view with a column (time, measurement) diagram for each monitor
- A textual view which simply lists the monitors and the currently measured values
- A flame view which produces spiffy flames, the sizes of which are determined by the values of the monitored device
And the applet supports monitoring the following hardware characteristics:
- CPU usage (all CPUs, or one at the time) - niced background processes such as SETI@home are automatically ignored
- Memory usage - cache and buffers are automatically ignored
- Swap usage
- Load average
- Disk usage (or disk space free)
- Network throughput (Ethernet, wireless, modem, serial link), either incoming or outgoing or both
- Temperatures from internal sensors (e.g. system board and CPU temperatures)
- Fan speeds from internal sensors
- To avoid eating CPU time when it is scarce, the applet lowers its priority.
Download (0.30MB)
Added: 2007-01-17 License: GPL (GNU General Public License) Price:
601 downloads
Hardware Monitor 1.4
Hardware Monitor is a multi-purpose, beautiful system-monitoring applet. more>>
Hardware Monitor is a multi-purpose, beautiful system-monitoring applet.
The Hardware Monitor applet is an applet for the GNOME panel which tries to be a beautiful all-around solution to system monitoring. It also strives to be user-friendly and generally nice and sensible, integrating pleasantly with the rest of your GNOME desktop.
Includes different viewers, including a flame effect, allows multiple devices to be monitored in the samme applet, uses smooth updating, polished graphs, clean HIG-compliant interface.
Main features:
- A graphical view where each monitor is represented by a (time, measurement) colored curve
- A bar-plot view with a horizontal bar per monitor
- A column view with a column (time, measurement) diagram for each monitor
- A textual view which simply lists the monitors and the currently measured values
- A flame view which produces spiffy flames, the sizes of which are determined by the values of the monitored device
And the applet supports monitoring the following hardware characteristics:
- CPU usage (all CPUs, or one at the time) - niced background processes such as SETI@home are automatically ignored
- Memory usage - cache and buffers are automatically ignored
- Swap usage
- Load average
- Disk usage (or disk space free)
- Network throughput (Ethernet, wireless, modem, serial link), either incoming or outgoing or both
- Temperatures from internal sensors (e.g. system board and CPU temperatures)
- Fan speeds from internal sensors
<<lessThe Hardware Monitor applet is an applet for the GNOME panel which tries to be a beautiful all-around solution to system monitoring. It also strives to be user-friendly and generally nice and sensible, integrating pleasantly with the rest of your GNOME desktop.
Includes different viewers, including a flame effect, allows multiple devices to be monitored in the samme applet, uses smooth updating, polished graphs, clean HIG-compliant interface.
Main features:
- A graphical view where each monitor is represented by a (time, measurement) colored curve
- A bar-plot view with a horizontal bar per monitor
- A column view with a column (time, measurement) diagram for each monitor
- A textual view which simply lists the monitors and the currently measured values
- A flame view which produces spiffy flames, the sizes of which are determined by the values of the monitored device
And the applet supports monitoring the following hardware characteristics:
- CPU usage (all CPUs, or one at the time) - niced background processes such as SETI@home are automatically ignored
- Memory usage - cache and buffers are automatically ignored
- Swap usage
- Load average
- Disk usage (or disk space free)
- Network throughput (Ethernet, wireless, modem, serial link), either incoming or outgoing or both
- Temperatures from internal sensors (e.g. system board and CPU temperatures)
- Fan speeds from internal sensors
Download (0.29MB)
Added: 2007-01-13 License: GPL (GNU General Public License) Price:
1037 downloads
High Performance Linpack 1.0a
High Performance Linpack is a highly parallel, high performance benchmarking tool. more>>
HPL is a software package that solves a (random) dense linear system in double precision (64 bits) arithmetic on distributed-memory computers. It can thus be regarded as a portable as well as freely available implementation of the High Performance Computing Linpack Benchmark.
The algorithm used by HPL can be summarized by the following keywords: Two-dimensional block-cyclic data distribution - Right-looking variant of the LU factorization with row partial pivoting featuring multiple look-ahead depths - Recursive panel factorization with pivot search and column broadcast combined - Various virtual panel broadcast topologies - bandwidth reducing swap-broadcast algorithm - backward substitution with look-ahead of depth 1.
The HPL package provides a testing and timing program to quantify the accuracy of the obtained solution as well as the time it took to compute it. The best performance achievable by this software on your system depends on a large variety of factors.
Nonetheless, with some restrictive assumptions on the interconnection network, the algorithm described here and its attached implementation are scalable in the sense that their parallel efficiency is maintained constant with respect to the per processor memory usage.
The HPL software package requires the availibility on your system of an implementation of the Message Passing Interface MPI (1.1 compliant). An implementation of either the Basic Linear Algebra Subprograms BLAS or the Vector Signal Image Processing Library VSIPL is also needed. Machine-specific as well as generic implementations of MPI, the BLAS and VSIPL are available for a large variety of systems.
<<lessThe algorithm used by HPL can be summarized by the following keywords: Two-dimensional block-cyclic data distribution - Right-looking variant of the LU factorization with row partial pivoting featuring multiple look-ahead depths - Recursive panel factorization with pivot search and column broadcast combined - Various virtual panel broadcast topologies - bandwidth reducing swap-broadcast algorithm - backward substitution with look-ahead of depth 1.
The HPL package provides a testing and timing program to quantify the accuracy of the obtained solution as well as the time it took to compute it. The best performance achievable by this software on your system depends on a large variety of factors.
Nonetheless, with some restrictive assumptions on the interconnection network, the algorithm described here and its attached implementation are scalable in the sense that their parallel efficiency is maintained constant with respect to the per processor memory usage.
The HPL software package requires the availibility on your system of an implementation of the Message Passing Interface MPI (1.1 compliant). An implementation of either the Basic Linear Algebra Subprograms BLAS or the Vector Signal Image Processing Library VSIPL is also needed. Machine-specific as well as generic implementations of MPI, the BLAS and VSIPL are available for a large variety of systems.
Download (0.50MB)
Added: 2005-04-11 License: BSD License Price:
1682 downloads
X Hardware Monitor 1.0
X Hardware Monitor is monitor hardware indicators for temperature, voltage etc... of a running system with a graphical panel. more>>
X Hardware Monitor is a hardware monitor that shows indicators for temperature, voltage, fan speed etc, of a running system with a graphical panel.
The default configuration allows to monitor up to 3 temperatures, 3 fan speeds and 6 voltages. This tool is more particularly adequate for bi-processor systems.
<<lessThe default configuration allows to monitor up to 3 temperatures, 3 fan speeds and 6 voltages. This tool is more particularly adequate for bi-processor systems.
Download (0.015MB)
Added: 2005-09-22 License: Freeware Price:
1496 downloads
Hardware::iButton::Device 0.03
Hardware::iButton::Device is a Perl object to represent iButtons. more>>
Hardware::iButton::Device is a Perl object to represent iButtons.
SYNOPSIS
use Hardware::iButton::Connection;
$c = new Hardware::iButton::Connection "/dev/ttyS0";
@b = $c->scan();
foreach $b (@b) {
print "id: ", $b->id(), ", reg0: ",$b->readreg(0),"n";
}
This module talks to iButtons via the "active" serial interface (anything using the DS2480, including the DS1411k and the DS 9097U). It builds up a list of devices available, lets you read and write their registers, etc.
The connection object is an Hardware::iButton::Connection. The main user-visible purpose of it is to provide a list of Hardware::iButton::Device objects. These can be subclassed once their family codes are known to provide specialized methods unique to the capabilities of that device. Those devices will then be Hardware::iButton::Device::DS1920, etc.
<<lessSYNOPSIS
use Hardware::iButton::Connection;
$c = new Hardware::iButton::Connection "/dev/ttyS0";
@b = $c->scan();
foreach $b (@b) {
print "id: ", $b->id(), ", reg0: ",$b->readreg(0),"n";
}
This module talks to iButtons via the "active" serial interface (anything using the DS2480, including the DS1411k and the DS 9097U). It builds up a list of devices available, lets you read and write their registers, etc.
The connection object is an Hardware::iButton::Connection. The main user-visible purpose of it is to provide a list of Hardware::iButton::Device objects. These can be subclassed once their family codes are known to provide specialized methods unique to the capabilities of that device. Those devices will then be Hardware::iButton::Device::DS1920, etc.
Download (0.021MB)
Added: 2007-06-18 License: Perl Artistic License Price:
861 downloads
Performance Co-Pilot 2.5.0
Performance Co-Pilot is a performance monitoring toolkit and API. more>>
Performance Co-Pilot (PCP) is a framework and services to support system-level performance monitoring and performance management.
The services offered by PCP are especially attractive for those tackling harder system-level performance problems. For example this may involve a transient performance degradation, or correlating end-user quality of service with platform activity, or diagnosing some complex interaction between resource demands on a single system, or management of performance on large systems with lots of "moving parts".
The distributed PCP architecture makes it especially useful for those seeking centralized monitoring of distributed processing (e.g. in a cluster or webserver farm environment), especially where a large number hosts are involved.
Main features:
- A single API for accessing the performance data that hides details of where the data comes from and how it was captured and imported into the PCP framework.
- A client-server architecture allows multiple clients to monitor the same host, and a single client to monitor multiple hosts (e.g. in a Beowulf cluster). This enables centralized monitoring of distributed processing.
- Integrated archive logging and replay so a client application can use the same API to process real-time data from a host or historical data from an archive.
- The framework supports APIs and configuration file formats that enable the scope of performance monitoring to be extended at all levels.
- An "plugin" framework (libraries, APIs, agents and daemon) to collect performance data from multiple sources on a single host, e.g. from the hardware, the kernel, the service layers, the application libraries, and the applications themselves.
- Libraries and sample implementations encourage the development of new "plugins" (or agents) to capture and export the performance data that matters in your application environment, along side the other generic performance data.
- An endian-safe transport layer for moving performance metrics between the collector and the monitoring applications over TCP/IP. This means an IRIX desktop with PCP can monitor one or more Linux systems with the Open Source release of PCP installed.
- A Linux agent that exports a broad range of performance data from most kernels circa 2.0.36 (RedHat 5.2) or later. This includes coverage of activity in the areas of: CPU, disk, memory, swapping, network, NFS, RPC, filesystems and all the per-process statistics.
- Other agents export performance data from:
- Web server activity logs
- arbitrary application-level tracing (via a PCP trace library)
- Cisco routers
- sendmail
- the mail queue
- the PCP infrastructure itself
- Assorted simple monitoring tools that use the PCP APIs to retrieve and display either arbitrary performance metrics, or specific groups of metrics (as in pmstat a cluster-aware vmstat lookalike).
- The PCP inference engine supports automated monitoring through a rule-based language and interpreter that performs user-defined actions when rule predicates are found to be true.
<<lessThe services offered by PCP are especially attractive for those tackling harder system-level performance problems. For example this may involve a transient performance degradation, or correlating end-user quality of service with platform activity, or diagnosing some complex interaction between resource demands on a single system, or management of performance on large systems with lots of "moving parts".
The distributed PCP architecture makes it especially useful for those seeking centralized monitoring of distributed processing (e.g. in a cluster or webserver farm environment), especially where a large number hosts are involved.
Main features:
- A single API for accessing the performance data that hides details of where the data comes from and how it was captured and imported into the PCP framework.
- A client-server architecture allows multiple clients to monitor the same host, and a single client to monitor multiple hosts (e.g. in a Beowulf cluster). This enables centralized monitoring of distributed processing.
- Integrated archive logging and replay so a client application can use the same API to process real-time data from a host or historical data from an archive.
- The framework supports APIs and configuration file formats that enable the scope of performance monitoring to be extended at all levels.
- An "plugin" framework (libraries, APIs, agents and daemon) to collect performance data from multiple sources on a single host, e.g. from the hardware, the kernel, the service layers, the application libraries, and the applications themselves.
- Libraries and sample implementations encourage the development of new "plugins" (or agents) to capture and export the performance data that matters in your application environment, along side the other generic performance data.
- An endian-safe transport layer for moving performance metrics between the collector and the monitoring applications over TCP/IP. This means an IRIX desktop with PCP can monitor one or more Linux systems with the Open Source release of PCP installed.
- A Linux agent that exports a broad range of performance data from most kernels circa 2.0.36 (RedHat 5.2) or later. This includes coverage of activity in the areas of: CPU, disk, memory, swapping, network, NFS, RPC, filesystems and all the per-process statistics.
- Other agents export performance data from:
- Web server activity logs
- arbitrary application-level tracing (via a PCP trace library)
- Cisco routers
- sendmail
- the mail queue
- the PCP infrastructure itself
- Assorted simple monitoring tools that use the PCP APIs to retrieve and display either arbitrary performance metrics, or specific groups of metrics (as in pmstat a cluster-aware vmstat lookalike).
- The PCP inference engine supports automated monitoring through a rule-based language and interpreter that performs user-defined actions when rule predicates are found to be true.
Download (1.3MB)
Added: 2006-10-25 License: LGPL (GNU Lesser General Public License) Price:
1094 downloads
Hardware lister B.02.11.01
Hardware Lister is a small tool to provide detailed information on the hardware configuration of the machine. more>>
lshw (Hardware Lister) is a small tool to provide detailed information on the hardware configuration of the machine.
Hardware lister can report exact memory configuration, firmware version, CPU version and speed, cache configuration, bus speed, mainboard configuration, etc. On DMI-capable x86 or EFI (IA-64) systems and on some PowerPC machines (PowerMac G4 is known to work).
Information can be output in plain text, XML or HTML.
It currently supports DMI (x86 and EFI only), OpenFirmware device tree (PowerPC only), PCI/AGP, ISA PnP (x86), CPUID (x86), IDE/ATA/ATAPI, PCMCIA (only tested on x86), USB and SCSI.
<<lessHardware lister can report exact memory configuration, firmware version, CPU version and speed, cache configuration, bus speed, mainboard configuration, etc. On DMI-capable x86 or EFI (IA-64) systems and on some PowerPC machines (PowerMac G4 is known to work).
Information can be output in plain text, XML or HTML.
It currently supports DMI (x86 and EFI only), OpenFirmware device tree (PowerPC only), PCI/AGP, ISA PnP (x86), CPUID (x86), IDE/ATA/ATAPI, PCMCIA (only tested on x86), USB and SCSI.
Download (1.1MB)
Added: 2007-08-06 License: GPL (GNU General Public License) Price:
819 downloads
Hardware 4 Linux 0.9.3
Hardware 4 Linux project contains a set of tools to report Linux-compatible hardware to hardware4linux.info. more>>
Hardware 4 Linux project contains a set of tools to report Linux-compatible hardware to hardware4linux.info.
Enhancements:
- This release anonymizes dmidecode output, collects OS version files instead of calling osinfo, collects audio codec files, adds a README, and collects PCI modules.
<<lessEnhancements:
- This release anonymizes dmidecode output, collects OS version files instead of calling osinfo, collects audio codec files, adds a README, and collects PCI modules.
Download (MB)
Added: 2007-08-11 License: GPL (GNU General Public License) Price:
494 downloads
Hardware::iButton 0.03
Hardware::iButton is a Perl module that allows to talk to DalSemi iButtons via a DS2480 serial widget. more>>
Hardware::iButton is a Perl module that allows to talk to DalSemi iButtons via a DS2480 serial widget.
SYNOPSIS
use Hardware::iButton::Connection;
$c = new Hardware::iButton::Connection "/dev/ttyS0";
@b = $c->scan();
foreach $b (@b) {
print "family: ",$b->family(), "serial number: ", $b->serial(),"n";
print "id: ",$b->id(),"n"; # id = family . serial . crc
print "reg0: ",$b->readreg(0),"n";
}
This module talks to iButtons via the "active" serial interface (anything using the DS2480, including the DS1411k and the DS 9097U). It builds up a list of devices available, lets you read and write their registers, etc.
The connection object is an Hardware::iButton::Connection. The main user-visible purpose of it is to provide a list of Hardware::iButton::Device objects. These can be subclassed once their family codes are known to provide specialized methods unique to the capabilities of that device. Those devices will then be Hardware::iButton::Device::DS1920, etc.
iButtons and solder-mount Touch Memory devices are each identified with a unique 64-bit number. This is broken up into 8 bits of a "family code", which specifies the part number (and consequently the capabilities), then 48 bits of device ID (which Dallas insures is globally unique), then 8 bits of CRC. When you pass these IDs to and from this package, use hex strings like "0123456789ab".
<<lessSYNOPSIS
use Hardware::iButton::Connection;
$c = new Hardware::iButton::Connection "/dev/ttyS0";
@b = $c->scan();
foreach $b (@b) {
print "family: ",$b->family(), "serial number: ", $b->serial(),"n";
print "id: ",$b->id(),"n"; # id = family . serial . crc
print "reg0: ",$b->readreg(0),"n";
}
This module talks to iButtons via the "active" serial interface (anything using the DS2480, including the DS1411k and the DS 9097U). It builds up a list of devices available, lets you read and write their registers, etc.
The connection object is an Hardware::iButton::Connection. The main user-visible purpose of it is to provide a list of Hardware::iButton::Device objects. These can be subclassed once their family codes are known to provide specialized methods unique to the capabilities of that device. Those devices will then be Hardware::iButton::Device::DS1920, etc.
iButtons and solder-mount Touch Memory devices are each identified with a unique 64-bit number. This is broken up into 8 bits of a "family code", which specifies the part number (and consequently the capabilities), then 48 bits of device ID (which Dallas insures is globally unique), then 8 bits of CRC. When you pass these IDs to and from this package, use hex strings like "0123456789ab".
Download (0.021MB)
Added: 2007-08-15 License: Perl Artistic License Price:
808 downloads
Distributed Hardware Evolution Project
Distributed Hardware Evolution Project is populations of circuits evolving in a distributed online genetic algorithm. more>>
The Distributed Hardware Evolution Project allows the distribution of a genetic algorithm evolving hardware designs across the Internet by setting up an island on each clients PC which will evolve during idle time. Individuals from these islands will migrate between each other as they compete for survival.
All source code is available at Sourceforge under the projects named JaGa, DistrIT, and IslandEv. The source code is generalizable to any genetic algorithm or distributed processing task.
<<lessAll source code is available at Sourceforge under the projects named JaGa, DistrIT, and IslandEv. The source code is generalizable to any genetic algorithm or distributed processing task.
Download (0.006MB)
Added: 2005-04-01 License: GPL (GNU General Public License) Price:
1670 downloads
Hardware::Vhdl::Lexer 1.00
Hardware::Vhdl::Lexer is a Perl module that can split VHDL code into lexical tokens. more>>
Hardware::Vhdl::Lexer is a Perl module that can split VHDL code into lexical tokens.
SYNOPSIS
use Hardware::Vhdl::Lexer;
# Open the file to get the VHDL code from
my $fh;
open $fh, new({ linesource => $fh });
# Dump all the tokens
my ($token, $type);
while( (($token, $type) = $lexer->get_next_token) && defined $token) {
print "# type = $type token=$tokenn";
}
Hardware::Vhdl::Lexer splits VHDL code into lexical tokens. To use it, you need to first create a lexer object, passing in something which will supply chunks of VHDL code to the lexer. Repeated calls to the get_next_token method of the lexer will then return VHDL tokens (in scalar context) or a token type code and the token (in list context). get_next_token returns undef when there are no more tokens to be read.
NB: in this documentation I refer to "lines" of VHDL code and "line" sources etc., but in fact the chunks of code dont have to be broken up at line-ends - they can be broken anywhere that isnt in the middle of a token. New-line characters just happen to be a simple and safe way to split up a file. You dont even have to split up the VHDL at all, you can pass in the whole thing as the first and only "line".
<<lessSYNOPSIS
use Hardware::Vhdl::Lexer;
# Open the file to get the VHDL code from
my $fh;
open $fh, new({ linesource => $fh });
# Dump all the tokens
my ($token, $type);
while( (($token, $type) = $lexer->get_next_token) && defined $token) {
print "# type = $type token=$tokenn";
}
Hardware::Vhdl::Lexer splits VHDL code into lexical tokens. To use it, you need to first create a lexer object, passing in something which will supply chunks of VHDL code to the lexer. Repeated calls to the get_next_token method of the lexer will then return VHDL tokens (in scalar context) or a token type code and the token (in list context). get_next_token returns undef when there are no more tokens to be read.
NB: in this documentation I refer to "lines" of VHDL code and "line" sources etc., but in fact the chunks of code dont have to be broken up at line-ends - they can be broken anywhere that isnt in the middle of a token. New-line characters just happen to be a simple and safe way to split up a file. You dont even have to split up the VHDL at all, you can pass in the whole thing as the first and only "line".
Download (0.011MB)
Added: 2007-04-20 License: Perl Artistic License Price:
926 downloads
Performance Co-Pilot viewer 0.0.2
pcpViewer is a 3D viewer of data gathered through the excellent Performance Co-Pilot library. more>>
pcpViewer is a 3D viewer of data gathered through the excellent "Performance Co-Pilot" library.
You can see usage of CPU time, net devices, memory, hard drives, and virtually any data exported by the pcp library and daemon.
I first started this "pet project" as a 3D xosview replacement (thanks for inspiration), so one of the goal is to get the same level of responsiveness as xosview.
<<lessYou can see usage of CPU time, net devices, memory, hard drives, and virtually any data exported by the pcp library and daemon.
I first started this "pet project" as a 3D xosview replacement (thanks for inspiration), so one of the goal is to get the same level of responsiveness as xosview.
Download (0.20MB)
Added: 2005-05-26 License: GPL (GNU General Public License) Price:
1611 downloads
Hardware::Simulator 0000_0005
Hardware::Simulator is a Perl extension for Perl Hardware Descriptor Language. more>>
Hardware::Simulator is a Perl extension for Perl Hardware Descriptor Language.
SYNOPSIS
use Hardware::Simulator;
# NewSignal( perl_variable [, initial_value]);
# create a signal called $in_clk, give it an initial value of 1
NewSignal(my $in_clk,1);
# Repeater ( time_units , code_ref)
# every time_units, call the code reference, starting at the current time
Repeater ( 5, sub{if ( $in_clk==0) { $in_clk=1;} else { $in_clk=0;}});
# Responder ( [signal_name ... signal_name], code_ref );
# respond to any changes to signals by calling code reference.
# any time out_clk changes, print value of clock and simulation time.
Responder ( $out_clk, sub
{
my $time = SimTime();
print "out_clk = $out_clk. time=$timen";
});
# start processing of events and event scheduling.
EventLoop();
Hardware::Simulator ==> a Perl Hardware Descriptor Language
Hardware::Simulator is a lightweight version of VHDL or Verilog HDL. All of these languages were developed as means to describe hardware.
Hardware::Simulator was created as a means to quickly prototype a basic hardware design and simulate it. VHDL and Verilog are both restrictive in their own ways. Hardware::Simulator was created to quickly put something together as a "proof of concept", to show that a design concept would work or not. and then the design could be translated to VHDL or Verilog.
The problem that started all of this was designing a fifo for a video scaling asic. The chip used a buffer to store incoming video data. The asic read the buffer to generate the outgoing video image. We estimated how large we thought the buffer needed to be, but we wanted to confirm that our numbers were right by running simulations.
The problem was we needed to run hundreds of different simulations, given the permutations of input image formats, output image formats, and input/output clock frequencies. We also had text files containing valid formats and frequencies. A text file as input called for perl to manipulate, split, format, and extract the data properly.
This data then had to be translated onto the a HDL simulation. The problem was that there was no easy way to write a perl script that would simulate hardware, so the only solution was to have perl drive a Verilog simulator and pass all these parameters via command line parameters. so then verilog files had to be created, and the simulator had to be driven, and the end result was a lot of work to simulate a simple fifo.
Time contraints did not allow me to develop a HDL package for perl to solve the original problem, but I took it on in my spare time. and eventually Hardware::Simulator was born.
<<lessSYNOPSIS
use Hardware::Simulator;
# NewSignal( perl_variable [, initial_value]);
# create a signal called $in_clk, give it an initial value of 1
NewSignal(my $in_clk,1);
# Repeater ( time_units , code_ref)
# every time_units, call the code reference, starting at the current time
Repeater ( 5, sub{if ( $in_clk==0) { $in_clk=1;} else { $in_clk=0;}});
# Responder ( [signal_name ... signal_name], code_ref );
# respond to any changes to signals by calling code reference.
# any time out_clk changes, print value of clock and simulation time.
Responder ( $out_clk, sub
{
my $time = SimTime();
print "out_clk = $out_clk. time=$timen";
});
# start processing of events and event scheduling.
EventLoop();
Hardware::Simulator ==> a Perl Hardware Descriptor Language
Hardware::Simulator is a lightweight version of VHDL or Verilog HDL. All of these languages were developed as means to describe hardware.
Hardware::Simulator was created as a means to quickly prototype a basic hardware design and simulate it. VHDL and Verilog are both restrictive in their own ways. Hardware::Simulator was created to quickly put something together as a "proof of concept", to show that a design concept would work or not. and then the design could be translated to VHDL or Verilog.
The problem that started all of this was designing a fifo for a video scaling asic. The chip used a buffer to store incoming video data. The asic read the buffer to generate the outgoing video image. We estimated how large we thought the buffer needed to be, but we wanted to confirm that our numbers were right by running simulations.
The problem was we needed to run hundreds of different simulations, given the permutations of input image formats, output image formats, and input/output clock frequencies. We also had text files containing valid formats and frequencies. A text file as input called for perl to manipulate, split, format, and extract the data properly.
This data then had to be translated onto the a HDL simulation. The problem was that there was no easy way to write a perl script that would simulate hardware, so the only solution was to have perl drive a Verilog simulator and pass all these parameters via command line parameters. so then verilog files had to be created, and the simulator had to be driven, and the end result was a lot of work to simulate a simple fifo.
Time contraints did not allow me to develop a HDL package for perl to solve the original problem, but I took it on in my spare time. and eventually Hardware::Simulator was born.
Download (0.010MB)
Added: 2007-07-20 License: Perl Artistic License Price:
840 downloads
DirectX support for Wine 2005-06-13
DirectX support for Wine project enables DirectX 9 support for Wine, which is useful for games and 3D graphics. more>>
DirectX support for Wine project enables DirectX 9 support for Wine, which is useful for games and 3D graphics.
DirectX support for Wine is a set of patches against Wine to implement DirectX 9. It allows modern games and 3D applications to run under Wine.
The patches include many experimental and beta features that have not yet made it into the stable Wine source tree.
The aim of the project is to provide full support for DirectX 8 and 9 so that all games and 3D applications will run on Linux or any other platform that Wine supports.
Main features:
- Shared wined3d codebase for Direct3D 8 and 9
- Hardware non-power2 texstures
- Improved compressed texture support
- Many more texture formats supported
- Offscreen texture improvements
- Colour corrections for textures
- A tonne of bug fixes and other improvements from earlier releases
Enhancements:
- Reworked support for non-power2 textures
- Support for Vertex buffer objects
- Support for caching
- Hardware vertex shaders
- Partial tidyup of vertex declarations
- Better support for compressed textures
- Fix for texturing problems in Axis and Allies and Evil Genius
- Fix for model corruption in Pirates
- Movies in Pirates
- A Fix for the lines on the landscape in Axis and Allies
- Crash fixes in fixupvertices with indexes data
- Numerous other performance improvements
<<lessDirectX support for Wine is a set of patches against Wine to implement DirectX 9. It allows modern games and 3D applications to run under Wine.
The patches include many experimental and beta features that have not yet made it into the stable Wine source tree.
The aim of the project is to provide full support for DirectX 8 and 9 so that all games and 3D applications will run on Linux or any other platform that Wine supports.
Main features:
- Shared wined3d codebase for Direct3D 8 and 9
- Hardware non-power2 texstures
- Improved compressed texture support
- Many more texture formats supported
- Offscreen texture improvements
- Colour corrections for textures
- A tonne of bug fixes and other improvements from earlier releases
Enhancements:
- Reworked support for non-power2 textures
- Support for Vertex buffer objects
- Support for caching
- Hardware vertex shaders
- Partial tidyup of vertex declarations
- Better support for compressed textures
- Fix for texturing problems in Axis and Allies and Evil Genius
- Fix for model corruption in Pirates
- Movies in Pirates
- A Fix for the lines on the landscape in Axis and Allies
- Crash fixes in fixupvertices with indexes data
- Numerous other performance improvements
Download (0.004MB)
Added: 2006-11-06 License: LGPL (GNU Lesser General Public License) Price:
1111 downloads
JPerfmeter 1.4
JPerfmeter is a Java Performance statistics monitor. more>>
JPerfmeter is a Java Performance statistics monitor.
JPerfmeter is a simple performance statistics monitor in the style of perfmeter, full Java.
Note that JPerfmeter needs the rpc.rstatd daemon to be running on the system its monitoring (available on Solaris systems and other various UNIX/Linux systems).
<<lessJPerfmeter is a simple performance statistics monitor in the style of perfmeter, full Java.
Note that JPerfmeter needs the rpc.rstatd daemon to be running on the system its monitoring (available on Solaris systems and other various UNIX/Linux systems).
Download (MB)
Added: 2007-03-28 License: BSD License Price:
945 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above hardware performance search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
