Friday, January 09, 2009

Linux Real Time Patch Review - Vanilla vs. RT patch comparison

Linux Real Time Patch Review - Vanilla vs. RT patch comparison

Hardly any standard operating system kernel is hard real time capable. At best, they're soft real time capable, with latencies up to milliseconds.

RTAI and Xenomai provide hard real time, which means that those operating systems (inserted between the hardware and Linux) can assure interrupt response times in the microsecond range. Not so with that standard Linux kernel. The 2.6 kernel - in comparison to the 2.4 kernel - has been much improved in regard to latencies, but still has some bottlenecks. Ingo Molnar provides a patch to compensate for those bottlenecks.
Ingo Molnar RealTime Preempt Patch

This patch improves the responsiveness of the kernel dramatically.
The tests below have been conducted with a tool provided by Andrew Morton. Within the amlat package, there is a tool called "realfeel" which also works on 2.6 kernels, despite the "amlat" tool which, well, doesn't even work on 2.4 kernels on recent systems.
Linux scheduling latency (Andrew Morton)

Here is a small tar.gz which provides just the "realfeel" tool from the AKPM package and the famous "hackbench" (tweaked to acually compile):
captest.tar.gz (2k)

Compile with "make".
# ./realfeel histogramfilename.hist
1400.038 MHz
secondsPerTick=0.000000
ticksPerSecond=1400037759.748198
2048 Hz
0.451 msec
0.361 msec
-0.004 msec
-0.029 msec
-0.146 msec
-0.205 msec

For the hackbench stress test call it like this:
# ./hackbench 100

Adjust the parameter - WARNING: if the parameter is too high, your system might freeze!

If you get something like this with "realfeel":
ioctl(RTC_IRQP_SET) failed: Invalid argument

do this:
# rmmod genrtc
# modprobe rtc

This removes the module "genrtc" and loads the "rtc" (real time clock driver).

In any case, you should unload the module "genrtc" and load the module "rtc".


THE RESULTS

The result with a vanilla 2.6.15 kernel:
(first column is in milliseconds; second column is the number of RTC (real time clock) interrupts received)

