Free hardware platform software for linux

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.

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.

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.

Untangle Gateway Platform is a Linux-based network gateway with pluggable modules for network applications like spam blocking, Web filtering, anti-virus, anti-spyware, intrusion prevention, VPN, SSL VPN, firewall, and more.
Enhancements:
- Bugfixes from 5.0.0-beta; this release is stable.

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".

The General Stream Manipulation Platform (GSMP) aims to become for sound what The GIMP is for graphics.
Some years ago, there had been a lack of useable audio-software for Linux - especially for a good multitrack wave-editor - so we decided to write a gtk-- based one that is available under the terms of the GPL.
Now we focus on building a complete and open-source Virtual Studio environment for Linux:
GSMP Studio will feature both MIDI and DSP/Audio as well as beeing open for other kind of data.
It is intended to become a powerfull framework for the user to assemble his own "virtual studio" within the application from various components (like multitrack hd-recorder, midi-sequencer, synth and signalprocessors).
Other than most commercial applications of this kind, the hd-recorder and midi-sequencer will not be the neccessary components of this studio, and setups without them will be possible. For example GSMP can be used as a synthesizer or multi-effect-proccessor in live-setups.
Main features:
- Non-destructive editing: All action on the audio data can be made undone. So you can play around with the effects without modifying any bit of your original data file.
- Multi-threaded design: GSMP is multi-threaded. Especially the the wave-plots and the FXs are generated in a background thread and the UI keeps interactive!
- Internal sample-format: 24/8 bit fixed-point arithmetic is used to allow overflows with no acurrany loss.
- Internal sample-index: 64 bit indexes are used to allow live takes even at 96kHz DVD quality.
- Track count: The track count is not limitted. Also multi-track recording is supported, too. In fact we used GSMP-Editor to record 10 channels with the MIDIMAN Delta 1010 two month ago!!! (BTW: 2-8% CPU load on an Athlon 600Mhz ...)
- Realtime effect prehearing: Most effects can be pre-heared during playback!
- Supported import-formats: Currently MS-Wave, Ogg/Vorbis and MP3 (experimental!!!) are supported. Decompression is done on-the-fly!
- Supported export-formats: Currently only Wave is supported.
- Current effects: Fadings, graphical-eq, some IIR filters, compressor, noise-gate, de-click and reverb.
- The editor has multi-selections. This means you can select non-continous regions (that can be cutted or pasted) - like in The GIMP. You have to press the "Shift" or "Strg" key while moving the mouse for this.
- To enable the OSS plugin when ALSA is also compiled you have to add "--oss" on the command line. (The next release will contain a real dialog to change this ...)
- The two button in the lower-left corner of the main-window are "Follow Current Position" and "Follor IO Position" to let the view automatikally follow a marker ;-)
- When you load (import) a file the zoom is not changed. So you might not see a wave, because the zoom is still 1:1 -> simply zoom out a bit.
- To speed-up GSMP you should pipe all the debugging informations into the "null-device": "gsmp > /dev/null"

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.