http://armel.applieddata.net/developers/linux/eabi/armel-root-fs.tar.bz2
http://armel.applieddata.net/developers/linux/eabi/armel-root-fs.tar.bz2.md5
http://wiki.debian.org/ArmEabiPort
CodeSourcery GNU: http://www.codesourcery.com/sgpp/lite/arm/portal/release642
By David F. Salisbury
Published: March 19, 2009
I magine a platoon of soldiers fighting in a hazardous urban environment who carry personal digital assistants that can display the location of enemy shooters in three dimensions and accurately identify the caliber and type of weapons they are firing.
Engineers at Vanderbilt University's Institute for Software Integrated Systems (ISIS) have developed a system that can give soldiers just such an edge by turning their combat helmets into "smart nodes” in a wireless sensor network.
ISIS developed this novel technology with the support of the Defense Advanced Research Project Agency and the university has patented the system's key elements.
Like several other shooter location systems developed in recent years, the ISIS system relies on the sound waves produced when a high-powered rifle is fired. These acoustic signals have distinctive characteristics that allow the systems to pick them out from other loud noises and track them back to their source. Current systems, however, rely on centralized or stand-alone sensor arrays. This limits their accuracy and restricts them to identifying shooters at line-of-sight locations.
By contrast, the ISIS system combines information from a number of nodes to triangulate on shooter positions and improve the accuracy of its location identification process. It also uses a patented technique to filter out the echoes that can throw off other acoustic detection systems, explains Akos Ledeczi, the senior research scientist at ISIS who heads up the development effort.
"When DARPA gave us the assignment of creating a shooter location system using nodes with very limited capabilities, they didn't think we could solve the technical problems,” Ledeczi admits. "At first, I didn't think we could do it either, but we figured out how to make it work!”
Retired U.S. Army Lieutenant Colonel Albert Sciarretta, who assesses new military technologies in urban environments for DARPA, is one of the experts who is impressed by the ISIS system: "It's strong points are that it isn't limited to locating shots fired in direct line-of-sight, it can pick up multiple shooters at the same time, and it can identify the caliber and type of weapon that is being fired.”
Sciarretta adds, "A leader can use the information that this system provides to react tactically to enemy shooters in ways that limit the number of friendly force and non-combatant casualties. The ISIS system could be easily developed into an operational war-fighting system.”
When a high-powered rifle is fired, it produces two different kinds of sound waves. One is the "muzzle blast” that expands outward in a spherical wave from the muzzle. The second is a conical shock wave that is produced by the bullet as it travels at supersonic speeds. Each node of the shooter location system contains an array of four sensitive microphones. If at least three of the microphones in a single node detect the muzzle blast, the information allows the nodes' microprocessor to calculate the direction that the sound came from. If the same array also detects the arrival time and angle of the bullet shockwave, a simple calculation gives the shooter's location.
"Because the microphones on the helmet are so close together, the precision is not very high,” Ledeczi says. "However, the nodes are continuously exchanging the times and angles of arrival for these acoustic signals, along with their own locations and orientations. When two or more nodes detect the shot, they can provide the bearing with better than one degree accuracy. The range is typically within a few meters even from as far as 300 meters. The more sensors that pick up the shot, the more accurate the localization.”
The ISIS system communicates its findings with the personal digital assistants that the soldiers carry. The PDAs are loaded with maps or overhead pictures of the area upon which the shooter locations are displayed.
In 2006, a team from the National Institute of Standards and Technology at the U.S. Army Aberdeen Test Center independently determined the accuracy of the system. Firing positions were located at distances of 50 to 300 meters from a 10-node sensor network. Six different weapons were used. The only shots that the system sometimes failed to track accurately were those that passed to one side of all of the nodes.
The field tests demonstrated that the system can pick out the location of high-powered sniper rifles even when they are firing at the same time as a submachine gun like the AK-47. They also proved that it can identify the window that a rifle is firing through even when the rifle is completely inside the building, the technique preferred by trained snipers.
These tests were performed with sensors in fixed locations. One of the problems with using a mobile network has been keeping track of the positions of the mobile nodes with sufficient precision. Standard GPS locations are inadequate for this purpose and satellite coverage can be spotty in urban environments. The ISIS team has recently solved this problem by adding an inexpensive radio chip that allows them to track the relative position of nodes using high-precision radio interferometry. The university has applied for a patent on the technique.
The ISIS shooter system uses wireless nodes invented at UC Berkeley and produced by Crossbow Technology Inc. of San Jose, Calif. These smart nodes, or motes, form self-organizing wireless-sensor networks and are the realization of the Pentagon's "smart-dust” concept of radically reducing the size and cost of sensor networks for military applications. Current commercial shooter location systems are extremely expensive, with prices ranging from $10,000 to $50,000 per unit. By contrast, an entire node for the ISIS system weighs only slightly more than the four AA batteries that power it and costs about $1,000 to construct using currently available commercial hardware.
If Isaac Newton had had access to a supercomputer, he'd have had it watch apples fall and let it figure out what that meant. But the computer would have needed to run an algorithm developed by Cornell researchers that can derive natural laws from observed data.
 Lindsay France/Cornell University Photography |
