• Complete implementation of the ECMAScript standard Fifth Edition
• Own bytecode-based ECMA262-complaint Regular Expression Engine
• Incremental praise / exact mark-and-sweep garbage collector
• UTF8/UCS2/UTF16/UCS4/UTF32 Unicode support (on level ECMAScript, UCS2/UTF16)
• Compatibility modes, so for example a facile JavaScript compatibility mode
• Bytecode compiler
• Call subroutine-threaded register-based virtual machine
• Context-threaded 32-bit x86 just-in-time compiler (JIT x64/AMD64 is in the work and a JIT for ARM EABI ARMv7 VFPUv1 CPUs with instruction set is planed)
• Constant folding
• Dead code elimination
• Abstract Syntax Tree-based optimizations
• Type inference (both exact and speculative)
• Property Inline Cache
• Performance optimized hash maps
• Self balanced trees (for example to sort on-the-fly items linked list of hash maps for very fast enumeration of array objects)
• Easy native Object Pascal class integration (via RTTI properties and methods published by by-hand-parsing of the native virtual method table)

And here it is finally also the link to BROOM: http://besen.sourceforge.net/

I would look forward to feedback.

Today sees the BeRoXM player is also now for the Nokia N900 and Maemo 5 in officially Maemo Extras-Devel repository (http://repository.maemo.org/ ) And in my own Maemo 5 repository repository where the data are as followed:

Catalog Name: Bero

Internet address: http://vserver.rosseaux.net/repositories/maemo/

Distribution: fremantle

Components: main

Or you call on your N900 directly following the Install URL http://vserver.rosseaux.net/repositories/maemo/install/fremantle/main/beroxmplayer.install on.

Moreover BeRoXM player, at least according to my knowledge, the first multimedia application or for Maemo5 for Nokia N900, which is implemented in Object Pascal and compiled with Free Pascal, and all this without the help of officially Maemo SDKs.

Have fun with it, including very nice bugs please report it:)

Pro N900/Maemo:

• Maemo is more open than Android root access on terms again. Say rootsh (root local) and OpenSSH root (via SSH connection) are installed directly on the Programmmananger, and you have root access, either locally in the X-Terminal and / or through an SSH connection.
• There is an unofficial Android 2.0.1 port for N900 (see maemo.org Forum). But that does not matter here, yes.
• The applications on Maemo run as a native ARM binaries. This means that the N900 visually at least for me seems a lot smoother than my Motorola Milestone with Dalvik-VM, which has exactly the same CPU with the same clock and same graphics unit as the N900. Say both have a QMAP3430 SoC with the same clock and PowerVR SGX 530 graphics than unity.
• 3D applications such as games (OpenGL ES 2.0) run amazingly fluid than in the Milestone, although both have the exact same graphics unit. Yet I could not compare to a first For this I would have to first write an identical small 3D benchmark that will run on both platforms (for Android then on JNI for native code).
• The N900 has TV-Out, which works surprisingly well.
• The N900 has an FM transmitter.
• The N900 has Flash working in Gecko-based browser, which also works surprisingly well, and "liquid".
• The scrolling in Gecko-based browser for N900 is liquid at length as the Android WebKit-based browser on the G1 and Milestone.
• The Internet browser of the N900 and Firefox add-ons such as swallows AdBlock Plus
• Under Maemo is a normal X server. Say if you want, you can also normal X The treatments in a chroot Debian environment to run make and without VNC Forwardingkram (as it is with the Debianchrootkram the G1 does), say for example, Gimp 2.0, Firefox, Open Office, Audacity, LXDE , Openbox, and so on.
• Maemo is a normal Linux distribution with a completely normal standard Linux directory structure and normal libraries (only just stop for ARM CPU target as translated), which is very praiseworthy for developers, as opposed to with Android BOINIC and such.
• The N900 has 32GB plus additional microSD slot internally.
• Most programs are in / opt (symlink to / home / opt on a 2GB NAND partition as / home) installed, so space is enough for many apps available.

Contra N900/Maemo:

