wc -l log/* | tail -n 1

例のP4の試験データ取得終了．あとはコイツをグラフ化すればCLOSEだが．
['Kay, to get all test log is completed now. I can CLOSE t3h P4
when I had made some graphs w/ these logs, though.]

 ttlog_BS1_SS1_CH21_16QAM1of2_TSSI13dBm_PeerATT51dB_RSSI-36.5dBm_UDP |  125 ++
 ttlog_BS1_SS1_CH21_16QAM1of2_TSSI13dBm_PeerATT54dB_RSSI-39.7dBm_UDP |  126 ++
 ttlog_BS1_SS1_CH21_16QAM1of2_TSSI13dBm_PeerATT59dB_RSSI-45.7dBm_UDP |  126 ++
 ttlog_BS1_SS1_CH21_16QAM1of2_TSSI13dBm_PeerATT63dB_RSSI-50.7dBm_UDP |  127 ++
 ttlog_BS1_SS1_CH21_16QAM1of2_TSSI13dBm_PeerATT68dB_RSSI-53.8dBm_UDP |  127 ++
 ttlog_BS1_SS1_CH21_16QAM1of2_TSSI13dBm_PeerATT72dB_RSSI-58.2dBm_UDP |  126 ++
 ttlog_BS1_SS1_CH21_16QAM1of2_TSSI13dBm_PeerATT74dB_RSSI-60.6dBm_UDP |  126 ++
 ttlog_BS1_SS1_CH21_16QAM1of2_TSSI13dBm_PeerATT75dB_RSSI-61.8dBm_UDP |  128 ++
 ttlog_BS1_SS1_CH21_16QAM1of2_TSSI13dBm_PeerATT76dB_RSSI-63.0dBm_UDP |  124 ++
 ttlog_BS1_SS1_CH21_16QAM1of2_TSSI13dBm_PeerATT78dB_RSSI-65.4dBm_UDP |  122 ++
 ttlog_BS1_SS1_CH21_16QAM1of2_TSSI13dBm_PeerATT80dB_RSSI-67.8dBm_UDP |  123 ++
 ttlog_BS1_SS1_CH21_16QAM1of2_TSSI13dBm_PeerATT82dB_RSSI-69.1dBm_UDP |  122 ++
 ttlog_BS1_SS1_CH21_16QAM1of2_TSSI13dBm_PeerATT83dB_RSSI-70.3dBm_UDP |  121 ++
 ttlog_BS1_SS1_CH21_16QAM1of2_TSSI13dBm_PeerATT84dB_RSSI-71.0dBm_UDP |  122 ++
 ttlog_BS1_SS1_CH21_16QAM1of2_TSSI13dBm_PeerATT85dB_RSSI-72.0dBm_UDP |  131 ++
 ttlog_BS1_SS1_CH21_16QAM1of2_TSSI13dBm_PeerATT86dB_RSSI-73.0dBm_UDP |  224 +++
 ttlog_BS1_SS1_CH21_16QAM1of2_TSSI13dBm_PeerATT87dB_RSSI-74.0dBm_UDP |  426 +++++++
 ttlog_BS1_SS1_CH21_16QAM3of4_TSSI13dBm_PeerATT51dB_RSSI-36.5dBm_UDP |  114 +
 ttlog_BS1_SS1_CH21_16QAM3of4_TSSI13dBm_PeerATT54dB_RSSI-39.7dBm_UDP |  115 +
 ttlog_BS1_SS1_CH21_16QAM3of4_TSSI13dBm_PeerATT59dB_RSSI-45.7dBm_UDP |  115 +
 ttlog_BS1_SS1_CH21_16QAM3of4_TSSI13dBm_PeerATT63dB_RSSI-50.7dBm_UDP |  115 +
 ttlog_BS1_SS1_CH21_16QAM3of4_TSSI13dBm_PeerATT68dB_RSSI-53.8dBm_UDP |  114 +
 ttlog_BS1_SS1_CH21_16QAM3of4_TSSI13dBm_PeerATT72dB_RSSI-58.2dBm_UDP |  115 +
 ttlog_BS1_SS1_CH21_16QAM3of4_TSSI13dBm_PeerATT74dB_RSSI-60.6dBm_UDP |  115 +
 ttlog_BS1_SS1_CH21_16QAM3of4_TSSI13dBm_PeerATT75dB_RSSI-61.8dBm_UDP |  115 +
 ttlog_BS1_SS1_CH21_16QAM3of4_TSSI13dBm_PeerATT76dB_RSSI-63.0dBm_UDP |  113 +
 ttlog_BS1_SS1_CH21_16QAM3of4_TSSI13dBm_PeerATT78dB_RSSI-65.4dBm_UDP |  111 +
 ttlog_BS1_SS1_CH21_16QAM3of4_TSSI13dBm_PeerATT80dB_RSSI-67.8dBm_UDP |  110 +
 ttlog_BS1_SS1_CH21_16QAM3of4_TSSI13dBm_PeerATT82dB_RSSI-69.1dBm_UDP |  111 +
 ttlog_BS1_SS1_CH21_16QAM3of4_TSSI13dBm_PeerATT83dB_RSSI-70.3dBm_UDP |  112 +
 ttlog_BS1_SS1_CH21_16QAM3of4_TSSI13dBm_PeerATT84dB_RSSI-71.0dBm_UDP |  118 ++
 ttlog_BS1_SS1_CH21_16QAM3of4_TSSI13dBm_PeerATT85dB_RSSI-72.0dBm_UDP |  139 ++
 ttlog_BS1_SS1_CH21_16QAM3of4_TSSI13dBm_PeerATT86dB_RSSI-73.0dBm_UDP |  317 +++++
 ttlog_BS1_SS1_CH21_BPSK3of4_TSSI13dBm_PeerATT51dB_RSSI-35.8dBm_UDP  |  135 ++
 ttlog_BS1_SS1_CH21_BPSK3of4_TSSI13dBm_PeerATT51dB_RSSI-36.5dBm_TCP  |  110 +
 ttlog_BS1_SS1_CH21_BPSK3of4_TSSI13dBm_PeerATT55dB_RSSI-40.0dBm_UDP  |  135 ++
 ttlog_BS1_SS1_CH21_BPSK3of4_TSSI13dBm_PeerATT59dB_RSSI-44.8dBm_UDP  |  135 ++
 ttlog_BS1_SS1_CH21_BPSK3of4_TSSI13dBm_PeerATT63dB_RSSI-49.9dBm_UDP  |  132 ++
 ttlog_BS1_SS1_CH21_BPSK3of4_TSSI13dBm_PeerATT65dB_RSSI-51.9dBm_UDP  |  129 ++
 ttlog_BS1_SS1_CH21_BPSK3of4_TSSI13dBm_PeerATT68dB_RSSI-52.8dBm_UDP  |  134 ++
 ttlog_BS1_SS1_CH21_BPSK3of4_TSSI13dBm_PeerATT69dB_RSSI-53.8dBm_UDP  |  135 ++
 ttlog_BS1_SS1_CH21_BPSK3of4_TSSI13dBm_PeerATT71dB_RSSI-56.0dBm_UDP  |  134 ++
 ttlog_BS1_SS1_CH21_BPSK3of4_TSSI13dBm_PeerATT73dB_RSSI-58.2dBm_UDP  |  131 ++
 ttlog_BS1_SS1_CH21_BPSK3of4_TSSI13dBm_PeerATT76dB_RSSI-62.3dBm_UDP  |  106 +
 ttlog_BS1_SS1_CH21_BPSK3of4_TSSI13dBm_PeerATT78dB_RSSI-65.4dBm_UDP  |  104 +
 ttlog_BS1_SS1_CH21_BPSK3of4_TSSI13dBm_PeerATT80dB_RSSI-67.8dBm_UDP  |  140 ++
 ttlog_BS1_SS1_CH21_BPSK3of4_TSSI13dBm_PeerATT82dB_RSSI-69.1dBm_UDP  |  143 ++
 ttlog_BS1_SS1_CH21_BPSK3of4_TSSI13dBm_PeerATT83dB_RSSI-70.3dBm_UDP  |  123 ++
 ttlog_BS1_SS1_CH21_BPSK3of4_TSSI13dBm_PeerATT84dB_RSSI-71.0dBm_UDP  |  141 ++
 ttlog_BS1_SS1_CH21_BPSK3of4_TSSI13dBm_PeerATT85dB_RSSI-72.0dBm_UDP  |  207 +++
 ttlog_BS1_SS1_CH21_QPSK1of2_TSSI13dBm_PeerATT51dB_RSSI-36.5dBm_UDP  |  114 +
 ttlog_BS1_SS1_CH21_QPSK1of2_TSSI13dBm_PeerATT54dB_RSSI-39.7dBm_UDP  |  114 +
 ttlog_BS1_SS1_CH21_QPSK1of2_TSSI13dBm_PeerATT59dB_RSSI-45.7dBm_UDP  |  117 ++
 ttlog_BS1_SS1_CH21_QPSK1of2_TSSI13dBm_PeerATT63dB_RSSI-50.7dBm_UDP  |  115 +
 ttlog_BS1_SS1_CH21_QPSK1of2_TSSI13dBm_PeerATT68dB_RSSI-53.8dBm_UDP  |  114 +
 ttlog_BS1_SS1_CH21_QPSK1of2_TSSI13dBm_PeerATT72dB_RSSI-58.2dBm_UDP  |  115 +
 ttlog_BS1_SS1_CH21_QPSK1of2_TSSI13dBm_PeerATT74dB_RSSI-60.6dBm_UDP  |  114 +
 ttlog_BS1_SS1_CH21_QPSK1of2_TSSI13dBm_PeerATT75dB_RSSI-61.8dBm_UDP  |  114 +
 ttlog_BS1_SS1_CH21_QPSK1of2_TSSI13dBm_PeerATT76dB_RSSI-63.0dBm_UDP  |  112 +
 ttlog_BS1_SS1_CH21_QPSK1of2_TSSI13dBm_PeerATT77dB_RSSI-64.7dBm_UDP  |  112 +
 ttlog_BS1_SS1_CH21_QPSK1of2_TSSI13dBm_PeerATT78dB_RSSI-65.4dBm_UDP  |  113 +
 ttlog_BS1_SS1_CH21_QPSK1of2_TSSI13dBm_PeerATT80dB_RSSI-67.8dBm_UDP  |  125 ++
 ttlog_BS1_SS1_CH21_QPSK1of2_TSSI13dBm_PeerATT82dB_RSSI-69.1dBm_UDP  |  126 ++
 ttlog_BS1_SS1_CH21_QPSK1of2_TSSI13dBm_PeerATT83dB_RSSI-70.3dBm_UDP  |  126 ++
 ttlog_BS1_SS1_CH21_QPSK1of2_TSSI13dBm_PeerATT84dB_RSSI-71.0dBm_UDP  |  129 ++
 ttlog_BS1_SS1_CH21_QPSK1of2_TSSI13dBm_PeerATT85dB_RSSI-72.0dBm_UDP  |  165 ++
 ttlog_BS1_SS1_CH21_QPSK1of2_TSSI13dBm_PeerATT86dB_RSSI-73.0dBm_UDP  |  462 +++++++
 ttlog_BS1_SS1_CH21_QPSK3of4_TSSI13dBm_PeerATT51dB_RSSI-36.5dBm_UDP  |  102 +
 ttlog_BS1_SS1_CH21_QPSK3of4_TSSI13dBm_PeerATT54dB_RSSI-39.7dBm_UDP  |  103 +
 ttlog_BS1_SS1_CH21_QPSK3of4_TSSI13dBm_PeerATT59dB_RSSI-45.7dBm_UDP  |  103 +
 ttlog_BS1_SS1_CH21_QPSK3of4_TSSI13dBm_PeerATT63dB_RSSI-50.3dBm_UDP  |  103 +
 ttlog_BS1_SS1_CH21_QPSK3of4_TSSI13dBm_PeerATT68dB_RSSI-53.8dBm_UDP  |  102 +
 ttlog_BS1_SS1_CH21_QPSK3of4_TSSI13dBm_PeerATT72dB_RSSI-58.2dBm_UDP  |  103 +
 ttlog_BS1_SS1_CH21_QPSK3of4_TSSI13dBm_PeerATT74dB_RSSI-60.6dBm_UDP  |  103 +
 ttlog_BS1_SS1_CH21_QPSK3of4_TSSI13dBm_PeerATT75dB_RSSI-61.8dBm_UDP  |  102 +
 ttlog_BS1_SS1_CH21_QPSK3of4_TSSI13dBm_PeerATT76dB_RSSI-63.0dBm_UDP  |  101 +
 ttlog_BS1_SS1_CH21_QPSK3of4_TSSI13dBm_PeerATT78dB_RSSI-65.4dBm_UDP  |  101 +
 ttlog_BS1_SS1_CH21_QPSK3of4_TSSI13dBm_PeerATT80dB_RSSI-67.8dBm_UDP  |  101 +
 ttlog_BS1_SS1_CH21_QPSK3of4_TSSI13dBm_PeerATT82dB_RSSI-69.1dBm_UDP  |  102 +
 ttlog_BS1_SS1_CH21_QPSK3of4_TSSI13dBm_PeerATT83dB_RSSI-70.3dBm_UDP  |  115 +
 ttlog_BS1_SS1_CH21_QPSK3of4_TSSI13dBm_PeerATT84dB_RSSI-71.0dBm_UDP  |  220 +++
 ttlog_BS1_SS1_CH21_QPSK3of4_TSSI13dBm_PeerATT85dB_RSSI-72.0dBm_UDP  |  583 ++++++++++
 ttlog_BS1_SS1_CH23_QPSK3of4_TSSI13dBm_PeerATT51dB_RSSI-36.5dBm_UDP  |  107 +
 ttlog_BS1_SS1_CH23_QPSK3of4_TSSI13dBm_PeerATT54dB_RSSI-39.7dBm_UDP  |  102 +
 ttlog_BS1_SS1_CH23_QPSK3of4_TSSI13dBm_PeerATT59dB_RSSI-45.7dBm_UDP  |  103 +
 ttlog_BS1_SS1_CH23_QPSK3of4_TSSI13dBm_PeerATT63dB_RSSI-50.7dBm_UDP  |  103 +
 ttlog_BS1_SS1_CH23_QPSK3of4_TSSI13dBm_PeerATT68dB_RSSI-53.8dBm_UDP  |  103 +
 ttlog_BS1_SS1_CH23_QPSK3of4_TSSI13dBm_PeerATT72dB_RSSI-58.2dBm_UDP  |  103 +
 ttlog_BS1_SS1_CH23_QPSK3of4_TSSI13dBm_PeerATT74dB_RSSI-60.6dBm_UDP  |  102 +
 ttlog_BS1_SS1_CH23_QPSK3of4_TSSI13dBm_PeerATT76dB_RSSI-63.0dBm_UDP  |  100 +
 ttlog_BS1_SS1_CH23_QPSK3of4_TSSI13dBm_PeerATT78dB_RSSI-65.4dBm_UDP  |  103 +
 ttlog_BS1_SS1_CH23_QPSK3of4_TSSI13dBm_PeerATT80dB_RSSI-67.8dBm_UDP  |  102 +
 ttlog_BS1_SS1_CH23_QPSK3of4_TSSI13dBm_PeerATT82dB_RSSI-69.1dBm_UDP  |  102 +
 ttlog_BS1_SS1_CH23_QPSK3of4_TSSI13dBm_PeerATT83dB_RSSI-70.3dBm_UDP  |  103 +
 ttlog_BS1_SS1_CH23_QPSK3of4_TSSI13dBm_PeerATT84dB_RSSI-71.0dBm_UDP  |  104 +
 ttlog_BS1_SS1_CH23_QPSK3of4_TSSI13dBm_PeerATT85dB_RSSI-72.0dBm_UDP  |  133 ++
 ttlog_BS1_SS1_CH23_QPSK3of4_TSSI13dBm_PeerATT86dB_RSSI-73.0dBm_UDP  |  464 +++++++
 ttlog_BS1_SS1_CH25_QPSK3of4_TSSI13dBm_PeerATT51dB_RSSI-36.5dBm_UDP  |  104 +
 ttlog_BS1_SS1_CH25_QPSK3of4_TSSI13dBm_PeerATT54dB_RSSI-39.7dBm_UDP  |  102 +
 ttlog_BS1_SS1_CH25_QPSK3of4_TSSI13dBm_PeerATT59dB_RSSI-45.7dBm_UDP  |  102 +
 ttlog_BS1_SS1_CH25_QPSK3of4_TSSI13dBm_PeerATT63dB_RSSI-50.7dBm_UDP  |  103 +
 ttlog_BS1_SS1_CH25_QPSK3of4_TSSI13dBm_PeerATT68dB_RSSI-53.8dBm_UDP  |  102 +
 ttlog_BS1_SS1_CH25_QPSK3of4_TSSI13dBm_PeerATT72dB_RSSI-58.2dBm_UDP  |  102 +
 ttlog_BS1_SS1_CH25_QPSK3of4_TSSI13dBm_PeerATT74dB_RSSI-60.6dBm_UDP  |  102 +
 ttlog_BS1_SS1_CH25_QPSK3of4_TSSI13dBm_PeerATT75dB_RSSI-61.8dBm_UDP  |  102 +
 ttlog_BS1_SS1_CH25_QPSK3of4_TSSI13dBm_PeerATT76dB_RSSI-63.0dBm_UDP  |  100 +
 ttlog_BS1_SS1_CH25_QPSK3of4_TSSI13dBm_PeerATT77dB_RSSI-64.7dBm_UDP  |  100 +
 ttlog_BS1_SS1_CH25_QPSK3of4_TSSI13dBm_PeerATT78dB_RSSI-65.4dBm_UDP  |  103 +
 ttlog_BS1_SS1_CH25_QPSK3of4_TSSI13dBm_PeerATT80dB_RSSI-67.8dBm_UDP  |  103 +
 ttlog_BS1_SS1_CH25_QPSK3of4_TSSI13dBm_PeerATT82dB_RSSI-69.1dBm_UDP  |  102 +
 ttlog_BS1_SS1_CH25_QPSK3of4_TSSI13dBm_PeerATT83dB_RSSI-70.3dBm_UDP  |  103 +
 ttlog_BS1_SS1_CH25_QPSK3of4_TSSI13dBm_PeerATT84dB_RSSI-71.0dBm_UDP  |  105 +
 ttlog_BS1_SS1_CH25_QPSK3of4_TSSI13dBm_PeerATT85dB_RSSI-72.0dBm_UDP  |  126 ++
 ttlog_BS1_SS1_CH25_QPSK3of4_TSSI13dBm_PeerATT86dB_RSSI-73.0dBm_UDP  |  385 ++++++
 ttlog_BS1_SS1_CH27_QPSK3of4_TSSI13dBm_PeerATT51dB_RSSI-36.5dBm_UDP  |  102 +
 ttlog_BS1_SS1_CH27_QPSK3of4_TSSI13dBm_PeerATT54dB_RSSI-39.7dBm_UDP  |  102 +
 ttlog_BS1_SS1_CH27_QPSK3of4_TSSI13dBm_PeerATT59dB_RSSI-45.7dBm_UDP  |  103 +
 ttlog_BS1_SS1_CH27_QPSK3of4_TSSI13dBm_PeerATT63dB_RSSI-50.7dBm_UDP  |  103 +
 ttlog_BS1_SS1_CH27_QPSK3of4_TSSI13dBm_PeerATT68dB_RSSI-53.8dBm_UDP  |  103 +
 ttlog_BS1_SS1_CH27_QPSK3of4_TSSI13dBm_PeerATT72dB_RSSI-58.2dBm_UDP  |  102 +
 ttlog_BS1_SS1_CH27_QPSK3of4_TSSI13dBm_PeerATT74dB_RSSI-60.6dBm_UDP  |  102 +
 ttlog_BS1_SS1_CH27_QPSK3of4_TSSI13dBm_PeerATT75dB_RSSI-61.8dBm_UDP  |  103 +
 ttlog_BS1_SS1_CH27_QPSK3of4_TSSI13dBm_PeerATT76dB_RSSI-63.0dBm_UDP  |  101 +
 ttlog_BS1_SS1_CH27_QPSK3of4_TSSI13dBm_PeerATT78dB_RSSI-65.4dBm_UDP  |  101 +
 ttlog_BS1_SS1_CH27_QPSK3of4_TSSI13dBm_PeerATT80dB_RSSI-67.8dBm_UDP  |  101 +
 ttlog_BS1_SS1_CH27_QPSK3of4_TSSI13dBm_PeerATT82dB_RSSI-69.1dBm_UDP  |  101 +
 ttlog_BS1_SS1_CH27_QPSK3of4_TSSI13dBm_PeerATT83dB_RSSI-70.3dBm_UDP  |  101 +
 ttlog_BS1_SS1_CH27_QPSK3of4_TSSI13dBm_PeerATT84dB_RSSI-71.0dBm_UDP  |  103 +
 ttlog_BS1_SS1_CH27_QPSK3of4_TSSI13dBm_PeerATT85dB_RSSI-72.0dBm_UDP  |  116 +
 ttlog_BS1_SS1_CH27_QPSK3of4_TSSI13dBm_PeerATT86dB_RSSI-73.0dBm_UDP  |  329 +++++
 ttlog_SS1_BS1_CH21_16QAM1of2_TSSI13dBm_PeerATT51dB_RSSI-36.5dBm_UDP |  126 ++
 ttlog_SS1_BS1_CH21_16QAM1of2_TSSI13dBm_PeerATT54dB_RSSI-39.7dBm_UDP |  127 ++
 ttlog_SS1_BS1_CH21_16QAM1of2_TSSI13dBm_PeerATT59dB_RSSI-45.7dBm_UDP |  126 ++
 ttlog_SS1_BS1_CH21_16QAM1of2_TSSI13dBm_PeerATT63dB_RSSI-50.7dBm_UDP |  127 ++
 ttlog_SS1_BS1_CH21_16QAM1of2_TSSI13dBm_PeerATT68dB_RSSI-53.8dBm_UDP |  126 ++
 ttlog_SS1_BS1_CH21_16QAM1of2_TSSI13dBm_PeerATT72dB_RSSI-58.2dBm_UDP |  126 ++
 ttlog_SS1_BS1_CH21_16QAM1of2_TSSI13dBm_PeerATT74dB_RSSI-60.6dBm_UDP |  126 ++
 ttlog_SS1_BS1_CH21_16QAM1of2_TSSI13dBm_PeerATT75dB_RSSI-61.8dBm_UDP |  127 ++
 ttlog_SS1_BS1_CH21_16QAM1of2_TSSI13dBm_PeerATT76dB_RSSI-63.0dBm_UDP |  127 ++
 ttlog_SS1_BS1_CH21_16QAM1of2_TSSI13dBm_PeerATT77dB_RSSI-64.7dBm_UDP |  129 ++
 ttlog_SS1_BS1_CH21_16QAM1of2_TSSI13dBm_PeerATT78dB_RSSI-65.4dBm_UDP |  128 ++
 ttlog_SS1_BS1_CH21_16QAM1of2_TSSI13dBm_PeerATT80dB_RSSI-67.8dBm_UDP |  127 ++
 ttlog_SS1_BS1_CH21_16QAM1of2_TSSI13dBm_PeerATT82dB_RSSI-69.1dBm_UDP |  127 ++
 ttlog_SS1_BS1_CH21_16QAM1of2_TSSI13dBm_PeerATT83dB_RSSI-70.3dBm_UDP |  127 ++
 ttlog_SS1_BS1_CH21_16QAM1of2_TSSI13dBm_PeerATT84dB_RSSI-71.0dBm_UDP |  128 ++
 ttlog_SS1_BS1_CH21_16QAM1of2_TSSI13dBm_PeerATT85dB_RSSI-72.0dBm_UDP |  138 ++
 ttlog_SS1_BS1_CH21_16QAM1of2_TSSI13dBm_PeerATT86dB_RSSI-73.0dBm_UDP |  282 ++++
 ttlog_SS1_BS1_CH21_16QAM3of4_TSSI13dBm_PeerATT51dB_RSSI-36.5dBm_UDP |  114 +
 ttlog_SS1_BS1_CH21_16QAM3of4_TSSI13dBm_PeerATT54dB_RSSI-39.7dBm_UDP |  115 +
 ttlog_SS1_BS1_CH21_16QAM3of4_TSSI13dBm_PeerATT59dB_RSSI-45.7dBm_UDP |  115 +
 ttlog_SS1_BS1_CH21_16QAM3of4_TSSI13dBm_PeerATT63dB_RSSI-50.7dBm_UDP |  127 ++
 ttlog_SS1_BS1_CH21_16QAM3of4_TSSI13dBm_PeerATT68dB_RSSI-53.8dBm_UDP |  115 +
 ttlog_SS1_BS1_CH21_16QAM3of4_TSSI13dBm_PeerATT72dB_RSSI-58.2dBm_UDP |  114 +
 ttlog_SS1_BS1_CH21_16QAM3of4_TSSI13dBm_PeerATT74dB_RSSI-60.6dBm_UDP |  115 +
 ttlog_SS1_BS1_CH21_16QAM3of4_TSSI13dBm_PeerATT75dB_RSSI-61.8dBm_UDP |  115 +
 ttlog_SS1_BS1_CH21_16QAM3of4_TSSI13dBm_PeerATT76dB_RSSI-63.0dBm_UDP |  116 +
 ttlog_SS1_BS1_CH21_16QAM3of4_TSSI13dBm_PeerATT78dB_RSSI-65.4dBm_UDP |  115 +
 ttlog_SS1_BS1_CH21_16QAM3of4_TSSI13dBm_PeerATT80dB_RSSI-67.8dBm_UDP |  114 +
 ttlog_SS1_BS1_CH21_16QAM3of4_TSSI13dBm_PeerATT82dB_RSSI-69.1dBm_UDP |  116 +
 ttlog_SS1_BS1_CH21_16QAM3of4_TSSI13dBm_PeerATT83dB_RSSI-70.3dBm_UDP |  123 ++
 ttlog_SS1_BS1_CH21_16QAM3of4_TSSI13dBm_PeerATT84dB_RSSI-71.0dBm_UDP |  144 ++
 ttlog_SS1_BS1_CH21_16QAM3of4_TSSI13dBm_PeerATT85dB_RSSI-72.0dBm_UDP |  352 ++++++
 ttlog_SS1_BS1_CH21_BPSK1of2_TSSI13dBm_PeerATT51dB_RSSI-36.5dBm_TCP  |   95 +
 ttlog_SS1_BS1_CH21_BPSK1of2_TSSI13dBm_PeerATT54dB_RSSI-39.7dBm_TCP  |   95 +
 ttlog_SS1_BS1_CH21_BPSK1of2_TSSI13dBm_PeerATT59dB_RSSI-45.7dBm_TCP  |   99 +
 ttlog_SS1_BS1_CH21_BPSK1of2_TSSI13dBm_PeerATT63dB_RSSI-50.7dBm_TCP  |   97 +
 ttlog_SS1_BS1_CH21_BPSK1of2_TSSI13dBm_PeerATT68dB_RSSI-53.8dBm_TCP  |   83 +
 ttlog_SS1_BS1_CH21_BPSK1of2_TSSI13dBm_PeerATT72dB_RSSI-58.2dBm_TCP  |  100 +
 ttlog_SS1_BS1_CH21_BPSK1of2_TSSI13dBm_PeerATT74dB_RSSI-60.6dBm_TCP  |  100 +
 ttlog_SS1_BS1_CH21_BPSK1of2_TSSI13dBm_PeerATT75dB_RSSI-61.8dBm_TCP  |  100 +
 ttlog_SS1_BS1_CH21_BPSK1of2_TSSI13dBm_PeerATT76dB_RSSI-63.0dBm_TCP  |  223 +++
 ttlog_SS1_BS1_CH21_BPSK1of2_TSSI13dBm_PeerATT78dB_RSSI-65.4dBm_TCP  |  228 +++
 ttlog_SS1_BS1_CH21_BPSK1of2_TSSI13dBm_PeerATT80dB_RSSI-67.8dBm_TCP  |  227 +++
 ttlog_SS1_BS1_CH21_BPSK1of2_TSSI13dBm_PeerATT82dB_RSSI-69.1dBm_TCP  |  221 +++
 ttlog_SS1_BS1_CH21_BPSK1of2_TSSI13dBm_PeerATT83dB_RSSI-70.3dBm_TCP  |  129 ++
 ttlog_SS1_BS1_CH21_BPSK1of2_TSSI13dBm_PeerATT84dB_RSSI-71.0dBm_TCP  |  125 ++
 ttlog_SS1_BS1_CH21_BPSK1of2_TSSI13dBm_PeerATT85dB_RSSI-72.0dBm_TCP  |  136 ++
 ttlog_SS1_BS1_CH21_BPSK1of2_TSSI13dBm_PeerATT86dB_RSSI-73.0dBm_TCP  |  302 +++++
 ttlog_SS1_BS1_CH21_BPSK3of4_TSSI13dBm_PeerATT51dB_RSSI-36.5dBm_TCP  |  111 +
 ttlog_SS1_BS1_CH21_BPSK3of4_TSSI13dBm_PeerATT51dB_RSSI-36.5dBm_UDP  |   98 +
 ttlog_SS1_BS1_CH21_BPSK3of4_TSSI13dBm_PeerATT54dB_RSSI-39.7dBm_UDP  |   97 +
 ttlog_SS1_BS1_CH21_BPSK3of4_TSSI13dBm_PeerATT59dB_RSSI-45.7dBm_UDP  |   92 +
 ttlog_SS1_BS1_CH21_BPSK3of4_TSSI13dBm_PeerATT63dB_RSSI-50.7dBm_UDP  |   96 +
 ttlog_SS1_BS1_CH21_BPSK3of4_TSSI13dBm_PeerATT68dB_RSSI-53.8dBm_UDP  |   97 +
 ttlog_SS1_BS1_CH21_BPSK3of4_TSSI13dBm_PeerATT72dB_RSSI-58.2dBm_UDP  |   96 +
 ttlog_SS1_BS1_CH21_BPSK3of4_TSSI13dBm_PeerATT74dB_RSSI-60.6dBm_UDP  |   94 +
 ttlog_SS1_BS1_CH21_BPSK3of4_TSSI13dBm_PeerATT75dB_RSSI-61.8dBm_UDP  |   96 +
 ttlog_SS1_BS1_CH21_BPSK3of4_TSSI13dBm_PeerATT76dB_RSSI-63.0dBm_UDP  |   98 +
 ttlog_SS1_BS1_CH21_BPSK3of4_TSSI13dBm_PeerATT78dB_RSSI-65.4dBm_UDP  |  103 +
 ttlog_SS1_BS1_CH21_BPSK3of4_TSSI13dBm_PeerATT80dB_RSSI-67.8dBm_UDP  |  107 +
 ttlog_SS1_BS1_CH21_BPSK3of4_TSSI13dBm_PeerATT82dB_RSSI-69.1dBm_UDP  |  107 +
 ttlog_SS1_BS1_CH21_BPSK3of4_TSSI13dBm_PeerATT83dB_RSSI-70.3dBm_UDP  |  106 +
 ttlog_SS1_BS1_CH21_BPSK3of4_TSSI13dBm_PeerATT84dB_RSSI-71.0dBm_UDP  |  115 +
 ttlog_SS1_BS1_CH21_BPSK3of4_TSSI13dBm_PeerATT85dB_RSSI-72.0dBm_UDP  |  185 +++
 ttlog_SS1_BS1_CH21_QPSK1of2_TSSI13dBm_PeerATT51dB_RSSI-36.5dBm_UDP  |  114 +
 ttlog_SS1_BS1_CH21_QPSK1of2_TSSI13dBm_PeerATT54dB_RSSI-39.7dBm_UDP  |  114 +
 ttlog_SS1_BS1_CH21_QPSK1of2_TSSI13dBm_PeerATT59dB_RSSI-45.7dBm_UDP  |  114 +
 ttlog_SS1_BS1_CH21_QPSK1of2_TSSI13dBm_PeerATT63dB_RSSI-50.7dBm_UDP  |  114 +
 ttlog_SS1_BS1_CH21_QPSK1of2_TSSI13dBm_PeerATT68dB_RSSI-53.8dBm_UDP  |  114 +
 ttlog_SS1_BS1_CH21_QPSK1of2_TSSI13dBm_PeerATT72dB_RSSI-58.2dBm_UDP  |  114 +
 ttlog_SS1_BS1_CH21_QPSK1of2_TSSI13dBm_PeerATT74dB_RSSI-60.6dBm_UDP  |  115 +
 ttlog_SS1_BS1_CH21_QPSK1of2_TSSI13dBm_PeerATT75dB_RSSI-61.8dBm_UDP  |  114 +
 ttlog_SS1_BS1_CH21_QPSK1of2_TSSI13dBm_PeerATT76dB_RSSI-63.0dBm_UDP  |  116 +
 ttlog_SS1_BS1_CH21_QPSK1of2_TSSI13dBm_PeerATT77dB_RSSI-64.7dBm_UDP  |  120 ++
 ttlog_SS1_BS1_CH21_QPSK1of2_TSSI13dBm_PeerATT78dB_RSSI-65.4dBm_UDP  |  119 ++
 ttlog_SS1_BS1_CH21_QPSK1of2_TSSI13dBm_PeerATT80dB_RSSI-67.8dBm_UDP  |  120 ++
 ttlog_SS1_BS1_CH21_QPSK1of2_TSSI13dBm_PeerATT82dB_RSSI-69.1dBm_UDP  |  120 ++
 ttlog_SS1_BS1_CH21_QPSK1of2_TSSI13dBm_PeerATT83dB_RSSI-70.3dBm_UDP  |  122 ++
 ttlog_SS1_BS1_CH21_QPSK1of2_TSSI13dBm_PeerATT84dB_RSSI-71.0dBm_UDP  |  135 ++
 ttlog_SS1_BS1_CH21_QPSK1of2_TSSI13dBm_PeerATT85dB_RSSI-72.0dBm_UDP  |  304 +++++
 ttlog_SS1_BS1_CH21_QPSK1of2_TSSI13dBm_PeerATT86dB_RSSI-73.0dBm_UDP  |  279 ++++
 ttlog_SS1_BS1_CH21_QPSK3of4_TSSI13dBm_PeerATT51dB_RSSI-36.5dBm_UDP  |  103 +
 ttlog_SS1_BS1_CH21_QPSK3of4_TSSI13dBm_PeerATT54dB_RSSI-39.7dBm_UDP  |  104 +
 ttlog_SS1_BS1_CH21_QPSK3of4_TSSI13dBm_PeerATT59dB_RSSI-45.7dBm_UDP  |  103 +
 ttlog_SS1_BS1_CH21_QPSK3of4_TSSI13dBm_PeerATT63dB_RSSI-50.7dBm_UDP  |  103 +
 ttlog_SS1_BS1_CH21_QPSK3of4_TSSI13dBm_PeerATT68dB_RSSI-53.8dBm_UDP  |  103 +
 ttlog_SS1_BS1_CH21_QPSK3of4_TSSI13dBm_PeerATT72dB_RSSI-58.2dBm_UDP  |  103 +
 ttlog_SS1_BS1_CH21_QPSK3of4_TSSI13dBm_PeerATT74dB_RSSI-60.6dBm_UDP  |  103 +
 ttlog_SS1_BS1_CH21_QPSK3of4_TSSI13dBm_PeerATT75dB_RSSI-61.8dBm_UDP  |  105 +
 ttlog_SS1_BS1_CH21_QPSK3of4_TSSI13dBm_PeerATT76dB_RSSI-63.0dBm_UDP  |  104 +
 ttlog_SS1_BS1_CH21_QPSK3of4_TSSI13dBm_PeerATT78dB_RSSI-65.4dBm_UDP  |  104 +
 ttlog_SS1_BS1_CH21_QPSK3of4_TSSI13dBm_PeerATT80dB_RSSI-67.8dBm_UDP  |  104 +
 ttlog_SS1_BS1_CH21_QPSK3of4_TSSI13dBm_PeerATT82dB_RSSI-69.1dBm_UDP  |  104 +
 ttlog_SS1_BS1_CH21_QPSK3of4_TSSI13dBm_PeerATT83dB_RSSI-70.3dBm_UDP  |  105 +
 ttlog_SS1_BS1_CH21_QPSK3of4_TSSI13dBm_PeerATT84dB_RSSI-71.0dBm_UDP  |  112 +
 ttlog_SS1_BS1_CH21_QPSK3of4_TSSI13dBm_PeerATT85dB_RSSI-72.0dBm_UDP  |  244 ++++
 226 files changed, 29677 insertions(+)

なんてこった．死ぬるな，これは． :DDD
[ZOMG, holly shit. :DDD]

do_imp(PJITTER); relaod(p_shippo);

今日は劣悪な無線伝送路越しから確実にログファイルを回収する為の
俺様アクセス制御を再考し．結局，最大値を指定可能な疑似ジッタ付
加で良いやー，って事でサクっとインプリ完了．
月曜日にまた現地に出張って終われば良いなーとか妄想中．
[Today, I pondered a pseudo userland MAC to get some log files
over a low-link-quality wireless medium. Finally, I've implemented
it w/ maximum delay restricted pseudo-jitter retrying.
Umm, I'd have to go t3h customer's lab to adj that implementation
again.]

そうそう，このプロジェクトP4が延びに延びた為か，しっぽが再生
してしまいました． :P
['Kay. This project P4's progess delays make my shippo reload, LOL. :P]

wc -l XXXXwrapper

ユーザーランドのSMEと称してPCI LB経由でHardMAC内部のレジ
スタを直にモニョれる様に改造したnet-wireless/wireless-tools
を使いまくって，sh(1p)+sed(1p)+awk(1p)なのに蝶unportable
なinitスクリプト作成中． :P
[Due to with modified net-wireless/wireless-tools which can
handle raw HardMAC register operation via PCI LB, t3h init script
as userland SME which I'm coding is really unportable even if it
only uses sh(1p), sed(1p) and awk(1p)． :P]

なんか1300 SLOCを超えているんですが，罠ですか？
そうですか． :DDD
[Well, it's over 1300 physical SLOC though. I'd heve to say "O RLY?"
and "YA RLY!" :DDD]

oldlibc.float.karma--; netdev.watchdog.karma--;

TSSIのRSSIへの回り込みはAGCのステートマシンをムニョって誤摩化した．
が，新たに二つ問題が発生．一つは解決済み，一つは原因を調査中．
[T3h TSSI/RSSI mixing issue, I worked around it by modifed FSM of AGC.
Meh, 2 new PITAs commin'. One of these were fixed, another one's progress
is still incestigating.]

前者は古いlibcをSH4なんつーマイナーなアーキテクチャで使用している為，
floatな演算が全部死んでいると言う悪夢．struct timevalの精度がusなので，
適当に10^6倍して整数で計算すると言うチキンな逃げもあったが，SoftFloat
をstdint.hでportしたブツでモニョった．Softfloatのライセンスに限ったモノ
でもないけれど，ライセンス云々はWTFPL以外ヨクワカンランし，詳細を
理解する気もあんまり無いので，後で叩かれない様にportしたブツはこの辺
に晒しておく．
[Former is due to old libc on SH4, a minor arch. It results nightmate of totally
invalid floating point arithmetic operation. As you know, resolution of struct
timeval is us, so in my case, to x10^6 w/ integer operation is enough to work
around this crap, how chicken though. To be no chicken is better I thought,
then I've poked it w/ SoftFloat portion w/ stdint.h. Any license is not easy to
understand its detail, except WTFPL IMHO. To prevant license violation, t3h
portion of SoftFloat is stuffed here.]

後者はSoftMACがnetdev watchdogなtransmission timeoutになる事．
多分，PCI DMA関連がハードもソフトも腐っているからだろうけど，
取り敢えず，要調査．
[Latter is a SoftMAC issue about netdev watchdog transmission faults
due to its timeout. Guess b/c PCI DMA's software/hardware suck0rz.
Anyway I'll fix ASAP.]

#if DUMB_RF_CHIP #include <tssi.h> #endif

"ごーるでんうぃーく"後半，しゅーりょー．
結局，

• 400ml献血．
  前と検査方法がちと変わっていた．


• ALSA AOAをムニャるが，ダメっぽい．
  さすがflameeyes様，release candidateでもなんともならんぜよ． :DDD
  gcc-4.1.2で-Osなんぞかましているからかもしれん．


• 土曜日の明け方に寝たら，日曜日の夜に起きたので，
  Overlayおよび~arch化は依然放置プレイ中． :P

つー感じでした．
[Last half of GW was over.

• 400ml blood donated.
  T3h test method has been changed.


• ALSA AOA still rock0rz.
  Gosh flameeyes, any release candidate won't help. :DDD
  Guess gcc-4.1.2 + -Os breaks some core stuffs?


• Went to bed at dawn of Sat, awaked at night of Sun.
  So Overlay and ~arch-nize has little progress. :P

]

で，次期AGCのコアとなる有理数型演算マクロを土日に寝ながら妄想．
やっぱ徐算が問題，ニュートン-ラプソン法+二進約分で何とかなるかな？
[Then, I thought some idea of next AGC core, rational OPs' macro in
my sleep. Yup, DIV may be kinda PITA, Newton-Raphson method +
binary reduction may help, or?]

で，SoftMACでOOPSしない様に負荷をかけつつ，HardMACをオシロや
ロジアナでムニャへニャすると，TSSIがRSSIに回り込んでいる事が発覚．
そこで回り込みですか，まじか． :(((
[So, I've continue the HardMAC stress test w/ oscilloscope and logic
analyzer. Blah, RSSI includes TSSI... Ugh, dumb fall through, ZOMG. :(((]

grabOOPS(&DMARBuf) ? DMARBuf.karma-- : DMARBuf.karma++;

"ごーるでんうぃーく"前半も終了しましたが如何がお過ごしでしょうか？
[Half of GW was over, sup ppl?]

受信側PHY下位層のゲイン調整マクロAGCの内部のステートマシンを修正．
送受信PHY下位層の直交変調復調マクロMODU/DMODUのオーバーフローを処理．
受信側PHY内部の周波数誤差補正マクロAFCのオーバーフローを処理．
送受信PHY内部のIFFT/FFTマクロのゲインを調整．
HARD_MAC/PHY間のインターフェースマクロMACIFを修正．
PCI LB/HARD_MAC間のインターフェースマクロBA_BUS_ADPを修正．
その他，色々．
[Under reception PHY, fix0rz FSM of AGC.
Under transmission/reception PHY, purge0rz OVR of MODU/DMODU.
Inside reception PHY, fix0rz OVR of AFC.
Inside transmission/reception PHY, tune0rz gain of IFFT/FFT.
Boundary of HARD_MAC/PHY, fix0rz semantics of MACIF.
Boundary of HARD_MAC, fix0rz semantics of BA_BUS_ADP.
Blah, blah, blah.]

で，やっとこさ，SoftMAC側の負荷試験が出来るなーとか思いつつ，
おもむろに"ping -f"とか"ping -s"を実行．
SoftMAC内部のPCI DMAのリングバッファがOOPSするbugが発覚．
そこでOOPSですか，まじか． :(((
[K, It's time of SoftMAC stress test.
"ping -f" and "ping -s" really sound rock.
T3h PCI DMA ring buffer sez OOPS.
Well, OOPS? O RLY? :(((]

最近，土日も関係無く仕事で，"ごーるでんうぃーく"前半をアレな感じで
フル出場してしまったので，「お前，休めよ」とボスからも"待った"を入れられる．
そこで強制休暇ですか，まじか． :DDD
[Meh, so half of GW was over now, kinda sucks.
My boss sez "U must have hols".
Well, U force me? O RLY? :DDD]

以下，"ごーるでんうぃーく"後半のTODO．

• 献血する


• ALSA AOAが死ぬのでムニャる


• 放置プレイしていたOverlayをモニョる


• ~archな先っぽでヘニャる

[Here is TODO of my last half of GW.

• blood donation


• Fix ALSA AOA


• Update my Overlay


• Play w/ ~arch

]

SIGERRFREE

祝エラーフリー，BER < 10^-7 @ 16QAM 3/4． :DDD
[LOL, SIGERRFREE now. BER < 10^-7 @ 16QAM 3/4. :DDD]

が，受信側PHY下位層のCCAに自分の送信信号が引っかかる問題が発覚．
そう言えば，送信側PHY下位層のステートマシンとこの部分のステートマシン，
別々だった．エレガントに修正しようとした所，ボスに割り込みをかけられ，
モチベーション低下． :(((
[Oh wait. CCA of under-layer than RX PHY sometimes mis-detects
own TX signal as others'. Hmm, FSM in the macros of under-layer than
TX PHY is isolated from under-layer than RX PHY's, ZOMG. I'd have to
fix it ASAP though my boss interrupts my fix0rz, dunno why...]

なので月末恒例の社内飲み会でコーラをがぶ飲みして，修正は明日にして
帰って来た．ゴールデンウィーク？知らんな，そんなもん． :P
[Blah, it drains my motivation completely. So I scored Coke at where t3h
monthly NomiKai b/c mark this bug LATER. I'll fix it tomorrow.
Eh, golden week? I dunno that craps. :P]

修正：b/c typos :P
[FIX: b/c typos :P]

DiffStat(pRepo, rc31, rc32);

今日の分．
入出力レイテンシを考慮して，無効な出力を禁止する処理を追加．
内部及び出力オーバフロー処理を追加して，一部ユニティゲインを調整．
firmwareにする為にISEでムニョらせて只今絶賛放置プレイ中． :P
[Here's today's one.
Reconsider input to output latencies, then make it inhibit invalid output.
Fix for internal and external overflow ceiling/flooring w/ tuning t3h
unity gain. To convert it to firmware needs to do it w/ retarded ISE craps. :P]

 bench/DUMB_RF.vhd  |   17 ++-
 vhdl/AGC_CA.vhd    |    6 -
 vhdl/AGC_FA.vhd    |  269 ++++++++++++++++++++++++++---------------------------
 vhdl/DMFx8.vhd     |    9 +
 vhdl/IPFx8.vhd     |    2 
 vhdl/PWRC.vhd      |   32 +++---
 vhdl/QDM_BPF.vhd   |   10 +
 vhdl/UGT.vhd       |   27 ++++-
 vhdl/UND_BLOCK.vhd |  124 ++++++++++++------------
 vhdl/UNI_BLOCK.vhd |   90 ++++++++---------
 vhdl/UNP_BLOCK.vhd |   54 ++++++----
 11 files changed, 337 insertions(+), 303 deletions(-)

AGCをモニョる事が出来る人間が居ないらしいので，
何故か次のブツのAGCも担当する事になっているっぽい．
ゲイン調整をする事自体が目的ではないので行列計算が出来る位，
ハードウェア側にリソースは与えられないし，PIDはそろそろ飽きた．
昔，スライディングモード制御をヘニョった記憶があるので，
有理数型のスライディングモード制御マクロとかで． :P
[TTT, b/c there is no one who can treat AGC ATM, I'd have to do it
for next project as well. IRL, tunig RF/IF bound gain is not main
propose of the project. Yup, matrix OPs capable resource is not available
and tuning PID paramter is bit of dull. IIRC, I've poked sliding mode
control method. So rational arithmetic sliding mode control macro
is a way to go? :P]

DiffStat(pRepo, beta16, rc31);

前回からのdiffstat．
相変わらず安定しない．．．． :P
[Here's diffstat from previous post.
Hmm, it's kinda unstable code... :P]

 a/vhdl/CCAD.vhd            |  116 -----
 a/vhdl/LOCKD.vhd           |   68 ---
 b/vhdl/DMFx2.vhd           |  112 +++++
 b/vhdl/DMFx8.vhd           |  112 +++++
 b/vhdl/IPFx2.vhd           |  114 +++++
 b/vhdl/IPFx8.vhd           |  114 +++++
 b/vhdl/PLSEXPI.vhd         |  104 ++++
 b/vhdl/QDM_BPF.vhd         |  134 ++++++
 b/vhdl/QM_BPF.vhd          |  143 ++++++
 bench/BENCH_AUGT.vhd       |   56 ++
 bench/BENCH_MODU_DMODU.vhd |   99 ++--
 bench/BENCH_UNPID.vhd      |   60 +-
 bench/DUMB_RF.vhd          |  143 +++++-
 bench/STA.vhd              |   24 -
 bench/STA2STA.vhd          |   12 
 vhdl/AAO_UGT.vhd           |  120 ++---
 vhdl/AGCSTM.vhd            |  441 +++++++++++++------
 vhdl/AGC_CA.vhd            |   71 +--
 vhdl/AGC_FA.vhd            |  119 +++--
 vhdl/AGC_NG.vhd            |  292 ++++++++++---
 vhdl/AUGT.vhd              |   52 +-
 vhdl/DC_BLOCK.vhd          |   51 +-
 vhdl/DMODU.vhd             |  405 ++++--------------
 vhdl/FFT.vhd               |   20 
 vhdl/FPGA1.vhd             |  192 ++++----
 vhdl/FPGA2.vhd             |  999 +++++++++++++++++++++++++++------------------
 vhdl/GPS3_U301.vhd         |   62 ++
 vhdl/GPS3_U801.vhd         |   76 ++-
 vhdl/HARD_MAC.vhd          |    8 
 vhdl/MODU.vhd              |  600 ++++-----------------------
 vhdl/MONSEL1.vhd           |  106 ++--
 vhdl/MONSEL2.vhd           |  496 ++++++++++++----------
 vhdl/NCDLY.vhd             |   36 -
 vhdl/PHY.vhd               |   43 +
 vhdl/PWRC.vhd              |  202 +++++----
 vhdl/ROUND.vhd             |   76 +--
 vhdl/RSSIC.vhd             |   72 ++-
 vhdl/RSSI_AGC.vhd          |  574 ++++++++++++-------------
 vhdl/RX_BBP.vhd            |  405 +++++++++++-------
 vhdl/SYNC_MA.vhd           |   54 +-
 vhdl/TX_BBP.vhd            |  130 ++---
 vhdl/UGT.vhd               |   74 +--
 vhdl/UND_BLOCK.vhd         |   95 ++--
 vhdl/UNI_BLOCK.vhd         |  103 ++--
 vhdl/UNP_BLOCK.vhd         |   28 -
 vhdl/VECTOR.vhd            |   74 ++-
 vhdl/btfly.vhd             |   27 +
 vhdl/outputIF.vhd          |  301 ++++++++-----
 48 files changed, 4517 insertions(+), 3298 deletions(-)

GentooJP.NomiKai++; /* URakuChou */