| Professor Hod Lipson and graduate student Michael Schmidt adjust a double pendulum. Refectors on the pendulum enable motion-tracking software to record position and velocity as the pendulum swings. From this a new computer algorithm can derive equations of motion. |
The researchers have taught a computer to find regularities in the natural world that represent natural laws -- without any prior scientific knowledge on the part of the computer. They have tested their method, or algorithm, on simple mechanical systems and believe it could be applied to more complex systems ranging from biology to cosmology and be useful in analyzing the mountains of data generated by modern experiments that use electronic data collection.
The research is described in the April 3 issue of the journal Science (Vol. 323, No. 5924) by Hod Lipson, associate professor of mechanical and aerospace engineering, and graduate student Michael Schmidt, a specialist in computational biology.
Their process begins by taking the derivatives of every variable observed with respect to every other -- a mathematical way of measuring how one quantity changes as another changes. Then the computer creates equations at random using various constants and variables from the data. It tests these against the known derivatives, keeps the equations that come closest to predicting correctly, modifies them at random and tests again, repeating until it literally evolves a set of equations that accurately describe the behavior of the real system.
Technically, the computer does not output equations, but finds "invariants" -- mathematical expressions that remain true all the time, from which human insights can derive equations.
"Even though it looks like it's changing erratically, there is always something deeper there that is always constant," Lipson explained. "That's the hint to the underlying physics. You want something that doesn't change, but the relationship between the variables in it changes in a way that's similar to [what we see in] the real system."
Once the invariants are found, potentially all equations describing the system are available: "All equations regarding a system must fit into and satisfy the invariants," Schmidt said. "But of course we still need a human interpreter to take this step."
The researchers tested the method with apparatus used in freshman physics courses: a spring-loaded linear oscillator, a single pendulum and a double pendulum. Given data on position and velocity over time, the computer found energy laws, and for the pendulum, the law of conservation of momentum. Given acceleration, it produced Newton's second law of motion.
The researchers point out that the computer evolves these laws without any prior knowledge of physics, kinematics or geometry. But evolution takes time. On a parallel computer with 32 processors, simple linear motion could be analyzed in a few minutes, but the complex double pendulum required 30 to 40 hours of computation. The researchers found that seeding the complex pendulum problem with terms from equations for the simple pendulum cut processing time to seven or eight hours. This "bootstrapping," they said, is similar to the way human scientists build on previous work.
Computers will not make scientists obsolete, the researchers conclude. Rather, they said, the computer can take over the grunt work, helping scientists focus quickly on the interesting phenomena and interpret their meaning.
The research was supported by the National Science Foundation.
__sfr __at (0x2007) CONFIG = _INTRC_OSC_NOCLKOUT & _WDT_OFF & _PWRTE_OFF & _MCLRE_OFF &
_CP_OFF & _IESO_OFF & _FCMEN_OFF & _BOR_OFF;
unsigned char delay1val;
unsigned char delay2val;
void delay()
{
__asm
CLRF _delay1val
CLRF _delay2val
loop:
DECFSZ _delay1val,f
GOTO loop
DECFSZ _delay2val,f
GOTO loop
__endasm;
}
void main()
{
// make C0 as output
TRISC0 = 0;
do {
RC0 = 1;
delay();
RC0 = 0;
delay();
} while (1);
}
OBJS=demo1.o PRJ=demo1 CHIP=690 ARCH=pic14 PLATFORM=16f$(CHIP) LIBPATH=-I/usr/local/share/gputils/lkr -I/usr/local/share/sdcc/lib/pic LINKSCRIPTPATH=/usr/local/share/gputils/lkr LIBS=libsdcc.lib pic$(PLATFORM).lib libm.lib CC=sdcc -V -m$(ARCH) -p$(PLATFORM) LINKER=/usr/local/bin/gplink CFLAGS=--opt-code-speed --stack-auto --main-return --profile --debug-xtra --no-pcode-opt --funsigned-char --Werror CPPFLAGS= .c.o: $(CC) $(CFLAGS) -D_16F$(CHIP) -c $< $(PRJ).hex: $(OBJS) $(LINKER) -w -O1 -m -o $(PRJ).hex $(OBJS) $(LIBPATH) -f 0 $(LIBS) -s $(LINKSCRIPTPATH)/$(PLATFORM).lkr all: $(PRJ).hex clean: @echo "cleaning up all generated files..." @for obj in $(OBJS); do \ if [ -e $$obj ] ; then rm $$obj ; fi \ done @rm *.lst @if [ -e $(PRJ).cod ] ; then rm $(PRJ).cod ; fi @if [ -e $(PRJ).hex ] ; then rm $(PRJ).hex ; fi @echo "done." install: pk2cmd -PPIC$(PLATFORM) -M -F$(PRJ).hex pk2cmd -PPIC$(PLATFORM) -T
<signal.h >
#include <sys/time.h >
#include
That is because when I do:
#ifndef CTDRV_H
#define CTDRV_H
#define PCI_VENDOR_CREATIVE 0x1102
#define PCI_DEVICE_CREATIVE_20K1 0x0005
#define PCI_DEVICE_CREATIVE_20K2 0x000B
#define PCI_SUBVENDOR_CREATIVE 0x1102
#define PCI_SUBSYS_CREATIVE_SB0760 0x0024
//#define PCI_SUBSYS_CREATIVE_SB0880 0x0041
#define PCI_SUBSYS_CREATIVE_SB0880 0x6003
#define PCI_SUBSYS_CREATIVE_HENDRIX 0x6000
//#define PCI_SUBSYS_CREATIVE_HENDRIX 0x6003
#define CT_XFI_DMA_MASK 0xffffffffUL /* 32 bits */
pcm.!default {
type hw
card 1
}
ctl.!default {
type hw
card 1
}
Windows could not start because the following file is missing or corrupt:\system32\hal.dll
Please re-install a copy of the above file
find . -iwholename *.avi -exec ffmpeg -target ntsc-svcd -acodec mp3 -y -i '{}' '{}.mpg' \;
ffmpeg -formats
#if defined(__cplusplus)
#include <cstdio>
#include <cstdlib>
#include <cstring>
#include <iostream>
#include <string>
#include <vector>
#else
error "must be CPP-enabled compiler to compile this program"
#endif
using namespace std;
class CPoint {
public:
CPoint(double a, double b) { x = a; y = b; };
friend std::ostream& operator<< (std::ostream& os, const CPoint& val);
double getX() { return x; };
double getY() { return y; };
private:
double x;
double y;
};
std::ostream& operator<< (ostream& os, const CPoint& pt)
{
return os << "(" << pt.x << ", " << pt.y << ")" ;
}
int main()
{
vector<CPoint> points;
vector<CPoint>::iterator it;
int i;
it = points.begin();
for (i=0; i<10; i++) {
it = points.insert( it, CPoint(10.5+double(i)/11, 22.7 - double(i)/13) );
}
cout << "Vector Demo" << endl << "-------------" << endl;
cout << "Vector size = " << points.size() << endl;
for (it = points.begin(), i=0; it < points.end(); it++,i++)
{
// cout << "points[" <<>x;
cout << " " << *it;
cout << endl;
}
for (i=0; i< points.size(); i++)
{
cout << "points[" << i << "] = " << points[i] << endl;
}
return 0;
}
IPADDR=192.168.1.4
NETMASK=255.255.255.0
NETWORK=
BROADCAST=
STARTMODE=auto
USERCONTROL=no
BRIDGE='yes'
BRIDGE_PORTS='eth0 eth1 eth2'
BRIDGE_AGEINGTIME='300'
BRIDGE_FORWARDDELAY='0'
BRIDGE_HELLOTIME='2'
BRIDGE_MAXAGE='20'
BRIDGE_PATHCOSTS='19'
BRIDGE_PORTPRIORITIES=
BRIDGE_PRIORITY=
BRIDGE_STP='on'
socat /dev/ttyS0,raw,echo=0,crnl /dev/ttyS1,raw,echo=0,crnlsocat TCP:time.nist.gov:13 -socat TCP-LISTEN:80,fork TCP:www.domain.org:80socat READLINE,history=$HOME/.cmd_history /dev/ttyS0,raw,echo=0,crnl socat TCP-LISTEN:port filenamesocat TCP:hostname:port filenamesocat - TCP4:www.domain.org:80 socat -d -d READLINE,history=$HOME/.http_history \
TCP4:www.domain.org:www,crnl
socat TCP4-LISTEN:www TCP4:www.domain.org:www
socat -d -d -lmlocal2 \
TCP4-LISTEN:80,bind=myaddr1,su=nobody,fork,range=10.0.0.0/8,reuseaddr \
TCP4:www.domain.org:80,bind=myaddr2
socat TCP4-LISTEN:5555,fork,tcpwrap=script \
EXEC:/bin/myscript,chroot=/home/sandbox,su-d=sandbox,pty,stderr
socat EXEC:"mail.sh target@domain.com",fdin=3,fdout=4 \
TCP4:mail.relay.org:25,crnl,bind=alias1.server.org,mss=512
socat - /dev/ttyS0,raw,echo=0,crnl
socat UNIX-LISTEN:/tmp/.X11-unix/X1,fork \
SOCKS4:host.victim.org:127.0.0.1:6000,socksuser=nobody,sourceport=20
socat -u /tmp/readdata,seek-end=0,ignoreeof -
(sleep 5; echo PASSWORD; sleep 5; echo ls; sleep 1) |
socat - EXEC:'ssh -l user server',pty,setsid,ctty
socat -u TCP4-LISTEN:3334,reuseaddr,fork \
OPEN:/tmp/in.log,creat,append
socat READLINE,noecho='[Pp]assword:' EXEC:'ftp ftp.server.com',pty,setsid,ctty
socat PTY,link=$HOME/dev/vmodem0,raw,echo=0,waitslave exec:'
socat TCP4-LISTEN:2022,reuseaddr,fork \
PROXY:proxy:www.domain.org:22,proxyport=3128,proxyauth=user:pass
echo |socat -u - file:/tmp/bigfile,create,largefile,seek=100000000000
socat tcp-l:7777,reuseaddr,fork system:filan -i 0 -s >&2,nofork
echo -e
socat - tcp:www.blackhat.org:31337,readbytes=1000
/tmp/com1_sock.
socat UNIX-CONNECT:/tmp/com1_socket TCP-LISTEN:8040
telnet localhost:8040sudo yast -i bridge-utils
BOOTPROTO='dhcp'
NETMASK='255.255.255.0'
STARTMODE='auto'
USERCONTROL='no'
DHCLIENT_TIMEOUT=30
BRIDGE_PORTS='eth0'
BOOTPROTO='static'
IPADDR='0.0.0.0'
VBoxAddIF tap0br0
| Incoming Mail (IMAP) Server - requires SSL: | imap.gmail.com Use SSL: Yes Port: 993 |
| Outgoing Mail (SMTP) Server - requires TLS: | smtp.gmail.com (use authentication) Use Authentication: Yes Use STARTTLS: Yes (some clients call this SSL) Port: 465 or 587 |
| Account Name: | your full email address (including @gmail.com) Google Apps users, please enter username@your_domain.com |
| Email Address: | your full Gmail email address (username@gmail.com) Google Apps users, please enter username@your_domain.com |
| Password: | your Gmail password |