Slashdot Mirror
T-Engine Enables Ubiquitous Computing
An anonymous reader writes "A Japanese-government sponsored research consortium that include five chip makers and 17 other Japanese high-tech firms, has announced that the T-Engine, a ubiquitous computing platform is ready for prime time. The engine is featured in a IEEE Computer Society article (PDF)
and discussed more on Windley's Technometria. The system is based on the iTron real-time OS and includes multiple boards for different applications."
So it's an embedded computing platform?
Ok, if I was a company [like say Motorola] and wanted to make some sort of portable device [say a cellphone perhaps?] I'd take a READILY AVAILABLE ARM core and drop the sucker into my design.
What really are they offering there other than perhaps a "standard" [though amongst ARM cores there are standards and they use well documented interfaces, etc...]
Is this just better because it's newer or?
Tom
Someday, I'll have a real sig.
"With any luck your 2007 Toyota Camry and your Mitsubishi food processor will be exchanging recipes in the not too distant future."
I'd prefer my car stick to driving, thank you.
The article states that MontaVista has ported its real-time version of Linux to run on the T-Engine. Additionally, Windows CE and Java have also been ported. However, running these systems on the T-Engine is known as running 'guest operating systems', which is a fancy word for 'translated operating sytems'.
I think I used to date this guy...
It's supposed to be completely automatic, but actually you have to press this button.
I don't think they will be able to get everyone to hew to the party line; there will be too many economic reasons to deviate.
.. take any single Asian-produced cell phone, and at its heart you will find pieces of the i-tron initiative. it has already been proven in this space that there are far, far greater reasons to comply with the party line than to deviate. insta-deviation for the sake of it is anathema to the i-tron initiative; it is this very powerful fact that has resulted in such growth in the Asian core and embedded mfr. market in the first place.
..
umm
american electronics/semiconductor giants ridiculed i-tron, and its resulting policies, in the 80's, and Asia has been eating the carcass of former US' manufacturing prowess for lunch. if it weren't for i-tron, philosophically, we wouldn't be buying EUro 5,- MP3 players, made in Taiwan instead of Kansas, at the Aldi checkout lines
if you're a US comp-sci person, and you haven't boned up on i-tron, you've got some history lessons ahead of you. quick, before its too late.
; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
As always, the TRON Web is the most valuable source of infomation on the TRON project in English.
You can find some good articles on the T-Engine platform here.
I've been waiting for a system of this calibre to come along for quite a while. To me, the T-Engine specification, along with iTron, is a tool that can revolutionize how we look at our daily life. For some, it means that they may not have to worry about having to leave their PC to make coffee during a Gentoo install. This specification can and will change the way we look at how we view computers in our daily lives. This is the age of the computer, plain and simple. This system will make computers an even more important, and more critical part of our daily lives.
And they wonder why I left Windows.....
- A phisher sends a small worm to your stereo, the stereo asks the user to re-input the password on the DRM system, the phisher collects that password and uses it to re-sell all your music (possibly making you lose the right to listen to it). Even at $0.02/song and a 5,000 song collection, the phisher gets $100 per cracked stereo.
- Phishers attack one, low-level device hoping that the phished password from that device is also used on other, more important devices. How many people might use the same password on their stereo's DRM system, their refrigerator's automatic reordering system, their car's ignition system, or their bank's online account access?
- Spams starts arriving on ALL audio devices -- audio pop-ups ("audiups"?) start intruding on iPODs, VOIP phones, stereos. Worse, the infection could attack anything with a sound chip. Imagine suggestive Viagra ads coming from your pop-up toaster oven.
- A sleazy marketer buys access to or plants spyware in your vehicle's navigation system. You start getting pop-ups for oil-lube places or the database of locations of competitors becomes corrupted misleading the driver on their location.
- Digital cameras become spam-sending zombies. Anyone who walks within bluetooth range of you suddenly finds an image file on their device that contains an ad for whatever is the latest spam du jour.
- ...... I'm sure there are a million other scenarios, but its early and my coffee hasn't sunk in.
The point: Cool technology, but I wonder if the core OS has needed security layers to prevent exploits like these. I wonder if the systems designers have embedded a strong sense of permissions on processes and interfaces.Two wrongs don't make a right, but three lefts do.
Has anyone outside MITI actually done an objective comparison of TRON with any contemporary RISC? The examples I've seen are ludicrous... comparisons "proving" that TRON is faster than RISC by comparing individual highly specialised TRON instructions with a straightforward unoptimized translation of the same code to an unspecified RISC processor. They don't even do any common subexpression elimination... who would write code like this? http://tronweb.super-nova.co.jp/tronvlsicpu.html
I used to work at Hitachi America so I know about TRON/iTRON/microITRON/etc. It's this weird, baroque API that's non-POSIX and not standard C library compatible. Kind of like an extreme example of Not-Invented-Here syndrome. For some reason Hitachi Japan thought everyone wanted it without realizing that nobody outside Japan cared about it. We kinda tried to humor them..."sure, we will distribute microITRON if customers ask for it".
It's an academic boondoggle that has enough support to keep it alive, but not enough to actually keep it up to date. Implementations of it, like T-engine, feel like circa 1990 era SDKs, particularly if you want to write actual user applications (you know, if you have a job) rather than low level drivers. For the most glaring example, there is no way (in the SDK that I have, at least) for process-based user applications to write to the screen. None. Yes, I'm serious. The one example in the SDK that attempts to do so fails (correctly) with an access violation. You actually have to write a custom screen driver if you want to allow your application to access the screen buffer. T-Engine is fussy, confusingly documented, and basically just unpleasant to use compared to modern application platforms like Symbian, BREW or J2ME. I don't exactly see device manufacturers abandoning ARM chipsets and OSes in droves either. This is just another joke announcement about a toy OS designed for HelloWorld level projects.
If you were blocking sigs, you wouldn't have to read this.
Ken Sakamura's a bit of a nutcase -- he always had this idea (common in Japan at the time, but wrong) that Unicode was some kind of conspiracy to take away Japanese identity and make everyone use a sinister Sino-American character set. So most Japanese computing initiatives have tended to avoid Unicode, and TRON insisted on seeing Unicode as just one charset among many, all mapped into a 'meta character set' space.
Thus when you say 'A' in TRON, you have to specify whether it's a Unicode 'A', a Mojikyou 'A', or some other 'A'. I am simplifying a bit.
In practise, ironically, everyone uses Shift-JIS, which really IS a sinister American conspiracy
Sakamura used to have a web page containing the most extraordinary rant about Unicode, with A LOT of factual errors, which was quite interesting for those wanting to see how certain very reactionary parts of the Japanese business community think. It wasn't exactly a good advert for TRON, though!
Whence? Hence. Whither? Thither.