Confusing issue of Android m5_rc14

I'm working on and off porting m5_rc14 to Zaurus. Yet I haven't seen anything on LCD. Just black out. In the emulator, fb0 the frame buffer device is in /dev/graphics instead of /dev like Zaurus Angstrom. Crossing fingers, I copied it to graphics directory.
# mkdir /dev/graphics
# cp /dev/fb0 /dev/graphics/fb0
# chmod 666 /dev/graphics/fb0
No luck. Still blank screen. Though fuser command and strace says that runtime and dalvikvm opens successfully /dev/graphics/fb0. Weird.

When I try to see Android log by logcat command, it says an error
/dev/log: Not a directory
Well, it is not a directory but a file in Zaurus. In the emulator, it is a directory. So I checked the source code of the logger and found
#define LOGGER_LOG_RADIO	"log_radio"	/* radio-related messages */
#define LOGGER_LOG_EVENTS "log_events" /* system/hardware events */
#define LOGGER_LOG_MAIN "log_main" /* everything else */
in include/linux/logger.h. This is really weird. logcat expects /dev/log as directory and logger driver creates log_xxx in /dev. Is there any glitches between m5_rc14 kernel and m5_rc14 Android?
posted by 安藤恐竜 at 11:16 | Comment(13) | TrackBack(0) | 日記




・マイブログの【設定】 > 【広告設定】 より、「60日間更新が無い場合」 の 「広告を表示しない」にチェックを入れて保存する。