This is indeed worth a wiki page. Does this work for the 2.0 codebase? Thanks & Regards Xun Sun
From: [email protected] [mailto:[email protected]] On Behalf Of Ylinen, Mikko Sent: Thursday, February 20, 2014 7:29 PM To: Deshpande, Ketan Cc: [email protected] Subject: Re: Getting the log output for WRT plugin On Thu, Feb 20, 2014 at 10:09 AM, Deshpande, Ketan <[email protected]<mailto:[email protected]>> wrote: Hello All, I have an NDiS 166 platform. I am trying to get the log on my system. I have already done following things 1. insmod /usr/lib/modules/3.12.4-10.1-x86-ivi/kernel/drivers/staging/android/logger.ko 2. chmod 666 /dev/log* 3. Enabled IVI based logs by modifyng /etc/profile.d/wrt_env.sh There seems to be some confusion still how logging (dlog) is configured in Tizen IVI. Let me clarify (perhaps worth putting this in a wiki as well): - libdlog output is configurable: it can output logs in Android logger FIFO or systemd Journal - the configuration is determined build time using '%bcond_with dlog_to_systemd_journal' - Tizen:IVI project has %define _with_dlog_to_systemd_journal 1 As Corentin pointed out, to enable libdlog output on the target one needs to $ dlogctl set platformlog 1 (dlogutil package needs to be installed first) And then simply $ journalctl <params> To use Android logger FIFO instead of Journal: - build dlog with $ gbs build <options> --define "_with_dlog_to_systemd_journal 0" - install new libdlog - dlogctl set platformlog 1 - modprobe logger.ko - run dlogutil -- Mikko
_______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
