**** BEGIN LOGGING AT Fri Jan 18 02:59:59 2013
Jan 18 06:13:42 <impulse> is there a shell mode for qtopia's gsm stack?
Jan 18 10:23:17 <radekp> impulse: no, but it can be implemented, but noone did it yet
Jan 18 10:23:29 <radekp> impulse: other option is to use QtMoko with FSO or with oFono
Jan 18 10:23:56 <radekp> impulse: you can google it up - search for QTMOKO_PHONE environment variable
Jan 18 11:34:45 <impulse> radekp: like FSO-abyss?
Jan 18 11:35:46 <impulse> oh good it uses libnl
Jan 18 13:11:11 <ayaka> GNUtoo-x60, my headmaster in college decide do camera in airplane, I need to use arm to encode video from camera and send it thought wlan, do you have any ideas and which ARM chip do you suggest?
Jan 18 13:28:14 <GNUtoo-x60> omap?
Jan 18 13:28:23 <GNUtoo-x60> so you have gstreamer support
Jan 18 13:28:37 <GNUtoo-x60> like omap3
Jan 18 13:32:17 <ayaka> GNUtoo-x60, does gstreamer support hardware encode ?
Jan 18 13:32:41 <GNUtoo-x60> for omap yes
Jan 18 13:32:56 <GNUtoo-x60> look at gst-dsp for instance
Jan 18 13:33:09 <GNUtoo-x60> but software encode should be fast too
Jan 18 13:33:13 <GNUtoo-x60> like with gstreamer 1.0
Jan 18 13:33:20 <GNUtoo-x60> with 0.10 it's another story
Jan 18 13:34:02 <ayaka> in 3.7 mainline, I only find OMAP2 and OMAP 1, does OMAP3 are lastest OMAP platform ?
Jan 18 13:34:17 <GNUtoo-x60> omap3 is in the omap2 directory
Jan 18 13:34:59 <ayaka> I don't know there is gstreamer 1.0, I only know there is 0.10, so software encode is also accept now?
Jan 18 13:35:41 <GNUtoo-x60> it depend on how efficent is the software
Jan 18 13:36:00 <GNUtoo-x60> but if the software is efficent it's faster and better than the "hardware" decoding on omap3
Jan 18 13:37:13 <GNUtoo-x60> basically gstreamer 0.10 is ultra inefficent in setting the pipes
Jan 18 13:37:17 <GNUtoo-x60> gstreamer 1.0 fixes that
Jan 18 13:37:50 <ayaka> I see
Jan 18 13:39:32 <ayaka> OMAP platform is much expensive than s3c6410, but headmaster said that he doesn't know embedded at all, if you can give me some info, I will think of it
Jan 18 13:40:16 <ayaka> GNUtoo-x60, what is the advantage of OMAP3 than s3c6410, if we use software
Jan 18 13:41:33 <GNUtoo-x60> if you use software decoding, it makes no differences I guess
Jan 18 13:41:46 <GNUtoo-x60> apart in the speed of the CPU
Jan 18 13:41:49 <GNUtoo-x60> let me look
Jan 18 13:42:56 <GNUtoo-x60> hmmm
Jan 18 13:43:04 <GNUtoo-x60> the s3c should be armv6-vfp
Jan 18 13:43:09 <GNUtoo-x60> so no neon
Jan 18 13:43:13 <GNUtoo-x60> which speeds things
Jan 18 13:43:51 <ayaka> yes
Jan 18 13:44:40 <GNUtoo-x60> if wlan is fast enough....
Jan 18 13:44:47 <GNUtoo-x60> you could encode in mjpeg for instance
Jan 18 13:45:03 <GNUtoo-x60> that way it would be fast enough
Jan 18 13:45:24 <ayaka> but it is only 500yuan as panda is 1740yuan and panda es is 1680yuan
Jan 18 13:45:55 <GNUtoo-x60> how much is beagle?
Jan 18 13:47:05 <GNUtoo-x60> I guess the s3c6410 is the mini6410 board
Jan 18 13:47:12 <ayaka> BeagleBoard-xM ARM Cortex-A8 is 1490 yuan
Jan 18 13:47:19 <GNUtoo-x60> ouch
Jan 18 13:47:53 <ayaka> http://www.witech.com.cn/product/TE-6410.html
Jan 18 13:48:45 <GNUtoo-x60> ah I didn't know this one
Jan 18 13:49:47 <ayaka> it is  s3c6410  dev board, I showing the url is to answer "I guess the s3c6410 is the mini6410 board"
Jan 18 13:49:59 <GNUtoo-x60> yes I know
Jan 18 13:50:01 <ayaka> I don't know which size is mini
Jan 18 13:50:13 <GNUtoo-x60> I don't remember the name exactly
Jan 18 13:50:22 <GNUtoo-x60> I'm not totally sure it's name is mini
Jan 18 13:50:28 <GNUtoo-x60> but it has 6410 in its name
Jan 18 13:50:58 <GNUtoo-x60> http://www.friendlyarm.net/products
Jan 18 13:51:00 <GNUtoo-x60> found it
Jan 18 13:51:16 <ayaka> http://www.arm9.net/mini6410-feature.asp
Jan 18 13:51:40 <ayaka> is that one ^^^ ?
Jan 18 13:51:56 <GNUtoo-x60> yes
Jan 18 13:52:01 <GNUtoo-x60> it's the one from friendlyarm
Jan 18 13:52:14 <GNUtoo-x60> the advantage is that it's very well supported
Jan 18 13:52:47 <ayaka> then how well it is supported
Jan 18 13:53:00 <GNUtoo-x60> what do you want to run on it?
Jan 18 13:53:10 <ayaka> in kernel source, I find s3c6410 doesn't need config board type
Jan 18 13:53:43 <GNUtoo-x60> mach-mini6410.c
Jan 18 13:54:02 <GNUtoo-x60> in arch/arm/mach-s3c64xx
Jan 18 13:54:48 <GNUtoo-x60> at least there is something in mainline
Jan 18 13:55:00 <ayaka> I don't know the exactly software, but I will encode video from camera, then send it through wlan, maybe the video is 720P
Jan 18 13:55:15 <GNUtoo-x60> ok
Jan 18 13:55:25 <GNUtoo-x60> I'm not sure on the required performances
Jan 18 13:55:32 <ayaka> is TE-6410  same to mini6410 ?
Jan 18 13:55:37 <GNUtoo-x60> no
Jan 18 13:57:01 <ayaka> I see, if I compile a kernel for mini6410 and run it on te6410, at lease, it won't damage my SoC, doesn't it
Jan 18 13:59:57 <GNUtoo-x60> it won't work at all probably
Jan 18 14:00:29 <GNUtoo-x60> and also note that they don't accept new board files, all boards have to be converted to device tree booting
Jan 18 14:00:58 <GNUtoo-x60> see arch/arm/boot/dts
Jan 18 14:01:10 <ayaka> but if won't damage board, at lease I can have a test and modify the board file, I know dts, but I think I can't write a one at once
Jan 18 14:01:25 <ayaka> you have teached me dts in the last year
Jan 18 14:01:38 <GNUtoo-x60> I can't assure that it won't damage the board
Jan 18 14:01:52 <GNUtoo-x60> it's not predictable
Jan 18 14:02:13 <ayaka> then I won't test
Jan 18 14:02:43 <GNUtoo-x60> ah maybe they still accept board files
Jan 18 14:02:51 <GNUtoo-x60> I saw patches for s3c device tree
Jan 18 14:02:58 <GNUtoo-x60> but I'm not sure that it's in yet
Jan 18 14:03:01 <ayaka> because headmaster can't wait so long, I may use 2.6 new
Jan 18 14:03:18 <GNUtoo-x60> here's the issue
Jan 18 14:03:22 <ayaka> when I have time , I will try to write a dts
Jan 18 14:03:25 <GNUtoo-x60> you're spending quite some money on a board
Jan 18 14:03:35 <GNUtoo-x60> you're not sure it will work for you
Jan 18 14:03:49 <GNUtoo-x60> so the thing is that with a well known board etc...
Jan 18 14:03:53 <GNUtoo-x60> you minimize the risk
Jan 18 14:04:10 <GNUtoo-x60> because you may have a bad kernel for the other not-very-well-known board
Jan 18 14:04:14 <GNUtoo-x60> like with software bugs
Jan 18 14:04:18 <GNUtoo-x60> like hard ones
Jan 18 14:04:26 <GNUtoo-x60> which prevent you to make your app work
Jan 18 14:04:32 <ayaka> yes, is there another dev board suggest, which is cheap
Jan 18 14:04:57 <GNUtoo-x60> are the friendly arm board cheap?
Jan 18 14:06:09 <ayaka> less than $140(1000yuan)
Jan 18 14:07:06 <GNUtoo-x60> maybe beaglebone then?
Jan 18 14:07:09 <GNUtoo-x60> or rasberry?
Jan 18 14:07:21 <GNUtoo-x60> but they have probably no wifi
Jan 18 14:08:52 <ayaka> I have a usb wifi adapter, or I can use wifi in SDIO adapter
Jan 18 14:09:27 <GNUtoo-x60> ok
Jan 18 14:09:30 <ayaka> but it seems that there is no 802.1n adapter in SDIO now
Jan 18 14:09:33 <GNUtoo-x60> then you need USB host
Jan 18 14:10:04 <GNUtoo-x60> worst case scenario with the not-well-known boards:
Jan 18 14:10:08 <GNUtoo-x60> -> no kernel sources
Jan 18 14:10:28 <GNUtoo-x60> -> doesn't have the driver for your webcam compiled in, no way to fix
Jan 18 14:12:01 <ayaka> sorry, go to WC, brb
Jan 18 14:14:57 <ayaka> back
Jan 18 14:15:27 <ayaka> BeagleBone，ARM Cortex A8,AM3358/AM3359 is only 680yuan but it doesn't have camera adapter
Jan 18 14:15:37 <GNUtoo-x60> ok
Jan 18 14:16:07 <ayaka> I don't know how to call the the camera adapter which with 20 pins
Jan 18 14:18:46 <ayaka> rasberry pi is also armv6 which doesn't support neon, doesn't it?
Jan 18 14:19:06 <GNUtoo-x60> yes but it's more well known
Jan 18 14:19:30 <ayaka> yes
Jan 18 14:21:43 <ayaka> really, I don't dare to use a board which doesn't have mainline support, but the price is the problem. All devboard the headmaster bought will ofter kernel source
Jan 18 14:21:57 <GNUtoo-x60> my point is to minimize issues
Jan 18 14:22:03 <GNUtoo-x60> if you buy an useless board....
Jan 18 14:22:07 <GNUtoo-x60> it's not good
Jan 18 14:22:19 <ayaka> yes
Jan 18 14:22:31 <GNUtoo-x60> so maybe tripple check before buying
Jan 18 14:22:47 <ayaka> but he has bought them, I have to try to do
Jan 18 14:22:52 <GNUtoo-x60> like check kernel sources etc...
Jan 18 14:22:55 <GNUtoo-x60> ah ok
Jan 18 14:23:10 <GNUtoo-x60> I'll go
Jan 18 14:23:15 <ayaka> I said the headmaster doesn't know embedded(he say that)
Jan 18 14:23:23 <ayaka> GNUtoo-x60,  thank you very much
Jan 18 14:23:24 <ayaka> see you
Jan 18 14:23:30 <GNUtoo-x60> ok see you
Jan 18 18:13:32 <MrMc> I would like to write a baremetal os for fun I have a GT02 how can I print hello world 
Jan 18 18:13:41 <MrMc> on the LCD
Jan 18 18:14:40 <slyon_> hi
Jan 18 18:14:53 <MrMc> hello
Jan 18 18:16:55 <slyon_> GNUtoo-x60, JaMa|Off: I've just fixed resolv.conf / DNS in our images. (in danny and shr branches)
Jan 18 18:17:21 <GNUtoo-x60> slyon_, ok thanks
Jan 18 18:18:31 <GNUtoo-x60> MrMc, maybe look at uboot code
Jan 18 18:27:56 <slyon> GNUtoo-x60, do you have admin rights in SHR's trac?
Jan 18 18:28:21 <GNUtoo-x60> I don't think so
Jan 18 18:28:28 <GNUtoo-x60> JaMa|Off, has
Jan 18 18:28:48 <MrMc> GNUtoo-x60: Thanks. I am reading the code 
Jan 18 18:29:20 <slyon> JaMa|Off, can you somehow recover my SHR-trac account? i wanted to change my email address, but trac doesn't send out the confirmation mail. so I've no rights anymore..
Jan 18 18:29:35 <MrMc> but cant see the gta02 stuff 
Jan 19 02:06:10 <mmagcww> Good evening, what I could use right now is a good reference to how these firmware images are loaded. I've been around in circles quite a few times already. I brute force placed both the firmware image along with the results of /proc/calibration in /etc/firmware/, /etc/firmware/wifi, /system/etc/firmware, /system/etc/firmware/wifi, /lib/firmware -- now that I think of it I haven't tried /lib/firmware/wifi
Jan 19 02:07:55 <mmagcww> Everytime I reboot, I have to do fsck, then I load msm_wifi and I check ifconfig, each time it shows a new MAC address, the same 3 fields with 3 new fields at the end. 
Jan 19 02:09:21 <mmagcww> The documentation is sparse, and everywhere, I'm trying to get this wpa_supplicant sorted out, then I can do a right up on the whole mess. I'll add it to tweaks for now.
Jan 19 02:12:41 <mmagcww> So to make the problem clear, I do all the steps check the state of rfkill0, make sure it's set to 1 then try and bring wlan0 up with ifconfig. That's when it freezes up, and maybe it's simple to fix, though I've been at it all day and have yet to find what I'm looking for
Jan 19 02:13:58 <mmagcww> I already have a successful wpa_supplicant.conf and working interface section to go on, so that helps rule that out, at least for when I try to ifup wlan0
Jan 19 02:15:24 <mmagcww> As you can see, I'm no programmer, not yet anyway, though I can start with writing a thorough documentation of my efforts while setting things up on the phone, a document with plenty of details all in one location
Jan 19 02:18:05 <mmagcww> I don't no where to look for my answers, I need the magic words
Jan 19 02:20:11 <mmagcww> Wait a second, ifconfig doesn't load the firmware
**** ENDING LOGGING AT Sat Jan 19 02:59:59 2013