Poking Geode, no virtual/yacc ATM

例のEmbedded uClibc GentooなGeodeは一応bootした．
シリアルコンソールとかFrame BufferとかdropbearなSSHとか，
まだ/etc以下の調整が必要也．
man, info, doc抜きで，展開したkernelのソース，ebuildのツリー，
Portageのキャッシュをお掃除して，self update/debugが最低限可能な様に
toolchainとGentooなバイナリを残した状態で大体，300MB弱になった．
runtime環境で必要十分な状態．．．
詰まり，ヘッダファイルや普段使わないライブラリやら
バイナリやらを整理すれば，100MB以下にする事も出来るケド，
わざわざbinpkgを作るのは性に合わないので，
ベースにするrootfsで無理なダイエットはしないつもり． :)
[The Geode one tentative boots w/ embedded uClibc Gentoo.
But, it needs more pokings for serial console, frame buffer, dropbear SSH or so
which are configured by /etc files.
No man/info/doc stuffs,
cleaning extracted kernel sources/ebuild tree/Portage cache,
to make it keep to update/debug itself, leaving tool chain and gentoo's utils.
Now, its size is about 300MB or so.
Of cource, really iif runtime env which is not madantory ton of headers,
unneeded libs, not normally bins.
And yes, it's not quiet difficult to reduce the size less than 100MB.
But to make binpkg myself is not my taste, duh.
So hardly diet for my base rootfs isn't sane, IMHO. :)]

で，sys-apps/pcmcia-csやらsys-apps/pcmciautilsを弄っていたら，
dev-utils/yaccとsys-devel/bisonでcollision-protectにハマる．
profileのsystemで入ってくるsys-devel/bisonを-yオプション付きで使えば，
YACC compatな動作をするので，dev-util/yaccを入れる必要は無いハズ．
今の所，virtual/yaccが無い所為でdev-util/yaccに直接DEPENDしてる． :(
#gentoo-dev-help@FreeNode.netで訊いてみると，
YACC compatなブツは四つ以上有るらしい．
後でbugzillaに貼っとくか，メモメモ． :P
[BTW, when poking sys-apps/pcmcia-cs and sys-apps/pcmciautils,
dev-util/yacc and sys-devel/bison have file collision for these bad dependencies.
These PCMCIA packages have dev-util/yacc as directly DEPEND atom,
but sys-devel/bison was emerged as one of system profle stuffs,
and then "bison -y" is YACC compat, though.
So, it's the fault of no virtual/yacc ATM.
According to #gentoo-dev-help guy,
4 or more YACC compat ones in official ebuild tree.
Hmm, this memo will remind me to need to file virtual/yacc RFC to bugzie. :P]

uClibc stage tarballs, ppc Mac mini

例の仕事で，NS Geode GX1 300MHzなBox PCの為に，
i586-*-linux-uclibc Embedded Gentooなルートファイルイメージを
作ってムニャヘニャしようとしたら，公式（？）に配布しているっぽい
tar玉が古過ぎる事に気付く．
[I've poked NS geode GX1 300MHz,
to create i586-*-linux-uclibc Embedded Gentoo rootfs.
But, umm, I realized official/experimental tarballs are
pretty old, though.]

0) stage3-x86-uclibc-2005.0.tar.bz2を展開して，
1) sys-apps/portageをアップデートして，
2) /etc/make.confと/var/run/bootstrap-progressをムニャヘニャして，
3) /usr/portage/scripts/bootstrap.sh && emerge -e systemを実行．
多分，古いtoolchainとかのゴミが残るので，お掃除しなきゃなー． :(
[0) Extract stage3-x86-uclibc-2005.0.tar.bz2,
1) Update sys-apps/portage,
2) Poking /etc/make.conf and /var/run/bootstrap-progress,
3) Do /usr/portage/scripts/bootstrap.sh && emerge -e system.
Hmm, some craps even are, need to purge it, though. :(]

で，念願のppc Mac miniを手に入れた．
メモリは512MBだけど，PowerPC G4 1.5GHzで
ATI Radeon 9200 64MBなブツが¥60k弱．
コイツはAthlon Thunderbird 1.2GHzでクタビれてきた奴の代わりにしようっと．
あ，でもdev-util/mercurialなレポジトリ用のサーバにもしたいなー． :)
[BTW, I got a ppc Mac mini.
512MB memory, PowerPC G4 1.5GHz, ATI Radeon 9200 64MB...
It was costed about ¥60k == $550.
Hmm, which is better choice use it as replacement of Athlon
Thunderbird 1.2GHz desktop or new dev-util/mercurial repo serv? :)]

FIX: silly typo on title (taralls -> tarballs)

x11-apps/slim, /me stabs bugzie