ナニのついでに有楽町で飲み会．
以下，技術的有用性皆無なメモ．

• 焼き鳥のガツは胃袋．
• パチンコの必勝法は店員と仲良くなる事だが，賭け事はマルチンゲール也．
• "ナガシ"の管理者とかカッコ良さ気．

[NomiKai at URakuChou.
Here is my useless memo.

• T3h "Gatsu" means tripe in YakiTori world.
• A winning strategy Pachinko is to get friendly the stuff, but all gamble is based on martingale.
• Admin of "Nagasi" sounds rock0rz.

]

午前中と飲みが終わってから日付が変わるまで会社にてAGCのパラメータ調整．
-30dBmから-65dBmまで受信したっぽいが，同期検出の相関値に問題有り．
明日，と言うか今日も出社予定也． :P
[This AM and after the Nomikai, I've poke some AGC parameters.
Its reception functionality is now capable of -30dBm to -65dBm as dynamic range.
But yes, it has a PITA WRT sync timing detection's correlation function's value.
SIGNEEDSTOFIX.]

DiffStat(pRepo, rc15, beta16);

あー，3/28に間に合わせる予定がー． :(((
SoftMACの方は終わっているのに，HardMACがまだまだ低品質．
で，今日までの分．
[ZOMG, 3/28, t3h date expired. :(((
SoftMAC is WORKSFORME, HardMAC is still b0rked.
Then, here's diffstat of rc15 to beta16.]

 b/vhdl/AGC_CA.vhd   |  137 +++++++++++++++++++++++++
 b/vhdl/AGC_FA.vhd   |  279 +++++++++++++++++++++++++++++++++++++++++++++++++++
 b/vhdl/SYNC_MA.vhd  |   94 +++++++++++++++++
 bench/DUMB_RF.vhd   |   16 ++
 vhdl/AAO_UGT.vhd    |   13 +-
 vhdl/AGC_NG.vhd     |   57 +++++++++-
 vhdl/AUGT.vhd       |   11 +-
 vhdl/FPGA2.vhd      |   37 ++++--
 vhdl/NCDLY.vhd      |   70 ++++++++----
 vhdl/PHY.vhd        |    9 +
 vhdl/PWRC.vhd       |  177 ++++++++++++++++++++++++--------
 vhdl/RSSIC.vhd      |  283 +++++++++++++++++++++++++---------------------------
 vhdl/RSSI_AGC.vhd   |    5 
 vhdl/RX_BBP.vhd     |   63 ++++++-----
 vhdl/RX_IOBlock.vhd |   13 +-
 vhdl/TX_BBP.vhd     |   21 ++-
 vhdl/UGT.vhd        |   76 +++++++------
 vhdl/UND_BLOCK.vhd  |   35 +++---
 vhdl/UNI_BLOCK.vhd  |   73 ++++++-------
 vhdl/UNP_BLOCK.vhd  |   74 +++++++------
 20 files changed, 1135 insertions(+), 408 deletions(-)

土日でどれ位ヤレるのかが勝負．:P
[Sat/Sun. Am I ready to ride'on kamikaze, this spring storm. :P]

DiffStat(pRepo, rc14, rc15);

ホンマモンのhot codeって，やっぱdiffだと思うのですよ，ハイ．
つー訳で，現在release candidateしまくりな例のrepositoryで約一週間分
に相当する1.0_rc15 - 1.0_rc14．
[Yup, t3h real hot code means the diff, I thought. So, here is a diffstat
from the repository between 1.0_rc14 and 1.0_rc15, it's about 1 week or so.]

 a/vhdl/AGC.vhd             |  203 -----------------
 a/vhdl/PIDCONT.vhd         |  265 -----------------------
 a/vhdl/RSSICONV.vhd        |   78 ------
 b/bench/BENCH_AUGT.vhd     |  106 +++++++++
 b/bench/BENCH_UNPID.vhd    |  231 ++++++++++++++++++++
 b/vhdl/AAO_UGT.vhd         |  159 +++++++++++++
 b/vhdl/AGCSTM.vhd          |  211 ++++++++++++++++++
 b/vhdl/AGC_NG.vhd          |  465 ++++++++++++++++++++++++++++++++++++++++
 b/vhdl/AUGT.vhd            |  195 +++++++++++++++++
 b/vhdl/UND_BLOCK.vhd       |  153 +++++++++++++
 b/vhdl/UNI_BLOCK.vhd       |  156 +++++++++++++
 b/vhdl/UNP_BLOCK.vhd       |   97 ++++++++
 bench/BENCH_MODU_DMODU.vhd |   67 +++--
 vhdl/CCAD.vhd              |   91 ++++++-
 vhdl/FPGA1.vhd             |   28 +-
 vhdl/FPGA2.vhd             |  400 ++++++++++++++++++-----------------
 vhdl/GPS3_U301.vhd         |   61 +++--
 vhdl/GPS3_U801.vhd         |   62 ++---
 vhdl/LOCKD.vhd             |   49 ++--
 vhdl/NCDLY.vhd             |   59 ++---
 vhdl/PWRC.vhd              |  318 ++++++++-------------------
 vhdl/RSSIC.vhd             |  265 +++++++++++++----------
 vhdl/RSSI_AGC.vhd          |  512 ++++++++++++++++++++++++---------------------
 vhdl/RX_BBP.vhd            |  247 +++++++++++----------
 vhdl/UGT.vhd               |  119 ++++------
 25 files changed, 2967 insertions(+), 1630 deletions(-)

んー，やっぱ思ったより少ない．
うへー，仕事してねぇー． :P
[Hmm, it's also kinda little, I expected. Well, b/c I was not so working
hard? :P]

HotCodeStat(&me);

今弄っているブツのrepositoryのSLOCがどれくらいあるのか晒してみる．
以前のナニからパクって来たモノや他人のブツを元に変更したモノは含めない．
「hot codeのSLOCがどれくらいあるのかが分かるのでは？」と言う目論見． :P
[I'll investigate t3h stuff in current repo's SLOC,
exclude previous project's ones and based on others' code.
I think it will show me my hot code SLOC capability, maybe. :P]

 bench/BENCH_AUGT.vhd       |  106 ++
 bench/BENCH_DSMP2.vhd      |  119 +++
 bench/BENCH_DSMP8.vhd      |  122 +++
 bench/BENCH_FAKE_ADDA.vhd  |  204 +++++
 bench/BENCH_MODU_DMODU.vhd |  283 +++++++
 bench/BENCH_ROUND16.vhd    |   89 ++
 bench/BENCH_UNPID.vhd      |  225 +++++
 bench/BENCH_USMP2.vhd      |  121 +++
 bench/BENCH_USMP8.vhd      |  124 +++
 bench/DUMB_RF.vhd          |  151 +++
 bench/FAKE_ADDA.vhd        |  297 +++++++
 bench/STA.vhd              |  785 ++++++++++++++++++++
 bench/STA2STA.vhd          |  264 ++++++
 do/Bench.do                |   30 
 do/Compile.do              |  424 ++++++++++
 stim/AP_STUB.asm           | 1731 ++++++++++++++++++++++++++++++++++++++++++++
 stim/STA_STUB.asm          | 1735 +++++++++++++++++++++++++++++++++++++++++++++
 stim/include/mk_dchirp.h   |   23 
 stim/src/mk_dchirp.c       |   67 +
 stim/stimgen_DCHIRP.sh     |  155 ++++
 stim/stimgen_TXBB.sh       |  198 +++++
 stim/update_mif.sh         |    3 
 vhdl/AAO_UGT.vhd           |  150 +++
 vhdl/AGCSTM.vhd            |  187 ++++
 vhdl/AUGT.vhd              |  187 ++++
 vhdl/CCAD.vhd              |   63 +
 vhdl/DMODU.vhd             |  375 +++++++++
 vhdl/DPRAM_VINIT.vhd       |   88 ++
 vhdl/DSMP.vhd              |  143 +++
 vhdl/FP1_CLK.vhd           |  110 ++
 vhdl/FP2_CLK.vhd           |   94 ++
 vhdl/FPGA1.vhd             | 1018 ++++++++++++++++++++++++++
 vhdl/FPGA2.vhd             | 1264 ++++++++++++++++++++++++++++++++
 vhdl/GPS3_U301.vhd         |  616 +++++++++++++++
 vhdl/GPS3_U801.vhd         |  518 +++++++++++++
 vhdl/MODU.vhd              |  576 ++++++++++++++
 vhdl/MONSEL1.vhd           |  113 ++
 vhdl/MONSEL2.vhd           |  419 ++++++++++
 vhdl/NCDLY.vhd             |   75 +
 vhdl/PLSEXP.vhd            |  115 ++
 vhdl/PWRC.vhd              |  214 +++++
 vhdl/ROUND.vhd             |   85 ++
 vhdl/RSSIC.vhd             |  266 ++++++
 vhdl/RSSI_AGC.vhd          |  406 ++++++++++
 vhdl/RX_BBP.vhd            |  395 ++++++++++
 vhdl/TX_ADJ.vhd            |  269 ++++++
 vhdl/TX_BBP.vhd            |  334 ++++++++
 vhdl/UGT.vhd               |  127 +++
 vhdl/UND_BLOCK.vhd         |  143 +++
 vhdl/UNI_BLOCK.vhd         |  150 +++
 vhdl/UNP_BLOCK.vhd         |   94 ++
 vhdl/USMP.vhd              |  149 +++
 52 files changed, 15999 insertions(+)

実際の所，この物理SLOCの半分以上はコメントやらお決まり文句のカタマリ．
つーことで，思ったより少ない．
単純計算で論理SLOCで10k以下なので，まだまだ修行あるのみ．
と言うか，テストコード(*.asm)がデカ過ぎ． :P
[Hmm, half of physical SLOC are comments or generic stuff for the syntax.
So, I'd have to say it's kinda nuts, I have to do code more.
Well, t3h test code (*.asm) sucks, too bloat. :P]

GentooJP.NomiKai++; /* OSC2007 Spring */

今日はOSC2007 Tokyo/Spring最終日（二日目）でした．
以下，忘れないうちにメモメモ．
[Today is OSC2007 Tokyo/Spring finale.
These note for my stupid limbo.]

• matsuuさんが持ってきたPS3と某S社のテレビを展示．
  中身のGentooより「SPUとかはどうなのよ？」的な展開が繰り広げられた． :P
  [matsuu displays PS3 w/ S0ny TV. Many comers were talking about
  its SPU functionalities and its software development status,
  instead of installed one. :p]


• 持参したPowerBookを放置プレイ．
  genkernelでこれにはまったり，emerge systemとか．
  [Leave PowerBook alone. genkernel fails due to this bug, but work around.
  Then, emerge system or somthing.]


• trombikさんのcfengine/puppetの発表．
  金曜日にやっていたヤツを10分(?)に短縮．
  [trombik preach down to us WRT neat sysadmin stuffs.
  But it's really rapid, b/c he has only 10 min or so.]


• idaniさんのGentooバッヂを売った/買った．
  在庫 - 10．
  [idani sells cool0rz Gentoo badge, I got new one.
  Stok - 10, ATM.]


• オラ本を買った．
  bin hackとmake．
  [Got O'REILLY books.
  bin hack and make.]


• SUSUBOARDを見てくるついでに，未踏とかどうだったのかを教えてもらう．
  ついでにFPGA技術を買った． :)
  [Admired SUSUBOARD, hearing WRT MiTou thingy.
  Of cource, I got awesome brochure is so-called "FPGA tech". :)]


• Rob Pike氏ネタでPlan9な人と話す．
  #ifdefはダメダメ.
  [9ish guy show me Rob Pike autographed ones.
  "#ifdef considered harmful."]


• 耐久性が二ヶ月に向上したUdaの生演奏．
  例のとんかつ屋が店仕舞いをした事を知る． :(((
  [Live Uda, this new one improved its durable, about ~2mon.
  BTW, t3h TonKatsu restaurant has been closed． :(((]


• lightning talkを拝聴．
  OSS開発者は更なる愛とイタリア料理とチョコレートを必要としています． :DDD
  [Lighting talk, a finale of this event.
  So, now we know OSS devs need more love/italian/chocolates. :DDD]


• 喫茶店でコーヒー．
  MAC層以下な事とか特許とか．
  [Gotta coffee.
  Something about lower layer than MAC and patents thingy.]


• 懇親会参加，なんか色々話した．
  データがデカ過ぎるのでファイルシステムとかDBとかの使い方とか，
  Google Desktopは慣れるとアレとか，
  購入するPCのメモリは多くしてくれとか，
  サーバのステータスのメールに関する教育的指導とか，
  CJK herd増員の計画とか．
  [NomiKai, misc ones are stuffed, feel like ones are missing, though.
  Large/Huge data, file system selection, use of DB dilemma.
  Google Desktop is now really cool, if you like it.
  So, plz give more RAM if you buy new PC.
  A inquisition about flood status mail from servers.
  CJK herd needs more really something.]

早いトコ，今の仕事を終わらせてムニャヘニャするべ． :P
['Kay, I'll do something related Gentoo ASAP when I've done this project.]

修正: typoとか．
[FIX: typos or so.]

(pRF->PWR > RefPWR) ? pRF->ATT++ : pRF->ATT--;

"でむぱのぱわー"を計測，ちょっと調整が必要だったが何とかなった．
残りの問題は，受信側PHY下層のダイナミックレンジ拡張とアレなSME
の仕様をまとめる事．
ナンダカンダで次の納期まで二週間位しかなったりするのは罠ですか，
そうですか． :P
[Measure power of the radio wave. Well, it still
needs to tune a bit, but that's OK ATM.
Then, two major subjects are, 1) increasing dynamic
range of lower layer of reception PHY, 2) mark down
some spec of t3h SME functionalities.
There is only 2 weeks as rest of workable hours?
Blah... :P]

で，今週末はOSC．
予想通り，土曜日のみの参加になりそうな気配．
[BTW, OSC will take place at this weekend.
WTH, I can join that bunch only at the Sat.]

TuneParam(&pRF->ATT);

客先の電波暗室にてRFでナニが通る事を確認．
明日も"でむぱのぱわー"を計測するので早朝から出張也．
巧く行けばこれで一段落するのでOSCには参加出来る見込み．
[In the shield room, RF in/out connected. Tomorrow, we'll
measure the power of radio wave, so I have to get up earlier
than today. If thongs go well, I can enjoy OSC.]

色々騙し騙しなトコが有るので，マジ納入までに何とかしなければ．
先ずは，inner loopとouter loopで五倍近く遅れ時間が違うので，
その辺りからかな？
で，離散時間最適レギュレータでもやらかすか？ :DDD
[Yes, some really somethings are, though. First of all, I'd have
to purge dumb difference delay (x5!) of between inner loop and
outer loop. Oh, wait.. I won't miss t3h "optimal regulator in
discrete time domain". :DDD]

ONCT.karma++; EUC.karma--;

ONCTの某恩師の方が酔っぱらって電話してきた．
今弄っているFPGA内のPID制御器があり得ない出来だった事とか，
あんまりここに書けないモニョモニョな事とか話してたら午前五時． :P
[A former teacher of ONCT call me who is drunk.
We talked about, e.g. a really rock0rz PID controller stuff and
several really somthings. It was already 5:00 AM. :P]

取り敢えず，これを教材に使うとか言い出すのは勘弁して下さい． :DDD
[Oh, plz give it a break. So, don't use this crap as a resume of control
theory class. :DDD]

TuneParam(&pPHY->RSSI_AGC);

IFでナニが通る事を確認．
次はRFでなのだが，小ロットで手に入るRFなチップの出来が低品質な為，
RSSI_AGCと呼んでいるブロックへの入出力に色々補正をしなければなら
ない事が発覚．
[Connected peer IF in/out.
Next is RF in/out tuning, but t3h suck0rz RF chip set is really
retarded. It's mandatory to some adjustment/correction.]

具体的にどの辺りが低品質かと言うと，制御入力が出力に筒抜けになる為，
目標値との偏差が大きい時の粗調段階でシステムが発振する． :(((
これにはテキトーな一次補正で対処．
[E.g. t3h RF chip set through its control input to plant output.
So, it makes hunting when error of targeted value is kinda mighty
in coarse adjustment phase. :(((
We needs to use one-loop correction for it.]

問題はここからで，復調部分にかなり高次のFIRフィルタを噛ませている
関係上，かなり遅れ時間が有る．しかもOFDM特有の時間領域でのトゲが
かなりウザい． :(((
FPGAの容量もギリギリなので二進重み付け平均で対処予定．
[The real subject is.
Part of OFDM demodulation has a high-order FIR filter, it has big
latencies. And then, generally, OFDM symbol in time domain has short
cycle peak. It's really annoying. :(((
I'd have to fix by using binary weighted moving average b/c the
FPGA's logic stuff's capacity limit.]

あとは適当にモニタ信号に色々突っ込んで順を追ってパラメータを調整して，
RFの個体差が誤差の範囲に入る事を祈るだけ． :P
[Well then, to pull some signals related this gain controller and
step by step paramter tuning is all I have to do.
Oh wait, I won't forget to pray t3h RF modules have no considerable
individual variability, though. :P]

doReport(&devProgress);

RAM/LUT over mappingをIFFT/FFT部のRAMをシフトレジスタ化して解決，
PCIバスロックの原因になっていた内部バス変換アダプタの非同期トリガを修正，
トップレベルの対向STAのテストベンチの中身にピンアサインを反映，
PLLからのクロック入力のピンアサインを忘れていたっぽいので追加，
D/A変換部が二の補数表現ではなくオフセットバイナリだったので修正，
RF部の抜けていた仕様からの要求でIF出力のオフセットをパラメータに追加．
[Fix RAM/LUT over mapping by using shifter in IFFT/FFT instead of RAM.
Fix PCI bus lock by purging async triggers of internal bus adapter.
Back port real pin assigned entity to top test bench of STA to/from STA.
Fix a pin assign constrain of clock input from PLL.
Fix D/A semantics part, it can only recognize offset binary representation,
not 2's complement's.
Add IF output offset paramter entity and functionalities for a missing RF spec.]

帰宅してから，最後の変更で必要になったパラメータを上位階層から与える
機能を追加し忘れた事に気付いて萎える． :(((
[Returned my home, the last commit is mandatory to add the semantics in upper
layer to specify the parameter, I realized it just now, ZOMG... :(((]

Crash(&Xilinx.ISE[8][2][i]);

VHDLのファイルを追加するとたまーに死ぬISE． :(((
なので，そーっと，そーっと．．．:DDD
[When it was added a VHDL file, it did *sometimes* crash.
ZOMG, retarded ISE. :(((
'Kay, I'll do more softly... it should be a overdelicate crap. :DDD]

Xilinx.ISE[8][2][i].karma--; /* XC3S500 */

楽しい楽しい休日出勤． :p
[Hmm, it's a delightful holiday work. :p]

鬼コードした約500モジュールのVHDLをISEでムニャる．
Optimize GoalをSpeedにしてムニョるとBlock RAMが足りない．
Optimize GoalをAreaにしてヘニャるとLUTが足りない．
と言うか，top levelでしかOptimimze *やら* Styleって指定出来ない構造？
つーか，Over mappingしているの分かっているのに次のstageに進むのって
build systemが低品質過ぎね？ :p
これだからbloatなIDEはだめだめなんじゃよ．
[I've poking about 500 momdules of VHDL w/ suck0rz Xilinx ISE.
When specified Optimize Goal to Speed or so, it sez exceeded Block RAM resource.
When specified Optimize Goal to Area or so, it sez exceeded LUT resource.
Well, it can not handle Optimize * or * Style feature at non-top level?
Blah, although it was already over mapped, t3h blob forces to go to next stage,
ZOMG... :p
That's why I hate bloated IDE.]

教訓：IDEは高校生まで．
[L: To use a IDE can be applicable, if U R a HS kid.]

suspend(&SimHDL);

シミュレーションを一時保留し，先行インプリを開始．
何気に一次納入カチカチな気配． :p
[Suspend HDL simulations, launching pre-implementation test.
Hmm, makin' 1st delivery kinda subtle, though. :p]

で，
Gmailのアクセス禁止を回避するユーザを検知する5つの方法
参照先のpop * crap^H^H^Hopはどーでもいーとして，
trombikせんせーにおこられないよーにしなければ！ :(((
[BTW,
Detecting malicious GMail users
We'd have to reconsider ourselves. :(((]

setTrap(&Chocolate);

全男性社員のデスクにチョコが光臨．
同じ階の上司さん（女）曰く，
「期待してるよー」
[Manifestation of chocolate on my desk,
then my bosses (female) sez,
"we're looking forward to your quid pro quo."]


















罠か！？ :(((
[WTF on the earth did they trap us!? :(((]

doEMail(&nwccDev, Engrish);

Eng'r'ishでめーるの返事を書くのにけっこー時間がかかってる．
まだまだぜよ．
[Replying e-mail w/ my bad Eng'r'ish takes me a bit
of long time, Hmm...]
















と言うかpatchを書いた方が早かったんじゃないかと今更気づいたり． :P
[Oh, wait...
To code a patch is better way to go ? :p]

doEbuild(&nwcc[0][7][1]);

sys-devel/nwcc-0.7.1を突っ込んだ．
昨日のmedia-gfx/exact-imageと同じく
configure/build/install scriptがアレ気． :p
jabberwocky上で"Hello, world!"を作ると
nwccの方がgccの二倍程デカいバイナリが出来る．
が，コンパイラそのもののbuildはちょー早い． :DDD
コンパイラは60kSLOC弱，プリプロセッサは10kSLOC強．
[Add sys-devel/nwcc-0.7.1.
Its configure/build/install script is bit of funny. :p
T3h "Hello, world!" of nwcc is bigger than gcc's about x2 or so.
But, required time to build nwcc is faster than gcc's, of cource.
Well, about 1/10 or so? :DDD
The compiler is 60kSLOC, preprocessor is 10kSLOC.]
Nils Weller's C compiler

doEbuild(&ExactImage[0][3][4]);

media-gfx/exact-image-0.3.4を突っ込んだ．
configure/build/install scriptがアレ気． :p
[Added media-gfx/exact-image-0.3.4.
Its configure/build/install script is a bit of funny. :p]
ExactImage

delta_delay.mess(&me);

今日は何故か，昨日動いたと思ったPCIMSがHardMACの上に
突っ込んだヤツだけ動かなくてハマった．
原因はtest bench内でのclockの接続が或る条件を満たす時のみ
再現するシミュレーション上でしか発生しないPCIMS内部に
存在するbug． :(((
[Today, t3h dumb PCIMS is dead again where top of
HardMAC, though top of memory did work.
b/c t3h PCIMS has silly rarely reproducible bug
only when it's in simulation phase, ZOMG! :(((]

で，教訓．
例えtest benchでもclockをsignalとして使うと何気に死ねる． :P
[L: So don't use clock as signal even if in test bench,
otherwise you will be *stabbed*. :p]

で，午前二時半ですがoverlay掃除中． :p
[Here is about 2:30 AM, /me pokes /me 's overlay. :p]

追記：
GGI 2.2.2を突っ込んだ．
[ADD:
Stuff GGI 2.2.2 ebuilds to overlay.]

2007/02/07 04:36:04 MooZ
     hy
2007/02/07 04:37:04 hiyuh
     yo :)
2007/02/07 04:37:34 MooZ
     hey hiyuh ! what's up?
2007/02/07 04:38:06 hiyuh
     poking 2.2.2 release on 64 bit userland :)
2007/02/07 04:38:14 MooZ
     :)
2007/02/07 04:39:12 hiyuh
     so some stuffs warn me like "no 64 bit safe", though. it needs
     to fix?
2007/02/07 04:39:24 MooZ
     yep!
2007/02/07 04:39:39 MooZ
     there're pointer to 32 bits int casts?
2007/02/07 04:41:12 hiyuh
     maybe, these are marked w/ ton of #warning. :p
2007/02/07 04:41:54 MooZ
     :)
2007/02/07 04:42:05 CIA-21
     cegger * ggi-core/libggi/programs/demos/cube3d.c: add newline in
     usage output.
2007/02/07 04:44:23 hiyuh
     hmm, this? http://devmanual.gentoo.org/archs/amd64/index.html
2007/02/07 04:45:39 MooZ
     arg
2007/02/07 04:45:55 MooZ
     sigsev : not enough brain left
2007/02/07 04:45:56 MooZ
     :)
2007/02/07 04:46:41 hiyuh
     muhehe

2007/02/07 06:02:52 hiyuh
     :) http://dev.gentoo.gr.jp/~hiyuh/cgi-bin/hgweb.cgi
2007/02/07 06:04:27 MooZ
     hehe nice :p
2007/02/07 06:04:37 hiyuh
     and the previous misc dir has now GGI 2.2.2 build logs on 64 bit
     userland w/ 2.6.20 headers.
2007/02/07 06:07:07 hiyuh
     umm, 6:00 AM...
2007/02/07 06:08:06 MooZ
     it's 6:00 am in Japan?
2007/02/07 06:09:06 hiyuh
     yup
2007/02/07 06:09:45 MooZ
     you are insomniac?
2007/02/07 06:09:51 hiyuh
     lol

ねむー． :p
[SIGZZZ :p]

PCI_MODEL_REQ.oxGNT.karma--;

PCI LBがやっと動いた． :p
[Pwnt, PCI LB WORKS FOR ME(tm). :p]

犯人はCPUとbus arbiterのモデルとして使っていたPCI_MODEL_REQ.vhd.
こいつのGNT#が他のbus masterからREQ#が入らないと不定だったと言うオチ．
PCI LBにぶら下がっているメモリモデルがbus master disableだったので，
PCI masterの内部マクロがイイ感じに暴走していた． :(((
サクっと*stab*して終了．
[It did not work b/c suck0rz PCI_MODEL_REQ.vhd as CPU + bus arbiter.
pre-fixed one can not determine its GNT# if REQ# from other bus mster
havenot been inputed, ZOMG...
The memory model at PCI LB is disabled PCI master functionalities.
Then, the master sub-macro did overide. :(((
The fix is simply *stab* '1' to its GNT# as initial value, PERIOD. ]

MOS-FETで言う所のゲートが浮いていたってトコか？ :p
[cf. the case of MOS-FET w/ floating gate. :p]

ModelSim[XE][III][6][1][e].karma--;

ModelSim XE III 6.1e，イイ感じに低品質，
Spartan-3 x 4個程度のシミュレーション程度で遅くなるとか，
シミュレーション中，たまにbacktraceを吐いて刺さるとか． :(((
[ModelSim XE III 6.1e really suck0rz.
It's getting slow when a simulation w/ Spartan-3 x 4,
then finally, it vomits rock0rz backtrace, ZOMG... :(((]

で，最近，標準仕様の後方互換性が非常に邪魔に感じる．
マイナーでも構わないのでまともなBUS仕様は無いもんかな？．
取り敢えず，Power ISAを読んで現実逃避． :p
[All backward compat is really eyesore for me, think that should be shot.
Plz let me know, if you know sane bus specification.
Minor ones are really welcome.
Now, I'm poking Power ISA, though. :p]

PCI_LB[3][0].karma--;

やっとHardMACから脱出して，一時的にPCI local busな感じ．
例によってちゃんと分かっている訳ではないので，PCI SIGの原文をムニャる．
二日間ムニャったが，PCI LB 3.0はダメダメ． :p
そしてPCI LB 2.xの時に作ったと言うPCI Master/SlaveのVHDLとかも
かなりアレ気で萎える． :(((
[Now, it's time to PCI local bus instead of t3h HardMAC.
I've poked PCI LB 3.0 specification from PCI SIG, though.
Well, my feeling is just "BLAH". :p
Hmm, t3h VHDL stuff was coded w/ PCI LB 2.x is "BLAH"-er. :(((]

ま，取り敢えず，納期も有るので機能的に問題の無い部分は保留して，
仕様書と整合性の取れていないブツに関して言及した上司へのメールに
以下のメッセージを追加．
[Meanwhile, the suck0rz thingy are now pending.
But, I had to try e-mail about inconsistencies of code and doc
w/ those message to my bosses.]

# WE NEED MORE AND SANE CONSISTENCIES.
# OTHERWISE, JUST ABANDON THESE CRAPS.

返事には「お前の言いたい事はよーくわかった」と書いてあった． :DDD
[The reply was "I know, but STFU n00b..." :DDD]

GentooJP.NomiKai++; /* First of 2007 */

飲み会でした． :)
trombik先生に教育的指導をして頂きました．
ほんとうにありがとうございます． :p
[NomiKai is over. :)
trombik's inquisition is really interesting for me, though.
Thanks a lot. :p]

何か飲んでいるうちに"びすた"が出てたっぽい．
[Hmm, when we were talking about spam'n'ham, vista seems to be out?]
!google vista 1/29

やっとglibc-2.4 fixでリリースされました． :)
[Finally, official glibc-2.4 fix is out, as well. :)]
[ggi-develop] [ANNOUNCEMENT] GGI 2.2.2 available

doInst(&iMac20, &Gentoo, ~amd64);

そうそう，年が変わってから20" iMacを買った．
特に理由は無いが，jabberwockeyと命名．
勿論，既にGentoo Linux ~amd64を突っ込んである． :DDD
emergeのlogがすげー早さで1680x1050の画面で流れていくなー． :p
[Oh, yeah, I've got 20" iMac for the new year dev env.
Well, the host name is jabberwockey.
Of cource, it was already installed Gentoo ~amd64. :DDD
LOL, the emerge log scrolls w/ amaging speed in 1680x1050 world! :p]

で，今日は恒例の月末飲み会@某C社．
寿司ごち！ :9
[BTW, today was NomiKai@certain-C for end of this month.
SIGSUSHI, yum-yum! :9]

今週日曜日にはGentooJP新年会がある．
今度は寝過ごさない様にしよう． :D
[Sunday of this week is NomiKai of New Year for GentooJP.
Hmm, I won't oversleep again. :D]

vec_doc = sub_vec(vec_const, vec_code);

イツノマニカ，アケマシテオメデトウゴザイマス． :DDD
[Well, @ Inappy n3vv y3ar. :DDD]

一通りドライバの仕様書が書き終わったので，
久しぶりにVHDLを鬼codingしていたら，
こっちが大分疎かになって仕舞った． :P
[That spec of SoftMAC is almost marked down,
so I've stuffed ton of VHDL code.
Then, I forgot to post my craps here. :P]

教訓：documentationとcodingはトレードオフな関係にあるっぽい．
[L: documentation and coding are traded-off, at least for me ATM.]

doDesc(HardMAC & SoftMAC);

なんかそれっぽい話題で盛り上がっていたらしい．
[Well, got off?]
livedoor Wirelessのラの字も考えてないWeb屋のネタ帳の誤読記事
livedoor wireless、MACアドレスによる認証を開始--ニンテンドーDSにも対応
セキュリティのセの字も考えてないライブドアの公衆無線LANサービス

何はともあれ，IEEE 802.11を読んでみましょ，話はそれからっす．
['kay, before we start to talk wireless thingy, Get IEEE 802.11.]

で，改訂版．
[BTW, here's improved one.]


無線伝送路として使用する周波数帯域自体が全く別のトコを使うのでIEEE 802.11*準拠*で
特に問題無いけど，現在作成中のこのブツ，ハードウェアの何処にもMACアドレスへの縛りが無い．
完全にソフトウェア側で，強引にやればruntimeや通信中でも変更可能．
かなり反則なハードウェアに仕上っている． :P
[It has no problem b/c it'll be used on not common radio frequency band,
this hardware has no hardware restriction for MAC address.
Its address can be changed even if in runtime.
Say, it really rocks, I thought. :P]

ARPのframe formatの話になるとモノを読んだ訳ではないからなんとも言えないけど，
IEEE 802.11ではAP側はMACアドレスをBSSIDとしてframe format中で使う．
このBSSIDはBSSと呼ばれるAPのサービス範囲に定期的に送信されるbeaconと
STAからのprobe requestに対するprobe responseに付加される事になっている．
これはClass I frameと呼ばれるブツでauthenticationやassociation，
つまり認証や論理接続する以前の段階で送受信が許されている．
[I dunno about ARP's frame format b/c I've not read ARP standard.
But, in IEEE 802.11, AP uses its own MAC address as BSSID.
This BSSID is payloaded on beacon and probe resposne.
These are included in Class I frame, it can be tx/rx-ed before
authentication/association is completed.]

つまり，IEEE 802.11に従う限り，APのMACアドレスを知る為にARPを使う必要は無い．
受信側のSTAをテキトーな周波数で固定して，beaconが捕まえられる通信圏内に入れて，
且つPMD/PLCPが適切な機能を持っていれば，無線伝送路上を行き交うモノはIEEE 802.11の
MACのレイヤーではoctet streamに変換される．
結局，ARPとは異なり，STAがAP側に何も送信せずにAPのMACアドレスが分かる．
これはpassive scan，具体的に言うとMLME-SCAN.requestのScanType==PASSIVEに相当する．
[So, in IEEE 802.11, to get AP's MAC address does not needs to use ARP.
All you have to do is, fixed STA's a channel and move into accress area
where it can grab AP's beacon and proper PMD/PLCP capability, you can
see all frame as octet stream in IEEE 802.11 MAC layer.
So, STA does not needs to transmit any frame to get AP's MAC address.]

更に，IEEE 802.11ではAPのBeaconPeriodを幾つにするかは規定されていない．
が，WiFiなんとかとか言う機関が異なるベンダーから提供されるIEEE 802.11な機器で
相互接続性が保証出来るか否かを検査しているらしい．
一般の消費者が使用するIEEE 802.11なブツがAPとして動作する場合，
100[ms]程度の間隔でbeaconを吐く様になっているらしい．
[And IEEE 802.11 does not specified BeaconPeriod value explicitly.
But WiFi-blah tests their connectivity for different vendor's products.
In general, most of IEEE 802.11 products which can be available for consumer
may transmit beacon every about 100[ms] interval.]

勿論，beacon自体を暗号化してしまう手もあるだろうが，
この辺はまた別でIEEE 802.11[a-z]の内，"せきゅりてぃ"なトコが担当しているので良く知らない．
そもそも暗号化したbeaconに対応しない機器では相互接続性は確立出来無い．
[Of cource, there is a way to encrypt beacon itself.
But it's beyond of IEEE 802.11, it's mentioned in security enhancement group
which is one of IEEE 802.11[a-z].
And you can easy to understand it breaks connectivity.]

単純に，「APがbeaconを吐かなきゃ良いじゃん」とか思ったりするが，それはそれで問題有り．
beaconはAPの存在をSTAに知らせる為のbroadcastなブツであり，
且つTSFタイマと言うAPが刻むBSS毎にuniqueなタイマのtimestampを使用して，
未だBSSに属していないSTAがこのTSFタイマに同期する為のブツとしても使用されている．
これはそもそもIEEE 802.11の規定する無線伝送路での通信手段として，
Ethernetで良く知られる
CSMA/CD == Carrier Sense Multiple Access/Collision Detection
ではなくて，
CSMA/CA == Carrier Sense Multiple Access/Collision Avoidance
を使っているから，BSSに未だ同期していないSTAは自ら無線伝送路にブツを吐けない．
勿論，Collision Avoidanceとは言ってもcollisionする事は考慮されているので，
dot11ShortRetryやらdot11LongRetryってのがIEEE 802.11 MAC MIBには存在する．
[Simply, "No beacon transmit is another way to go", of course no.
Beacon is broadcast one to announce where AP is at all,
and it's for synchronize TSF timer which is unique timer of each
BSS as well.
Well, IEEE 802.11 is based on CSMA/CA, not CSMA/CD AKA which is use
base of Ethernet.
So, STA wouldn't transmit any frame before synchronized BSS.]

それからWEPはその名の通り，Wired Equivalent Privacy．
つまり，有線と同等の"ぷらいばしー"と言う意味．
利用可能な周波数のチャネル数がバカHUBの台数だけしかなくて，
それらのポートが空中に浮いていると思えば良い．
通信路の途中でframeを盗聴するなんて簡単なのがよーく分かるはず．
[BTW, WEP stands for Wired Equivalent Privacy.
Imagine, number of available frequency channel is equal to
number of repeater and everyone can use these repeater.
It's really easy to get other's frame by simply tapping.]

まとめると，リンク先で盛り上がっているMACアドレスによるfilteringって話は，
Frame Control fieldのoctet streamに対する単純なdecoderでしかない
address recognizerの部分をSMEを経由してソフトウェア側で実現しているだけ．
[That MAC address filtering is simple.
It is software implementation of SME of address recognizer
which decode octet stream of one of Frame Control filed stuffs.]

つまり，ハードウェアにヘチョいブツ混じっているのがまず問題なんじゃね？
と言う訳で，みなさんはハードウェアには投資して下さい． :P
[So, the problem is, many dumb hardware are?
Say, pay to get proper/sane hardware, plz. :P]

sanitize(0xBADC0D); hg.commit(tip);

社内のSH7751Rなボードの開発環境が起動しないアリエナイ状況に陥る．
[T3h old SH7751R dev box didn't boot, ZOMG...]

仕方無いので，ThinkPadにGentoo Linux ~x86を突っ込んだ後に，サクっと
sys-devel/crossdevでsh4-unknown-linux-gnuなクロスコンパイル環境を
仕立てて，"ぷろだくとれべる"で仕上がっている2.4.18ベースのkernelから
patchをテキトーに分離して，キレイキレイしてからdev-util/mercurialな
repositoryにcommitしまくる．
[So, I've installed Gentoo Linux ~x86 to ThinkPad and make it dev box of
sh4-unknown-linux-gnu by using sys-devel/crossdev.
Then, pull'n'split patches from t3h productive kernel src was beased on 2.4.18,
and commit them to dev-util/mercurial repository w/ my stupid code sanitizing.]

更に，以前の開発環境が2.9xベースと言う古代の遺物．
これまたテキトーにcompile fixなpatchもでっち上げた．
取り敢えずzImageが作れる所まで直ったらしい．
[But it won't build due to t3h src depends old toolchain behavior.
So, I've poke it and make zImage build.]

あとはボード上に置いてみてdebug'n'fixするだけ．
時間が余ればupstrteamなpatch repositoryもでっち上げたので
仕事をしているフリをしてbackport遊びをするかもしれない． :p
[The last one is to deploy stuffs on the board and debug'n'fix.
Once IT JUST WORKS(tm), it may be time to backport only for fun. :p]

で，新Greg-KH本が出たらしい． :)
[BTW, New Greg-KH's book is now available, I heard. :)]
New book explains how to build Linux 2.6 kernels (LinuxDevices.com)

Draw(SoftMAC & HardMAC);

IEEE 802.11/IEEE 802.11aのMAC/PHYの辺りのイメージ．
SoftMACのフローチャートまで手を付けられなかった．
納期がヤヴァい． :P
[Here's my stupid image of IEEE 802.11/IEEE 802.11a MAC/PHY.
Well, I'd have to stuff completely SoftMAC flow charts, though.
Umm, blah. :P]



修正：
Network SubsystemとかPCI DMAとかも．
Ring BufferとかARP Cache本体とかを書く場所が無いなー． :P
[FIX:
Forgot to add Network Subsystem and PCI DMA or so.
Oh well, there is no space to describe Ring Buffer
and ARP Cache itself. :P]



修正：
変な所に在ったIEEE 802.x LANをIEEE 802.3として分離．
IEEE 802.1 BridgingとIEEE 802.2 LLCを追加．
ねむー． :P
[FIX:
Separated IEEE 802.x LAN as IEEE 802.3 for example was wrong placed.
Added IEEE 802.1 Bridging and IEEE 802.2 LLC.
Well, SIGZZZ. :P]

goto t3h_Y; t3h_Y: doTT4(SoftMAC & HardMAC);

当初はハードウェアな人間だと思われていたらしいが，
何時の間にかソフトウェアな人間だと言われて，
更にそっち系のメンバーが不足していたとの事で
便利屋且つ厄介者として扱われる今日この頃． :P
先週は木曜日にYなトコロで主にハードウェアのレビュー，次の日にP4のミーティング四回目．
[My bosses thought I was hardware-oriented, though I'm now
deemed software-oriented.
To make matters worse, my office lacks software-oriented ones.
So, I act like the handy man, otherwise like nuisance. :P
Last week, the Thursday is a review of hardware specs @ t3h 'Y'.
Then, Friday is 4th meeting of P4.]

レビューにて，お客さんはRadio Frequencyな人らしく，
ハードウェアの方にはAGC/LNAな感じで突っ込みが厳しかった．
逆にソフトウェアの方はお任せな感じだった．
曰く，「聴いてもヨクワカラナイ」からとか． :P
[The reviewer is really Radio Frequency guy, he pointed at AGC/LNA thingy.
But he'd let leave up me about software thingy.
B/c, he said "Well, I'm unprofessional that thingy as you know." :P]

ミーティングにて，結局，自分がSoftMACのフローチャートを書く事になった．
以下，メモ．
[On the meeting, it made me have to design SoftMAC implementation.
The follows are P4 iff SoftMAC.]

 * P4 iif SoftMAC
   + active scanning
   + best-effort hand-off
   + misc MLME ioctl(2)
   + misc PLME ioctl(2)

で，高専の頃，誰かが言っていた事を思い出した． :P
「エラい人の言葉でも専門外の事だったら疑ってかかれ」
[So, I'd have to say a phrase that I heard I was a student of ONCT. :P
"You should doubt what someone said, even if he was your guru,
especially when he mentioned about unprofessional thigy."]

修正： typoとか．
[FIX: Typos or so.]

ISE[8][2][i].karma--;

今日はBPFを弄った．
要求としては16MHzキャリアに乗っている5MHz帯域の信号を
エイリアシング/イメージングから保護する事．
[I've Poked the BPFs.
Requested spec is to attenaute aliasing/imaging
for 5MHz band signal on 16MHz carrier.]

DCと32MHzにアレが出て来るって事を考慮しただけだと20次で良さ気なモノが出来た．
一応，実績のある過去の設計仕様では48次で作っているブツがあったので，
48次を限度に低周波減衰域/高周波減衰域を広く取ったブツも作った．
[Simply to attenaute DC and 32MHz ones required 20 deg.
Some referenced previous designs used 48 deg, so I've tried
to enlarge high/low attenaution band w/ 48 deg as well.]

で，XilinxのISE 8.2iでジェネってみた．
んー，使い方がヨクワカリマセンネー．
ツールの名前だけ見るとFIRをジェネる為のブツが二個有るみたい．
仕方無いので英語なマニュアル約40ページと約60ページを印刷．
明日はYなトコロに出張予定なので行き帰りにでも読むつもり．
[Then, I've tried to generate w/ ISE 8.2i.
Blah, that's really bloated and enough to confuse.
So why does it have 2 FIR code gen?
Well, I'll read about 40+60 page manual written in English,
though on the way to and from t3h 'Y'.]

で，そこそこsys-apps/qingyに人気が出てきたっぽいし，
dev-libs/DirectFBもPV==1.0_rc2なので，
中身はC++だけど，コンパイル時間がそんなに要らない
x11-misc/slim-1.2.6に乗り換えてみた．
その内，自分用のテーマを作る．
[My minor oriented karma force me not to use sys-apps/qingy,
due to dev-libs/DirectFB's PV==1.0_rc2.
The replacement is x11-misc/slim-1.2.6 is written in C++ though,
not takes so long time.
So, I'll make my own theme sooner or later.]
Bug 107526 x11-misc/{slim,slim-themes} - new ebuild

あ，Splashyってのもあるのかー． :P
[Oh well, Splashy is, too. :P]
Splashy

MATLAB.karma--;

SoftMACの部分が一段落しつつあるので，新しいトコに着手．
マルチキャリアの直交変復調近辺のデジタルフィルタの設計．
んー，一年振りのz変換は或る意味，新鮮だったりする． :P
[SoftMAC thingy is mostly DONE, then I'd poke next thingy.
The ones are design digital filter which is implemented
before/after quadrature modulation/demodulation.
Hmm, the "z transform" is much nicer, after an absence of
a year. :P]

ダウンサンプラ/アップサンプラの前段/後段にかますLPFを弄った．
このLPFは，エイリアシング/イメージングを抑制する為のモノで，
前段/後段のサンプラと合わせて，デシメータ/インタポレータと呼んでいる．
[Well, I've poked LPFs before/after down-sampler/up-sampler.
These LPFs attenuate these samplers' aliasing/imaging.
These combined ones are so-called decimator/interpolator.]

MATLABの低品質なUIと自分の巨大なappsを扱えない憶えの悪さが禍して，
フィルタ設計ツールの使い方を理解するまでに一日．
z変換と離散時間制御と離散時間信号処理の復習に半日，
デシメータ/インターポレータの原理とFPGA上での実現方法の勉強に半日．
[Due to MATLAB's suck UI and bloat, it takes 1 day
to realize how to use filter designing tools for me.
And then, restudy about z-transform, control theory and signal
processing of discrete time domain, that takes half of a day.
Studying about functionalities and implementation techs
of decimator/interpolator, that takes another half of a day.]

出来上がったインターポレータ/デシメータは，
インターポレータ
= (2xアップサンプラ + 50次等リプルLPF)
+ (8xアップサンプラ + 14次線形補間LPF)
デシメータ
= (8xダウンサンプラ + 54次等リプルLPF)
+ (2xダウンサンプラ + 6次等リプルLPF)
[Finally, I've designed like this,
Interpolator
= (2x up-sampler + equiripple LPF of 50 deg.)
+ (8x up-sampler + linear interpolation of 14 deg.)
Decimator
= (8x down-sampler + equiripple LPF of 54 deg.)
+ (2x down-sampler + equiripple LPF of 6 deg.)]

で，中ではParks-McClellanアルゴリズムと言うRemezアルゴリズムと
Chebyshev近似を併用したブツを使っているらしい．
IEEE 802.11のMAC部分はLinuxに実装があるけど，
PHY以下は殆んどデバイスの仕事だしRFにも依存するのでソフトウェアで実装するとか
アレな真似をしている人は居ないのかも．
HDL設計/コーディングでは期待値検証に使えそうな感じはするけれど，
控えめに見積もってもシミュレーション程度にしかならないからかな？ :P
[BTW, internal of that designing tools use Parks-McClellan
algorithm which is combined Remez algorithm and Chebychev
approximation, I heard.
Linux has a IEEE 802.11 MAC part implementation though,
these is no implementation one which is under PHY thingy.
Well, I know that "under PHY thingy" is hardware functionalities,
and it depends on RF part.
Their use is only for a expectation collation for HDL, or simply
for its simulation. :P]

明日は直交変復調の前段/後段のBPFを弄る予定．
[Hmm, tomorrow, I'll poke BPFs which is implemented before/after
quadrature modulation/demodulation.]

doTT3(HardMAC & SoftMAC); dosomethings2();

P4のミーティング三回目．
んー，なんか結局，開発に参加してもらう方，約二名に
IEEE 802.11な英文を読んでもらう事になってしまった．
ま，被害者^H^H^H仲間が増えるだけなので問題無し． :P
[P4 meeting 3rd.
Hmm, co-devs will read the IEEE 802.11 one.
Well, they look like victims^H^H^H^H^H^Hambitious. :P]

で，USE="xcb"は鬼門ですねー．
x11-terms/xterm + app-i18n/scimとかjavaのpluginがぶっ壊れるっぽい．
一応言及しておくとXCBが悪い訳ではなくて，twice lock/unlockとかしている
appsの方が阿呆過ぎなだけです．
Momongaでは一時的な対策（？）として，twice lock/unlockをassert(3)で
検出している部分をコメントアウトすると言うパッチまで用意してるし，それはマズくね？ :P
CFLAGS+="-g" + USE="debug"なx11-libs/*をでっち上げて，
upstreamのpatchを幾つか拾ってきたので，暇な時に直す予定，多分． :P
[BTW, USE="xcb" really l^Hrocks.
x11-terms/xterm + app-i18n/scim and java plugins are bombed.
FYI, that isn't XCB's fault b/c some apps try twice lock/unlock itself,
these crappy code shoudl be shot.
OTOH, Momonga ab^H^Huses a patch which deletes assert(3) for invalid
twice lock/unlock. :P
So, I prepared x11-libs/* w/ CFLAGS+="-g" + USE="debug" to fix it.
I'll poke something sooner or later, maybe. :P]

で，net-misc/dhcpcd-3.0.0も鬼門ですねー．
uberlordさんがcomplete rewriteしたのでKEYWORDSが一度外されて，
ちょこちょこ追加されているのだけれど，htonl(3)をサボっている箇所で
little endianなホストが刺さったっぽい．
一応，パッチは公開されているが，今はbugzieが死んでる，新しいのになるっぽい．
[Then, net-misc/dhcpcd-3.0.0, IT JUST WORKS(tm).
uberlord did complete re-write, and droped KEYWORDS.
But, there are some limbos of endian consideration,
so no htonl(3) is IT DOESN'T WORK(tm) on little endian host.
There is byte-order fix patch, but bugzie is now dead, for resurrection.]

で，遂に需要の少なそうなブツを公開． :9
dev-util/mercurialでclone出来ます．
[Yay, a little demanded one is finally out. :9
You can clone it w/ dev-util/mercurial.]
$ hg http://dev.gentoo.gr.jp/~hiyuh/cgi-bin/hgweb.cgi portage
hiyuh's misc Portage Overaly

追記：
bugzie復活したっぽい．
net-misc/dhcpcd-3.0.1が突っ込まれたっぽい．
んー，ねるー． :P
[ADD:
Bugzie is resurrected.
net-misc/dhcpcd-3.0.1 is added.
Well, SIGZZZ. :P]

GentooJP.NomiKai--; /* LDAP */

11/26のLDAPな飲み会は寝過ごしました，すいません．
忘年会は寝過ごさないように気を付けます． :P
[hmm, I've overslept the LDAP-favor NomiKai, sorry.
Well, I'll be no late next NomiKai AKA BouNenKai. :P]

で，x11-libs/libX11とmedia-libs/mesaにUSE=xcbが導入されてます．
XCBってのは，コレ．
[BTW, USE=xcb is added to x11-libs/libX11 and media-libs/mesa.]
XCB Wiki
XCB (Wikipedia)

現在，build_with_useが抜けているので，気を付けましょう．
[However, these have a silly build_with_use bug, so be careful.]
bug #156397

Office.NomiKai++; /* Nov. */

11月分，月末飲み会でした．
社内でピザ -> 飲み屋に移動 -> 駅前のカラオケのコンボ．
あー，喉がー，喉がー． :P
[Today is a NomiKai of end of Nov,
pizza in the office -> NimiYa -> KaraOke.
Hmm, I have a scratchy throat, though :P]

doTT2(SoftMAC & HardMAC); doSomethings();

P4のミーティング二回目．
今日までのアクションアイテムはこなしたつもり．
次のミーティングまでに課せられたアクションアイテムはちょっち手強そうな感じ．
しかし，やるしか道は無し，っと． :P
[Today, I had 2nd meeting of P4.
I've done my action items for this one.
However, I have to do some time-consumings for next one.
But yes, only what I can do is to do it, anyway. :P]


他人の吐露を見ておいて思う事がありながら，書かない事は失礼なんだろー，
と時々思うので書いてみる．
[It's a bit of unfair for me that what I only saw other's mumbles
even if I'd have to mention that thingy.
So, here we go.]

Chofu-sai (AO diary)
「せめて現役の学生さんに幸せに働く卒業生像を見せてあげたい．」
["I'd show that some OB really fun his works for these students."]

仕事が面白過ぎて日付が変わる前に帰宅するのに苦労しております． :P
[Well, I'm really fun my works.
Every time I have to leave work due to dateline coming,
I feel my heartbreak. :P]

記憶に残っている，うちの社長語録には，
「食う為にこの手の仕事をやるつもりなら，それは諦めた方が良い．
楽してそこそこ儲けたいなら，他にもっと良い仕事がある．」
って言うイカす台詞があった．
[IIRC, my boss said,
"If you would work for clothing/food/housing, we can't recommend that doing.
For have an easy life, there are many other way to go."]

OSM亡き後どうすんのかという話 (みんな仲良しのつもり)
「開発をやってる電通大からは外にCVSが出来ないという凄い問題があるので
リポジトリのアップデートが非常に面倒だったりする。。」
["UEC's network doesn't allow to me to access CVS repos, how annoying..."]

それ，自分もすーぱー困ってました． :P
ポリシー上仕方の無い処置だったのかもしれないケド，
その辺りに詳しい管理者でもないので何ともならなかったなー．
[Yep, that was really PITA, too. :P
Due to their policy, it might not help, though I'm not sure about that truth
b/c I was not one of that admins.]


Officeの機能は思考を規定する (備忘録)
「結果としては、引出しは多い方が良い、ITリテラシーは高いほうがいい、
というつまらないことなんだけれど、Officeに進化は必要か、といわれれば、
引出しが増えるような進化が必要だと言いたい。
ちなみに、文書フォーマットがXMLになればPerl/Ruby/PythonでExcelを
もっと処理しやすくなるから進化歓迎!なんていう意見もあるけどね（笑）」
["As a result, to add more option would be good, to have highly IT
literacy as well.
So, I'd like to say to add more options is needed as Office's innovation.
BTW, once it change its format to XML, Perl/Ruby/Python make it easy to
poke its data, so that 'if' is much nicer, LOL."]

個人的に引出しを無駄に多くする事は歓迎出来無い，
他人から手取り足取りで教えられたツールの使い方を溜め込む記憶力を"あいてーりてらしー"とは呼びたくない．
辞書は必要充分なインデックスで必要十分な中身が取り出せれば良いと思う．
最後の一文はちょー賛成，表計算するのにマウスでカチカチカチカチやりたくない．
そして，イルカはカッコいい！ :P
[IMHO, to add many option is not so better thing.
I wouldn't define to stuff about giving every possible help
how to use one tool as a comp-literacy.
All dictionary should contain 'if and only if' indexes and
'if and only if' contents, I thought.
The last line is what I'd always have to say.
To click many times to calculate something is really annoying me.
BTW, that dolphin really rocks! :P]

現代に跳梁跋扈するWIMPyなGUIに対して，ARG曰く，
「その主たる理由は，一般大衆市場におけるコンピュータの経済的な成功であり，
この市場を構成する大部分は素人である．
我々は，この状況を変え，玄人の為のグラフィカルユーザーインターフェースを提供する．
勿論，我々はこの様な事がすき間産業然としている事は十分承知している．」
[Nowadays, there are many WIMPy apps, ARG criticized,
"The main reason has been the economical success of computers
in the normal consumer market, which consists of unexperienced users mainly.
Our motivation is to change this situation and to provide a graphical
user interface for experienced users, though we know that this market is
a niche. "]

Javaでソートアルゴリズム (WEBLOG SIDE)
qsort(3p)と{b,h,l,t}search(3p)で"ぎぶあっぷ"です． :(
比較関数は，比較対象2要素のvoid*からの適当なキャストと
return + カスケード条件代入文で論理SLOC 3で終了です． :)
[qsort(3p) and {b,h,l,t}search(3p) is enough for me. :(
Any compare function is constructed by,
sane casting for 2 arguments and
return + cascaded conditional substitution.
These are only logical 3 SLOC, period. :)]

a result of my jaw

今日は例のP4の実質的な開発方針を決める為のミーティングでした．
色々リスクの種はあるけれど，始まっちまえばつっ走るだけだから，
何とかなるっしょ？ :P
[Today, I attended a meeting of t3h P4 dev-direction.
Well, it may have some pitas, though all I can do is
just do it if the project is runnig. :P]

実質的なミーティングの後，無駄な余裕が出てきたのか，やはりオフトピになる．
色々ムニャヘニャ文句を言った結果，上司の方が，
「P4が終った後に，あのCPUボードとFPGAボードとAD/DAボードのセットで，
upstreamなLinuxの開発環境をムニャる社内プロジェクトっぽいモノを考えておく」
みたいな事を言われた．
[When the meeting was over, I jawed some of OTs.
So, a my boss mumbled like,
"Okay, like you said, we may plan a private project
that's for creating upstream-flavor dev-env of Linux on
our CPU+FPGA+AD/DA board-set, after the P4 was over."]

アレなスケジュールではP4は来年二月，遅くとも今年度末にはケリをつけたいブツなので，
始まるとすればそれ以降になるけど，ちょー期待，まだ口約束だけどな！ :DDD
Gentooが云百万のFPGAを制御する日は近い，たぶん． :P
[Hmm, according to the P4's schedule, that will be over
until Feb. or so.
Then, the awesome plan will start, I hope.
But it's still verbal one, though! :DDD
So, we'll see FPGAs which is really expensive and Gentoo's
collaboration, I guess. :P ]

Merge(&EixTrunk, &MyPatches); Exchange(&PB.battery);

昨日，貼ったばかりのapp-portage/eix-0.8.1のパッチが速攻でマージされた． :)
テキトーに符号付き/符号無しの警告を黙らせていた所をまともな修正に変更した以外は，
全部current svn trunkに突っ込んでもらえたみたい．
[Yesterday, I filed warning silence patch of app-portage/eix-0.8.1
bugzie, as you see.
Then, the dev quickly review'n'test that stupid ones and did merged
to current svn trunk, except my wrong singed/unsigned pokings.]

で，マニュアルdiff(1)で生成したパッチをcat(1)でテキトーにまとめて貼ったもんだから，
Subversionの使い方が分かっていない事がバレたっぽい，howto書かれているし．
取り敢えず，Mercurial使いなのだと言い訳をしておいた． :P
[And then, he realized I didn't know use of Subversion b/c that was
cat(1)-ed from manually diff(1)-ed ones.
So, he suggested me to use of it by mini howto.
Well, I had to say I'm a user of Mercurial, not Subversion, though. :P]

Gentoo/PPCなPowerBookのバッテリがAppleの交換プログラムに該当していた．
以前からしっかり筐体に嵌まらないから変だなーとは思っていたが不良品だったとは．
取り敢えず，タダなので交換の手続きをしておいた．
んー，良く見るとバッテリのパッケージの境目が気持ち黄色っぽいのだが気の所為か？ :P
[BTW, my Gentoo/PPC PowerBook's battery was one of defective ones,
as Apple announced already.
Hmm, I already got suspicious due to this one didn't fit precisely its main frame.
This exchange program is no charge, so there is no reason of to do it.
Umm, If I made attention to see this one, its boundary lines look like
bit of yellowish, though. :P]

doTT(HardMAC & SoftMAC); eix.warning--;

と言う訳で，8時間程かけてHardMACとSoftMACの極意を伝授された． :P
明日からは仕様書をムニャる予定．
[Today, I've been transferd technical thingy of HardMAC and
SoftMAC from my bosses.
Well, it takes 8 hours or so, though. :P
Next, I'd have to note some detail of its spec to the sheet.]

app-portage/eixの警告が何かに気に入らなかったので直してみた．
0.8.1がportageに入ったので，bugzieに貼っておく． :P
[app-portage/eix has ton of warnings, so I've fixed some of these.
And 0.8.1 was out, it needs to fix official ASAP. :P]
silence warnings when compiling app-portage/eix-0.8.1

+ (dot11 | MAC & PHY) * (1.0 / 4.0);

"IEEE802.11 MAC and PHY"な"すたんだーどどらふと"(?)を更に1/4程消化．
直接ナントヤラと赤外線なPHYなので，残り半分はすっ飛ばした．
明日，上司の方にHardMACとSoftMACの境目を教えてもらったら，
ブツの仕様書を書く事になっているけど，どーなるんでしょーかー？ :P
["IEEE802.11 MAC and PHY" as known as the standard
draft, plus about 1/4 is DONE.
DS thingy and InfraRed thingy of PHY are skipped as a 1/2 of
that draft.
Tomorrow, once my bosses tell me about boundary of HardMAC
and SoftMAC thingy, I'll do write down its spec or so.
Well, who knows what will happen? :P]

で，感想．
重要なのは分かるけど，backward-compatって新しくモノを作る時は，
大方足枷になるっぽい．
アレなbackward-compatな仕様だったので読むのが大変だった．
と言う訳で，Abandon! Abandon! :P
[My impression is,
I know a backward-compat is a really important thing, though.
But those many considerations drive me nuts, I'd have to say.
All I would say is "Abandon! Abandon!" :P]

(dot11 | MAC & PHY) * (1.0/4.0)

"IEEE802.11 MAC and PHY"な"すたんだーどどらふと"(?)を1/4程消化．
しかし，当然英文なのでボロクソに読むスピードが遅い．
やっとauthenticationとかassociationの意味が分かってきた．
mobilityが分かってないとイカンのね，何を言っているのか分からなかった訳だ．
と言うか，MSDUとかIFSとかDCFとか．．．acronymが多過ぎ． :P
[I'm reading "IEEE 802.11 MAC and PHY" as known as the standard
draft, about 1/4 is DONE.
But, yes, my speed is really slow due to these are written in English.
Finally, I realize the authentication and the association thingy,
to understand it requires to know these mobility thingy, damn it!
BTW, that stuff has many acronym like MSDU, IFS and DCF or so,
these are enough for me to do limbo, even if when I'm reading it. :P]

OFDMな部分も一通り読んだ．
理解出来無い話じゃないけど，一つ気付いた事は数学の知識がかなり忘却の彼方に逝っているっぽい事．
使わないと忘れるとは良く言われるけど，実体験するとは思わなかったなー．
[At the same time, I'm poking OFDM thingy.
That stuff is not quite difficult for me, though.
But I'd have to say I really forgot some mathematics thingy even I was
good at ones.
As it is often said,
"Once you didn't use it, you'll forgot use of it, even if you were good at it."]

えーと，例え話にすると，
彼の狩人，仙道に入りて徳積む事幾星霜，鳥を射るに弓矢使わず．
麓の里にて弓矢を示し，「これは何の道具か？」と訊いたそうな． :P
[Well, so like that,
A hunter, he want to become hsien and he did train harder'n'harder in mountains.
Finally, he can do shoot a bird w/o bow'n'arrow, then he went down mountains.
When he saw a bow'n'arrow in a store of a village, he pointed it and asked,
"Hmm, what's that for?" :P]

God kills a kitten...

#gentoo-bugsにて．
[From #gentoo-bugs snippet log.]

11/09 04:44:01 jeeves
    [New Bug] https://bugs.gentoo.org/154496 nor, P2, All,
    ejs76@conceptsfa.nl-bug-wranglers@gentoo.org, NEW, pending,
    nvidia-drivers-9742-beta have been released
11/09 04:44:25 jakub
    ZOMG!
11/09 04:44:59 Opfer
    Jiiiiha
11/09 04:45:33 jakub
    where's the 0day kitten link
11/09 04:47:04 Faustov
    dunno but i got an f1 crash link: http://warpdrive.se/upl/30527.jpg
11/09 04:47:18 jakub
    lol
11/09 04:47:24 Faustov
    :)

11/09 05:02:38 hiyuh
    jakub: http://allen.brooker.gb.net/misc/kitten-0day.jpg
11/09 05:03:00 jakub
    hiyuh: ty; already found it in bookmarks
11/09 05:03:05 hiyuh
    lol
11/09 05:04:21 hiyuh
    http://perso.orange.fr/patrice.mandin/images/nv-kitten.jpg
11/09 05:04:44 jakub
    ahahahah!
11/09 05:05:39 jakub
    bonsaikitten: ^^^ :D
11/09 05:05:50 zlin
    haha
11/09 05:07:10 *
    bonsaikitten segfaults
11/09 05:07:17 armin76
    lol
11/09 05:07:28 hiyuh
    needs to gdb him

dig(DMA.alloc_methods);

今日は，"どっといれぶん"なヘッダを調べつつ，ドライバのDMAな部分に着手．
取り敢えず，念頭においておかなけれならない事は二つ．
[Today, I've poked "dot-eleven" header structure and DMA thingy.
So, DMA thingy has 2 points.]

• デバイス側のDMAコントローラの動作に従う必要が有るので，
  DMAでアクセスすべきメモリ領域の配置に制限を加える事になる．
  [Deu to limitation of device side DMA controller,
  we have to restrict these memory mapping.]


• 実メモリが不足しがちなハードウェアだと，DMAなメモリ領域を動的に，
  且つ細切れで確保すると色々面倒．
  [On small memory hardware, dynamic allocation of fragment
  memories will became only PITA.]

ま，userlandで無駄に*alloc(3)する事と話は変わらないって事ね．
[All I can say is that points are similar to use of *alloc(3)
in useland.]

/* A consistent allocation */
uint8_t essential_memory[SIZE_OF_REQUIRED_MEMORY_IN_OCTET];

/* do somthing here. */

と
[Or,]

/* A dynamic allocation */
uint8_t *p_essential_memory;

p_essential_memory =
    (uint8_t)malloc(
        sizeof(uint8_t *)
        * SIZE_OF_REQUIRED_MEMORY_IN_OCTET
    );
if (p_essential_memory == (uint8_t *)NULL) {
    /*
     * You should do recover allocation failure anyhow,
     * Otherwise, you have to give up.
     */
}

/* do something here. */

free(p_essential_memory);

やっぱり，*alloc(3)にはそれなりの使い方ってのが有る．
オーバーヘッドや繁雑なエラーハンドリングをする苦労をしてでも，
動的にメモリを確保したい場合にだけ使うべき．
[So, use of *alloc(3) depends on its needs.
Whan it uses *alloc(3), it should have some reason
for costs of that overhead and coding error handling.]

仮にオーバーヘッドを気にしない用途だったとしても，
エラーハンドリングを怠っているとSIGSEGVを喰らったり，
"せきゅりてぃほーる"を作るだけ．
manページを読めば分かるけど，OOM killer，所謂メモリ不足解決器も居るし．
[If it's no matter to have some overheads, lacking error
handling produce SIGSEGV annoying, dumb ass^H^H^Hsecurity holes.
To make matte worse, OOM killer is, which is a out of memory beast,
according to man pages.]

これがデバイスドライバのDMAなメモリ領域になると，
大方は連続な領域を確保する必要が有るので，
安直にタイマ無しで動的にメモリ領域を確保しようとすると簡単にロックアップする．
[If we'd talk about device driver's memory allocation,
DMA needs to reserve continuous physical memory.
So, trying reserve it w/o timeout is a easy way to lock-up.]

結局，動作中にDMAなメモリ領域確保に失敗すると話にならないので，
initializeな部分でDMAなメモリ領域を適切な方法で予約して使いまわす．
モジュールと言うportabilityを犠牲にしてもドライバをrobustにしたければ，
メモリマップを変更してしまうと言う荒技もあるが，それは反則なんだと． :P
[Thus, failure of dynamic allocation for DMA is totally nonsense
as a point of view of driver's robustness.
A way to go is reserve memory as sane DMA mapping when it do initialize.
If you really want to completely robust driver and you're ready to
sacrifice its modularize portability, you can do re-map canonical
memory mapping, though.
Of course, I'd have to say it's just abuse. :P]

A SNS so-called MySpace

取り敢えず，作ってみた．
変なSNSですな． :P
[Well, done.
That's bit of subtle, though. :P]
hiyuh's MySpace

(hasFW(&ORiNOCO) && hasFW(&Prism54)) ? P4.curse++ : P4.curse--;

例のプロジェクトP4，イイ感じに雲行きが怪しい！ :X
[That project P4 really su^H^Hrocks! :X]

今日は，ORiNOCOとPrism54なチップの詳細を調べていた．
と言うのは，MACとPHYを突っ込んだFPGA向けにドライバを書く事が一番のTODOなのだけれど，
大体の802.11a/b/gなチップってのはPHYが物理的に論理回路の形で存在して，
MACの半分はembeddedなCPUとは別の内部プロセッサが担当していて，
更にfirmwareを利用して残り半分のMACを実装しているっぽい．
[Today, I've dug ORiNOCO and Prism54 thingy.
Because, my bosses' plan has writing driver for the FPGA which is implemented
our PHY+MAC IP as first TODO.
But, almost of 802.11a/b/g chips has PHY as logical circuit,
and a half of MAC is small embedded processor, the half of MAC is firmware, IIRC.]

で，その半分の中にauthenticationとかassosiationとかの部分が入っているみたい．
うへ，この俺様チップにはembeddedな内部プロセッサは無いがな．
しかも，firmwareが逆アセンブルなソースやS-Recode形式でしか
お目にかかれないって，ヤバくね？ :P
[Then, that MAC part has authentication and association thingy.
Well, our FPGA has no internal embedded processor, though.
And to make matter worse, these firmware can be available as only disassembled
source or S-Recode stuff, ZOMG. :P]

ま，何とかするしかないので，引き続きモニョる予定．
[Hum, all I will do is only do it, though.]

Note(&SKorea[4]) ? FlightBack(&me) : CrackUp(&me);

韓国四日目．
"みょんぼん"(?)と言う所のLOTTEの免税店に行ってきた．
が，"ぶらんど"なブツとかしか見当たらず，何も買えず仕舞い． :(
結局，空港で15万ウォンの茶器セットを実家へのお土産に買いました，
日本円で言うと2万円弱位．
雨が降っていて微妙な天気だった所為か，帰りの飛行機は横に揺れてた．
明日からは何時も通りに仕事．
[SKorea 4th day.
We went to LOTTE's duty-free store of "MyonBon"(?).
However, there are many brand-ed stores, but only like that.
So, I couldn't bought any souvenir. :(
Finally, I bought tea set which is priced 150,000 won for my parents.
FYI, 150,00 won is about 20,000 yen or so.
Well, it was rainy in SKorea, so the aircraft which we were boarding
were rolling somehow, though.
Tomorrow, we'll go on with our working day.]

今回の旅行の感想，「キムチ，一生分喰ったんじゃなかろうか？」 :P
[The summary of this trip is "We can't eat Kimchi any more, I guess?" :P]

Note(&SKorea[3]);

韓国三日目．
今日は怪しい車で市内観光．
博物館っぽい所に行った後，石焼ビビンバを喰って，高麗人参のお茶を飲まされ，
アメジストの押売を華麗に躱し，60階位あるビルみたいな所の展望台に行った後，
遊覧船に乗って，免税店が一杯在る通りを何も買わずに通り過ぎた．
悉く地名を覚えていない． :P
[SKorea 3rd day.
Today, We went to see the city sights.
Seeing museum's stuffs, eating bibimbap, korean ginseng has really subtle gamy,
avoiding forced amethyst sales, up'n'down to/from observatory where is 60 levels,
a boat riding, just passing over duty-free shops.
I just forgot all of their name. :P]

夜は焼肉，"さかな"と言う意味の名前を持つバーでコーラをがぶ飲み．
その後，昨日4時まで上司の方々が42本もビールを飲んでいた言う怪しいカラオケ(?)に行くが，
何かの準備が出来ていないとかで，皆から「残念だな！」と意味不明な事を言われた．
結局，昨日の夜，一体何が起こったのかは謎． :(
[At the night, eating ton of Korean-style grilled meat stuffs,
and going to a bar whose name means "Sakana", I've just drank cola.
And then, we went to a KaraOke, which my bosses drank'n'drank 42 beers at the last
night.
However, the master said like "Sorry, today we're not ready to violent welcome...",
and my bosses said to me like "You, too bad!".
Anyway, I can't realize what happened at the last night there. :(]

明日は，午前中は自由行動らしい，午後は飛行機で日本に帰国の予定．
が，ハングルが全く読/書/発音不能の上，英語も日本語も通じないので，
上司の方々に付いて行くしか選択肢は無さ気．
と言うか，何も御土産を買ってないので，何か用意せねば．
[Tomorrow, we have no plan to use our time of all morning.
But, I can't read/write/pronounce any sucky Hangeul.
So, I have no choice, have to follow my bosses, though.
BTW, I haven't bought any souvenir ATM, would have to buy something, though.]

以下，個人的笑^H衝撃(?)の事実．
韓国にも．．．．
[Below, my LOL'n'SHOCKING memo.
SKorea have also...]

















冥土(?)喫茶が存在する，らしい． :P
[Meido-Kissa is, I heard. :P]

Note(&SKorea[2]), Init(&GentooJP.admin);

韓国二日目．
今日は，38度線(?)まで行きました，所謂非武装地帯ってヤツ．
板門店の中に有る会議をする為の建物の中で，国境を跨いで北朝鮮に入れた． :P
[SKorea 2nd day.
Today, I visited the 38th parallel, there are so-called DMZ or so.
At Panmunjeom, I've been over the borderline to NKorea. :P]

で，その後，「韓国のアキバっぽい所は無いの？」と訊いたらラジデパっぽい所に逝けた．
486DXとかSuperSPARCとかがショーケースの中に鎮座ましましていた．
しかし，土日は殆ど店が閉まっていたので買えなんだ． :P
[Then, we went to a place like Radio-Department of AkiBa.
There were 486DX and SuperSPARC or so.
However, almost of store haven't opened due to today is holiday.
So, I can't buy that junks. :P]

それからGentooJPのadminに入れたっぽい．
取り敢えず，IRCとMLでムニャヘニャする役らしい． :)
[BTW, I've join as a GentooJP admin.
Meanwhile, I have to continue to play at IRC and ML or so. :)]

Note(&SKorea[1]), ricer.point += 10;

現在，韓国一日目．
今日は移動 + 肉のみ，明日はDMZに行くとかなんとか．
感想，"ひこーき"はホントに飛ぶんですねー，すげー． :>
[Now, I'm in SKorea.
Today, I have first flight and ton of meat. :)
My bosses plan to go to DMZ tomorrow.
My impression is, aircraft was really flying, ZOMG. :>]

で，ホテルに着いてもやることは，#gentoo-bugsにてヒキコモx2．
旅行に来て何やってんだかなー．:P
[BTW, I was playing in #gentoo-bugs even in SKorea. :P]

11/04 00:54:12 armin76
    steev64, i guess that qt thing is because qt4 enables qt3 useflag,
    and so the dependency
11/04 00:54:29 steev64
    what
11/04 00:54:30 armin76
    that's why in my case, at least
11/04 00:54:41 armin76
    dbus and qt thingy, gentoo-dev
11/04 00:54:41 steev64
    i have no clue
11/04 00:54:43 steev64
    i hate qt
11/04 00:54:50 steev64
    i don't deal with it at all
11/04 00:55:26 armin76
    really dunno why qt4 enables qt3 use flag
11/04 00:55:43 steev64
    something to take up with the qt herd
11/04 00:56:02 steev64
    they wanted to unmask qt4 beforce dbus was read
11/04 00:56:03 steev64
    y
11/04 01:01:03 steev64
    either way, i blame qt
11/04 01:05:36 jakub
    still better than gtk :P
11/04 01:08:50 armin76
    use tk then
11/04 01:09:21 jakub
    yucky!

11/04 01:11:26 armin76
    with reiser4
11/04 01:12:26 *
    jakub runs
11/04 01:12:38 jakub
    armin76: ricer herd, anyone? :P
11/04 01:14:52 armin76
    haha
11/04 01:15:19 hiyuh
    !herd ricer
11/04 01:15:20 jeeves
    hiyuh: unable to find ricer ; Perhaps one of us is malfunctioning?
11/04 01:15:29 hiyuh
    no herd :P
11/04 01:15:34 jakub
    too bad
11/04 01:15:37 hiyuh
    haha
11/04 01:15:38 jakub
    :>
11/04 01:16:21 jakub
    could have a nifty profile... alpha gcc/glibc snapshots, mm-sources
    and all :P
11/04 01:17:56 jakub
    and of cource -fvisibility-inlines-hidden and --ffast-math by default
    for added ricer feeling
11/04 01:18:40 armin76
    -funroll-loops
11/04 01:19:13 hiyuh
    -funroll-all-loops would be better. :P
11/04 01:23:21 drac
    symlink /usr/portaga/profiles/package.mask to
    /etc/portage/package.unmask by default
11/04 01:24:15 hiyuh
    lol
11/04 01:25:03 jakub
    yay!
11/04 01:25:23 jakub
    drac: +10 ricer points!
11/04 01:25:33 drac
    !!
11/04 01:25:43 drac
    o/ ricerdance
11/04 01:25:50 jakub
    *plop*
11/04 01:30:10 armin76
    lol

isTripping(&me) ? GentooJP.NomiKai-- : GentooJP.NomiKai++;

11/{3,4,5,6}は韓国です．
コンセントの変換コネクタをどっかで買わないとなー．
で，飲み会に行けない． :(
[I'll be tripping at 11/{3,4,5,6} to Skorea.
So I needs AC trans plug somehow.
Well, so I'll be absent that NomiKai. :(]

A stuff of x11-plugins/*

#gentoo-ppcにて，
[On #gentoo-ppc,]

11/01 01:34:51 mabi
    hi folks
11/01 01:35:39 nixnut
    hey mabi
11/01 01:38:17 mabi
    nixnut: your opinion on bug #133806 ?
11/01 01:38:18 jeeves
    mabi: https://bugs.gentoo.org/133806 nor, P2, All,
    ben@berkano.net-maintainer-needed@gentoo.org, NEW, pending,
    gkrellsun-0.12.* does not compile on GCC-4
11/01 01:38:41 mabi
    imho we need to remove the stable keyword from the affected ebuild...
11/01 01:40:16 *
    nixnut looks
11/01 01:42:16 nixnut
    yay, marked stable more than two years ago
11/01 01:42:22 ChrisWhite|Work
       CurrentGMTTime = (long) time(NULL);
11/01 01:42:23 ChrisWhite|Work
       time_struc = gmtime((time_t)&CurrentGMTTime);
11/01 01:42:26 ChrisWhite|Work
    rofl wtf
11/01 01:42:49 ChrisWhite|Work
    "Let's cast it to re-cast it immediately afterwards!"
11/01 01:42:51 ChrisWhite|Work
    that's just hilarious
11/01 01:44:26 nixnut
    mabi: does gkrellsun-1.0.0 work?
11/01 01:46:07 hiyuh
    bah, dumb lvalue unary :P
11/01 01:46:08 hansmi
    ChrisWhite|Work: and even then it's wrong. gmtime wants a time_t*.
11/01 01:48:05 hiyuh
    hmm, (time_t *)&... w/ -fno-strict-aliasing?
11/01 01:48:43 hansmi
    using anything other than time_t there is ugly.
11/01 01:49:00 ChrisWhite|Work
    DESCRIPTION="A GKrellM plugin that shows sunrise and sunset times."
11/01 01:49:02 ChrisWhite|Work
    useless :p
11/01 01:49:10 hiyuh
    hah
11/01 01:49:13 nixnut
    heh
11/01 01:49:42 ChrisWhite|Work
    I wonder how they find bugs in it
11/01 01:49:55 ChrisWhite|Work
    stay up from 4AM onwards :P?
11/01 01:50:53 nixnut
    or just download a list with the sunset/rise times for the next
    couple of decades
11/01 01:54:19 hiyuh
    "so where is that cool list? I really want to know sunset/rise
    times!" j/k :P
11/01 01:55:41 ChrisWhite|Work
    http://www.cmpsolv.com/los/sunset.html

あるのかー！？ :P
[Damn, what cool list!? :P]

(SH + FPGA(MAC, PHY) + RF_mod) / Linux, pthreads, Linkers & Loaders;

夏頃からイイカンジにデスマーチを演出したプロジェクトP3（仮称）が終って，
今度は続きでP4（仮称）をやる事になった． :>
自社製SHボードにFPGAを乗っけて，ソイツに自社IPとして鬼コーディングした
所謂"どっといれぶん"なVHDLマクロでMACとPHYをインプリしつつ，
更に並行して設計が進んでいるRFモジュールをくっつけると言う，
しかもLinuxで動かす気満々な気配． :D
で，その明らかに誰も持っていないチップのデバドラは誰が書くんすか？ :P
[So, I had been beaten by the project P3 since this summer, though.
Then, the project P4 comes, ZOMG. :>
My bosses plan to use our SH board w/ FPGA.
And implement MAC and PHY by using our so-called dot-eleven IP which
is written in VHDL, of course modularized RF part is mandatory.
And then that guys plan to use it w/ Linux, yay! :D
However, who can do code that device driver in spite of there's no one
who has that really rare custom chip? :P]

で，Pthreadsをモニョっている，オラ本で．
APIはPOSIXなので古くても問題無し，中身は何気に結構笑えるポイントがあってイイ感じ． :P
この系統の情報は本の方が良いな，先っぽを追いかけるのも面白いけど．
[BTW, I'm poking Pthreads w/ the O'reilly book
It looks like no problem b/c that API is POSIX-ed.
And that contents have bits of LOL. :P
I'd have to say these thingy needs to be well-documented.
OTOH, ricing has a bit of curios, I knew.]

んで，Linkers & Loadersも読んでいる．
Binaryな野郎を目指していれば，
elf(5)/ld(1)とかのmanページから始めるよりは楽しめると思う． :P
そう言えば，最近，PPC ASMでspammingをされたな． :P
[Well, Linkers & Loaders, I had.
If you're binarian-major, it's quite not worse stuff than man pages of elf(5)/ld(1). :P
BTW, why on the earth does he spam me w/ PPC ASM? :P]

GentooJP.NomiKai++; /* OSC2006 Fall */

と言う訳で，一日だけで800人くらい来ていたOSC2006 Fallでした． :)
以下，簡単な流れとイイ加減なメモ，ど忘れ/勘違いしてるモノもあるかも．
メモはメンドイので日本語のみ．
[Wee, OSC2006 Fall were over.
We would have to thank organizers and 800~ OSS {free,} riders. :)
Here's my memo (only for Japanese) of that event, but it might include
my limbo/misremember, though.]

10/27 night
* #gentoo-jaで準備の話，NETGEARな24ポートHUBがデカすぎると言われる．
* 2005.xなままだったが，Armadillo-9を持って行く事にした．
* #gentoo-{ppc,bugs}で戯れる．
* 取り敢えず，一眠り．

10/28 early-morning
* 夜光性なのと遅刻の恐怖に勝てず熟睡出来ず．
* 仕方無いので，xynth-svn-20061027をsvn coして弄る．
* 更に，mercurialでxynth用レポジトリをでっちあげて，
strict-aliasing, signed/unsigned, PICを直す．

10/28 morning
* 大久保で迷子になるが，二番手で会場入り．
* Gentooポスターとかを止めるテープが無かった．
* HUBを鬼カスケード．
* Armadillo-9用のMicroDriveのファイルシステムがぶっ壊れていた．
* マイナスドライバーが無くて，Armadillo-230の中身が拝めず．
* Gentooバッグを購入，¥3150也．
* 配布するパンフはpress releaseのみでabout.xmlは無し．
* Plan9/Infernoえーなー．
* Exciteは何気に強敵．
* dev-libs/DirectFBとsys-fs/fusionのCVS snapshot ebuildをアップデート．
* プチ壊れたdev-libs/DirectFB関係のブツをrevdep-rebuild．
* Debianは不^H安定だと言うお客さん登場．
* Gentooはもっと不^H安定に出来ると自虐^H慢．

10/28 noon
* www-client/mozilla-firefox-2.0をunmask'n'emergeして放置．
* タイ料理屋で
+ スパムの話．
+ ファイルシステムの話．
+ ビデオカードの話．
+ デバイスドライバの話．

10/28 afternoon
* www-client/mozilla-firefox-2.0のemergeが終っていた，無事動作．
* 2006.1なCDもパンフも捌き終っていた．
* app-i18n/scim-anthy on x11-terms/xtermが
+ DOESNOTWORK(tm).
+ WORKSFORME(tm).
* KでFでUECな知人が来る．
* UでkokenでUECな知人が来る．
* 最新版ウダーを触る．

10/28 early-evening
* 片付け + 机と椅子の移動．
* コーヒーショップで
+ LDAP/HaskellなGentoo devsの話．
+ ebuildjp tree cleanerの話．
+ SOXとISOの話．
+ ADSLモデムと二色のUTPケーブルの話．
+ dev-util/{subversion,mercurial}の話．

10/28 evening
* 懇親会で，
+ ビール
+ コーラ
+ オレンジジュース
+ 青椒肉糸？
+ 春巻？
+ サラダ
+ ポテト
+ じゃんけん，主に本争奪の為．
+ 放置中のbugに関しての謝罪．

一番ショックだった事は，何故かdev-util/subversionが大人気な事． :P
[Bah, you guys really lovin' dev-util/subversion? :P]

NatsuYasumi, sys-apps/pkgcore, autotools hell, notepad++

と言う訳で，例のブツが取り敢えず終ったので，
10/21から10/29まで夏休み(!?)になりました． :P
で，やること．
[K, I've done t3h thingy.
So, I'll take a week off as summer vacation(!?). :P
Then, here's my TODO in that week.]

1) 2006.1 press releaseを訳す．
2) Xynth on Armadillo-9 w/ Gentoo
3) 実家に顔を出す．
[1) Translate 2006.1 press release to Japanese.
2) Xynth on Armadillo-9 w/ Gentoo
3) Homecoming]

OSCがあるので1)は急ぎ，2)は間に合えば，3)は気が向けば，かな？
[We have OSC at 10/28.
So 1) is critical, 2) is major, 3) is minor.]

#gentoo-dev-helpにてsys-apps/pkgcoreの存在を知る．
[At #gentoo-dev-help, marienz said sys-apps/pkgcore is.]

10/18 01:31:17 hiyuh
    !rdep yacc
10/18 01:31:18 jeeves
    dev-util/yacc <- app-shells/ash dev-libs/tinyq dev-util/cdecl
    mail-client/etpan-ng net-p2p/gtk-gnutella sys-fs/lde
10/18 01:31:35 hiyuh
    !rdep bison
10/18 01:31:38 jeeves
    yikes 30 pkgs reverse rdepend on bison! Try digging around here
    instead. http://tinderbox.dev.gentoo.org/misc/rindex/
10/18 01:31:48 hiyuh
    hmm
10/18 01:43:28 marienz
    hiyuh: what are you trying to do? pquery from pkgcore lets you do
    this kind of search restricted to a category or other things (although
    it's a bit slower than jeeves since it doesn't have an index for it)
10/18 01:58:50 hiyuh
    marienz: I'm thinking about virtual/yacc enhancement. in portage
    tree, there're some YACCs. directly depends dev-util/aycc or so may
    be OK, but sys-devel/bison is mandatory for sys-devel/gcc, IIRC. and
    "bison -y" == "yacc".
10/18 02:00:37 marienz
    hmm, don't know enough about that to help you
10/18 02:00:50 marienz
    pquery --revdep dev-util/yacc --raw should give you a list of stuff
    though :)
10/18 02:01:17 hiyuh
    ok, thanks :)
10/18 02:18:46 hiyuh
    marienz: argh, sys-apps/pkgcore is not ~ppc keyworded, isn't it so
    arch depends? :(
10/18 02:19:02 marienz
    hiyuh: it's pretty new. There's an extremely good chance it will
    just work.
10/18 02:19:43 hiyuh
    ok, i'll try.
10/18 02:19:54 marienz
    hiyuh: (if it fails it'll fail in the c bits, which are fairly well
    tested if you set FEATURES=test)
10/18 02:20:31 hiyuh
    k
10/18 02:28:13 hiyuh
    marienz: looks like "IT JUST WORKS (tm)" :)
10/18 02:28:32 marienz
    hiyuh: yay, guess I should find a ppc arch team member at some point
    to add that keyword
10/18 02:32:56 ChrisWhite|Work
    I'd add it myself if I wasn't ppc (not ~ppc)
10/18 02:46:17 hiyuh
    wow, pquery really rocks...

同じく#gentoo-dev-helpにて，autotoolsの被害者が発生．
[At #gentoo-dev-help too, autotools beat _masterdriverz_.]

10/18 19:30:45 _masterdriverz_
    a package im writing an ebuild for says it requires libxfree86,
    which is a bit ambiguous
10/18 19:31:14 _masterdriverz_
    is it x11-libs/libXxf86dga, x11-libs/libXxf86misc, x11-libs/libXxf86vm
    or something else?
10/18 21:20:59 hiyuh
    _masterdriverz_: on my system "locate xfree86" shows no
    libxfree86.{so,a}, but x11-libs/libXxf86{dga,misc,vm} are
    installed. so guess you need "something else".
10/18 21:21:30 _masterdriverz_
    hiyuh, i think its a debian/rpm package, but im not sure what its
    gentoo name is
10/18 21:22:24 hiyuh
    heh, btw what's that?
10/18 21:25:55 zzam
    _masterdriverz_: it will require some libX11 and more I suspect -
    if it is no very strange package
10/18 21:26:23 _masterdriverz_
    hiyuh, http://vision.eng.shu.ac.uk/mediawiki-1.4.10/index.php/Mimas
10/18 21:26:41 _masterdriverz_
    zzam, ok thanks, looks like ill have to test and find out :(
10/18 21:27:54 zzam
    _masterdriverz_: ignore the text from readme of the package and read
    the text about modular-x-porting
10/18 21:29:13 zzam
    the ebuild seems to have a long list in DEPEND :)
10/18 21:29:14 _masterdriverz_
    zzam, will do, but the README is less than helpful - going through
    configure.in shows it has loads of dependencies that it doesn't list
    in the README :(
10/18 21:29:42 _masterdriverz_
    zzam, err, what ebuild?
10/18 21:30:11 zzam
    the one you are writing
10/18 21:30:18 _masterdriverz_
    ah
10/18 21:31:03 _masterdriverz_
    you had me worried there - im supposed to be writing some unique
    ebuilds in preparation for devship (yay!), and this one's taken me
    ages :(
10/18 21:40:21 hiyuh
    _masterdriverz_: heh, I guess to do "grep -e -lX configure" helps.
10/18 21:40:56 _masterdriverz_
    hiyuh, to be honest, i think its the least of my worries :(
10/18 21:41:26 _masterdriverz_
    this package has tooo many automagic dependencies
10/18 21:41:43 _masterdriverz_
    eg, just found it (might) use libdc1394, but it might not
10/18 21:42:08 hiyuh
    yep, that's so-called autotools hell.
10/18 21:43:21 *
    _masterdriverz_ senses a big patch for the Makefile, and a big smack
    from his cluebat for the author :)
10/18 21:43:53 hiyuh
    maybe, it requires libX{11,ext,mu,t,i}.
10/18 21:44:45 _masterdriverz_
    hiyuh, i think its xine actually
10/18 21:44:48 _masterdriverz_
    :(
10/18 21:44:59 _masterdriverz_
    why can't people come up with sane names for packages?
10/18 21:46:20 hiyuh
    beacause, we like ACRONYM? :P
10/18 21:47:04 _masterdriverz_
    but libxfree86 is just sooo ambiguous its stupid
10/18 21:48:18 hiyuh
    couldn't help, it's just histrical relic. :P
10/18 21:48:23 zzam
    you also can just build it now and analyze the linkage of the binary
10/18 21:49:08 hiyuh
    yep, if you have missing ones, linker will tell some missing symbols.
10/18 21:50:10 _masterdriverz_
    zzam, haven't got that far yet *sigh*
10/18 21:50:31 _masterdriverz_
    i think im gonna commit suicide before i finish src_compile :(
10/18 21:50:52 zzam
    hiyuh: problem is: packages are installed and silently linked against
10/18 21:52:16 _masterdriverz_
    "Please report bugs to jan@wedesoft.de" :)
10/18 21:52:24 hiyuh
    if so, it needs runtime testing, though.
10/18 21:53:18 _masterdriverz_
    there is not _one_ single instance of ./configure checking whether
    i want the option disabled or not
10/18 21:55:49 _masterdriverz_
    hiyuh, zzam, either of you got an example of a decent configure
    script so i can work out how to patch it correctly?
10/18 21:56:12 zzam
    autoconf is crazy
10/18 22:01:24 _masterdriverz_
    err, not the answer i was looking for
10/18 22:01:27 hiyuh
    zzam: agreed.
10/18 22:03:51 hiyuh
    _masterdriverz_: IIRC, dev-manual tells bit of autotools detail.
10/18 22:04:06 _masterdriverz_
    hiyuh, thanks
10/18 22:04:10 hiyuh
    np

そして，Windows上でMercurialのデフォルトのエディタはnotepadになりました． :P
[Default editor for Mercurial on Windows should be notepad. :P]
[PATCH] Default editor for Windows installer is now notepad. [Issue 256]
Re: [PATCH] Default editor for Windows installer is now notepad. [Issue 256]