Internal latency, are they really worth Ph.D?

今日は，内部のレイテンシーまで考えが回らず，ハマる．
まだ頭がRTL記述に追いついていない感じがする．
故に，修行あるのみ．
[Today, I have many internal latancy issues.
Well, I couldn't consider some RTL concepts.
Thus, it means my TODO is only train and train for it.]

全く関係ないが，某所で知る．
[BTW, it's a kinda topics.]

博士が100人いるむら
[A village where are 100 Ph.Ds]

医者になった博士16人の内，
医者になりたくてなったのは何人なんだろう？
大学の先生になった博士14人の内，
大学の先生になりたくてなったのは何人なんだろう？
ポスドクに就いた博士20人の内，
ポスドクに就きたくて就いたのは何人なんだろう？
会社員になった博士8人の内，
会社員になりたくてなったのは何人なんだろう？
公務員になった博士11人の内，
公務員になりたくてなったのは何人なんだろう？
他の分野に進んだ博士7人の内，
他の分野に進みたくて進んだの何人なんだろう？
無職になってしまった博士16人の内，
無職になりたくてなったのは何人なんだろう？
逝ってしまった博士8人の内，
逝きたくて逝ったのは何人なんだろう？
[How many the Ph.D who wanted to become doctor
among who became doctor?
How many the Ph.D who wanted to become professor
among who became professor?
How many the Ph.D who wanted to become post-doctor
among who became post-doctor?
How many the Ph.D who wanted to become salaried employee
among who become salaried employee?
How many the Ph.D who wanted to go to other area
among who went to other area?
How many the Ph.D who wanted to be unemployed
among who were unemployed?
How many the Ph.D who wanted to be vanished
among who were vanished?]

そもそも，博士100人の内，
博士になりたくて博士になったのは何人なんだろう？
20年近く学び舎に通い続けて，
彼らは自ら何を得ようとしたのだろう？
[Well, I shold say before that stupid Qs like that...
How many the Ph.D who want to be Ph.D?
And then, what did they want to get in education.]

某大学某所で以前耳にした衝撃的な言葉を思い出す．
確か，就職活動か大学院進学か何かの面接対策が
どうのこうのとか言う話だったと思う．
「俺／私は巧く猫を被っていけるから，絶対大丈夫！」
[I've heard a crap phrases when I was a undergraduate.
These phrases ware out for interview's work-arounding or so on.
"All OK, because fully prepared my stuffs of lie!"]

そんな事を本気で考えているヤツがいるなんて素で驚いた．
「そろそろ自分に嘘を吐く事は止めた方が良い」
と言ってやりたかったが言えなかった．
こんな事を言うと，
「言っている事は理に適っている，だが疎まれる」
と言う面倒な状況に追い込まれる事は目に見えていたから．
[Well, it made only insane me if he/she was serious.
So, I'd say,
"Hey, why couldn't stop to lie yourself?"
But, I couldn't so because of
it would make sane for me spite of getting on the bad side.]

他の人の都合やら何やらも考えて，
こう言う歪みを小さくする事が出来る人も居るんだろう．
自分にはそこまで能力が無かったし，
そう言う事をしなければならないとも思わなかった．
その贖罪ではないけれど，他人に云々強いる事をする代わりに，
少なくともそう思っているからにはこの方針で自分はやる事にした．
求めるモノを十分に確保出来無かった某大学を見限って，
修行する為に某社に就職した理由の一つ．
[Maybe, there are some kinda buddha who can consider
such people's PITAs.
But I couldn't do so, I wouldn't do so.
Although, if it make my sin,
I'd like to stop lynig myself instead of to force things on others.
It's one of the reasons which I'm a trainee now.]

修行，修行．
そして，休みの日はヒキコモってGentooと戯れる．
そんな毎日． :P
[Train and train.
Then, at the holiday, I'll be HikiKomori with my Gentoo stuffs.
So, I'm in such day and night. :P]

AirCon.Duct--; TEL.Junction--;

週末に光が来る予定だったのに，失敗． :(
[Well, I have no connenction at my home, yet. :(]

事前に工事の下見に来た人が外からエアコンのダクトを見ただけで，
「コイツを使えば楽勝だ」
と思ったのか，実際には件のダクトは壁の中を入り込んで仕舞っていて，
内側に線が出せない事が発覚．
[The previewer just found air conditioner's duct on the outside.
My be he should think,
"Hrmm, it's easy to use the duct as fiber's loophole."
But the duct ran inside the wall and roof.
So, it cann't be available.]

次に，電話線の通っている管を使う事になったが，
この管が隣の部屋の人の電話線と共通になっている部分があって，
その分配点が不味い事に屋根裏のヨクワカラナイ所にある事が判明．
[Then, we would use the pipe which is used for TEL connection for it.
But, a part of the pipe is used common mine and next-door's.
And then, its junction hide with the roof or so on.]

ありがたい事に，
大家さんが設計を依頼した所に連絡すると言ってくれた．
うー，お家でportageをsyncさせてくれー． :(
[My landlord said to me that he will ask architect's office
for the detail.
Umm, I'd like sync my portage tree at my home. :(]

NomiKai, Hikari, groff sticks into bugzie!

何故か，月の最後の金曜日は社内で飲み会をやる事になっているらしい．
先月もやったのだけれど，書くの忘れてた．
で，ピザのおまけに付いて来たコーラを貰う，ラッキー． :)
[I don't know why it give NomiKai at last weekend of every month.
Of cource, it was last month too.
But I forgot to write it, though.
Then, I got a coke as free gift of pizza, yum! ;)]

今週末に光が来るので，これからはrsyncし放題． :9
[At this weekend, I'll get optical fiber.
So, it means weekend spree. :9]

loudear（敬称略）が本家のbugzillaに例のgroff-1.19.*なebuildを
投稿してくれたので，仕事中なのにIRCでsolarとSpanKYにチョッカイ
を出す不良社員振りを発揮．
詳細はbugzillaでどうぞ．
各員は週末を利用してテストする様に． :P
[loudear filed groff-1.19.*'s ebuild into the bugzie.
Despite I was at work, I poked solar and SpanKY.
It sound like scally?
The detail can be available at the bug report.
At this weekend, we should poke/test it. :P]

Endian variant issue

今日は在るVHDLモジュールのテストベンチの為に，
C言語でコード生成アプリを作ってた．
で，エンディアン処理みたいなモノにハマる．
[Today, I made tiny app for code generater for a VHDL module's
test bench by C lang.
When I poke that my stupid code, I had endian variant issue.]

どう言うモノかと言うと，
例えば，十六進数の0xABCDを"ABCD"と言う文字列で表したとする．
これを，人間が読みやすい様に，
char hex_str[] = "ABCD";
として，内部で最上位ニブルのAを取り出そうとすると，
hex_str[0];
と書かなければならないし，最下位ニブルを取り出そうとすると，
hex_str[3];
としなければならない．
逆に，hex_str[0]を最下位ニブルにして，
hex_str[3]を最上位ニブルにすると，
char hex_str[] = "DCBA";
として処理しなければならない．
[For instance, to represented 0xABCD as hexadecimal,
in the code has "ABCD" as string.
When it put into C lang world as keep human readability,
char hex_str = "ABCD";
It means that if you want to get upper nibble, it's required to code that
hex_str[0];
And then, if you want to get bottom nibble, it's required to code that
hex_str[3];
OTOH, if you want to get hex_str[0] as bottom nibble
and hex_str[3] as upper nibble,
you should code it like that
char hex_str[] = "DCBA";
So, it seems endian variant issue.]

結局，コード生成の為のアプリなので，内部で置換処理を行う事にした．
デバドラとか固定長の入出力なら#defineマクロで一発なんだろうけど，
可変長入力で，内部で文字列としてのビット列への変換ルーチンも必要．
ま，一度作って仕舞えば，共通部分は流用出来るしねー．
でも，{m,c,re}allocとかで動的確保したメモリ上でそんな事したもんだから，
いっぱいSIGSEGVを喰らいましましたとさ． :P
[Finally, due to it's for code generater app,
I've implement the code like dynamic byte swapping fucs.
The most known way for work-around endian issue in device driver world,
only put it into #define macros.
But, I need its funs as dynamic range and trans to binary strings.
So, I've these funcs are splited by common uses.
But, I poked the heaps which are allocated by {m,c,re}alloc fucs,
so I got ton of SIGSEGV, though. :P]

new(groff-1.19.*); YuuBinKyoku--;

IRC上でloudear（敬称略）からgroff-1.18.*が削除された事を知った．
ChangeLogを見るとsolar（敬称略）がセキュリティホールを理由に
削除してしまったらしい．
自分のOVERLAYにgcc-4.1でコンパイルエラーを直した時のブツが
残っていたので全然気が付かなかった．
以下，#gentoo-embeddedでのログ．
[On IRC, I heard form loudear that groff-1.18.* was removed.
I've skimed its ChangeLog, solar did to remove vulnabile packages.
Well, I couldn't see before I heard because of my OVERLAY has another
groff ebuild which was made for gcc-4.1.0 compilation issues.
I had poked solar with SpanKY on #gentoo-embedded.
The snipped logs are on below.]

5/24 11:35:58 hiyuh
    solar: why did you remove groff-1.18.*?
    it's requred app-i18n/man-pages-* stuffs which are non-english
    manual pages... but I know that ebuild is warned by GLSA.
    so, could you mind to re-put it into tree and p.mask?
5/24 11:38:31 SpanKY
    solar: yeah, you cant remove all 1.18.x versions
5/24 11:38:44 SpanKY
    you'll have to restore one
5/24 11:38:51 SpanKY
    cjk users cannot use 1.19.x
[SNIP]
5/24 11:43:01 hiyuh
    SpanKY++
5/24 11:45:20 SpanKY
    cjk users suck
5/24 11:45:23 SpanKY
    need to update their crap ;)
5/24 11:47:11 hiyuh
    yeah, it's horrible so old l10n stuffs, not i18n.
    but it's in app-i18n category or so on. :P
5/24 11:48:41 SpanKY
    you should be happy some people even know what i18n is let
    along l10n :p
5/24 11:49:01 SpanKY
    i bet majority of english/gentoo peeps you ask have any clue
    what l10n is :P
5/24 11:53:01 hiyuh
    hehe
[SNIP]
5/24 11:55:11 solar
    hrmm shit
5/24 11:55:24 solar
    SpanKY: I'm not sobr atm and would rathr not touch cvs.
5/24 11:55:34 solar
    mind fixing that?
5/24 11:56:03 solar
    a non vuln version.
5/24 11:56:48 solar
    if vuln is the only thing left then they are going to have to
    be SOL till a future release.
[SNIP]
5/24 12:01:16 hiyuh
    solar: I'm not sure detail of its vuln,
    but groff-1.19.* + japanese patch are in other distro repos,
    I know. so, groff-1.19.* has no vuln? if so, I'll try to put
    these patch into portage tree, though.
5/24 12:02:59 solar
    cool thats the best way to move fwd.
5/24 12:03:33 solar
    I'd help right now. But I don't think it would be wise
[SNIP]
5/24 12:13:43 SpanKY
    solar: the 1.18.1.1 in portage shouldnt be vuln
5/24 12:13:46 SpanKY
    it uses deb patchset
5/24 12:14:27 SpanKY
    hiyuh: should be set now
5/24 12:15:37 solar
    thanks

と，言う訳で，取り敢えず元には戻ったみたい．
で，momongaにgroff-1.19.*のパッチが在る事をloudearにポロっと言った所，
何とebuildを作ってくれた． :)
うん，週末に試すかー．
で，cjkな人に突っ込んで貰おうっと． :9
相変わらず，パッチがデカいなー． :(
[So, it seems SpanKY restore it.
I've said groff-1.19.* patches are in momonga repository to loudear,
then he made its ebuid, coo. :)
I'll try that in this weekend, then a great cjk dev will put it into officeal tree.
Hmm, though the patch is so huge like not patch. :(]

昼間に，実家から
「ブツを送ったから今日は早めに帰って家に居ろ」
と突然連絡が来る．
んな，阿呆な．此処人等早めに帰ってもする事は大して変わらんよ．．． :(
面倒だったが，取り敢えず七時に会社を出て，家に帰るとポストに不在届け．
読むと五時頃来たらしい．定時までに帰ろうと頑張ったのかなー？
あー，再配達の手続きとか面倒だなー． :(
[BTW, I got TEL from my mom, she said.
"I sent you something to eat. It'll arrived tonight. so, be in your apartment."
Well, when I was in my home or office, I should stick my PB, though. :(
Thus, it means to go home for that is only waste the time in the office.
But, I went to my home for that. Then I got a sheet for ordering redelver.
The post-officer came at about 5:00 PM.
Well, he want to leave the opffice on time?
Hmm, the ordering is only waste the time for me, too. :(]

A promenade

今日は，例のガイドのテキトーな翻訳をしつつ，O宮をブラブラ．
久し振りに，日の下を歩いた，気紛れだけど． :P
[I was enjoying to promenade around O-Miya for translating the guide.
Well, long time no see the sun, though it seems be just vagaries. :P]

下の写真は或る喫茶店でvim-7上でguide_ja.texをムニャっている所．
関係無いけど，注文したココアが甘過ぎた．
今度は違うモノを頼もうかな，機会が有れば．
[The pic on the below shows editing guide_ja.tex by vim-7.
BTW, hot cocoa is too sweet for me which I ordered.
Well, I'll order something except that, whenever the occasion may arise.]

Snipped rainbow

昼過ぎに滅茶苦茶雨が降っている音で目が覚めた．
面倒だったが兵糧が尽きていたので，
仕方無く降りが弱くなったのを見計らってスーパーに行った．
帰りには雨が止んでいた．
コーラを飲みつつ，雨に濡れた帰り道，遠くに虹の端っこが見えました．
[I awoke when the afternoon because of the rain is so noisy.
I had no stock of something to eat, so I went to buy it to a supermarket.
When I was going to my home from a supermarket, it has no raining anymore.
I drank the cola. On a street, snipped rainbow was.]

特に深い意味は無い． :P
[Nothing. :P]

Expectation collation, wmii-3 is out!

今日は，部品の発注確認をチョコチョコやりつつ，
或るモジュールとその期待値を生成するスティミュラスと
それを組み合わせて実行するテストベンチをコーディング．
へー，こう言うコーディングスタイルは面白いなー． :)
[Today, I ordered some parts and codeing a VHDL module,
its stimulus which generate some expectations
and their combining test bench.
Heh, that coding style make sane for me. :)]

で，ついにwmii-3が出た！ ;)
でも，ガイドの翻訳はやりかけのまま． :(
土日を使うかなー？
[Yay, wmii-3 is out! ;)
But my own translating the guide is not complete yet. :(
Hmm, should I do it this weekend?]

VB IDE sucks, cross compile madness

またVBで課題をやっている．
インテリセンス（？）が激しく邪魔．
課題に集中したいのに，
VBの癖を憶えなきゃならないってどう言う事だ．．． :(
[I'm duking VB again.
Well, sutpid "intelli-sence?" sucks me.
I'd play with that work, so VB is just crimp for me... :(]

何かやらされる度に，ギャーギャー喚いて文句を言うと，
「今は時期尚早」
とか．
でも，
「そのうち適当なSCMで，会社のヴァーチャルな資産を一元管理したい」
とか言っている．
で，ストリーム処理の為のコマンドラインのアプリを作ると，
GUIを作らなければならない．．．意味無ぇ．．．
[I'm grump my bosses when they and I should use insane env or apps.
My bosses said me like
"Well, we will/would use a SCM for management some resources."
But, OTOH,
"Your judgement is premature, we think."
So, any command line apps requires GUI front-end in that stupid policies.
That doesn't make sane.]

さっさとエラくなって，こんなんダメダメな事を思い知らせたる！
とか，強気で言ってみる． :P
[I'll get to poke that system for knocking sense into their heads!
Well, I might have gone too far. :P]

全然関係無いけど，ちょっとやり過ぎ． :)
[BTW, that seems more madness. :)]

FAX!

きょうは，はじめて"ふぁっくす"をおくりました． :P
[So, I did first FAXing today. :P]

最近やっていた部品整理が一段落したので，
足りないブツの見積書やら注文書やらを作って送ったのです．
弥生と言うソフトのデータベースを一ファイル化状態で保存していて，
Windowsサーバで皆が共有しているみたい．
でも，そのデータベースは設計の為のCADやらドキュメントやらとの
データベースとは連動していない（そもそも無い？）から，
結局，使うソフトが変わるとデータを人間が手入力，
或いは一から作り直さないとダメみたい．
[These are the result of ton of counting mixed devices as
estimate sheet or order sheet.
These sheet are made by Yayoi as a accounting software.
It has one file as unified DB on Windows server,
but other DBs are and each DB would not sync...
So, it means when using other software in same dev process,
many dull human inputs are required.]

マトモなデータベースをつくって，
ストリームでデータを処理して，
TeXで組版すれば良いのに． :P
[Boo, you shall create true unified DB,
and processing the data as stream,
put it out via TeX. :P]

It seems hard way...

最近，修行中の身でありながら，
先日の投稿の様にポロっと仕事のやり方をボロクソに言って仕舞う．
生意気なだヤツだと自分でも思うが，
上司の方達は建設的な意見だと思って聴いてくれているケド，
費用対効果と言う完璧に近い論理武装されてるし，
自分も話し合いに持って行く程に前準備している訳でもない．
[Well, I know I'm a newbie in that office.
But I couldn't stop a bit of blame like that posts.
Yes, I had too much talking back,
though my bosses listen my stupid saying as constructive advice.
But they protect their mind with cost-effectiveness.
And then, I'm not ready for completely saying...]

結局，
「趣味でやっているんじゃないんだよ，
会社の実務としての仕事でやってるんだよ？」とか，
「それはキミの理想でしょ？
言ってる事はマトモで耳が痛いんだけどね」とか，
「某のシステムはこうであるべきって言うけど，
先ずはキミは会社の仕事を先に憶えるべきでしょ？」とか言われて仕舞う．
[When all is said and done, my bosses said to me like...
"Well, we wouldn't do it as hobbies, it's working, OK?"
"OK, is it your ideal? though that makes sane."
"If you said the system should be like that,
but you shall get used to like that, huh?"]

あー，すっかり忘れていた．
「良く憶えておくんだ．皆はキミの様に出来無いんだよ」
って言われたのになー．
ま，何時の誰の話だか忘れたけど． :P
[Well, I completely forgot...
"Please remenber, they cann't do like you."
I cann't remenber that who/when said that, though. :P]

Poke the parts boxes, some communities

実装屋さんから戻って来た混ぜこぜの部品を更に社内で混ぜて
仕舞った部品箱から，受注した或るブツを作る為の部品と数の
確認作業をしているのだけれど，
バルクのチップ抵抗とかなんて誰も二度と数えたくないだろうから，
データベース化する気満々で部品のPDFとにらめっこ．
[I'm poking the parts boxes which contain some remained parts
return from factories comissioned to assembly or so on.
I've been ordered to make it split and check whether it has enough stocks
for compose some CPU/FPGA board, though.
Well, I think nobody like to count bulk chip regs.
So, I'd make some tiny DB for it.
Thus, I gazed the PDFs of these parts' specifications.]

何を考えていたかと言うと，
[What I was plannig is...]
　1. 個々の部品名とスペックをデータベース化．
　[1. Put each parts' specificantion into DB.]
　2. 部品の上位互換性を半順序関係と見なせば，
　　データベースに登録された部品は半順序集合の集合，
　　つまり半順序冪集合となる．
　[2. Let parts' upper compat is "partial order",
　 the parts that in the DB equals to a set of "partially ordered set".
　 Thus it's a "partially orderded powerset".]
　3. 設計ポリシーを定義する．
　　これは各々の半順序集合の最大元と最小元を定めるから，
　　結局，半順序冪集合は束集合と見なせる．
　[3. Define the policies of the designing.
　　 It's equals to restriction which makes "the gretest element"
　　 and "the least element" in each partially ordered set.
　　 Thus, it's a set of "lattice".
　4. 回路が要求するスペックと必要数をクエリ．
　　これで一つの束を指定出来る．
　[4. Input the quantities and required its spec by designed circuit
　　 as query for the DB.
　　 It can enable only specified lattice.
　5. 在庫の有無，使用出来る部品とその数が分かる．
　　詰まり，指定された元とそれより大なる元を辿れば，
　　最大元に行き着くまでに部品数が足りるか否かが分かる．
　[5. Finally, it can report the stoks are ready or not ready.
　　 Because of it can calcurate by following and summing
　　 with traceing the elements toward upper compat.]
と，相変わらず変態な事を考えた． :P
[So, it has a bit of complicate. :P]

が，上司の方達にそれに掛かる時間や一元管理データベースを
この程度の小ロットでやった場合のランニングコストなどを言われた挙げ句，
「ま，互換性を見るんなら勉強になるし，やってみれば？」
と消極的な許可を貰う．
うーむ，金銭やら信用の絡んでくる会社の仕事になるとそう言う制限が
有るよなー． :(
[Of cource, my bosses said to me what does it worth to use that time and
running cost of making unified DB for small lots.
Finally, "BTW, studying compat of parts is worth, do it?"
Hmm, it means not only OK sign but also not active enough to improvement.
Umm, money and time make me less and less free... :(]

一方で会社の現在の方針としては，
やっぱり設計だけで稼いで行きたいらしく，
理想的には外部に部品管理を投げて，社内の余計な余剰在庫ゼロに，
あわよくば余剰在庫ゼロでありたいと言う．
「そんな部品管理を小ロットで引き受けてくれる都合のイイ会社がある？」
みたいな事を言ったら，「未だそう言うモノは存在しない」と．
「自分の設計したブツの部品くらいだったら，
フツーはストリームな処理で管理出来るハズ．
それさえ出来無いヤツのボードなんかどうなんよ？」
と言うと，
「尤もな事だ．変な言い訳はしたくないが，
実際の設計プロジェクトのFIFOが溢れそうなんで今は未だ勘弁してくれ」と．
「"今は未だ"と言っている様ではそのままなの分かってますよね？」と．
ここで一問一答しても効率が悪いのはお互い分かっていた様で，
禅問答は取り敢えずこの辺りで保留に．
[OTOH,
the official bussiness policeis would direct to system design specialized,
non-creative works like poke parts boxes is not support anymore.
So, it means would throwing out these stupid dull routine-works.
To tell the truth, no too many redundancy devices stoks is good.
Of cource, no redundancy devices stoks is better.
"Any corp works management for small lots devices supporting is in real, huh?"
"Yeah, these are't, TTTT."
"IMHO, you do design that board. So, you have entire info of that.
what/why cann't it makes no stream process for devices parts management?"
"Indeed. But, our project FIFO goes to overflow status... please no flame war now."
"Now? If you said so, that woudn't mean now, I think it means future, though."
OK, We understand that like Zen-MonDou does not make us sane.]

何と言うか，上司の方達は精鋭（？）なんだろうけど如何せん少数過ぎて，
こう言う系統のシステムの改善の為には満足に人と時間が割り当てられない現状らしい．
やはりこの会社はGentooだらけにしなければならない様だな！ :P
[Sorta maybe kinda, my bosses has many excellence,
but cann't maintain corp system improvement themselves still now.
That means our corp should use Gentoo on all over the bottle-neck places. :P]

で，何がどう言う事になっていて，
どんな風にやるのがマナーなのかヨクワランので
まずはmixiのコミュニティ（？）を漁りつつ，
それっぽいモノにバカスカ参加してみる．
んで，行き当たりばったりにメッセージの返信やら送信をしてみる．
少し遊べそうな感じがしてこないでもないなー． :P
[BTW,
I have little tips or manner of SNS.
So, I did registration some communities,
replied and sent some messages.
Well, I'll poke it in virtual. :P]

mixi, linux-arm.org, PPC EPM with Gentoo

cpw将軍にmixiに招待された． :P
以前から「mixiはやらないの？」とIRCで訊かれていたし，
中の人達の記述にも興味があったけれど，
「自分の意見をオープンにしないのはなー」とか思っていたり，
「お前はモヒカン族だろー！」とかヨクワカラン事を言う輩が居たりと，
色々思う所があった．
ま，リアルでの環境も変わったし，イイ機会なのかな？
取り敢えず，日記はこっちで続ける事にしようっと．
[General cpw has invite me into mixi. :P
Well, I was asked like "are you in mixi?", though.
Of cource, I was interesting to check what man wrote in the mixi.
But, I had bit of lump...
IMHO, "Well, why did you make your opinion un-open?"
Someone who shall be MuRaBito I think said to me "You shall be MoHiKan-Zoku!"
Now, I'm thinking about the time to change my env both real and virtual.
Meanwhile, I'll plan this blog continues here, anyway.]

で，IRCでSpanKY（敬称略）がチェックしていたサイトを拾った． :P
[SpanKY seems check this site, I stole. :P]
http://www.linux-arm.org


んで，PPCなEPM，Gentoo付きで如何？ ;)
[Then,
PPC EPM will come with Gentoo, huh? ;)]

No Qt for me, UART, linux-headers-2.6.16

結局，回路図はWindows上でムニャって誤魔化した．
だって，Qtのコンパイルしたくないもんなー． :P
Bschを使って書いている時に，上司の方に
「何使ってんの？」と言われる．
うーむ，何気に行動が監視されているなー．
[Well, I've done faking it to drawing the scheme on Windows.
Ah, because of I do not want to compile Qt, though. :P
When I was poking the mice to draw it,
my boss asked me "What's the tool are you using?"
Umm, I've been obbo-ed on the quiet?]

次の課題はUART．
実用向きなブツなので面白くなって来たぞ．
で，ペラリとめくった上司の方に貰った課題の走り書きの裏には
「MAC部開発　G-Ether部　HDL設計　木村」
え，マジで？ ;P
[Then, next step is UART.
That step is getting into practical decives, so that it's exciting space for me.
BTW,
on the back side of the paper which my boss gave me as UART diagram
"Development of MAC part, G-Ether part, HDL codeing, KIMURA"
Well, isn't it sane plan? ;P]

#gentoo-ppcにてCpuID（敬称略）がお薦めなので，
sys-kernel/linux-headers-2.6.16にemerge --oneshotする．
が，自前のmedia-libs/libgii-1.0.1とdev-libs/DirectFB-20060507で
-Werror-implicit-function-declarationにハマる．
今週中にムニャる事にしよう．
[On #gentoo-ppc, I've heard that status from CpuID.
So, I've emerged sys-kernel/linux-headers-2.6.16 with --oneshot.
But, my ebuilds like media-libs/libgii-1.0.1 and dev-libs/DirectFB-20060507
get choking by -Werror-implicit-function-declaration, though.
I'll squash the bugs in this week.]

32bit Adder/Subtractor and misc stuffs

GW中にヒキコモリつつムニャヘニャした結果，32bit加減算器とかが出来た．
その内，乗算器と除算器も作ろう．
まだまだALUとは呼べなんだ． :)
[I had been as a HikiKomori during nice GW,
then I've coded 32bit adder/subtracter in VHDL.
I'll code some ALU components like multiplier/divider or so on. :)]

機は熟した，多分． :P
[It's the time to translate, maybe. :P]

で，例のCPU+RAM/ROMの課題を回路図っぽくせよとの事なので，
久しぶりにBSchを使おうかと水魚堂さんを見る．
あー，相変わらず，Qtで頑張ってますねー．
でも，これだけの為に~ARCHなPowerBookでx11-libs/qt-4.1.1は．．． :(
MacBookProとかに乗り換えたら，TKGateとか諸共ebuildにしなきゃなー． :P
[Today's my subject is to draw the sheme of the CPU+ROM/RAM
which was one of my current subject.
So, I'll try to use BSch which is made in SuiGyoDo.
Heh, he fight with Qt, though.
Hmm... Meanwhile, I'm not installing any version's Qt on my PowerBook.
If I used it, it means to compile x11-libs/qt-4.1.1 on ~ARCH userland... :(
Well, I'll keep on eyes it and TKGate 2.0 or so on... until making ebuild on new PC. :P]

で，DirectFB-0.9.25が出た．
勿論，portageにぶち込まれる．
SpanKY，カッケー．．．;)
[OK, DirectFB-0.9.25 is out.
Of cource, it's already in the portage.
Cool, SpanKY. ;)]

ROM/RAM, LEON2

今日は例の8bit CPUにROMとRAMをインプリメント．
設計段階でチップイネーブル(CE)を忘れたと捨て台詞を残して行かれた
上司の方が一足先にお休みに入って仕舞ったので，
取り敢えず，アドレスバスから1bit拝借して再実装． :P
[Today, I implemented ROM/RAM to the stupid 8bit CPU.
My boss said to me "Well, I forgot to designing it has CE, though."
And then, my boss is already enjoying his vacation.
So, I've re-used a bit which is MSB of address bus as its CE. :P]

で，Gaisler Researchさんから
LEON2のVHDLを拝借してモニョろうかと思ったら，
オリジナルでバンドルされているMakefileがGHDLに対応しているよ． :o
さくっとテストベンチまで走る．
相当ヤヴァいな，この会社． ;P
[And then,
I got LEON2 VHDL source from Gaisler Research
for poke it with GHDL.
Fortunately, its Makefile already has GHDL target.
And then it can run its test-bench without any editing. :o
Well, it should be awesome, IMHO. ;P]

Translate the guide, GW, some videos

wmii-3リリースに向けてMLの流量が増えている模様．
ビギナーズガイドがTeXで書かれていて変態過ぎるので，
勢いで翻訳し始めた途端，garbeam（敬称略）が大幅に更新を．．． :S
むぅ，いつの間にか5/1にリリースが延びてるし，
もう少し放置しておくか．
[The ML seems have some flood for wmii-3 release.
Its beginner's guide is written in TeX, so I can translate it.
But, I was translating it, though garbeam do big changes... :S
Umm, this release seems be postponed at 5/1.
I'll be patient.]

それはそうと，もうゴールデンウィークなんですなー．
「来週は二日しかないよー」と上司に言われて，
「あれ，何かあるんすか？」と言って仕舞った．
世捨て人まっしぐらだな！ :P
[GW will comes, I forgot it, though.
My boss said "Next week has only two days",
I've asked "Why?", though.
Well, seems to be on a career hermit! :P]

で，良いブツを見つけた．
だが，流石にリアルタイムでは聞き取れないな．．．
[Yum, nice stuffs are.
But, I cann't understand thier english as real-time, though.]