#gentoo-bugs@FreeNode.netにて．
[On #gentoo-bugs@FreeNode.net．]

8/18 16:19:00 *
    jakub smacks bugzilla
8/18 16:19:30 *
    DrEeevil hands jakub the BFH
8/18 16:19:49 jakub
    *wheeeeeee*
8/18 16:19:51 jeeves
    jakub needs to grow up

Bugzillaが反応がノロいとjakubがキレる，そして何故かjeevesが諌める．
で，jeevesは淡々とbugzillaの新しいポストを報告するボットだったりする． :P
[Sometimes jakub smacks/stabs bugzie, then jeeves try to make
him calm down.
Yay, jeeves is a really cool bot, though. :P]

8/18 16:23:02 jeeves
    [New Bug] http://bugs.gentoo.org/144281 nor, P2, All,
    tuna@lyua.org->bug-wranglers@gentoo.org, NEW, pending, pyFltk ebuild
8/18 16:50:01 jeeves
    [New Bug] http://bugs.gentoo.org/144283 cri, P2, x86,
    csad2635@uibk.ac.at->bug-wranglers@gentoo.org, NEW, pending,
    xpaint-2.7.0 fails to compile (libXaw95.a does not exist)
8/18 16:52:02 jeeves
    [New Bug] http://bugs.gentoo.org/144284 nor, P2, All,
    ethouris@gmail.com->bug-wranglers@gentoo.org, NEW, pending,
    dev-tcltk/itcl compilation failed
8/18 16:55:02 jeeves
    [New Bug] http://bugs.gentoo.org/144285 nor, P2, All,
    niknik79@bossmail.de->bug-wranglers@gentoo.org, NEW, pending,
    dev-tex/mpm-2.5.2398_beta14 broken
8/18 16:56:02 jeeves
    [New Bug] http://bugs.gentoo.org/144286 nor, P2, x86,
    w.pessenhofer@tugraz.at->bug-wranglers@gentoo.org, NEW, pending,
    qtiplot 0.8.6-2 (Version bump)
8/18 17:22:01 jeeves
    [New Bug] http://bugs.gentoo.org/144287 nor, P2, All,
    tuna@lyua.org->bug-wranglers@gentoo.org, NEW, pending, flconvert
    ebuild

あまりにも反応がノロくなると二重投稿が発生する！ :(
[Well, BugzieIsAwfulySlowYaBastardDontMakeSoDupeOhNOOOO!!]

8/18 17:23:02 jeeves
    [New Bug] http://bugs.gentoo.org/144288 nor, P2, AMD64,
    ivashin@ihep.ru->bug-wranglers@gentoo.org, NEW, pending, mit-krb5
    ebuild bug
8/18 17:24:03 jeeves
    [New Bug] http://bugs.gentoo.org/144289 nor, P2, AMD64,
    ivashin@ihep.ru->bug-wranglers@gentoo.org, NEW, pending, mit-krb5
    ebuild bug
8/18 17:29:15 jakub
    more!!!111!
8/18 17:38:26 Caster
    respond!!!!!
8/18 17:38:31 hiyuh
    ah, slow....
8/18 17:38:43 jakub
    s/slow/dead/
8/18 17:39:15 Caster
    hiyuh actually meant: ah, dead....
8/18 17:39:45 jakub
    Please stand by ...
8/18 17:39:50 jakub
    *finger*
8/18 17:40:00 hiyuh
    hopefully, rebirth...
8/18 17:40:21 Caster
    500
8/18 17:40:26 jakub
    Please stand by ...
8/18 17:40:44 Caster
    does webmaster@g.o get many mails? because it encourages to spam it :)
8/18 17:40:56 jakub
    hmmm... Zero byte response
8/18 17:41:07 jakub
    haven't seen that one for some time :P
8/18 17:41:14 hiyuh
    yeah
8/18 17:42:16 hiyuh
    ugh, 500...
8/18 17:44:26 *
    hiyuh preps ton of SPAMs.
8/18 17:45:13 Caster
    the page should tell you to mail infra@ though
8/18 17:46:12 jakub
    junk, junk, junk...
8/18 17:46:13 hiyuh
    it sounds like a misconfiguration :P

んー，固まるなー． :(
[Why does ya bastard so freeze?! :(]

8/18 20:34:35 hiyuh
    bleh, dead again!?
8/18 20:35:35 dragonheart
    damnit - I was going to put in a recruitment bug too
8/18 20:36:18 DrEeevil
    hehe
8/18 20:36:26 DrEeevil
    bugzie say "nooo!" ;-)
8/18 20:36:31 *
    hiyuh stabs.
8/18 20:36:56 *
    DrEeevil hands hiyuh the BFH
8/18 20:40:02 genstef
    it is even more frustrating to see that there is a patch in bugzilla
    to fix it but they are unable to apply it :(
8/18 20:40:24 jakub
    :S
8/18 20:40:56 DrEeevil
    tehehe
8/18 20:41:01 DrEeevil
    it's less than 20 lines

で，何でこんな事をしていたのかと言うと，
例のPentium-Mなノートにブートスプラッシュとログインマネージャを
インストールして，納品する時にはそれっぽく見せようかとムニャっていた為．
sys-apps/qingyを入れようと思ったのだけれど，dev-libs/DirectFBと
vesafb/vesafb-tng/i810fb/intelfbでハマる．
やっぱメインメモリ共有なチップはダメだな． :P
[That's why I stabed bugzie, I'd try to install bootsplash and login
maneger to the Pentium-M's one.
So, I poked sys-apps/qingy, but dev-libs/DirectFB and
vesafb/vesafb-tng/i810fb/intelfb make me choke.
So, a video chip which has no real own vram would be pretty bad. :P]

で，SLiMを発見，
勿論，いつもの如くcompilation waringsを鬼fixしたから． :P
[Then, I found SLiM.
So, it should fix compilation warnings completely w/ my code audit. :P]
Gentoo Bugzilla #107526

そしてupstreamを突っつく． :P
が，パッチを貼っ付けるべき所にコメントして仕舞ったー． :(
[Of cource, poking upstream is Gentooism. :P
Bah, I've mis-posted that my comment as patch, though. :(]
SLiM Patches #001358

8/18 21:23:17 hiyuh
    Bleh, BerliOS' interface sucks...
8/18 21:23:48 DrEeevil
    somebody donate me the hardware and pay my rent and I'll build
    a replacement
8/18 21:24:17 jakub
    hiyuh: s/interface// :P
8/18 21:24:38 hiyuh
    hehe

ま，結局笑って誤魔化すケドなー． :P
[Hopefully, no one blames me. :P]

Eng"r"ish, ~x86 on Pentium-M

#gentoo-ppc@FreeNode.netにて．
[On #gentoo-ppc@FreeNode.net]

8/16 20:22:17 zoidberg
    hey guys
8/16 20:22:30 zoidberg
    i'm wondering if someone can help me answer a few questions
8/16 20:22:31 zoidberg
    ?
8/16 20:22:34 zoidberg
    anyone out there?
8/16 20:24:54 zoidberg
    hey is there anyone out there who can help me out?
8/16 20:25:48 zoidberg
    anyone out there?
8/16 20:26:01 hiyuh
    zoidberg: please, don't ask to ask. just ask, then someone will
    answer.
8/16 20:26:17 zoidberg
    sorry
8/16 20:26:25 zoidberg
    well i have never used Gentoo before
8/16 20:26:40 zoidberg
    i have  a G3 lombard Powerbook 333mhz 64 mb ram
8/16 20:26:48 zoidberg
    i got Ubuntu badger to work on it
8/16 20:27:06 zoidberg
    i tried breezy but breezy doesnt support G3 powerpcs
8/16 20:27:26 zoidberg
    so i tried installing badger again and i get this white screen when
    its partitioning the disk
8/16 20:28:07 zoidberg
    anyways i dunno if anyone here can help me out with that particular
    problem...but i was wondering if you guys can tell me how efficient
    will Gentoo-ppc be on my machine
8/16 20:28:07 zoidberg
    ?
8/16 20:30:01 zoidberg
    can anyone help me out?
8/16 20:30:19 hiyuh
    zoidberg: Unfortunately, I haven't poked G3, sorry. :(
8/16 20:30:23 hiyuh
    but IIRC, G3 guys may be. be patient.
8/16 20:30:51 zoidberg
    what?
8/16 20:31:14 zoidberg
    hiyuh, i'm not sure i understand what you just said
8/16 20:32:08 hiyuh
    zoidberg: sorry, I'm jap. if you couldn't understand what I said,
    please just ignore. :P
8/16 20:32:19 zoidberg
    lol
8/16 20:34:04 *
    hiyuh speaks Eng"r"ish.
8/16 20:36:29 zoidberg
    lol

久しぶりに言っている事が訳分からんと笑われた． :P
['Key, my English definitely Eng"r"ish. :P]

で，Pentium-Mなノートを~x86なGentooにして，
例のプロジェクトの開発環境にした．
2006.0だとtoolchainのアップデートは二回．
そろそろ，新しいリリースが必要ですな． :)
[BTW, I've poked Pentium-M lappy as ~x86 Gentoo for the dev env.
2006.0 forces me to update the toolchain 2 times.
Hmm, it needs to new release. :)]

Embedded newbies are...

多分，夏休みだからかな？
[Maybe, it's fault of summer vacation?]

8/15 18:18:02 Sante
    Hi all
8/15 18:18:14 Sante
    i am working in a fakeroot environment trying to compile something
    video related (NMM)
8/15 18:18:20 Sante
    it says im missing a library called ltdl
8/15 18:18:25 Sante
     so i installed libtool-1.5.22
8/15 18:18:32 Sante
    i am using a powerpc architecture so when i run ./configure i use
    CC=ppc-gcc CXX=ppc-g++ --arch=ppc
8/15 18:18:38 Sante
    then run make and make install
8/15 18:18:42 Sante
    and it appears fine
8/15 18:18:48 Sante
    but when i run file library it says Intel 80386
8/15 18:18:48 Sante
    Sante anyone could help me as to what I am doing wrong ?
8/15 18:18:48 Sante
    Sante .............. anyone awake ?
8/15 18:18:55 Sante
    sorry wrong paste
8/15 18:19:16 Sante
    so any1 kno anything to help me out ??
8/15 18:22:36 mmp
    Sante: when the compilation starts, you see that make calls 'ppc-gcc',
    or just 'gcc?
8/15 18:23:00 Sante
    ppc-gcc
8/15 18:25:15 mmp
    hmm, and if you do file *.o in the build directory, the files are
    ppc or 386 ones?
8/15 18:25:34 *
    mmp wonders how could be ppc files linked into 386 executable
8/15 18:26:12 Sante
    hang on
8/15 18:28:01 Sante
    the build directory, u mean the directory in which the files are
    installed?
8/15 18:28:16 Sante
    ie usr/local/lib?
8/15 18:30:37 jooopy
    Hi, yesterday I had a problem and until today I didn't solve
    it. When trying to bootstrap stage1 uclibc I get the error right
    at the strat of the process: * Executing: emerge --oneshot -p -v
    virtual/os-headers sys-apps/texinfo sys-devel/binutils sys-devel/gcc
    virtual/libc virtual/baselayout sys-libs/zlib ------ These are the
    packages that I would merge, in order: ----- Calculating dependencies
    |!!! Cannot resolve a virtual p
8/15 18:32:16 mmp
    Sante: where you build the sources, where are the object files
8/15 18:32:36 mmp
    Sorry that I did not write it more clear...
8/15 18:35:32 Sante
    the object file is POWERPC
8/15 18:37:48 jooopy
    is the http://www.bulah.com/embedded-guide.html should work? Are
    ppl here have experience with it?
8/15 18:37:54 hiyuh
    Sante: to use more sane CHOST/CTARGET/CBUILD is worth to consider,
    though.
8/15 18:38:06 hiyuh
    Sante: and then,  -I$target_incdir -L$taregt_libdir could help. but
    some apps'/libs' configure script sucks x-compile.
8/15 18:38:24 jooopy
    I also have something I don't understand
8/15 18:38:41 *
    theBear doesn't understand many things
8/15 18:39:12 jooopy
    If I run on the host system : ROOT="/tmp/minime" USE="make-symlinks"
    emerge uclibc busybox baselayout-lite dropbear
8/15 18:39:36 jooopy
    This should make an image, or I need more steps?
8/15 18:40:09 hiyuh
    jooopy: nope, virtual/* will be provided by installed packages,
    IIRC. don't emerge explicitly these virutal stuffs.
8/15 18:40:14 Sante
    ok
8/15 18:40:50 Sante
    what do u mean by CHOST/CTARTGET/CBUILD
8/15 18:41:22 jooopy
    hiyuh:  How do I know what are the virtual stuffs?
8/15 18:41:38 theBear
    the category is virtual/
8/15 18:41:39 jooopy
    hiyuh: I just ran ./bootstrap
8/15 18:42:34 jooopy
    hiyuh: should I block libiconv in /etc/portage/packages.mask ?
8/15 18:43:12 hiyuh
    jooopy: the sources always with you. :P
8/15 18:43:43 Sante
    hiyuh: i dont understand the CHOST stuff, and what u wrote next
8/15 18:44:44 hiyuh
    jooopy: sound like you're trying to build from stage1?
8/15 18:45:26 jooopy
    hiyuh: yep, but I don't realy have to. I just follow
    http://www.bulah.com/embeddedgentoo.html
8/15 18:45:38 jooopy
    hiyuh: Should I start from stage 3?
8/15 18:46:17 jooopy
    hiyuh: can you refer me to a good howto ?
8/15 18:47:54 hiyuh
    jooopy: first of all, see the
    topic. http://arcanux.org/guidexml/cross-development.html
8/15 18:48:30 jooopy
    ok
8/15 18:49:25 hiyuh
    Sante: you should read env-ver section in this documents.
8/15 18:49:48 Sante
    ok
8/15 18:49:55 Sante
    ehmm which documents?
8/15 18:50:00 Sante
    http://arcanux.org/guidexml/cross-development.html ?
8/15 18:50:05 hiyuh
    yep
8/15 18:50:25 Sante
    im not using gentoo btw
8/15 18:50:30 Sante
    but ill have a look
8/15 18:53:20 hiyuh
    Sante: except some commands in this document, these info are common
    knowledge of x-development, IMHO.
8/15 18:54:49 Sante
    ok
8/15 18:55:09 Sante
    i still dont really get my problem, i mean it appears to be compiling
    correctly
8/15 18:55:26 Sante
    can i show u the ./config and make dumps ? maybe u can help me out
8/15 18:57:37 hiyuh
    Sante: of cource, you can show us. but I cann't bet you expext. :P
8/15 18:58:08 hiyuh
    s/expext/expect/
8/15 18:58:12 Sante
    hehe
8/15 18:59:05 Sante
    http://pastebin.ca/132432
8/15 18:59:08 Sante
    thats configure
8/15 18:59:39 Sante
    and make
8/15 18:59:40 Sante
    http://pastebin.ca/132433
8/15 19:04:15 Sante
    any idea ?
8/15 19:08:07 hiyuh
    Sante: hmm? it looks libtool installing is ok. then, you mean you
    couldn't link target libs?
8/15 19:15:35 Sante
    i mean
8/15 19:15:49 Sante
    when i try to compile my app it says ltdl not found
8/15 19:21:46 hiyuh
    hmm? so, ltdl is "libltdl.{a,so}" as your target lib?
8/15 19:29:31 hiyuh
    Sante: FYI, this is "locate ltdl" result of my ~ppc gentoo (but
    notice, only self compilation tools was installed).
8/15 19:30:02 hiyuh
    http://rafb.net/paste/results/OmlsA693.html
8/15 19:30:25 hiyuh
    So, if your apps need to link libltdl.{so,a}, you should do like that.
8/15 19:30:38 hiyuh
    1) compile it with "-I$inc_dir", $inc_dir is where target's ltdl.h is.
8/15 19:30:41 hiyuh
    2) link it with "-L$lib_dir -lltdl", $lib_dir is where libltdl.{so,a}
    are.
8/15 19:31:24 hiyuh
    maybe, you should check step 2), IMHO.
8/15 19:48:44 Sante
    wait
8/15 19:48:56 Sante
    at what step do I link with -L$lib_dir -lltdl"
8/15 19:48:57 Sante
    ?
8/15 19:49:23 Sante
    and i dont have libltdl.so
8/15 19:49:49 Sante
    only .a
8/15 19:50:00 Sante
    when i compile with standard gcc i get the .so aswell
8/15 19:50:07 Sante
    hiyuh: is that normal ?
8/15 20:33:35 hiyuh
    Sante: *.a is an "ar archive" for static link. *.so is "shared object"
    for dynamic link... if you specfied to build only "ar archive"
    or your x-compiler can only build static ones, it is normal.
8/15 20:34:27 Sante
    ah ok
8/15 20:34:37 Sante
    then my compiler can only do static ones
8/15 20:35:05 Sante
    but why does my app complain that ltdl is not installed then ?
8/15 20:40:22 hiyuh
    Sante: nope, it may be not your apps' fault. to link is to working
    of linker as a part of toolchain...
8/15 20:40:35 Sante
    hmm ok
8/15 20:40:37 hiyuh
    in static link case, libltdl.a should be linked when it was build,
    and it's in $lib_dir was specfied -L option. and then you need
    -static as well.
8/15 20:40:50 Sante
    hang on
8/15 20:40:52 Sante
    where do i do this ?
8/15 20:42:47 hiyuh
    sane fixing is poking *.{in,am,ac} or so. otherwise, poking Makefile
    or manually link it where it failed, IMHO.
8/15 20:43:27 Mimil
    hi all
8/15 20:44:07 Sante
    ok
8/15 20:44:08 Sante
    safe
8/15 20:44:28 Sante
    10x
8/15 20:44:58 hiyuh
    np

教訓: マニュアルとドキュメントを読みましょう． :P
[L: Do read the fine manuals/documents. :P]

CQpub.karma == DesignWave.price?

#ep93xx@FreeNode.netにて，CQ出版社についてムニャる． :P
[Talking about CQ pub w/ the folks on #ep93xx@FreeNode.net. :P]

8/14 18:29:55 jcath
    .
8/14 18:36:37 lennert
    ..
8/14 18:36:52 koen
    ...
8/14 18:37:54 lennert
    ....
8/14 18:40:43 hiyuh
    .....
8/14 18:40:58 jcath
    :D
8/14 18:41:10 hiyuh
    ;p
8/14 18:46:49 jcath
    hiyuh, do you know "CQ publishing house
8/14 18:46:53 jcath
    in Japan
8/14 18:47:34 jcath
    it publishs some very good books and magazines
8/14 18:49:43 hiyuh
    jcath: yeah, it's famous and practical.
8/14 18:52:15 hiyuh
    well, silly japanese only... http://www.cqpub.co.jp/
8/14 18:52:17 jcath
    but all in japanese :(
8/14 18:54:42 jcath
    I ream some article before
8/14 18:54:45 jcath
    really good
8/14 18:55:17 jcath
    but I dont know japanese, so, just guess with the waveform and
    schematic figure
8/14 18:55:55 lennert
    hehe
8/14 18:56:08 lennert
    by that definition, i can read chinese too :)
8/14 18:56:54 hiyuh
    well, but, please don't blame me. :P
8/14 18:57:38 jcath
    :) just think of that and tell u, hiyuh
8/14 18:57:56 hiyuh
    hehe
8/14 18:58:55 lennert
    noone blames you :)
8/14 19:00:16 jcath
    is the magazine"design wave" expensive ?
8/14 19:03:55 hiyuh
    bit of expensive WRT its thickness. but sometime it comes with nice
    supplement like sample board (a tiny CPU and FPGA or so).

うーん，その手の雑誌は海の向こうには無いのかな？
[Well, any pub like CQ doesn't be at overseas?]

KandR[2].Appendix.interest++;

C++が気に入らなくて，現実逃避でK&R 第二版を読み直してたら，
何気に付録が面白い事に気付く．
で，bison/flex (yacc/lex)が使いたくなってきた．
無謀にも少しモニョってみる．．．つもり． :P
[C++ seems stab me.
So, I did cop-out w/ rereading K&R SE.
Then, I realized its appendix is bit of interesting.
It makes me proceed bison/flex (yacc/lex) way.
Well, a kamikaze plan is... but it's just for fun. :P]

memo of autoconf-2.60 bugs.

autoconf-2.60関連のメモ．

• */*-svnなパッケージとかでautogen.shを使っているブツ．
  inherit autotoolsでeautoreconfを使って，autogen.shは使わない．
  


• ${S}/m4な感じでm4マクロが分かれているブツ．
  inherit autoconfでAT_M4DIR=${S}/m4 eautoreconf．

[A memo of autoconf-2.60 stupidness...

• kinda */*-svn packages or so which uses autogen.sh.
  inherit autotools and use eautoreconf, instead of autogen.sh.
  


• has ${S}/m4 as modulized m4 macros.
  inherit autoconf and use AT_M4DIR=${S}/m4 eautoreconf.

]

と言う訳で，cjkなエラい人様々，
このブツがautoconf-2.60で"プチ"壊れていますのでヨロシク． :)
[@cjk devs, please fix this silly autoconf-2.60 bugs. :)]
Bug #143053

autoconf_2_60.karma--; or so

BCBでムニャヘニャしている隣で，
Gentoo on PowerBookのemerge -e worldを走らせていた．
で，sys-devel/autoconf-2.60が幾つかのebuildでハマる原因に
なっているっぽい事に気付く．
[Still poking BCB ones.
Beside that, my PB heats to emerge -e world.
Then, seems sys-devel/autoconf-2.60 makes some
b0rked it.]

(Snippet log of #gentoo-bugs@FreeNode.net)
8/03 11:54:37 hiyuh
    grr, autoconf_2_60.karma--;
8/03 12:07:09 dragonheart
    hiyuh: thanks for the reminder (-commits)
8/03 12:07:19 dragonheart
    hiyuh: how has it broken your life?
8/03 12:44:41 hiyuh
    dragonheart: I guess sort of that. but half of
    my breakages is in my own ebuilds (unofficial ones).
8/03 12:44:50 hiyuh
    I'll try to figure each casus out,
    then poke upstream or bugzie.

と言う事で，もう少し弄ってみる事にする． :)
[K, need a bit of to poke it. :)]

で，例のモノはまだ色々dead lockするパターンが．．．

(Snippet log of #ep93xx@FreeNode.net)
8/03 17:20:30 *
    hiyuh got some dead lockings in his stupid threads
    progs.
8/03 17:44:00 *
    lennert replaces all of hiyuh's locks by nops and
    solves the problem :)
8/03 17:45:47 koen
    mov r0,r0?
8/03 17:47:44 hiyuh
    hehe
8/03 17:50:11 lennert
    koen: that's the one

こっちも頑張らねば． :(
[Hmm, all I can do is only to code it, though. :(]

hg2svn.tailor, BCB.PITA++;

dev-util/tailor．．．使い方がヨクワカラン． :P
subversionのレポジトリ構成を理解していない所為だなー．
多分，どこか間違ってるハズ．
[dev-util/tailor... it makes me messy. :P
Well, that must depend on my ignorance about
subversion repository structure and scheme or so.
Some bad things are...]

[DEFAULT]
verbose = True

[project]
target = svn:default-target
start-revision = INITIAL
root-directory = /tmp/commit_dir
state-file = hg2svn.tailor.state
source = hg:default-source
subdir = svn_co
patch-name-format = 

[hg:default-source]
module = /
repository = /usr/local/portage

[svn:default-target]
module = /trunk
repository = file:///tmp/commit_dir/svn_repos

例のBCBなプログラム，なめてかかっていたら色々面倒な事やっているっぽい．
「制限時間付き待ち行列の各要素に対する運用上問題の無いハッシュ関数」？
グローバル変数のカウンタを回しつつ，似非mutexでロック．
現場でハッシュの値域が足りなければ，
カウンタの上限を上げてcut and tryって，美しくねぇー． :P
[The stupid BCP progs, that makes me really cofuse.
"An operational well-evaluated hash function
for event queuing which has a time limimt"？
Its implementation is,
* Count up crappy global var with a defined maximum value.
* Lock it with dirty mutexing to prevant accessing conflicts.
* If the rage hash value was too narrow, redefine its maxmum value.
For define that maximum value, to cut and try is the way to evaluation.
Bleh, it makes me.code.karma--; :P]

あと，双方向リストのpush/pull/findをdead-lockしない様にに実装せねば．．．
やべー，納期がー，あー，納期がー． :P
[And then, it required no dead-locking push/pull/find
functionalities for bi-directional list...
Oh, well, there're some dead-locks, here's some dead-lines. :P]

tailor can be hg2svn?

hg2svnみたいなのが無いか，#mercurial@FreeNode.netで調査．
[Seeking the tool like "hg2svn" in #mercurial@FreeNode.net...]

7/31 20:28:04 hiyuh
    uhm, no clue to use mercurial repo in code.google.com?
7/31 20:35:52 Habbie
    not currently possible, as far as we know
7/31 20:36:05 xorAxAx
    Habbie: whats not possible?
7/31 20:36:24 Habbie
    hosting a mercurial repo on google code hosting
7/31 20:36:30 xorAxAx
    ah
7/31 20:36:54 Habbie
    http://code.google.com/p/branch/
7/31 20:38:03 xorAxAx
    only bzr support
7/31 20:38:31 xorAxAx
    ok, not really
7/31 20:38:33 Habbie
    that will change
7/31 20:38:38 xorAxAx
    http://branch.googlecode.com/svn/trunk/
7/31 20:38:39 Habbie
    but this is just a project, not google itself :)
7/31 20:38:44 xorAxAx
    ah
7/31 20:54:28 hiyuh
    hmm, thanks. :(
7/31 20:54:34 hiyuh
    then, how can I do like "local_hg_repo -> hg2svn -> google_svn_repo"? :)
7/31 21:10:48 Habbie
    i'm sure tailor could do that
7/31 21:11:40 hiyuh
    heh, I'll try that. thanks, Habbie.

で，dev-util/tailor発見．
~ppcでキーワードされていないケド，
「Pythonで書かれているっぽいし，動くだろ？」
と言う事でローカルなoverlayに~ppcにして持って来た．
動いたらキーワードリクエストを投げるとして，もうちょっと弄る．
暫し待たれよ． :P
[Uhm, dev-util/tailor has not been ~pp keyworded.
I though, "Well, it smells python-flavor, maybe it'll work."
If it works, I'll file it a keyword request, though.
Put it into my overlay with ~ppc sin.
Well, it's not commited yet. :P]

と言うか，もしかしてdev-utils/darcsってHaskellで書かれてる気配？
[BTW, dev-util/darcs is written in "the" Haskell?]

My own Portage Overlay is?

コレ，勢いで作った． :P
その内，丸ごとcommitする．
が，なんでmercurialじゃないんだー． :(
[Now, it seems ready. :P
ATM, this repo was no commited, but I'll do.
BTW, why not mercurial... :(]

mutex-flavor FIFO, NomiKai

例のBorland C++ Builderなブツ．
子プロセス生成方法をCreateProcess()とfork(2)しか知らないので，
VCL+GDIなブツと統一感を持った状態を維持しつつ，
適当な複数のスレッドを一つの子プロセスに閉じ込められない事に気付いた．
方法を調べるのが面倒だし，なんか気に食わないので，
自前のmutexを仕込んだFIFOとSleep()で誤摩化しておいた． :P
[Smacked the Borland C++ Builder stuff.
I've only coded for creating child proc by CreateProcess()
or fork(2).
It means this low level system calls make VCL+GDI stuff
crap, IMHO.
So, I realized there is no clue to encapsulate sane threads
into one child proc, if no new stuff learning.
Then, I coded it w/ my stupid mutex-flavor FIFO to fake it. :P]

今日は早めに仕事を終わり，月末定例飲み会．
何故か手始めにボーリングを1ゲームだけやってから，
社長の隣でコーラをガブ飲みしていたら色々絡まれる．
「新人は遅刻しちゃダメ，早く来て会社で寝てろ」とか．
おいおい，それはイイのかー？ :P
「MLとかbugzieを見てウケてると，
何時の間にか朝になっているんです」とか
ムニャムニャ言い訳をしておいた． ;)
[Today was NomiKai.
Played bowling, stuffed Cola where next seat of my boss.
Then, he said,
"You should have no morning tardiness, OK?
To snooze when the office time is better."
Well, is really better? :P
So, I outed like,
"Nah, ML and bugzie make me LOL,
and it makes shorter my sleeping time, thogh." ;)]

BCB.karma--; mercurial.pv.minor++;

Borland C++ BuilderのAnsiStringが変態過ぎる．
何時もながらインテリセンス（？）が激しくウザい．
VCL+GDIでコードがイイ感じにスパゲティになる．
まー，しゃーねーなー． :P
[Borland C++ Builder has weird one, AnsiString.
Intelli-Sense(?) sucks.
VCL+GDI makes my code Spaghetti.
Ah, there're no clue. :P]

で，mercurialが0.9.1になりました． :)
[Yay, mercurial bumps to 0.9.1. :)]

no more zombie, tracing NPTL?

今日は，dumbtcpdが複数のホストからのtelnet DoS攻撃で
zombie大量発生な感じにならない様にした． :P
7/21からのdiffstatはこんな感じ．
無駄にドキュメンテーションしている所為で遅い． :(
[Today, I've coded to make dumbtcpd has no zombie
procs by using telnet DoS attacking from sevral clients
at same time. :P
Here's its diffstat 7/21~.
Well, my stupid documentation makes slow progress. :(]

 README                          |    8 -
 b/Makefile                      |   76 +++++++++++++++++
 b/doc/Makefile                  |   48 +++++++++++
 b/doc/api_dec/accept_dec.c      |    4 
 b/doc/api_dec/bind_dec.c        |    4 
 b/doc/api_dec/connect_dec.c     |    4 
 b/doc/api_dec/getaddrinfo_dec.c |   22 +++++
 b/doc/api_dec/listen_dec.c      |    4 
 b/doc/api_dec/socket_dec.c      |    4 
 b/doc/restudy_socket_progs.tex  |  173 ++++++++++++++++++++++++++++++++++++++++
 b/include/dumbtcpd_common.h     |   30 ++++++
 b/include/dumbtcpd_main.h       |   12 ++
 b/include/dumbtcpd_service.h    |    9 ++
 b/include/dumbtcpd_signal.h     |    9 ++
 b/include/dumbtcpd_socket.h     |   12 ++
 b/src/dumbtcpd_common.c         |   93 +++++++++++++++++++++
 b/src/dumbtcpd_main.c           |   56 ++++++++++++
 b/src/dumbtcpd_service.c        |   20 ++++
 b/src/dumbtcpd_signal.c         |   94 +++++++++++++++++++++
 b/src/dumbtcpd_socket.c         |  131 ++++++++++++++++++++++++++++++
 20 files changed, 809 insertions(+), 4 deletions(-)

一応，マルチプロセスな並行サーバなのだけれど，
無意味にマルチスレッドにしようかとNPTLなサンプルプログラムを漁るが，
流石になかなか見付からんなー． :(
と思ったら思わぬ収穫．
[ATM, that app is a multi-processing concurrent server,
of cource.
I'd like to make it multi-thread, so I want some simple
NPTL sample code snippets.
Umm, there are no good sample for me.
BTW, I found it, though.]

NPTL Trace Tool Project

おー，サンプルがすげー． :)
[Heh, this sample is quite curious for me. :)]

ton of warnings, was mentioned by splint

うー，splint先生が厳し過ぎます．
CFLAGS="-O3 -Wall -Werror"で警告無しでもバカスカ怒られる． :(
日々，是精進也． :P
[Umm, splint so buzzes my stupid code.
That code has no warnings w/ CFLAGS="-O3 -Wall -Werror", though.
All I can do is to do code, anyway. :P]

socket progs, WRT 10kLOC, poking pciutils

例の仕事の為に，madwifi-ngに関してサルベージしつつ，
socketプログラミングを復習中．
select(2)を使うとIPv4/IPv6両対応に出来るらしいが，
man 2 selectが理解不能也．
今回はスループットを測定するのが目的なので，
実際には全然関係無かったりする． :P
[I'm skiming about madwifi-ng and restudying socket progs.
By using select(2), it can support both IPv4/IPv6, I heard.
But "man 2 select" is so messy for me.
Well, this project's propose is measurement some throughput.
So, it's completely unrelated thigs, though. :P]

wmii MLの10kloc projectに関するスレッドが熱い．
まさかUriel（敬称略）の投稿でウケるとは夢想だにしなかったー． :D
[WRT 10kloc project thread in wmii ML got a bit of heat.
Hehe, it's really unexpected that a Uriel's post make me LOL. :D]

で，bug #141111．
どうすっかなー？ :/
[BTW, bug #141111.
Uhm, it's subtle... :/]

Forgot yesterday is UmiNoHi, dwm

あー，海の日を忘れて，会社に逝って仕舞いました． :P
[Well, I went to the office yesterday, that's why I forgot UmiNoHi. :P]

まだ会社のカードキーを貰っていないので，中にも入れず，
三十分程「何かあったっけ？」と考えながら突っ立っていた．
で，宅急便の人が来て，月曜日着の荷物を届けに来たと言うので，
取り敢えず，ソイツを出社した証拠代わりに預かって，帰宅．
[So, I have no card-key for the office, that meant all I could do
is to stand around doing nothing and to have several Qs of what's
it going on.
Elapsed 30mins or so, delivery service man cames.
He said like that "this is due NLT today, though."
So, I received that packages as a evidence of I had been.
Then, returned home.]

今朝，出社してから昨日は海の日だったと気付く．
で，預かった荷物を総務の人に渡して
「昨日，間違えて出社したので，ついでに預かっておきました．」
と言った所，何故か大笑いされた． :P
[Today's moring, I saw tha calendar in the office.
Of cource, I realized yesterday is UmiNoHi.
Then, I brought that package to Coordination Division,
"Well, I've kept this package, because I came to here yesterday,
that's why I forgot UmiNoHi."
So, they were LOL. :P]

で，dwm．
あー，やっぱり逝くトコまで逝ったかー． :D
[BTW, dwm is.
Aww, kinda like. :D]

編集：
おー，10kloc.orgになっとる． :D
[Heh, he got 10kloc.org as its domain. :D]

133MHz, new project will be...

出来たー．133MHzで動いたー． :)
よくやった，自分． :P
[Wheee, it works with 133MHz synchronous clock. :)
echo "Good job" > /me. :P ]

で，新しいプロジェクトが始まりそうな予感．
Linuxなwireless中継マシンのプログラミングらしい．
あー，GNAP？ :P
上司の方によると，きちんとそれに関してやるべき事が決まるまでは，
今までと同じ様なVHDLマクロでヒーヒー言わせると言う腹らしい．
流石に実務はスパルタで一味違うなー．
[Then, new project will be, programing for wireless Linux boxes.
Well, sound like GNAP？ :P
My bosses would like to make me feel stuck with messy VHDL macros,
untill this project runs.
Hehe, it's definitely Spartan edu, unlike other ones!]

取り敢えず，一区切りついたので，土日はbugzieでも突っつくか，
ebuildをムニャるか，秘密のVHDLなレポジトリでモニョるかなー？ :)
[Hmm, in this week end, I'd like to poke/stub the bugzie,
or play some ebuilds, otherwise crazy commit my secret VHDL repos? :)]

Ugh, misunderstood the specs, silly me...

何だか例のマクロの内部レイテンシがちょっとだけ合わないので，
ボスに仕様を確認したら，どうも色々間違って解釈していたみたい．．． :(
結局，半日も方眼紙でタイムチャートのお絵描きをして内部カウントの
スキームとかを再考していた．
納期がやばいので，さっさと直さねば．．． :(
前の投稿で終わりそうと言っておきながら，ホントに終わるのか？ :P
[Uhm, I realized my misunderstanding that macro's specs.
That's why I was getting a bit of screwing up some mismatchings
about internal latencies, was mentioned my VHDL gurus... :(
Finally, I've poke its timing chart half of today for re-construct
internal count scheme or so on, though.
Ugh, the deadline will come... So, I should fix it as soon as possible... :(
Hmm, cann't it be released? :P]

131MHz, TDS, BK in VHDL #2

そろそろ例のマクロのコーディングに区切りが着くっぽい．
ムニャヘニャした結果，131MHzくらいで動きそうな感じ． :)
そんな今日のdiffstatはー．
[So, that macdo coding will finish.
I've poked it and tested, then it may work with 131MHz clock as maximum. :)
Here's today's diffstat!]

 b/compile/DPNC_TOP.vhd |  204 +++++++++++++++++++++++++
 vhdl/DPNC.vhd          |   14 +
 vhdl/IXSW_MOD.vhd      |    6 
 vhdl/RCTRL_MOD.vhd     |  391 +++++++++++++++++++++++++++----------------------
 vhdl/WCTRL_MOD.vhd     |  231 ++++++++++++++++------------
 5 files changed, 574 insertions(+), 272 deletions(-)

ちょっと物足りないのは内部レイテンシを仕様に合わせる為に，
代入タイミングを変えたり，
非同期なゲート処理をprocess文に埋め込んだりしたから．
[Well, yeah, it got under 1kSLOC.
That's why, today's work is not code stuff,
I've fixed by changing some signal substitute schem and/or
make async-flavor logics embed into process statements for internal latencies issue.]

更に今日悟った事は，
次のP_CASEとP_IFプロセスは全然違うブツだと言う事．
[Then, I realized these process, P_CASE and P_IF are completely different scheme.]

P_CASE : process (ixRST, iCLK)
begin
    if (ixRST = '0') then
        oDECODE <= (others => '0');
    elsif (iCLK'event and iCLK = '1') then
        case iMODE is
            when cMODE1 =>
                oDECODE <= cCODE1;
            when cMODE2 =>
                oDECODE <= cCODE2;
            :
            :
            when others =>
                oDECODE <= cCODE_INVALID;
        end case;
    end if;
end process;
:
:
P_IF : process (ixRST, iCLK)
begin
    if (ixRST = '0') then
        oDECODE <= (others => '0');
    elsif (iCLK'event and iCLK = '1') then
        if (iMODE = cMODE1) then
            oDECODE <= cCODE1;
        elsif (iMODE = cMODE2) then
            oDECODE <= cCODE2;
        :
        :
        else
            oDCODE <= cCODE_INVALID;
        end if;
    end if;
end process;

Bugzie is a bit of..., TDS

何だか最近の本家のbugzillaが遅い．
DBがロックするからとか何とか．
今日は"Please stand by..."とまで表示する始末．
なに，まじめに仕事しろって？ :P
[Uhm, bugzie is getting slow, though.
Cuz DB locking or so on, I heard.
Today, I've seen that bugzie displayed "Please stand by...".
Um? Should I work more harder? :P]

で，この前から今日までのdiffstat．
[These are my diffstat 7/4 ~ today.]

 a/stim/dat/16QAM_1of2        |   80 --------
 a/stim/dat/16QAM_3of4        |   80 --------
 a/stim/dat/64QAM_2of3        |   80 --------
 a/stim/dat/64QAM_3of4        |   80 --------
 a/stim/dat/BPSK_1of2         |   80 --------
 a/stim/dat/BPSK_3of4         |   80 --------
 a/stim/dat/QPSK_1of2         |   80 --------
 a/stim/dat/QPSK_3of4         |   80 --------
 b/bench/BENCH_DPNC.vhd       |  327 +++++++++++++++++++++++++++++++++
 b/stim/Makefile.ghdl         |  118 ++++++++++++
 b/stim/dat/16QAM_1of2.txt.in |   80 ++++++++
 b/stim/dat/16QAM_3of4.txt.in |   80 ++++++++
 b/stim/dat/64QAM_2of3.txt.in |   80 ++++++++
 b/stim/dat/64QAM_3of4.txt.in |   80 ++++++++
 b/stim/dat/BPSK_1of2.txt.in  |   80 ++++++++
 b/stim/dat/BPSK_3of4.txt.in  |   80 ++++++++
 b/stim/dat/DPNC_STIM1.txt    |   81 ++++++++
 b/stim/dat/DPNC_STIM1.vhd    |  136 ++++++++++++++
 b/stim/dat/DPNC_STIM2.txt    |   81 ++++++++
 b/stim/dat/DPNC_STIM2.vhd    |  136 ++++++++++++++
 b/stim/dat/DPNC_STIM3.txt    |   81 ++++++++
 b/stim/dat/DPNC_STIM3.vhd    |  136 ++++++++++++++
 b/stim/dat/DPNC_STIM4.txt    |   81 ++++++++
 b/stim/dat/DPNC_STIM4.vhd    |  136 ++++++++++++++
 b/stim/dat/DPNC_STIM5.txt    |   81 ++++++++
 b/stim/dat/DPNC_STIM5.vhd    |  136 ++++++++++++++
 b/stim/dat/DPNC_STIM6.txt    |   81 ++++++++
 b/stim/dat/DPNC_STIM6.vhd    |  136 ++++++++++++++
 b/stim/dat/DPNC_STIM7.txt    |   81 ++++++++
 b/stim/dat/DPNC_STIM7.vhd    |  136 ++++++++++++++
 b/stim/dat/DPNC_STIM8.txt    |   81 ++++++++
 b/stim/dat/DPNC_STIM8.vhd    |  136 ++++++++++++++
 b/stim/dat/QPSK_1of2.txt.in  |   80 ++++++++
 b/stim/dat/QPSK_3of4.txt.in  |   80 ++++++++
 b/vhdl/DPNC.vhd              |  354 ++++++++++++++++++++++++++++++++++++
 b/vhdl/IXSW_MOD.vhd          |  243 +++++++++++++++++++++++++
 b/vhdl/RCTRL_MOD.vhd         |  370 ++++++++++++++++++++++++++++++++++++++
 b/vhdl/WCTRL_MOD.vhd         |  300 +++++++++++++++++++++++++++++++
 b/vhdl/XSW_MOD.vhd           |  195 ++++++++++++++++++++
 b/vhdl/common/DELAYRAM.vhd   |   93 +++++++++
 stim/Makefile.gcc            |   20 +-
 stim/include/dpnc_internal.h |   67 +++---
 stim/include/dpnc_process.h  |    9 
 stim/ref/Makefile            |    4 
 stim/ref/tex/DPNC_memo.tex   |   10 -
 stim/src/dpnc_expect.c       |   18 -
 stim/src/dpnc_internal.c     |  415 ++++++++++++++++++-------------------------
 stim/src/dpnc_process.c      |   63 +++---
 stim/stimgen.sh              |   56 ++++-
 49 files changed, 4698 insertions(+), 980 deletions(-)

My diff stat 6/30~.

否，もはや何も言うまいて． :P
他にも色々あったけど，まだちゃんと動いてないのでもう少し頑張る．
[Well, I have no saying. :P
Hmm, it's a bit of buggy still now, I have to fix it, though.]

 a/stim/dat/BPSK_1of2           |   80 -----
 b/stim/dat/16QAM_1of2.iCLK     |   80 +++++
 b/stim/dat/16QAM_1of2.iDIN0    |   80 +++++
 b/stim/dat/16QAM_1of2.iDIN1    |   80 +++++
 b/stim/dat/16QAM_1of2.iDIN2    |   80 +++++
 b/stim/dat/16QAM_1of2.iDIN3    |   80 +++++
 b/stim/dat/16QAM_1of2.iDIN4    |   80 +++++
 b/stim/dat/16QAM_1of2.iDIN5    |   80 +++++
 b/stim/dat/16QAM_1of2.iMODE    |   80 +++++
 b/stim/dat/16QAM_1of2.iRDEN    |   80 +++++
 b/stim/dat/16QAM_1of2.iRDSTART |   80 +++++
 b/stim/dat/16QAM_1of2.iWDEN    |   80 +++++
 b/stim/dat/16QAM_1of2.iWDSTART |   80 +++++
 b/stim/dat/16QAM_1of2.ixRST    |   80 +++++
 b/stim/dat/16QAM_1of2.txt      |  160 +++++++++++
 b/stim/dat/16QAM_1of2.txt.in   |   80 +++++
 b/stim/dat/16QAM_3of4.iCLK     |   80 +++++
 b/stim/dat/16QAM_3of4.iDIN0    |   80 +++++
 b/stim/dat/16QAM_3of4.iDIN1    |   80 +++++
 b/stim/dat/16QAM_3of4.iDIN2    |   80 +++++
 b/stim/dat/16QAM_3of4.iDIN3    |   80 +++++
 b/stim/dat/16QAM_3of4.iDIN4    |   80 +++++
 b/stim/dat/16QAM_3of4.iDIN5    |   80 +++++
 b/stim/dat/16QAM_3of4.iMODE    |   80 +++++
 b/stim/dat/16QAM_3of4.iRDEN    |   80 +++++
 b/stim/dat/16QAM_3of4.iRDSTART |   80 +++++
 b/stim/dat/16QAM_3of4.iWDEN    |   80 +++++
 b/stim/dat/16QAM_3of4.iWDSTART |   80 +++++
 b/stim/dat/16QAM_3of4.ixRST    |   80 +++++
 b/stim/dat/16QAM_3of4.txt      |  160 +++++++++++
 b/stim/dat/16QAM_3of4.txt.in   |   80 +++++
 b/stim/dat/64QAM_2of3.iCLK     |   80 +++++
 b/stim/dat/64QAM_2of3.iDIN0    |   80 +++++
 b/stim/dat/64QAM_2of3.iDIN1    |   80 +++++
 b/stim/dat/64QAM_2of3.iDIN2    |   80 +++++
 b/stim/dat/64QAM_2of3.iDIN3    |   80 +++++
 b/stim/dat/64QAM_2of3.iDIN4    |   80 +++++
 b/stim/dat/64QAM_2of3.iDIN5    |   80 +++++
 b/stim/dat/64QAM_2of3.iMODE    |   80 +++++
 b/stim/dat/64QAM_2of3.iRDEN    |   80 +++++
 b/stim/dat/64QAM_2of3.iRDSTART |   80 +++++
 b/stim/dat/64QAM_2of3.iWDEN    |   80 +++++
 b/stim/dat/64QAM_2of3.iWDSTART |   80 +++++
 b/stim/dat/64QAM_2of3.ixRST    |   80 +++++
 b/stim/dat/64QAM_2of3.txt      |  160 +++++++++++
 b/stim/dat/64QAM_2of3.txt.in   |   80 +++++
 b/stim/dat/64QAM_3of4.iCLK     |   80 +++++
 b/stim/dat/64QAM_3of4.iDIN0    |   80 +++++
 b/stim/dat/64QAM_3of4.iDIN1    |   80 +++++
 b/stim/dat/64QAM_3of4.iDIN2    |   80 +++++
 b/stim/dat/64QAM_3of4.iDIN3    |   80 +++++
 b/stim/dat/64QAM_3of4.iDIN4    |   80 +++++
 b/stim/dat/64QAM_3of4.iDIN5    |   80 +++++
 b/stim/dat/64QAM_3of4.iMODE    |   80 +++++
 b/stim/dat/64QAM_3of4.iRDEN    |   80 +++++
 b/stim/dat/64QAM_3of4.iRDSTART |   80 +++++
 b/stim/dat/64QAM_3of4.iWDEN    |   80 +++++
 b/stim/dat/64QAM_3of4.iWDSTART |   80 +++++
 b/stim/dat/64QAM_3of4.ixRST    |   80 +++++
 b/stim/dat/64QAM_3of4.txt      |  160 +++++++++++
 b/stim/dat/64QAM_3of4.txt.in   |   80 +++++
 b/stim/dat/BPSK_1of2.txt       |  160 +++++++++++
 b/stim/dat/BPSK_1of2.txt.in    |   80 +++++
 b/stim/dat/BPSK_3of4.iCLK      |   80 +++++
 b/stim/dat/BPSK_3of4.iDIN0     |   80 +++++
 b/stim/dat/BPSK_3of4.iDIN1     |   80 +++++
 b/stim/dat/BPSK_3of4.iDIN2     |   80 +++++
 b/stim/dat/BPSK_3of4.iDIN3     |   80 +++++
 b/stim/dat/BPSK_3of4.iDIN4     |   80 +++++
 b/stim/dat/BPSK_3of4.iDIN5     |   80 +++++
 b/stim/dat/BPSK_3of4.iMODE     |   80 +++++
 b/stim/dat/BPSK_3of4.iRDEN     |   80 +++++
 b/stim/dat/BPSK_3of4.iRDSTART  |   80 +++++
 b/stim/dat/BPSK_3of4.iWDEN     |   80 +++++
 b/stim/dat/BPSK_3of4.iWDSTART  |   80 +++++
 b/stim/dat/BPSK_3of4.ixRST     |   80 +++++
 b/stim/dat/BPSK_3of4.txt       |  160 +++++++++++
 b/stim/dat/BPSK_3of4.txt.in    |   80 +++++
 b/stim/dat/QPSK_1of2.iCLK      |   80 +++++
 b/stim/dat/QPSK_1of2.iDIN0     |   80 +++++
 b/stim/dat/QPSK_1of2.iDIN1     |   80 +++++
 b/stim/dat/QPSK_1of2.iDIN2     |   80 +++++
 b/stim/dat/QPSK_1of2.iDIN3     |   80 +++++
 b/stim/dat/QPSK_1of2.iDIN4     |   80 +++++
 b/stim/dat/QPSK_1of2.iDIN5     |   80 +++++
 b/stim/dat/QPSK_1of2.iMODE     |   80 +++++
 b/stim/dat/QPSK_1of2.iRDEN     |   80 +++++
 b/stim/dat/QPSK_1of2.iRDSTART  |   80 +++++
 b/stim/dat/QPSK_1of2.iWDEN     |   80 +++++
 b/stim/dat/QPSK_1of2.iWDSTART  |   80 +++++
 b/stim/dat/QPSK_1of2.ixRST     |   80 +++++
 b/stim/dat/QPSK_1of2.txt       |  160 +++++++++++
 b/stim/dat/QPSK_1of2.txt.in    |   80 +++++
 b/stim/dat/QPSK_3of4.iCLK      |   80 +++++
 b/stim/dat/QPSK_3of4.iDIN0     |   80 +++++
 b/stim/dat/QPSK_3of4.iDIN1     |   80 +++++
 b/stim/dat/QPSK_3of4.iDIN2     |   80 +++++
 b/stim/dat/QPSK_3of4.iDIN3     |   80 +++++
 b/stim/dat/QPSK_3of4.iDIN4     |   80 +++++
 b/stim/dat/QPSK_3of4.iDIN5     |   80 +++++
 b/stim/dat/QPSK_3of4.iMODE     |   80 +++++
 b/stim/dat/QPSK_3of4.iRDEN     |   80 +++++
 b/stim/dat/QPSK_3of4.iRDSTART  |   80 +++++
 b/stim/dat/QPSK_3of4.iWDEN     |   80 +++++
 b/stim/dat/QPSK_3of4.iWDSTART  |   80 +++++
 b/stim/dat/QPSK_3of4.ixRST     |   80 +++++
 b/stim/dat/QPSK_3of4.txt       |  160 +++++++++++
 b/stim/dat/QPSK_3of4.txt.in    |   80 +++++
 stim/Makefile.gcc              |   14 -
 stim/include/dpnc_internal.h   |  187 +++++++------
 stim/include/dpnc_process.h    |   13 
 stim/src/dpnc_expect.c         |  170 ++++++------
 stim/src/dpnc_internal.c       |  529 ++++++++++++++++++++-------------------
 stim/src/dpnc_io.c             |    4 
 stim/src/dpnc_process.c        |  240 +++++++++--------
 stim/src/nxg.c                 |    2 
 stim/src/ram_internal.c        |    6 
 stim/stimgen.sh                |  551 +++++++++++++++++++++++++++++++++++++----
 118 files changed, 10330 insertions(+), 666 deletions(-)

Crunch, -fno-more-strict-aliasing, TDS

今日の出来事．

#ep93xx@freenode.netにて，
lennert（敬称略）のCirrus Logic EP93xx　Maverick Crunchな
パッチがupstreamにマージされた． :D
[On #ep93xx@freenode.net,
lennert's patches are merged to upstream who coded Cirrus Logic
EP93xx's Maverick Crunch implementation, coo. :D]

6/29 09:44:26 lennert
    whee
6/29 09:44:28 lennert    

http://www.kernel.org/git/?p=linux/kernel/git/torvalds...

6/29 09:48:17 hiyuh
    awesome :)
6/29 09:48:31 lennert
    yeah, i'm very happy

#gentoo-ppc@freenode.net
まだstrict aliasingの問題がいっぱい． :(
[Umm, many strict aliasing issues are. :(]

6/29 17:15:35 mabi
    mh, i guess libmp4v2 will get problems with strict-aliasing,
    it's crying during compile
6/29 17:31:34 hiyuh
    mabi: work around by "inherit flag-o-matic and append-flags
    -fno-strict-aliasing" or just fix it,
    I've poked ton of those ugly issue...
6/29 17:32:42 mabi
    hiyuh: sure, +poking upstream
6/29 17:33:02 mabi
    for the fixing, i know nothing of this package
6/29 17:34:10 mabi
    glibc-2.4 took twice the time of glibc-2.3 o_O
6/29 17:34:42 hiyuh
    yeah, to put -fno-strict-aliasing into global CFLAGS
    by /etc/make.conf is not good idea, IMHO.

Today's diff status，略してTDS．
[Here is my TDS, so-called today's diff status.]

 b/stim/dat/BPSK_1of2            |   80 +++++++++++++++++++++
 b/stim/dat/BPSK_1of2.iCLK       |   80 +++++++++++++++++++++
 b/stim/dat/BPSK_1of2.iDIN0      |   80 +++++++++++++++++++++
 b/stim/dat/BPSK_1of2.iDIN1      |   80 +++++++++++++++++++++
 b/stim/dat/BPSK_1of2.iDIN2      |   80 +++++++++++++++++++++
 b/stim/dat/BPSK_1of2.iDIN3      |   80 +++++++++++++++++++++
 b/stim/dat/BPSK_1of2.iDIN4      |   80 +++++++++++++++++++++
 b/stim/dat/BPSK_1of2.iDIN5      |   80 +++++++++++++++++++++
 b/stim/dat/BPSK_1of2.iMODE      |   80 +++++++++++++++++++++
 b/stim/dat/BPSK_1of2.iRDEN      |   80 +++++++++++++++++++++
 b/stim/dat/BPSK_1of2.iRDSTART   |   80 +++++++++++++++++++++
 b/stim/dat/BPSK_1of2.iWDEN      |   80 +++++++++++++++++++++
 b/stim/dat/BPSK_1of2.iWDSTART   |   80 +++++++++++++++++++++
 b/stim/dat/BPSK_1of2.ixRST      |   80 +++++++++++++++++++++
 b/stim/src/nxg.c                |   85 ++++++++++++++++++++++
 b/stim/stimgen.sh               |   50 +++++++++++++
 stim/Makefile.gcc               |   18 +++-
 stim/include/dpnc_internal.h    |    4 +
 stim/include/dpnc_process.h     |    2 
 stim/ref/Makefile.BENCH_DL_MOD  |   22 ++---
 stim/ref/Makefile.BENCH_XSW_MOD |   24 +++---
 stim/src/conv_func.c            |   31 +++++---
 stim/src/dpnc_expect.c          |  149 +++++++++++++++++++++-------------------
 stim/src/dpnc_internal.c        |   13 +++
 stim/src/dpnc_io.c              |    6 -
 stim/src/dpnc_process.c         |    5 +
 26 files changed, 1419 insertions(+), 110 deletions(-)

Stuffed over 1k SLOC, the e-mail

今日のdiffstatは1k SLOC越え． :P
未だ未だ修行あるのみ．
[Today's my diffstat shows was stuffed over 1k SLOC. :P
And, yeah, all I can do is train & train.]

 b/stim/include/dpnc_expect.h |    8 
 b/stim/include/dpnc_io.h     |   18 +
 b/stim/src/dpnc_expect.c     |  220 ++++++++++++++++++++
 b/stim/src/dpnc_io.c         |  171 +++++++++++++++
 stim/Makefile.gcc            |   28 +-
 stim/include/dpnc_internal.h |  121 ++++++++---
 stim/include/dpnc_process.h  |  125 +++++++++++
 stim/include/ram_internal.h  |   26 --
 stim/src/dpnc_internal.c     |  194 +++++++++++++----
 stim/src/dpnc_process.c      |  468 +++++++++++++++++++++++++++----------------
 stim/src/ram_internal.c      |   12 -
 11 files changed, 1108 insertions(+), 283 deletions(-)

で，あのメールが来た．
こちらは何となく秘密にしておこうっと． :P
[The e-mail has been received.
Well, that is on the QT, but there is no reason why, though. :P]

CJK_Ugh*3, br0ken man.conf, today's diffstat

CJKのbugsに手を出してヘマをやらかした．．． :(
FEPと変換エンジンの違いを忘れているとかダメダメだな，コレは．
[I misdirected WRT the CJK bugs... :(
Well, forgot the difference of FEPs and conversion engines, so awkward.]

更に，sys-apps/man-1.6dのアップデートで/etc/man.confが壊れて，
一時的にapp-i18n/man-pages-jaが読めなくなってハマった． :(
すぐ直ったけど，そもそもsys-apps/groffの設定ファイルが
sys-apps/manで上書きされるのはどうなのだろう？
忘れないうちにbugzillaに貼っとくかな．．．
[Ah, worse thig,
I had broken my /etc/man.conf by updating sys-apps/man-1.6d.
So, it had been temporarily unable to read app-i18n/man-pages-ja.
Of cource, it had been fixed, immediately.
But, yeah, why man.conf has sys-apps/groff's configuration,
even it's included in sys-apps/man, though?
Hmm, should it post that groff's bug info...]

弄くっていたVHDLマクロのレポジトリのdiffstatも大した事無いし，
うーん，何か調子悪いのか？ :(
[And other worse thing,
today's diffstat of my VHDL repos is not so good.
Umm, in bad shape?]

否々，修行あるのみ！ :P
[NO, of cource NO.
the answer is doing! :P]

Fix app-dicts/kasumi-2.0, some events are

昼休みにbugs.gentoo.orgで遊んでた．
Bug 137540
あのjakub（敬称略）とflameeys（敬称略）のコンボで瞬殺death． :P
[I poked bugs.gentoo.org at lunch.
Bug 137540
Well, jakub and flameeys squashed it like ram's attacking, so fast. :P]

で，某所でアレなイベントを知る．
CodeFest Akihabara 2006
Japan Regional Technical Jamboree #9 - July 13th, 2006
[These event smell kinda nerd's flavor.
CodeFest Akihabara 2006
Japan Regional Technical Jamboree #9 - July 13th, 2006]

version bump, yield CPU_Board

取り敢えず，自前のebuildは先っぽを突っ走らないとね． :P
ヴァージョンアップ．
[K, my ebuilds should ready to rice, AT ANY GIVEN TIME. :P]

games-engines/onscripter-20060618
つい最近騒いでいたstrict aliasing関係の（潜在的）バグを
潰してもらってたりする．
[Squashed the bug which was mentioned a while ago.]

x11-wm/wmii-3.1
こちらもbug fixなリリース．
実は未だstrict aliasingとuninitializationな警告が出たりするので，
ムニャらねば．
[This is a big fix release.
It has some warning which mention strict aliasing and uninitialization.
So, should fix.]

で，
お昼までニコニコで期待値生成のプログラムをコーディングしていたら，
午後は例のボードを追加生産する為の荷造りを言い渡された．
うーん，疲れたー． :(
[BTW,
I've enjoyed my stupid coding to expect collation,
my boss tell me what to packing the parts for re-production the board.
Well, I have bit of stiff shoulder. :(]

Fixed some ebuilds, where is ppc Mac mini?

今日はHDL guruなボスが午前中出張だったので，
仕事をやりつつ，隙を見てebuildを弄った． :P
以下，ChangeLogっぽいモノ．
[Today, my HDL guru had official trip till noon.
So, it was the time to poke my ebuilds. :P
Kinda like ChangeLog is on the below.]

sys-power/yacpi
中止，試しに野良コンパイルしてから
PowerBookではACPIが動かない事を知る． :<
仕方無いので/sysからバッテリ残量を計算するスクリプトを
~/.wmii-3/wmiircに仕込んだ．
[Boo, I've poke it, but my PB couldn't handle ACPI. :<
Instead, I've put a script which calculate battery status from
/sys into ~/.wmii-3/wmiirc.]

net-irc/ii
すぐ出来た．適当にムニャったらnet-irc/xchatをemerge -Cする予定．
[Made. After tasting it, I'll do emerge -C net-irc/xchat.]

sci-electronics/tkgate
未だ，Tcl/Tkは分かってないので後回し．
[Later. Because of I'm not familliar with Tcl/Tk stuffs.]

x11-terms/sdl-terminal
media-libs/sdl-terminalから適当にコピーして作ってみたけど，
ライブラリ以外は単なるデモでしかないので，中止．
[Copied from media-libs/sdl-terminal and somethig edited.
But it has only demo except its libs.]

?/xynth
野良コンパイルしてみたけど，portされたライブラリと一緒に
/optあたりに突っ込んで，LD_LIBRARY_PATHを弄くる/etc/env.d
以下のファイルも作らなきゃならんみたい．なので後回し．
[Compiled, but it's mandatory to install some ported libs into /opt or so on,
and then, its runtime required LD_LIBRARY_PATH tweaking as a /etc/env.d
stuff. Later.]

media-libs/libmad
CLAGSのsanitizing，sigend/unsignedの修正，
ALSAの為のconfigureオプションの追加，
inherit flag-o-maticでreplace-flagsまで使ってやっと直った． :)
[Sanitizing CFLAGS, fix signed/unsigned warnigns,
added configure option for ALSA,
using replace-flags which is in flag-o-matic.eclass.
Finally, it seems fixed for me. :)]

media-libs/sdl-mixer
本家のeffect-positionパッチを追加，直ったかどうかは未確認．
repomanにパッチがデカ過ぎると怒られるので，
${FILESDIR}に入れたままgzipして誤摩化した． :P
[Added contributed effect-opsition patch,
but didn't care whether it's really fixed.
repoman saz that it's too large patch,
so faked it by gziped in ${FILESDIR}. :P]

x11-libs/fltk
2.0.xはリリースされていないみたい，最新のsnapshotを使ってみたが，
まだmakeが通らないので後回し．
コイツがemerge出来無いとwww-client/dilloの
x11-libs/gtk+-1.*依存から脱却出来無い．．． :(
[2.0.x haven't been released yet. Tested most recently snapshot,
but its make process keep choking.
If that versions libs are not available,
www-client/dillo depends on x11-libs/gtk-1.*... :(]

media-gfx/fondu
20060102にversion bump．
[Version bump too 20060102.]

ppc版のMac miniが欲しい．
web上で探しても在庫が無さ気．
会社の据え置きGentooマシンとお家のhardened uclibcサーバに二台．
どっかにないかな？ :P
[BTW, I want *ppc* Mac mini.
I've search its stocks on the web, it shows no/few stock.
I'd like to setup it as office gentoo box and my home hardened uclibc server.
Well, where is ppc Mac mini? :P]

158MHz, my ebuilds' dev progress

例のBRマクロは動作周波数158MHzで動くっぽい．
で，今度のヤツは128MHzで動かせと．
何だか無茶苦茶ややこしいブツみたいだけど，大丈夫かな．．． :(
パンクチャド，デパンクチャド！ :P
[The BR macro may works with ~158MHz synchrnous CLK.
Well, the next macro should work ~128MHz synchnous CLK.
But, it seems a bit complex func enough to be mess, though. :(
Punctured, De-punctured! :P]

以下，Gentooな作業メモ．
[These are my ebuilds' dev progress.]

作成予定ebuild．
[These ebuilds will be make.]
sys-power/yacpi
net-irc/ii
sci-electronics/tkgate
x11-terms/sdl-terminal
?/xynth

修正予定ebuild．
[These ebuilds should be fix.]
media-libs/libmad
media-libs/sdl-mixer
x11-libs/fltk
media-gfx/fondu

BR, 500xFasterThanOldOneLOL!

OJTな感じで切り分けてもらったBRと呼ばれるVHDLマクロのコーデングに
一週間もかかっていたが，どうにか終わったっぽい気配．
後はイイ感じにModelSimでシミュレーション結果を残して，
サーバに突っ込むだけ．
入社二ヶ月で内部レイテンシー67CLKsのVHDLマクロを書かせるとは，
流石に現場はスパルタで一味違うなー． :)
[On job training, I've done almost process of coding the BR macro.
Well, it took 1 week or so on due to my little coding skill, though.
I'll do simulate it w/ ModelSim or so on, then stuff it into the server.
So, I'm a newbie who have been working for 2 mounth or so on,
but I've coded the macro which has 67CLKs as internal latencies.
It smells spicy for me. :)]

次はコイツの一部かな．．．メモメモ．．．
Viterbi algorithm
おー，サンプルがPythonで書いてあるよ． :D
[Hmm, next macro is a part of it...?
Viterbi algorithm
Coo, that samples are written in python. :D]

で，以前，Pythonで作っていたコードジェネレータ．
試験用のデータを云万行単位で入力されて，
「シミュレーションよりコード生成の方が遅ぇ．．．」
とかボロクソ言われていた．
悔しいので休みの間にプロファイルして午前中に改良を施したら，
何か500倍くらい早くなった． :DDD
[BTW, I had coded a code-gen which is written in Python.
Someone pokes it w/ a ton of test data, then he said...
"ThatCodeGenTakesMoreTimeThanSimulateItSucks!"
So, I've profiled it at last weekend, and poke it.
YayThatCodeGenHasBeenImproved500xFasterThanOldOneLOL! :DDD]

「それがPythonの本当の姿」 (c) cpw
教訓一：コードの再利用は時と場合を選んで．
教訓二：数値以外との算術演算子の多用はフラグメンテーションの元かも？
["That is truth of the python." (c) cpw
L1: Code reuse depends on the situation.
L2: Ton of aritmetic oprs with non numeric vars lead to mem-frangmentation?]

gated clock, register RAM

修行の成果（？）として，BK in VHDLでもやってみる．
[Here is my BK in VHDL.]

以下のプロセスpFOOとpBARは根本的に別モノである．
[The process of pFOO and pBAR are totally different.]

pFOO : process (ixRST, iCLK)
begin
    if (ixRST = '0') then
        -- RESET IT!
        :
        :
    elsif (iCLK'event and iCLK = '1') then
        if (ixEN = '0') then
            -- DO IT!
            :
            :
        end if;
    end if;
end process;
----------------------------------------------
pBAR : process (ixRST, iCLK)
begin
    if (ixRST = '0') then
        -- RESET IT!
        :
        :
    elsif (iCLK'event and iCLK = '1' and ixEN = '0') then
        -- DO IT!
        :
        :
    end if;
end process;

以下の記述の違いで，
インプリするデバイスによってはハマる可能性がある．
[You may choke by difference of between FOO and BAR
when it was implement into specific HW.]

archtecture RTL of FOO is
    subtype tADDR is std_logic_vector(AL-1 downto 0);
    subtype tWORD is std_logic_vector(WL-1 downto 0);
    :
    :
    type tMEMORY is array(0 to 2**AL-1) of tWARD;
    :
    :
    signal rRA      : tADDR;
    signal rINIT_RD : std_logic;
    signal aRAM     : tMEMORY;
begin
    pRAM_RD : process (iCLK)
    begin
        if (iCLK'event and iCLK = '1') then
            rINIT_RD <= iINIT_RD;
            rRA      <= iRA;
            if (rINIT_RD = '1') then
                oDOUT_RD <= (others => '0');
            else
                oDOUT_RD <= aRAM(conv_integer(rRA));            
            end if;
        end if;
    end process;
    :
    :
    pRAM_WR : process (iCLK)
    begin
        if (iCLK'event and iCLK = '1') then
            if (iWE = '1') then
                aRAM(conv_integer(iWA)) <= iDIN_WR;
            end if;
        end if;
    end process;
end RTL;
----------------------------------------------
archtecture RTL of BAR is
    subtype tADDR is std_logic_vector(AL-1 downto 0);
    subtype tWORD is std_logic_vector(WL-1 downto 0);
    :
    :
    type tMEMORY is array(0 to 2**AL-1) of tWARD;
    :
    :
    signal aRAM : tMEMORY;
begin
    pRAM_RD : process (iCLK)
    begin
        if (iCLK'event and iCLK = '1') then
            if (iINIT_RD = '1') then
                oDOUT_RD <= (others => '0');
            else
                oDOUT_RD <= aRAM(conv_integer(iRA));            
            end if;
        end if;
    end process;
    :
    :
    pRAM_WR : process (iCLK)
    begin
        if (iCLK'event and iCLK = '1') then
            if (iWE = '1') then
                aRAM(conv_integer(iWA)) <= iDIN_WR;
            end if;
        end if;
    end process;
end RTL;

違いの分かる漢のVHDL，か？ :P
[Hey, any of you guy of VHDL got it? :P]

strict aliasing traps, mercurial++

make.conf.exampleが付けておけと言うので気になったから，
#gentoo-ppcで-fno-strict-aliasingを使っているかと訊いてみた．
-O2, -O3だと自動的に効いて仕舞うので，
今までは-fno-strict-aliasingを後方に付けていたのだが，
無くても殆ど問題無いと言う情報を入手．
さっそく，Rice開始！ :9
[make.conf.example saz to use -fno-strict-aliasing
if you wanto to use -O2 or -O3.
So, I've asked why that flags are recommended.
Peaple answered to me that has no/little problem.
Gotcha, it's the time to Rice! :9]

...で，ちょっと壊れたみたい． :P
特にC++なアプリやmedia-*以下のマルチメディアなライブラリで
激しくcastをしているブツは要注意．
[...Well, some packages seems have a bit of breakages. :P
Especially, several fscking C++ apps or multimedia oriented libs under meda-*
categories which uses ton of incredible cast.]

教訓その一：Gentoo is Rice.
教訓その二：-O3 -Werrorでコンパイル，patchで対処．
教訓その四：それでもダメなら，inherit flag-o-maticで*-flagsを使う．
[L1: Gentoo is Rice.
L2: Try to compile with -O3 -Werror, then do patch.
L3: If it has no clue, try to *-flags by inherit flag-o-matic.]

で，mercurialが便利過ぎて，
或るVHDLマクロの為にでっちあげた
ローカルなレポジトリに土日なのに20回以上commitしてた．
我ながら，ちょっと馬鹿じゃね？ :P
[BTW, mercurial is so cool.
That make me cann't stop to commit to local VHDL macro repos over 20 times.
It was weekend even though.
It amazed even me. :P]

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

State Machine + ALU == CPU

加算が出来た．
今度はアセンブラを作らねばならんなー． :P
[This is add instruction waveform.
Hmm, I should code its assembler? :P]

Oversleep, State Machine, MacBook Pro

いつかやらかすだろうと思ってはいたが，
二度寝して会社に遅刻した． :P
やはり携帯のアラームだけではダメなのかもしれない．
[Well, I've overslept today.
Umm, only use phone-alarm is not so safe, though.]

PCB設計用のCADを主に使っている先輩の仕事が佳境に入ったらしく，
今度はVHDLの課題を与えられる．
RTLなFFを一つだけこなした後に，いきなりステートマシンですか．
流石にスパルタだ，すぐ終わったけど． :P
[A boss who mainly use the CAD for PCB design looks like so busy.
So, my boss gave me some VHDL subjects.
I've coded for a Flip-Flop as RTL model, then next was a state machine.
Sounds like so Spartan education, though I've done it. :P]

ModelSimのライセンスサーバを上司の方がモニョっている間に，
PowerBook上のGHDL + GTKWaveでムニャっていたら，
「何でシミュレーション出来てるの？」と訊かれた．
「これはGCC technologyを使ってエラい人が作ったFreeな．．．」
と少し説明，std_logic*な信号しかダンプ出来無いので色々癖が有る事も．
「ModelSimのライセンスが高過ぎるし，勉強にはそれを使っても良い」
との許しが出たので，
PCB設計用のCADに戻るまではGentoo上で生活出来そう． :P
[When my boss poked floating license server which for ModelSim,
I've code it on my PowerBook with GHDL and GTKWave.
So, my boss asked me "Why you can do the simulation without ModelSim?",
I've answered "There is a VHDL simulater using GCC technology, it's free...",
I've explained about it can only dump std_logic* signals and known some restrictions.
Finally, my boss said to me "To tell the truth, ModelSim's license is so expensive.
So, if you can use it, education use is OK."
Kay, sound like working on Gentoo is OK,
until restart edu of PCB design CAD. :P]

次のブツを下調べ．
やはりMacBook Proか．
評判も悪くないし，DRIも行けそうだ．
おまけにTriple Bootまでついてくるらしい．
問題は，12"モデルが無い事と何処から資金を調達するかだなー． :(
[Sneaky way for next things.
Hmm, MacBook Pro is.
Sounds like not so bad, DRI will work,
and then it can triple boot, though.
My PITA is no 12" model, and no money. :(]

Squash my bugs, PCB, wmii-3 will come

一通り終わりかと思いきや，
ちょこちょこ要望が出るわ，しょぼいbugが見つかるわで，
少しずつ例のPythonスクリプトを弄っていました． :P
[I've had tweaking/fixing my stupid python script
for some requests and to squashing bugs.]

で，その合間にPCB設計用のCADを弄くっていろとのお達しで，
英語のヘルプを読みつつ弄ると，
流石に商品なだけあって色々良く出来ている．
でも，
単一のアプリケーションに独自に作り込んだデータベース機能とか，
パスワード設定とか他のアプリケ−ションとは相容れないし，
慣れるまで時間がかかりそうですなー．
*NIX系に作り込めば色んな機能やらライブラリやらが再利用出来るし，
何より一々同じ機能の為にそのアプリケーション独自の使い方や作法を
覚えなくて済むのだなー，と有り難みと息苦しさを同時に感じる．
．．．むー，作るかって？ :P
[BTW, I've poke the CAD which for designing PCB or so.
I've skimed its help file which is written in English.
It seems work fine as product level software.
But almos its features implementations smells itselfish.
E.g. Database storage, password mechanism...
It seems make me lost a time.
If it was implemented in *NIX env,
some features and mechanisms already have been, though.
And I have, otherwise I would.
Anyway,
to learn the use for same feature/mechanism for only one app
is so bad idea for me, IMHO.
Umm, it means I'll make it? :P]

さぁ，4月中にはwmiiのversion 3が！
一足先に20060414のsnapshotをムニャってみたが．．．
相変わらず良い仕事するねー． ;)
[K, in April, wmii version 3 will come!
I've tried the snap 20060414...
Well, I should say "ah, nice work." ;)]

Office.Nomikai++; VB + redirect == bad;

新入社員歓迎会と言う事で金曜日の夜は飲み会をして頂きました．
でも，最初の乾杯のビール一杯と少しで回って仕舞い，
その後は，コーラでお付き合い．
飲み屋，飲み屋，カラオケ，飲み屋と巡って朝五時に帰宅．
で，気付いたら日曜日の昼でした．
色々ムニャムニャ語って仕舞って先輩達に，
「キミは新入社員っぽくないねー」と言われた． :P
[At last Friday, I've attended the welcome party.
But, I couldn't get second beer.
So, I've taken with many cola. :P
IZakaYa, IZakaYa, Karaoke, IZakaYa, then,
I've returned my home at about 5:00 AM.
got some Z's, awoke at noon of Sunday.
Some seniors said to me like that
"You look like not a fresh man, though." :P]

で，嫌々やっていたVBのコーディングですが，
一応それっぽくなったので早々に終了する．
ハマッたのはVB内部から外部の実行ファイルをコマンドラインに含めて実行，
その標準出力をリダイレクトして任意のファイル名を付ける部分．
調べた結果，VB内部からリダイレクトを直接使う事は仕様上不可能で，
一時的にバッチファイルをOpen()やらPrintやらで記述して，
その後にこいつをShell()かCreateProcess()で叩くと言う意味不明な仕様．．． :(
[BTW, about my stupid VB coding.
It looks like kinda working.
The PITA was to execute external executable binary inside VB.
According to some VB gurus stuffs,
VB cann't handle to execute external executable binary
with any redirections, directly.
So, it should do like that,
1. create temporary batch file with Open() or Print.
2. execute it by Shell() or CreateProcess().
Umm, so awkward... :(]

New PC, coding in Python

会社から与えられた``にゅーまっしーん''は
Celeron D + Intelの新しいonboard graphic chipなブツで，
DRIはそこそこな感じなのだが，Frame bufferと激しく相性が悪い．．． :S
XenもVTが有効にならないし，qemuはCADを使うには遅過ぎるので，
クロスプラットフォームなアプリケーションのテスト環境，
及び仕事の為のメール端末と言う事にした．
仕方無いので，Gentoo on PowerBookと共に出社しております．
シェルと端末エミュレータが無いと何も出来無い体になってる，ヤバい． :S
[I got new PC which for office working
It's constructed with Celeron D + new Intel onboard graphic chip or so.
So, DRI works and it seems not so bad,
but the frame buffer is sometimes mess... :S
Xen didn't work with VT feature, qemu is not so fast when use a CAD.
So, I decided its use is for only test cross-platform apps
and e-mail terminal for office working.
Meanwhile, I'm working with Gentoo on PowerBook, still now.
Hmm, no {shell, terminal-emulater} is no life for me. :S]

一昨日からやって一段落ついたお仕事は，
HDLの設計で或る作業の為に使うコードジェネレータの作成．
会社としてはこれが2bit幅の信号もマトモに処理出来無い（明らかにバグ！）
30万円位する購入を検討していたWindows専用ソフトの代わりらしい．
簡単な仕様を頂いて，三日間一人でPythonを使ってコーディングしたら，
それっぽいCUIなブツが出来て仕舞い，こっちを使うとか言われた． :P
py2exeでWindows用の実行バイナリを作成して
ソースコードと一緒に会社のサーバにぶち込んでおいた． :)
[ATM, My DONE is coding a HDL code generater.
Like a boss said,
it's for a replacement of the closed Windows centric software
which will cost about 300,000 yen,
and then, it won't work for a simple 2bit signal analysis, BUG!
I got an easy spec for it, coded in Python for 3 days or so.
My stupid CUI script seems work, and a boss decided used it. :P
So, I made it as executable binary by using py2exe.
I've stuffed it with its sources on office server. :)]

次はGUIを被せるとか何とか．
「要らないと思うんですが」と生意気にも意見すると
「いや，便利でしょ？」とか，
「あとでGUIは無いのか？と訊かれるよ」と言われたので，
「じゃあ，PyGTKでやります」と言ったら
「ダメ，次はVBで作って」と言われた． :/
理由は他人がメンテナンス出来無いからだとか，
GUIをメンテナンスしてどうするんだろうか．．．
と言うか，コアはPythonのままで良いのかな．．．
[Next is coding GUI front-end for it.
So, I've said "GUI is not so sane for it", IMHO,
then a boss said "No, no, just for useful"
otherwise "you will be asked by others why GUI isn't, everytime."
Then, I've said "Okay, PyGTK is", IMHO,
then a boss said "No, use VB". :/
According to a boss said,
that's why others can/cann't maintain it.
But why maintain GUI front-end by others?
And then, the core is written in Python is OK?]

何れにしても，
Write Once Run Anywhre
はこう言うモノにはあんまり重要じゃないのですなー．
なるほど，
ヤッツケ仕事なら或る意味クロスプラットフォーム性より重要ですな．
と言うか，仕様を頂いた上司も監督役の上司もPythonの存在すら知らなかったらしい．
「Pythonって今まで他の会社とかで実績があるのか？」と訊かれて
「そんな事は考えた事無いです」と答えた． :P
だが，知らないだけに不安だ．．．やはりマイナーなのか？ :S
[Anyway, it's not so important "Write Onece Run Anywhere" for its use.
I see, like my stupid coding, that's more important than cross-platform app.
Unfortunately,
a boss who gave me a spec and a boss who is a hardware guru haven't known Python is.
They asked me like "Python has so many past records?",
then I've said "Dunno." :P
Umm, coding in Python is so minority? :S]

My first working... and beyond sources.

初出社，やはり社内はNDAでガチガチであった．
この御時世なので，社長直々に「Winnyは使ってないよね？」と訊かれて，
「Gentooしか使っていません」と答えた． :P
ハードウェア寄りの上司に教えを垂れて頂いて，
暫くは通信工学の基礎から勉強しつつ，
Gigabit Ethernet関連の開発に巻き込まれそうな感じ．．
[Today is my first working. And in the office, many NDA restrictions are.
My boss said to me "haven't you use Winny?",
I've answered "I use only Gentoo", yay. :P
I'll re-study about basis of comminucation engineering
with the hardware guru as my chief in the development of Gigabit Ethernet.]

更に，仕事で使うツールはWindows上でのみ動くブツらしいので，
Xenかqemuで暮らす事になるケド，
どちらにするかはこれから支給されるマシンのスペック次第．
それよりも日報がExcelで書かれている．
OpenOffice.orgをコンパイルせにゃならんのか．．． :S
[Umm, the tools for the development can be used on only Windows platform.
So, I should do it with Xen or qemu.
The selection of virtualization/emulation tools depends on new PC which is given as dev env.
Unfortuantely, the daily report is written by Excel.
So, I must compile OpenOffice.org. :S]

全然関係無いが，beyond sourcesに期待． :)
[Hmm, it's completely non-related things, though.
beyond sources is appreciated for me. :)]

Open AP?

あらら，接続出来ちゃった． :P
[Well, it seems open, though. :P]

引っ越しは終了．．．取り敢えず，筋肉痛． :(
あと一週間位はゴタゴタしそうな感じ．
[Erm, the moving done... umm, I have muscle ache.
I'm busy until this weekend.]