Hi, I’m Kaiwan N Billimoria, a software developer / consultant / trainer / evangelist! -whew 😉
I essentially work on the Linux platform, mostly systems kind of stuff… I have contributed some driver code into the mainline Linux kernel. To earn a living (and I enjoy it!), I provide Corporate Training on various Linux kernel / driver / embedded / systems programming topics.
If you’d like to see it, this is my LinkedIn profile page.
(All links open a new window).
Do browse through my blog… I would truly appreciate your comments,
TIA, kaiwan.
kaiwanTECH: Kaiwan's Tech Blog 
Hello Kaiwan,
I am wondering if you were ever successful in your efforts to port Android to the ts7200 and if you would be willing to share a copy of the port?
Thanks for your time (and effort!)
Les Parker
Les,
Thanks for your interest..
I got to the point where I had the Android-kernel booting off the TS7200 but did not proceed any further into userspace porting (mainly becoz I don’t have a LCD/kbd attached).
So what exactly would you like me to share? The diff of the kernel? I could do that… let me know, regards,
kaiwan.
I will take whatever you are willing to share – preferably a copy of the SD card image you are booting from or a tar file if the boot directory containing the zImage and files. If you need space, let me know and I will set up an ftp or ssh account on my server.
Thanks again,
les@bpnrg.com
Hi Kaiwan,
Thanks for article on “Setting up kdump on ARM 32”
I have some basic queries while i am trying to enable kdump(to generate vmcore) on ARM based board..
https://www.kernel.org/doc/Documentation/kdump/kdump.txt [1]
followed above link;
my host is x86(ubuntu) having linux -android
In my ARM board source (board config file), i couldn’t see below configs
CONFIG_KEXEC=y
CONFIG_SYSFS=y <>
CONFIG_DEBUG_INFO=y
CONFIG_CRASH_DUMP=y
CONFIG_PROC_VMCORE=y
kindly correct me if i am wrong..!
Thanks in advance…
Pawamana Tanjore.
(I know my reply’s v late, apologies… ) my post is based on a vanilla Linux kernel whereas you seem to be on an Android kernel.. assuming it’s a kernel for a custom device, its quite possible the kdump/kexec options have been removed by the BSP/platform team