• Android Market is at length filled and better use than the App Store and repository (for apt-get on the console and in the Program Manager, Maemo deal) would certainly be no 15/08 users.
• Touchscreen capability / usability of the N900 with a resistive touch screen is very far Androidgeräten with capacitive touch screens. for example, in many places you need the stylus to many places to take at all exact.
• The Maemosteuerung is something illogical in some places, such as how to get in the program list, or, as it scrolls.
• The N900 is compared to my T-Mobile G1 Motorola Milestone and clearly a lot thicker.
• The keyboard of the N900 is significantly behind that of the T-Mobile G1s but roughly at the same level of that of the Motorola milestones.
• The Bildschirmuflösung the N900 with 800x480 pixel wide is lower by some as the Milestone with 854x480, but this is not particularly strong when compared to the weight. And the G1 has only 320x480 anyway here in the cold.
• The maximum volume of the internal speaker is smaller than my Motorola Milestone.
• Nokia is still undecided, which is now their primary OS, whether Symbian or Maemo. Say Maemo has yet an uncertain market future for those like me as app developers.
• Maemo is currently almost exclusively only in landscape mode to use the telephone application in portrait mode as the exception.
• The N900 does not have a digital compass.

Conclusion:

Maemo is in my opinion still strongly behind Android to make up for the mainstream users, and must still strong. So Maemo is rather more for geeks and Android rather more for the mainstream user. The bottom line is I will continue to mainly develop more programs for Android, and now and develop something for Maemo, Maemo has to be established properly.

Photos:

Nokia N900 vs. Motorola Milestone
Nokia N900 vs. T-Mobile Dream G1/HTC with the standard battery and cover (The stronger one thicker 2600 mAh battery for the photos I have previously replaced by the standard battery and replace the thicker cover by the thinner standard cover)

Memory consumption of the N900:

Nokia-N900-51-1: ~ # df-h
Filesystem Size Used Available Use% Mounted on
227.9M 160.7M 63.0M 72% rootfs /
ubi0: rootfs 227.9M 160.7M 63.0M 72% /
tmpfs 1.0M 64.0k 960.0k 6% / tmp
tmpfs 256.0k 84.0k 172.0k 33% / var / run
none 10.0M 80.0k 9.9m 1% / dev
64.0m 64.0m 4.0K tmpfs 0% / dev / shm
/ Dev/mmcblk0p2 2.0G 112.4M 1.8G 6% / home
/ Opt/pymaemo/usr/lib/python2.5
2.0G 112.4M 1.8G 6% / usr/lib/python2.5
/ Opt / pymaemo / usr / share / pyshared
2.0G 112.4M 1.8G 6% / usr / share / pyshared
/ Opt / pymaemo / usr / lib / pyshared
2.0G 112.4M 1.8G 6% / usr / lib / pyshared
/ Opt / pymaemo / usr / share / python-support
2.0G 112.4M 1.8G 6% / usr / share / python-support
/ Opt / pymaemo / usr / lib / python-support
2.0G 112.4M 1.8G 6% / usr / lib / python-support
/ Dev/mmcblk0p1 227.6M 27.0G 26.8G 1% / home / user / MyDocs
/ 7.4g dev/mmcblk1p1 2.0G 5.4G 27% / media/mmc1

Prior to the 160 GB HD, it was resolved through an appropriate boot.ini entry to the hidden Dell Media Direct Windows XP Embedded partition, then point out invited the GRUB boot sector.

But now I had a new empty SSD with nothing on it. I first of all, therefore, partitioned by the SSD with the UBCD in 6 partitions. Here's how:

Then I installed Ubuntu 9.10 and then 64-bit Windows 7, and presented using the LiveCD grub2 MBR restore.

And then I finally made myself to work. I invited my grub2 1.97 Beta 4 herrunter sources including Ubuntu 9:10 patches and then I modified the / boot/i386/pc/boot.S so, so that when I "not" press the Media Direct button to turn on, then that of the MBR boot sector of first partition (/ dev/sda1) loads and runs, and even before the rest of grub2 stuff is loaded from the MBR, that is in fact almost at the very beginning of the MBR code. Andif I turn now the MediaDirect button to confirm my eingepatchter code is skipped by a jump condition and then reloaded the grub2 Main code and executes it. Grub2 loads according näturlich then the Linux kernel.