0.0 54410
0.1 32
0.2 8
0.3 5
0.4 3
0.5 1
0.6 1
0.8 1
1.0 1
1.4 1
1.5 1
2.0 1
3.7 1
As you can see, the max. latency of the RTC interrupt was about 3.7 milliseconds. (UPDATE: with "hackbench" I've even got more than ONE SECOND!!!)

Results with the rt16 RT patch:
0.0 308821
0.1 832
0.2 104
As you can see, the max. latency was just about 200 microseconds. (UPDATE: with "hackbench" I got a max. of about 400us)

If there is no or almost no load on your system, take into account that SMI (System Maintenance Interrupts on e.g. Intel 82845 845 (Brookdale) motherboards) can and will produce latencies of > 200us. Also see: Xenomai: High latencies with SMI not disabled

CONCLUSIONS:

If you need to have a low latency system for audio, music or video processing, the Molnar low latency patch might be the right thing for you.
But still, if you need hard real time performance, where latencies must not be higher than a few tens of microseconds, you'll better off with RTAI or XENOMAI.

Appendix:

Here are a few stress testing routines proven to be good for determining the worst case latencies.


# dd if=/dev/zero of=bigfile bs=1024000 count=1024
# ping -l 100000 -q -s 10 -f localhost
# ping -f -s 1400 & dd if=/dev/urandom of=/dev/null & ls -lR /
# - a=0; while "true"; do cat /proc/interrupts; a=`expr $a + 1`; echo $a; done
# while :; do dd if=/dev/zero of=/tmp/foo bs=1M count=500; sync; rm /tmp/foo; done


If you want to combine some of those:
#!/bin/sh
dd if=/dev/zero of=bigfile1 bs=1024000 count=1000 &
ping -l 100000 -q -s 10 -f localhost &
du / &
-or one from Paolo Mantegazza (RTAI.org)
a=0; while "true"; do dd if=/dev/hda1 of=/dev/null bs=1M count=1000;
a=`expr $a + 1`; date; echo $a; done
(this is just one line!)

If you use "hackbench" you can try this:
#!/bin/sh
while true; do dd if=/dev/zero of=bigfile bs=1024000 count=1024; done &
while true; do killall hackbench; sleep 5; done &
while true; do ./hackbench 20; done &
ping -l 100000 -q -s 10 -f localhost &
du / &


Most hardcore test
Philippe Gerum (Ingo Molnar):
http://lkml.org/lkml/2005/6/22/347
while true; do dd if=/dev/zero of=bigfile bs=1024000 count=1024; done &
while true; do killall hackbench; sleep 5; done &
while true; do ./hackbench 20; done &
( cd ltp-full-20040707; while true; do ./runalltests.sh -x 40; done; ) &
ping -l 100000 -q -s 10 -f localhost &
du / &


And last but not least, here is a process listing of the processes on a RT preempt patch patched kernel and a vanilla kernel just after booting on a debian sarge system ...
... to illustrate the differences between the rt-patch and vanilla kernel system:

2.6.15-rt16
# ps -A
PID TTY TIME CMD
1 ? 00:00:00 init
2 ? 00:00:00 softirq-high/0
3 ? 00:00:00 softirq-timer/0
4 ? 00:00:00 softirq-net-tx/
5 ? 00:00:00 softirq-net-rx/
6 ? 00:00:00 softirq-scsi/0
7 ? 00:00:00 softirq-tasklet
8 ? 00:00:00 desched/0
9 ? 00:00:03 events/0
10 ? 00:00:00 khelper
11 ? 00:00:00 kthread
12 ? 00:00:00 kblockd/0
13 ? 00:00:00 pdflush
14 ? 00:00:00 pdflush
16 ? 00:00:00 aio/0
15 ? 00:00:00 kswapd0
17 ? 00:00:00 kseriod
18 ? 00:00:00 IRQ 12
19 ? 00:00:00 IRQ 14
20 ? 00:00:00 kjournald
21 ? 00:00:00 IRQ 1
378 ? 00:00:00 IRQ 19
389 ? 00:00:00 IRQ 4
392 ? 00:00:00 IRQ 3
544 ? 00:00:00 syslogd
547 ? 00:00:00 klogd
579 ? 00:00:00 exim4
584 ? 00:00:00 inetd
592 ? 00:00:00 sshd
597 ? 00:00:00 atd
600 ? 00:00:00 cron
606 tty1 00:00:00 getty
607 tty2 00:00:00 getty
608 tty3 00:00:00 getty
609 tty4 00:00:00 getty
610 tty5 00:00:00 getty
611 tty6 00:00:00 getty
612 ? 00:00:00 sshd
614 pts/0 00:00:00 bash
618 pts/0 00:00:00 ps


2.6.15 vanilla
# ps -A
PID TTY TIME CMD
1 ? 00:00:00 init
2 ? 00:00:00 ksoftirqd/0
3 ? 00:00:04 events/0
4 ? 00:00:00 khelper
5 ? 00:00:00 kthread
6 ? 00:00:00 kblockd/0
7 ? 00:00:00 pdflush
8 ? 00:00:00 pdflush
10 ? 00:00:00 aio/0
9 ? 00:00:00 kswapd0
11 ? 00:00:00 kseriod
12 ? 00:00:00 kjournald
532 ? 00:00:00 syslogd
535 ? 00:00:00 klogd
567 ? 00:00:00 exim4
572 ? 00:00:00 inetd
580 ? 00:00:00 sshd
585 ? 00:00:00 atd
588 ? 00:00:00 cron
594 tty1 00:00:00 getty
595 tty2 00:00:00 getty
596 tty3 00:00:00 getty
597 tty4 00:00:00 getty
598 tty5 00:00:00 getty
599 tty6 00:00:00 getty
602 ? 00:00:00 sshd
604 pts/0 00:00:00 bash
609 pts/0 00:00:00 ps


Last-Modified: Thu, 09 Feb 2006 19:14:41 GMT

Linus Torvalds on git

轉自 http://people.debian.org.tw/~chihchun/2008/12/19/linus-torvalds-on-git/

Linus Torvalds on git

這段錄影已經躺在硬碟中很久,這兩日才利用通勤的時間消化了一番。這是 Linus Torvalds 在 Google 所進行的一段演講,身為一個性格強硬的硬底子駭客,他時常發出驚人的評論,有些有趣的言論甚至被整理成格言集,像是 The 10 Best Linus Torvalds Quotes 或 Linus Torvalds Quotes。

在這段演講中,身為 Git 計畫的發起人,Linus 說明了為什麼需要設計這樣的一套工具,基本的設計哲學與其他類似的工具的比較。

在技術的觀點上,他直接且尖銳的同時批判了 CVS 與 Subversion, 演講一開始 Linus 就給了 CVS 贊頌 - 負面的贊頌,雖然 Linus 從來不用 CVS 管理 Kernel source tree,但是還是在商業公司有過一段不短時間的使用經驗,而且 Linus 打從心裡強烈的厭惡這個工具。同時他也批判 Subversion 這個計畫是他看過最沒有意義的,因為 Subversion 從各方面試著去改善 CVS 的一些技術上的缺點,卻無法根本的解決一些基本使用限制。具體來說 Subversion 改善的創建分支的成本 (意思是相對 CVS 所利用的硬碟、計算資源比較少),但是卻沒辦法解決合併分支的需求,任何使用過 Subversion 合併分支的人都知道那是如何痛苦的折磨。而許多高度開發中的專案,都時常需要為不同的新功能開分支、合併,Subversion 解決了開分支的成本,卻沒有考慮到合併的人工成本。如此讓 Subversion 變成一個沒有未來的軟體計畫。

因此,基於過去在 BitKeeper 上得使用經驗,Linus 設計了新的 Git, 並將效能視為主要的需求。當然分散式的設計也是最重要的概念之一,Linus 提到幾個觀點,討論如下。

第一個是分散式的概念,解決了政治紛爭。所謂政治紛爭指 commit/checkout/create branch 的權利,傳統中央集權式開發模式,你若想要創建一個新的分支,或者進行一些實驗性的開發,通常必須獲得主開發者授予 提交者 (commitor) 的權限,意指你是受到信任的一份子,有權限可以自行修改軟體程式碼,被授權進行一些嘗試。(唐鳳的人人皆為提交者開發模式為例外)

這種模式,很自然的排擠了在所謂信任圈 (core developers) 外的人。對,你依然可以在中央控管的機制下嘗試,你依然可以透過 patch 提交你想要做的更動。但是工具本身的限制,直接的限縮了自由發展的可能性。舉例來說,你相對不容易組成一個工作小組 (Task Group),因為分享程式碼的變動並不容易,你可能必須建立另外一個獨立的程式碼管理系統給這個工作小組使用。而不像分散式的管理工具如 Git/Mercurial 開發者間可以透過數種管道接取/同步雙方的進度。

或者中央集權工具的另外一個根本上的問題是 - 它阻礙了開發者的實驗精神。

簡單講,就是開發者礙於每次提交 (commit),都可能因為程式碼的不相容性,造成其他人必須停下來彙整變更,影響到其他人的工作進度的後果,因此每次提交/儲存都會有所疑慮。因此很 容易就演變成開發者埋頭苦幹,直到最後一刻才一口氣提交上線,結果造成的不相容與衝擊更大,反而造成最後的工作成果難以融合。

在分散式開發工具的輔助下,你可以隨意的開立新分支,自行修改、測試、同步、實驗,這些在本地的提交除了完全不會影響到其他人外,同時你也可以輕易的匯出成特定格式 (patches),讓他人更容易的整合。這大幅改善了協同開發模式的磨合問題。

Git 是以分散式開發模式為根本,自然可以融合於相對單純的中央集權 (cvs/svn) 的權利結構。Linus 在演講中也提出了一個我認為很值得討論的觀點,即是應用於 Linux kernel 開發的多層次分散權利結構。Linus 提了一個重點,基本上開發社群中有一種信任關係 (Web of trust),像 Linux Kernel 這樣的龐大計畫,每個版本參與的開發者大約千人。 實際上主要開發者如 Linus 不可能認識這麼多人,很自然的,他只能信任最熟識的幾個人,他指知道幾個人的智商與能力都是足以信賴的,於是他只需要仰賴這些人的成果。而其他人在於自己 的信賴圈內,找到其他可以仰賴的人,於是利用這樣的信賴機制來擴展成網狀的開發社群。

在實務上,社群中也會演化出幾個角色,像是司令官 (dictator)、副官 (lieutenants)、開發者。幾位副官只要專注在他們熟悉的領域,整合開發者的成果,並提交給司令官做最後的整合決策。這麼一來,各種不同的專業 領域都可以交給最熟悉的開發人員管理,而開發不會被限制、停頓在某個角色身上,相對而言是一個比較具有效率的開發社群結構。且分散式開發,也讓不同的開發 者得以有權利與自由自行發展,不受限於官僚機制的限制。

上述為演講內容的一些提要。

Web of trust 是我相當認同的一個概念,任何所謂社群中,都會自然的因為信賴關係存在更小的團體,有人誤解這是一種分裂,但是我認為這是一種演化,不該消弭小圈圈的存 在,反而應該鼓勵小團體的成立,自行交流、合作,才有機會產生或再演化出更大、更有力量、更健康的社群。(應該有什麼什麼政治學、社會學的理論在講這件事 情吧 ?)

另外也推薦一個網站,是即將被國家綁架去服役的 kanru 翻譯的「為什麼 Git 比 X 棒」(Why Git is Better than X)。這個網站簡約的說明了 git 與其他程式碼控制軟體的比較,可以讓你比較容易了解各種軟體間的差異細節。

另外 為什麼 Git 比 X 棒 這個網站中介紹的 github 服務,我個人相當欣賞,它基本上提供了 Git 的 hosting 服務,但同時也包含了更多 Web 2.0 的概念,是所謂 “Social coding hosting”,基本的功能除了提供 Git 外,像一般的社交網站一樣,你可以追蹤別人的狀態,別的網站你追蹤的是朋友發出來的訊息,這裡你追蹤的是朋友寫出來的程式碼,而且你可以直接在線上「複 製」(branching) 別人的工作成果,也提供了相當美觀的介面,讓你看到程式碼更動的網路關聯圖,相當有趣。剛開始使用 Git 時,可以試試這個網站。

若想學習 Git, 請參考 Learning git 一文的連結。

一小時內搞懂 Git

此文轉自:http://people.debian.org.tw/~chihchun/2009/01/05/understand-git-in-one-hour/


我已經在 Learning git 中提到 Scott Chacon 的 GitCasts 網站,網站中包含相當多的操作示範影片。但是其中有一則在原本的文章沒提到的是 Scoot 在 RailsConf 2008 對 Git 做了一個相當精彩的演講,若你原本有使用其他版本控制系統的經驗,花一個小時聽完 Scott 的介紹應該是最有效率的方法。

這場演講中,Scott 廣泛的介紹 Git 的設計理念與使用方法,解釋了 Git 所使用的 DAG Storage 與 SVN 所用的 Delta Stroage 的內涵差異,深入說明 Git 所使用的 Object Model,並解釋那些特別容易令人困惑的 index, remote/local branches 的概念,甚至幫你說明了最重要的幾個 Git 指令的使用方式。專心聽完,真的可以馬上學會喔。


(請按播放視窗的圖示將影像全螢幕較適合閱讀。)

簡報可於 SlideShare 取得。聽完還意猶未盡的話,請深入閱讀 Git Community Book 吧。

對了,Perl 社群最近也開始使用 Git 來作為版本控制系統了。

January 5th, 2009 at 8:00 am | Comments & Trackbacks (1) | Permalink

Thursday, January 08, 2009

詩篇 第 一四三 章

143:0 大衛的詩。
143:1 耶和華阿,求你聽我的禱告,側耳聽我的懇求,憑你的信實和公義應允我;
143:2 求你不要傳喚你的僕人去受審,因為在你面前,凡活著的人沒有一個是義的。
143:3 原來仇敵逼迫我,將我的命壓倒在地,使我住在幽暗之處,像死了許久的人一樣。
143:4 所以,我的靈在我裏面發昏;我的心在我裏面驚懼。
143:5 我追想古時之日,默念你的一切作為,默想你手的工作。
143:6 我向你伸開雙手禱告,我的魂渴想你,如乾旱之地盼雨一樣。〔細拉〕
143:7 耶和華阿,求你速速應允我;我的靈耗盡。不要向我掩面,免得我像那些下坑的人一樣。
143:8 求你使我清晨得聽你的慈愛,因我信靠你。求你使我知道當行的道路,因我的魂仰望你。
143:9 耶和華阿,求你救我脫離我的仇敵;我逃往你那裏避難。
143:10 求你指教我遵行你的旨意,因你是我的神;願你至善的靈引我到平坦之地。
143:11 耶和華阿,求你為你的名將我救活;憑你的公義,將我從患難中領出來;
143:12 憑你的慈愛剪除我的仇敵,滅絕一切欺壓我的人,因我是你的僕人。

Wednesday, January 07, 2009

轉帳非IE不可?WebATM不必再受限!

http://tw.news.yahoo.com/article/url/d/a/090107/52/1ckos.html

你曾碰過使用WebATM服務,卻因為網路瀏覽器並非微軟IE而失敗嗎?現在這樣的情況將可獲得改善。由於國內民眾使用其他網路瀏覽器的比例越來越高,玉山銀行首創先例,將旗下WebATM擴大支援Firefox、GoogleChrome、Opera等瀏覽器,讓民眾從事網路金融交易更為方便。

...
這次擴大WebATM服務範圍,玉山銀行將提供支援Firefox、GoogleChrome、Opera等瀏覽器的軟體,民眾只要上網下載安裝驅動程式後,就能省略掉切換瀏覽器,才能使用WebATM的麻煩。

The Linux Kernel Module Programming Guide

The Linux Kernel Module Programming Guide

http://tldp.org/LDP/lkmpg/2.6/html/

Wednesday, December 31, 2008

Eclipse adds embedded device projects

http://www.linuxdevices.com/news/NS3129544707.html

Apr. 14, 2008


The open-source Eclipse Foundation announced four initiatives that address embedded and mobile device development. The new Device Software Development Project (DSDP) initiatives include a framework for communications among debugging and monitoring devices, and a Texas Instruments (TI)-sponsored project devoted to creating and configuring C/C++ tools for "highly constrained" devices.

In brief, the four new initiatives include:
  • Real-time System Components (RTSC) -- This TI-led project will create a programming model and Eclipse tools for developing and configuring C and C++ applications for highly constrained devices such as digital signal processors (DSPs) and microcontrollers (more info below).

  • Target Communications Framework (TCF) -- The TCF is a lightweight extensible communications protocol for communications between devices and development tools, including debugging, monitoring, analysis, and test tools (more below).

  • Device Debugging (DD) -- Release 1.0 will be made available as part of the Ganymede release in June, says the Eclipse Foundation. The project defines an extensible Debugger Services Framework (DSF) for enabling commercial tool vendors to build debugger integrations in Eclipse. The 1.0 release adds a reference implementation that supports the GDB debug engine.

    Wind River's Doug Gaff, who leads the DSDP's project management committee, observed, "We needed a customized debugger implementation to deal with multicore, hardware-software agent connections, and so on. Wind River has adopted it commercially already, and it's starting to get community pickup as well."

  • Target Management (TM) with support for Windows Embedded (formerly Windows CE) -- The ETM project will add support for Windows Embedded (formerly Windows CE, enabling developers to remotely edit, update, and delete files directly on remote devices or development targets. Gaff explained that the project came about because, "We had a contributor who has to use Windows CE in a remote system, and needed the capability to manipulate it."

    TM for CE aims to let developers mount, browse, edit, and sync remote filesystems as if they were local. It uses Windows's filesystem interface, and so is filesystem agnostic.

    Gaff proudly notes, "Microsoft's tools only allow read-only access [to remote filesystems], so you have to manually re-upload during edit, compile, debug. We have something that's better, and that's kind of exciting."

    Gaff noted that TM does not yet support remotely debugging CE systems, however. For that, developers still have to use Cygwin or the WinCW emulator. However, Microsoft has published its debug services API, he adds, so there's no technical obstacle to adding remote debug support. "You can download the APIs from Microsoft. Someone just needs to do the work."

    Asked whether Microsoft might be interested in contributing that work, Gaff replied, "Actually, my preference would be for Microsoft to show up to the Eclipse Project."

    He quickly added, "That's a bit tongue-in-cheek. But Microsoft is taking steps in the right direction. Sam Ramji, who directs the Open Source Lab at Microsoft, spoke at EclipseCon. And they are involved in SWT (standard widget set). So, they are engaging directly with Eclipse now on a couple of areas where there's clear opportunity with open source."
DSDP background

The four highlighted projects are all part of the Eclipse Device Software Development Platform (DSDP) Project. Founded in 2005, the DSDP was spearheaded by Wind River, and now boasts seven sub-projects, with an eighth EDA-related project also proposed. Three projects are led by Wind River employees. One, the Eclipse C/C++ Development Tooling (CDT) Project, has been downloaded over a million times in the last year, the Foundation claims.

The sub-projects are aimed at creating plugins for the modular, open-source, Eclipse IDE (integrated development environment). The IDE has been widely adopted by embedded tools vendors, in part because it runs on Linux, Windows, Solaris, and Macintosh development hosts, saving vendors the trouble of maintaining their tools on multiple platforms.

The next milestone for the Eclipse Foundation is the yearly coordinated code release in June. Based on version 3.4 of the Eclipse Framework, and code-named "Ganymede," the coordinated release is a kind of snapshot that allows tool and application vendors to evaluate available project software as a single, more or less pre-integrated collection, albeit one mixing mature and pre-1.0 code.

The previous major release of DSDP project software took place last June, with the 21-project Europa release, which comprised 17 million lines of code. Previous to that, the DSDP was represented by a more modest release in November 2006, when 1.0 versions of the Target Management and Embedded Rich Client Platform plugins launched, alongside a release of the Mobile Tools for Java plugin.

The new projects: RTSC and TCF

The RTSC project is intended to generate a new Eclipse development model and tools for C/C++ embedded real-time software components for DSPs and 16-bit microcontrollers. The project is led by Dave Russo, TI's CTO of target software infrastructure.

Russo explains, "In 25 words or less, we're defining a C-based component model, and providing a set of supporting tools for developing, delivering, and deploying real-time software for a diverse set of platforms, from 16-bit MCUs like the MSP430 and Intel 8051 to traditional DSPs."

Russo adds, "On these resource constrained processors, most people still write in C. But we'd like to have the benefits of 'component-ization' that the Java community enjoys. Write-once-deploy in many places, for example, where one group defines an interface, another implements it, and another uses it. It's aimed at allowing C to scale the way Java has been able to scale -- like with the Eclipse project, for example."

In addition to contributing RTSC to the Eclipse project, TI has actually adopted the Eclipse framework for the newest version 4 releases of Code Composer Studio, Russo notes. He adds that RTSC is based on extremely mature technology that has been used by TI internally for many years. "We started developing it in 2000, and have fielded a number of embedded products that use it. For example, DSP BIOS, that's an RTSC component."

TI hopes RTSC will see adoption by other tools vendors, and component makers such as codec suppliers, so as to start a "feedback cycle." And, he adds, "Now that it's open in Eclipse, we've had some discussion with Freescale. We're also hoping for adoption by tools vendors and components vendors."

RTSC will require little or no pre-deployed infrastructure, as would a Java runtime, says the group. Aside from a component's C/C++ runtime, all that is needed for each component is JavaScript code that runs in both the component's development environment during application assembly, as well as in rich client platforms for execution monitoring.

Eclipse-based tools will specify components using an ANTLR-based IDL, then implement the components using both C/C++ and JavaScript. The JavaScript is part of a component that runs on top of Rhino, enabling the component to actively participate in all stages of its lifecycle, from assembly to real-time monitoring.

RTSC components can leverage "traditional" Java-based component environments as well as "satisfying the resource constraints of its embedded C/C++ element running within the embedded device," says the group. This "dual existence," spanning assembly and rich-client implementations, should enable integration with the following projects:
  • CDT
  • TPTP (Test Performance and Tools Platform Project)
  • SODA (Service Oriented Device Architecture), for the Device Kit portion of the project
  • COSMOS (Community-driven Systems Management in Open Source) monitoring and data collection components
  • EMF (Eclipse Modeling Framework), enabling UML tools to specify components that generate resource-efficient RTSC components
In a statement, Russo said, "By open-sourcing RTSC technology under the Eclipse Public License, we are moving to standardize the way embedded C content is specified, packaged and integrated so that producers and consumers of this content can more easily supply, assemble, and reuse components to create integrated application solutions.�

Target Communications Framework (TCF)

The lofty goal of the TCF project, which is led by Wind River, Freescale, and Power.org, is to be the "Eclipse 'Explorer of the Network Neighborhood,'" offering "pluggable information providers under a single, consistent UI," says the group. The idea is to enable developers to use the lightweight protocol to interactively discover, drill down, and analyze remote systems.

The protocol is designed to work with a variety of debugging, monitoring, analysis, and test tools, including target agents, JTAG probes, and target simulators. The intent is to streamline testing and development of heterogeneous, multiple-vendor device configurations such as are commonly found with multicore and system-on-a chip (SoC) processors.

The TCF toolkit includes a core Remote System Explorer (RSE) framework that is said to integrate heterogeneous remote resources via pluggable subsystems. The toolkit also includes a "Remote Files" subsystem that enables transparent operation on remote computers, as well as a shell and a processes subsystem. The toolkit also provides a lightweight terminal and a "Network Discovery" framework.

Stated Steve Furr, Freescale Semiconductor, "As the embedded industry moves to ever more complex SoC's, including the extensive use of multiple symmetric cores, getting all of the various tools required to do effective development connected to the appropriate data collection mechanisms is the next big issue that needs to be addressed. TCF is a great way for the community to work together to solve this problem."

All four projects will be demonstrated by the Foundation at the Embedded Systems Conference in San Jose this week.

Monday, December 29, 2008

Linux 驅動程式的中斷處理

Linux 驅動程式的中斷處理: 1 request_irq 基本觀念
http://www.jollen.org/blog/2008/03/interrupt_handling_1.html

Linux 驅動程式的中斷處理, #2: 深入淺出中斷模式
http://www.jollen.org/blog/2008/03/interrupt_handling_semaphore.html

Linux 驅動程式的中斷處理, #3: Bottom Half 的觀念
http://www.jollen.org/blog/2008/03/interrupt_handling_bottom_half.html

Tuesday, December 23, 2008

When 'V' meets 'W' ...

When 'V' meets 'W' ...
http://zangyp.blogspot.com/

By 'V' and 'W', I am not talking about "Volkswagen" ;-P , but I mean "vehicles" and "wireless", or to say when the automotive insustry meets the wireless industry...

Monday, December 08, 2008

冬戀大雪山林

看起來view不錯的樣子
列入景點

冬戀大雪山林 站上環繞365度視覺空間
更新日期:2008/12/07 01:26 羅惠文

【大台灣旅遊網TTNews記者羅惠文】

台中縣大雪山林是許多喜愛山林人士的登山旅遊勝地,登上大雪山林,一年四季萬化的美景盡收眼底,讓人難忘。

  擁有居高臨下地理優勢的彩雲居,位於海拔約一公尺高的至高點,坐擁山間、優美絕佳的視覺,365度的感受台灣雲瀑、雲海的壯闊之美,這令人感動山河與壯闊,離不開視覺的景緻,還有從晨曦到日出、午後、夕陽餘暉到夜晚,一幕又一幕的唯美畫作。

  彩雲居除了擁有絕佳位置之外,登高望遠的當下,還可以遠望大甲溪、大安溪,台中港、大度山脈、往北的苗栗卓蘭,享受這山林悠悠之美,入住這飽覽自然景緻的住宿環境裡。(圖/彩雲居觀景民宿提供)

大雪山民宿‧彩雲居觀景民宿:http://0425971275.travel-web.com.tw/

東勢石岡之旅:http://423.travel-web.com.tw/

Saturday, December 06, 2008

神說,當你笑了,全世界都會跟著笑

上帝說,當你笑了,全世界都會跟著笑,原來快樂跟病毒一樣也有傳染力!美國研究發現,如果身邊的人常保著快樂的情緒,那麼身邊的人也就會快樂起來,認識快樂的人越多,自己跟著快樂的機率也就越高,想要快樂其實很簡單。

美國哈佛大學與 加州大學聖地牙哥分校,以20年的時間持續追蹤5千多位成年人,結果發現只要身邊的人快樂,自己也會跟著感到快樂。研究結果顯示,如果另一半快樂,自己有 8%的機率也會跟著快樂,而如果朋友快樂,自己則有9%的機會也會變快樂,至於想要在最短時間內獲得快樂,那找個快樂的鄰居威力最強,快樂上身的機率高達 34%。

既然快樂會傳染,那不開心的情緒當然也會影響到身邊的人,經濟不景氣,想要擺脫憂鬱,簡單的嘴角上揚,自己快樂還能造福他人,作一個健康的「快樂帶原者」。(新聞來源:東森新聞記者羅紜辰)

Wednesday, December 03, 2008

2008.11.29嘉義-布袋



生態走廊石碑正被這觀光魚筏看版綁的喘不過氣來。

(過於頻繁的經濟活動,壓縮了自然生態的空間。)


這對母女,正捕捉著被夕陽染紅的大海,而我的快門正記錄著這暖暖的幸福


暈開了醉人的昏黃 一如妳初妝
PS詩嘛~總是會加些擬人的用法...so寫者無意,而讀者也勿多心


紅色 在霞雲深處被隱去


紫色的初夜,映落在大海洶湧的胸口


天際的霞,微映在徐動的水痕上,卻留住了佇足

Tuesday, December 02, 2008

The mac80211 subsystem for kernel developers

mac80211 is the Linux stack for 802.11 hardware that implements only partial functionality in hard- or firmware. This document defines the interface between mac80211 and low-level hardware drivers.

http://linuxwireless.org/mac80211book/

The Linux Cross Reference

the Linux Cross Reference
http://lxr.linux.no/

Thursday, November 27, 2008

信主帶來新幸福

感謝主,把我們從黑暗權柄中分別出來
才能享受主這豐富並包羅萬有的生命水流
我們是主的恢復 主也是我們的恢復
感謝讚美主
是這樣何等的一位

然而在這達到榮耀的路上總是有許多打岔
就有如主囑咐召會先到海上;但海上常常有逆風和暴浪攪擾一樣。
主也告訴彼得不要做那小信的人,只需單純的信靠主的話,就連大海會敬拜在主的腳下
我讀過馬太福音的這一段時
我有一個想法: 我要讓自己做一個完全信靠主的人
然而這樣卻變的很痛苦,並常常活在絆跌中,
因為只犯了一個錯誤:想要憑自己的力量改變自己成大信的人
感謝主,恩賜給我這樣的看見
現在,我什麼都不做,我只禱告主呼求他的赦免與加多,
主啊~求你將我的信靠不斷的加多,主啊~你更是那末後的亞當賜生命的靈,
求你把屬天生命的水流將我全人浸透,並將我完全的浸入到基督的身體裡
主啊~請取去我的掙扎與抵抗,請在我裡面大大的建造,直到滿了基督滿了你的同在

因主的復活的大能與憐憫,所以生命的亮光一直伴隨在我的心裡
感謝主,恩賜給我這樣的看見
主的光是因我們的信靠而在我們生命裡放彩
當我們否認己,並把自己轉入到靈中,與神靈調和在一起時
那麼主在我們心中的光便如太陽,
如果我們不信靠主時...那麼我們的生命就像那飄忽的燭光,只要一絲微風便要熄滅

主是那世界的光,是那生命的糧
主啊~請賜我永遠的饑渴,接受你那全備的供應,好讓主能豐豐富富的住在我們裡面

====
so...
信主帶來新幸福

馬太福音生命讀經 第四十四篇

馬太福音生命讀經

第四十四篇 達到榮耀的路(三)

http://www.life-study1984.org/webdata/read/read.php?no=40-44

這一篇非常的豐富
非常的有享受
主啊~我們都要單純的來信靠你
我們也要接受你生命的醫治~