Free ds homebrew software for linux

DeSmuME project is a Nintendo DS emulator that can run both commercial games and homebrew applications.

The original author of DeSmuME is YopYop156. He has stopped working on it on the beginning of april 2006 and passed the torch to a new team of developers. You can now follow the progress of DeSmuME on this site.

the mg2bot is an IRC bot that was originally written to do unique channel maintenance but which now sports a homebrew plugin system, increased channel awareness, and a bot networking capability.
Enhancements:
- Added tinyurl plugin
- Added karma plugin
- Fixed rydia plugin
- Worked out a bug or two from 0.62b
- First non-beta release

RT-Thread is a real-time operating system. It is designed specifically for small memory footprint platforms. The kernel supports the tranditional RTOS services, such as multiple threads, semaphores, mutexes, event flags, mailboxes, etc.
RT-Thread project also provides a C-expression interpreter shell, from which a programmer can access kernel variables and invoke system functions.
Main features:
Kernel Object System
- There is a kernel object system, which can access and manage all of the kernel objects. Kernel objects include most of the facilities in the kernel, for example, thread, semaphore etc. Kernel objects can be static objects, whose memory is allocated in compiling. It can be dynamic objects as well, whose memory is allocated from system heaps in runtime. Through the kernel object system, RT-Thread operating system can be independent from the memory management system and greatly enhance the scalability of the system.
Multi-Task/Thread Scheduling
- RT-Thread operating system supports multi-task systems, which are based on thread scheduling. The scheduling algorithm used in RT-Thread operating system is a full preemptive priority-based scheduling algorithm. It supports 256 priority levels, in which 0 is the highest and 255 the lowest. The 255th priority is used for idle thread. The scheduling algorithm also supports threads running at same priority level. The shared time-slice round-robin scheduling is used for this case. The time of scheduler to determine the next highest ready thread is determinant. The number of threads in the system is unlimited, only related with RAM.
Synchronization Mechanisms
- RT-Thread operating system supports the traditional semaphore and mutex. Mutex objects use inherited priority to prevent priority reversion. The semaphore release action is safe for interrupt service routine. Moreover, the block queue for thread to obtain semaphore or mutex can be sorted by priority or FIFO.
Inter-Thread Communication
- RT-Thread operating systems supports event/fast event, mail box and message queue. The event mechanism is used to awake a thead by setting one or more corresponding bit of a binary number when an event ocurs. The fast event supports event thread queue. Once a one bit event occurs, the corresponding blocked thread can be found out timing accurately, then will be waked up. In mailbox, a mail length is fixed to 4 byte, which is more effective than message queue. The send action for communication facilities is also safe for interrupt service routine.
Clock and Timer
- In default, the system uses clock tick to implement shared time-slice scheduling. The timing sensitivity of thread is implemented by timers. The timer can be set as one-shot or periodic timeout.
Memory Management
- RT-Thread operating system supports two types memory management: static memory pool management and dynamic memory heap management. The time to allocate a memory block from the memory pool is determinant and when the memory pool is empty, the allocated thread can be blocked (or immediately return, or waiting for sometime to return, which are determined by a timeout parameter). When other thread releases memory blocks to this memory pool, the blocked thread is wake up.
Enhancements:
- More porting was done to Samsung S3C44b0 CPU, AMTEL AT91SAM7S64, Nintendo DS, and Intel i386.

DSLinux is a project that aims to port Linux to the Nintendo DS gaming console.
Important information:
root password for DSLinux builds since Jun 28 2005 is "uClinux" (case sensitive!)
Works on real hardware, use on emulators is not supported
Since Apr 28 2007, RAM build is integrated in the DLDI build.
Enhancements:
- Restored user/mc/src/vfs/mad.c
- Restored user/mc/src/vfs/mad.h
- Restored user/mc/src/intl/libintl.h
- D toolchain/patches/elf2flt-20051225.diff
- A toolchain/patches/elf2flt-20070723.diff
- U toolchain/Makefile
- U vendors/Nintendo/DLDI/config.uClibc
- U lib/uClibc++/Rules.mak
- U lib/uClibc++/extra/Configs/dslinux_config
- D lib/uClibc++/include/system_configuration.h
- U lib/uClibc++/Makefile
- U linux-2.6.x/arch/arm/kernel/ptrace.c
- U linux-2.6.x/arch/arm/mm/fault.c
- Updated to revision 1851.

Jhead is a command line driven utility for extracting digital camera settings from the Exif format files used by many digital cameras. It handles the various confusing ways these can be expressed, and displays them as F-stop, shutter speed, etc.
Jhead project is also able to reduce the size of digital camera JPEGs without loss of information, by deleting integral thumbnails that digital cameras put into the Exif header. If you need to add Exif support to a program, this is a simple program to cut and paste from. Many projects, including PHP, have reused code from this utility.
Things jhead can extract from an Exif jpeg file:
- Integral low-res Exif thumbnail
- Shutter speed
- Camera F-stop number
- Flash used (yes/no)
- Distance camera was focused at
- Focal length and calculate 35 mm equivalent focal length
- Image resolution
- Time and date picture was taken
- Camera make and model
Things jhead can modify in an exif jpeg file:
- Up-right images according to rotation tag using jpegtran
- Set or relative adjust internal exif timestamps
- Re-name or date stamp fils according to exif timestamp
- Transfer exif headers between images
- Edit jpeg comments
- Delete exif or comment sections from jpeg images
Enhancements:
- The "-mkexif" option to create a new minimal EXIF section in an existing image was added.
- The "-ds" and "-dsft" options to manipulate the EXIF date and time were added.
- Image and thumbnail rotation flag handling was fixed.

Sync4j is a mobile application server, and more. Sync4j includes a suite of tools to develop, deploy and manage any mobile project. It is a certified implementation of the Open Mobile Alliance Data Synchronization and Device Management protocols (OMA DS and DM, formerly known as SyncML).
Sync4j reached more than 19,000 downloads in a single month and it is supported by one of the largest mobile developers community in the world.
Main features:
- Sync4j Server: a mobile application server with connectors to SQL relational databases, Microsoft Exchange, Lotus Domino and SugarCRM.
- Sync4j Clients: applications for Outlook, Windows Mobile PocketPC, BlackBerry, Palm and iPod that you can use to synchronize your PIM data (address book and calendar) with the server
- Sync4j Email Gateway: a POP, IMAP and SMTP gateway, to support your mobile email needs.
- Sync4j Software Development Kit: tools to develop sometimes-connected mobile applications on devices (in Java - J2SE and J2ME - and C++) and to add data sources to the server
- Sync4j Device Management: an OMA DM server to remotely manage mobile devices
A wireless application needs data. The information must be available even when the device is off-line. Synchronization between multiple mobile devices and corporate servers is a fundamental component in every wireless project: data is supposed to be consistent when accessed by multiple users who are not always connected to the network.
Once a wireless application is developed, it needs to be transferred to a remote device, over-the-air. Then, it must be kept up-to-date. Application provisioning is pivotal for the success of any mobile project.
Developers of applications around the world have been looking for a platform that would make it easier to create mobile applications. IT Managers are struggling with PIM synchronization and mobile email deployments, locked by commercial vendors on a spiraling high cost structure and unable to manage a fast growing fleet of mobile devices. Sync4j is the solution they are looking for.
Open source means freedom from vendor lock-in and high quality software (thousand of eyes on the code, an enourmous community effort for testing). Sync4j is well supported by the community and the company behind it, Funambol.
Sync4j is an open source complete and unique mobile application server, addressing all the aspects of the equation:
- data synchronization, including PIM and email
- application provisioning
- device management
Sync4j is multi-device and multi-platform, running both in Windows and Linux. It runs on Tomcat and on top of J2EE application servers. It has been designed for carrier-grade deployments.
Since day one, scalability and reliability have been a clear focus of the Sync4j architecture, Sync4j is built on the Open Mobile Alliance data synchronization and device management standards (OMA DS and DM, formerly known as SyncML), thus leveraging the availability of SyncML clients pre-installed on cellular phones (such as all Symbian, Nokia, Motorola, Sony Ericsson, Siemens and others). For devices where a SyncML client is missing, Sync4j provides its own clients: Outlook, Windows Mobile PocketPC, BlackBerry, Palm and iPod.
Sync4j target market is everyone looking to build, deploy and manage a mobile project:
- Developers who need to extend an existing product to the mobile world or are looking for an easy way to create new mobile applications, grabbing data from existing data sources (such as SQL databases, Exchange, Domino or SugarCRM) or adding new data sources.
- IT Managers that want to deploy a PIM and mobile email solution or just need a way to manage a fleet of mobile devices.
- Device Manufacturers, that are looking for an OMA DM or DS client.
Download includes:
Apache Tomcat 5.0, Sync4j Admin 1.2.4, Sync4j Java GUI Client 1.0.9, PIM Web Demo 1.1.7. Runs out-of-the-box.
Enhancements:
- Major bugfixes

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

jrawio is a Service Provider Implementation for the Java ImageIO API. It provides the ability to read images coded in a digital "camera raw" format (such as NEF for Nikon or CRW/CR2 for Canon).
jrawio is to be pointed out that jrawio is implemented in 100% pure Java.
In simple words, a Camera RAW format is the dump of the data collected by the camera sensor, with basically no post-processing applied. While it has the pitfall of requiring heavy processing in order to achieve a displayable image, the basic advantage is that any transformatio applied to it is "reversible".
From this point of view a Camera RAW format can be thought as a "digital negative". But dont confuse this with Adobes Digital Negative format (.DNG), which is just the try to define a standard format of RAW images. Indeed every camera manufacturer (e.g. Nikon, Canon, ...) has its own format.
jrawio is presently a Release Candidate for v1.0, so its coming out of beta stage. Please refer also to the Release Notes for information about issues.
It has been tested with about 8,000 photos taken with Nikon D100 and D70 cameras and with about 250 samples of various cameras downloaded from the web. jrawio has been explicitly tested with the following models:
Canon CR2 Digital Rebel, EOS 1D MkII, EOS 1Ds MkII, EOS 350D
Canon CRW D30, EOD 10D, EOS 300D
Leica DNG R8, R9
Minolta MRW DiMAGE 5, DiMAGE 7i, DiMAGE 7Hi
Nikon NEF CoolPix 5400, CoolPix 5700, CoolPix 8700, CoolPix 8800, D1, D100, D1X, D200, D2H, D2X, D50, D70, D70s
Pentax PEF *ist D, *ist DL, *ist DS
Sony SRF F828
Enhancements:
- This release fixes bugs related to application integration.