The query whether it has confirmed the Media Direct button is quite simple. So depending on when you have confirmed the MediaDirect button or not, the BIOS uses the CMOS on the site of the 0x79 bit 3 (bitmask 0x08) or not. The one in the MBR can then query as follows on quite easily (Intel x86 16-bit real mode syntax):

cli
mov al, 0x79
out 0x70, al
nop
nop
nop
in al, 0x71
sti
and al, 0x08

jnz Media Direct Button Pressed

MediaDirectButtonNotPressed:

.....
Media Direct Button Pressed:

And now here finally is the link to the patch: http://vserver.rosseaux.net/stuff/m1330boot.diff.txt

Have fun!

http://vserver.rosseaux.net/projects/brutsd/

BRUTSD but should actually work for many other touch screen controller and the many other Linux distributions.

I hope you have fun so

And why did I post this blog post now, also has a simple reason, which their here can read.

# 100 (previous)

# 102 (next)

BRSMSD contains a complete MIME encoder / decoder with support for all possible character including UTF8 and HTML to Plain text converter, which among other things, tables etc. correct ASCII converted to a graphic. Extra SMS and EMS are supported näturlich completely.

The POP3 and SMTP Kommunkation itself is outsourced to multiple threads, and supports SMTP authentication, the HMAC-MD5 and the POP3 APOP authentication. IMAP support was indeed once planned, but after some considerations I came to the conclusion that here for this use for SMS messages would be something overkil but, at least in relation to the implementation / debugging effort.

In addition, there are still two Kammandozeilen Tools brsmsdread and brsmsdsend. With brsmsdread can read the messages on a shell and send brsmsdsend either the shell or as brsmsdsend parameter eg in bash scripts and messages.

And BRSMSD runs with me not only on the Gigabyte M912M but also on my Dell XPS M1330 Dell subnotebook with a WWAN 5520 UMTS / HSDPA MiniPCI Express card and on my Linksys NSLU2 with Debian Lenny on a 160 GB HDD and a USB Huawei E172 USB UMTS Stick.

The only disadvantage, as long as you have to stop BRSMSD if you want a GPRS / UMTS / HSDPA / HSUPA data call and use, and then start again. Otherwise it runs fine here so far.

And then here's a short Screenshot:

As a new WLAN MiniPCI Express card is the Intel WiFi Link 5100AGN used, which on Linux works for me right out-of-the-box, and only two instead of Draft N really needs three antennas, so that the perfect old B / G only Atheros WLAN MiniPCI Express card can be replaced.

As GSM/GPRS/EDGE/UMTS/7, 2mbitHSDPA/GPS MiniPCI Express card, the Novatel EU850D is used, where I previously have the PIN scratched 20 contact and cut through, so that the pin 20 no longer in contact with the rest of the electronics on MiniPCI Express card, so that the EU850D MiniPCI Express card can work at all in the M912M thanks to a hardware lock. The overstickering of the pin 20 with a tape of course I have previously tried it. However, because the tape always slipped when inserted, so that the pin 20 then unfortunately had resumed contact. At the EU850D MiniPCI Express card otherwise hang two antennas, one outside the 6-cell 7800 mAh battery and an inside straight to the EU850D on the inside cover. served as the basis for the procedure these instructions from jkkmobile

As RAM is a 2 GB RAM DDR2-667 bar from Kingson used.

When is the Super Talent SSD Ultra Drive 128GB ME used, which is really fast, even faster than some of the 7200rpm hard drive in my desktop, even with random access read and write at.

Bluetooth 2.1 + EDR is still available, and the ExpressCard34 slot is still free.

Update: I'm on the night of 17th May 2008 to 18 May 2008 as a number of 3G UMTS / HSDPA speed test run here and added screenshots. During the day I got on the day (17 May 2008) only a maximum of 500 kbit / s down and at night but then I got loose up to about 3.2 mbit / s down.

And here the photos and screenshots: