**** BEGIN LOGGING AT Sun Nov 10 02:59:58 2013
Nov 10 04:40:10 <lumag> ant_home, I wander how it did work. It looks like I found an error in locomo backlight handling.
Nov 10 04:42:54 <lumag> In locomo_m62332_sendbit (arch/arm/common/locomo.c) change second 'r &=  ~(LOCOMO_DAC_SCLOEB);' line to read 'r &=  ~(LOCOMO_DAC_SDAOEB);'
Nov 10 04:55:45 <lumag> ant_home, and most probably you need to have obj-... += backlight/  in the end of drivers/video/Makefile, instead of it being somewhere in the middle
Nov 10 08:13:09 <bikerer> whee, fantastic, combined kexecboot into a recovery.img for android, so first kexecboot can start, then when you can quit and enter recovery mode
Nov 10 08:13:23 <bikerer> CM recovery
Nov 10 08:15:17 <Jay7> cool! write post about it and give us a link :)
Nov 10 08:18:49 <bikerer> was about to upload the image to my server and xda it ;)
Nov 10 08:19:34 <bikerer> just barely made it within 5 megs too, got adb too since its recovery :D
Nov 10 08:19:41 <bikerer> couldnt make room for bash though
Nov 10 08:21:37 <Jay7> try another shell
Nov 10 08:22:11 <Jay7> dash e.g.
Nov 10 08:24:13 <bikerer> http://threader.zapto.org/experimental/s7/kexecboot-recovery/recovery-kex.img
Nov 10 08:24:35 <bikerer> there is a shell trough busybox
Nov 10 08:24:37 <bikerer> or cm recovery
Nov 10 08:24:41 <bikerer> so we have as hell
Nov 10 08:24:43 <bikerer> shell
Nov 10 08:24:44 <bikerer> :D
Nov 10 08:24:45 <Jay7> ah, ok then
Nov 10 08:25:25 <Jay7> for which tablet/phone is this image?
Nov 10 08:25:46 <ant_home> gm
Nov 10 08:25:49 <ant_home> hi Jay7
Nov 10 08:26:36 <bikerer> Jay7, huawei s7 , a qsd8x50
Nov 10 08:27:14 <Jay7> ant_home: hi
Nov 10 08:27:57 <Jay7> ant_home: may be good idea to place link to bikerer's post on kexecboot.org site ;)
Nov 10 08:28:50 * Jay7 afk for some hours
Nov 10 08:30:04 <bikerer> see ya jay! thanks :>
Nov 10 08:34:03 <lumag_> ant_home, gm
Nov 10 08:34:30 <lumag_> How is your kid feeling, btw?
Nov 10 08:40:32 <ant_home> 37+*
Nov 10 08:40:52 <lumag_> :(
Nov 10 08:44:22 <lumag_> I have sent your an idea regarding lcd. I'm not 100% sure that it is the reason of 'stalled' pictures, but it is worth trying.
Nov 10 08:45:41 <lumag_> gtg/bbl
Nov 10 08:46:45 <ant_home> ah, yes, I'll test in a few mins
Nov 10 08:47:44 <ant_home> finishing the mtd-tests
Nov 10 08:47:53 <ant_home> all fine until now
Nov 10 08:52:20 <bikerer> hum, now, how to boot android then :D
Nov 10 09:09:59 <bikerer> aah excellent :D
Nov 10 09:10:16 <bikerer> android booted just fine with the initrd thinige
Nov 10 09:10:39 <bikerer> uuh
Nov 10 09:11:05 <bikerer> nvm :D
Nov 10 09:36:46 <bikerer> funny, i lost adb when booting android ?
Nov 10 09:58:40 <bikerer> http://forum.xda-developers.com/showthread.php?t=2520663 still no photos though, probably wont be until later, promised a friend i would help tare something down, and burn it :D
Nov 10 10:38:00 <ant_home> lumag: the difference is that i get a white screen
Nov 10 10:38:42 <ant_home> iirc this happened postponing backlight
Nov 10 10:38:53 <ant_home> maybe need a precise line
Nov 10 10:41:37 <ant_home> before vfb.o ?
Nov 10 10:41:46 <ant_home> no idea...
Nov 10 10:50:43 <bikerer> heh. the abd enabling at boot is lost, i have to re-enable it in the menu of android
Nov 10 10:56:11 <bikerer> hm, ok, no its lost completely
Nov 10 10:57:04 <bikerer> and then it crashes
Nov 10 10:57:28 <bikerer> must be failing to launch adbd
Nov 10 11:04:02 <bikerer> hmm, does not like sleep modes either
Nov 10 11:25:33 <ant_home> lumag: mtd_torturetest: Page 0 has 512 bytes/3584 bits failing verify, starting at offset 0x0
Nov 10 11:25:33 <ant_home> Offset       Read                          Written
Nov 10 11:25:33 <ant_home> 0x00000000:  80 80 80 80 80 80 80 80  ***  ff ff ff ff ff ff ff ff
Nov 10 11:25:43 <ant_home> that same 808080 status
Nov 10 11:27:03 <ant_home> as ubi had
Nov 10 11:27:05 <ant_home> sa1100: Chip not ready for buffer write. Xstatus = 80808080, status = 80808080
Nov 10 12:04:09 <bikerer> uhm, is RAMDISK i a valid config entry?
Nov 10 12:04:23 <bikerer> since kexec supports it
Nov 10 15:06:40 <bikerer> ugh, had to add a bunch of "oneshot" to every service in init.rc for the thing not to go bananas
Nov 10 16:09:45 <Jay7> bikerer: http://kexecboot.org/documentation/how_to_write_config
Nov 10 16:10:16 <Jay7> i.e. no RAMDISK
Nov 10 16:13:43 <bikerer> started trying to add it
Nov 10 16:13:53 <bikerer> but doesnt seem to make much difference
Nov 10 16:13:54 <ant_home> bbl
Nov 10 16:13:57 <bikerer> initrd or ramdisk
Nov 10 18:24:22 <ant_home> lumag: about chip not ready:  http://mhonarc.axis.se/jffs-dev/msg00703.html
Nov 10 18:32:08 <ant_home> I've sent this as well to linux-mtd
Nov 10 18:37:32 <lumag_> This is over my understanding of mtd...
Nov 10 18:38:13 <ant_home> an old post about ipaq was...overheating...
Nov 10 18:38:34 <ant_home> http://pastebin.com/y92ZZsuF
Nov 10 18:38:49 <ant_home> ^^ I've sent this logs to linux-mtd
Nov 10 18:40:00 <ant_home> note how mtd_stresstest fails with count > 15
Nov 10 18:40:11 <ant_home> loops? loks?
Nov 10 18:40:36 <ant_home> I have to catch dwmw2, he wrote this code 13 yrs ago
Nov 10 18:40:41 <ant_home> :p
Nov 10 18:41:14 <ant_home> oh, about collie, any other idea for backlight?
Nov 10 18:43:39 <ant_home> wher would you put it in Makefile?
Nov 10 18:49:17 <ant_home> fwiw
Nov 10 18:49:19 <ant_home> root@collie:~# cat /proc/interrupts
Nov 10 18:49:19 <ant_home>            CPU0
Nov 10 18:49:19 <ant_home>   1:          0    GPIO-l  ac
Nov 10 18:49:19 <ant_home>  12:        167        SC  LCD
Nov 10 18:49:19 <ant_home>  17:       1953        SC  sa11x0-uart
Nov 10 18:49:20 <ant_home>  26:       8257        SC  ost0
Nov 10 18:49:22 <ant_home>  35:       5440    GPIO-h  pata_pcmcia
Nov 10 18:49:24 <ant_home>  41:          2    GPIO-h  main full
Nov 10 18:49:26 <ant_home>  43:          2    GPIO-h  PCMCIA0 CD
Nov 10 18:49:28 <ant_home>  49:          0    LOCOMO  locomokbd
Nov 10 18:49:30 <ant_home> Err:          0
Nov 10 18:51:04 <ant_home> and iomem
Nov 10 18:51:06 <ant_home> root@collie:~# cat /proc/iomem
Nov 10 18:51:06 <ant_home> 00000000-00ffffff : sa1100-mtd
Nov 10 18:51:06 <ant_home>   00000000-00ffffff : sa1100
Nov 10 18:51:07 <ant_home> 20000000-2fffffff : PCMCIA socket 0
Nov 10 18:51:09 <ant_home>   20000000-23ffffff : io
Nov 10 18:51:11 <ant_home>   28000000-2bffffff : attribute
Nov 10 18:51:13 <ant_home>   2c000000-2fffffff : memory
Nov 10 18:51:15 <ant_home> 40000000-40001fff : locomo.0
Nov 10 18:51:17 <ant_home> 40800000-40800fff : sharp-scoop
Nov 10 18:51:19 <ant_home> 80000000-8000ffff : sa11x0-udc
Nov 10 18:51:21 <ant_home> 80010000-8001ffff : sa11x0-uart.1
Nov 10 18:51:23 <ant_home>   80010000-80010023 : sa11x0-uart
Nov 10 18:51:25 <ant_home> 80030000-80030023 : sa11x0-ir
Nov 10 18:51:27 <ant_home> 80040060-8004007b : sa11x0-ir
Nov 10 18:51:29 <ant_home> 80050000-8005ffff : sa11x0-uart.3
Nov 10 18:51:31 <ant_home>   80050000-80050023 : sa11x0-uart
Nov 10 18:51:35 <ant_home> 80060000-8006ffff : sa11x0-mcp
Nov 10 18:51:37 <ant_home>   80060000-8006ffff : sa11x0-mcp
Nov 10 18:51:39 <ant_home> 80070000-8007ffff : sa11x0-ssp
Nov 10 18:51:41 <ant_home> 90010000-9001003f : sa1100-rtc
Nov 10 18:51:43 <ant_home> 90050000-9005ffff : irqs
Nov 10 18:51:45 <ant_home> 90060028-9006002b : sa11x0-ir
Nov 10 18:51:47 <ant_home> 90060030-90060033 : sa11x0-mcp
Nov 10 18:51:49 <ant_home>   90060030-90060033 : sa11x0-mcp
Nov 10 18:51:51 <ant_home> b0000000-b00000bf : sa11x0-dma
Nov 10 18:51:53 <ant_home> b0100000-b010ffff : sa11x0-fb
Nov 10 18:51:55 <ant_home>   b0100000-b010ffff : LCD
Nov 10 18:51:57 <ant_home> c0000000-c3ffffff : System RAM
Nov 10 18:51:59 <ant_home>   c0008000-c07e6a8f : Kernel code
Nov 10 18:52:01 <ant_home>   c0852000-c0932fc7 : Kernel data
Nov 10 18:52:05 <ant_home> c4848040-c484804f : locomokbd
Nov 10 18:52:07 <ant_home> root@collie:~#
Nov 10 19:04:07 * lumag_ is finishing with cleaned up locomo
Nov 10 19:05:23 <lumag_> Hope updated locomo backlight will be more robust
Nov 10 19:09:09 <lumag_> ant_home, few questions about collie kernels.
Nov 10 19:09:34 <lumag_> I checked up the current OE's kernel. In quemu, but...
Nov 10 19:10:30 <lumag_> 1) Is lzma fast enough on real hw? It is rather slow in qemu.
Nov 10 19:10:52 <lumag_> 2) Do we really need all raid modules? I rather doubt somebody will have raids on Zaurii
Nov 10 19:53:50 <ant_home> sure, the yocto kernel is huge
Nov 10 19:54:19 <ant_home> unfortunately some features are not opt-in so we need a specific fragment to 'unset' i.e. raid
Nov 10 19:54:45 <ant_home> atm I've only tried to standardize the features, building around linux-yocto
Nov 10 19:54:57 <ant_home> about lzma, it was neede by linux-kexecboot
Nov 10 19:55:01 <ant_home> that's all
Nov 10 19:56:51 <lumag_> ah, ok
Nov 10 19:57:48 <ant_home> I'd remove llvm, kprobe, profiling etc
Nov 10 20:04:11 <ant_home> lumag_: cpu freq cannot be disabled
Nov 10 20:04:38 <ant_home> and there are no ARM CPU freq drivers...
Nov 10 20:04:55 <ant_home> iirc this is a 2.6.32/33 change
Nov 10 20:05:51 <lumag_> Edit arch/arm/Kconfig, remove "select CPU_FREQ" under ARCH_SA1100
Nov 10 20:05:56 <ant_home> fwiw I've suspended/&resumed now on collie ;)
Nov 10 20:06:04 <lumag_> he-he.
Nov 10 20:06:24 <ant_home> btw the backlight dims off by itself after some time
Nov 10 20:06:34 <lumag_> As I said once sa1100 is somewhat better than pxa. There is no place to do things completely wrong.
Nov 10 20:06:35 <ant_home> even in kexecboot menu
Nov 10 20:06:47 <lumag_> That is VT blanking I think
Nov 10 20:07:08 <ant_home> someone said that unbtil recently sa1100 was broken because of missing freq table...you? linusw?
Nov 10 20:07:31 <lumag_> Dunno. There were patches to fix that.
Nov 10 20:07:47 <lumag_> There is a problem with cpu_freq
Nov 10 20:08:04 <lumag_> sa1110 driver depends on availability of dram timings table.
Nov 10 20:08:33 <lumag_> So each sa1110 _board_ that wants to support cpu_freq should select correct symbol
Nov 10 20:08:49 <ant_home> ah, that table
Nov 10 20:09:04 <lumag_> And then it should provide used dram timings in drivers/cpufreq/*sa1110*
Nov 10 20:09:22 <lumag_> No, there also was some problem with sa1100 (or sa1110) frequencies table.
Nov 10 20:10:24 * lumag_ is trying to catch linusw with a question regarding pinctrl.
Nov 10 20:10:29 <ant_home> hm.. sorry.. 1110 vs. 1100
Nov 10 20:10:45 <ant_home> bluelightning: we lost linusw bouncing patches :/
Nov 10 20:10:57 <ant_home> until tomorrow...
Nov 10 20:11:05 <lumag_> He doesn't show on irc
Nov 10 20:11:15 <lumag_> Ah, maybe due to the merge window he is hiding
Nov 10 20:11:18 <lumag_> ant_home, yes
Nov 10 20:11:24 <ant_home> during week usually
Nov 10 20:12:07 <lumag_> sa1100 did not support SDRAM, sa1110 does. But it does that so strangely, that cpufreq driver needs to know dram timings
Nov 10 20:12:26 <ant_home> heh, the engineers
Nov 10 20:12:40 <lumag_> ant_home, regarding backlight.
Nov 10 20:13:05 <lumag_> Could you please try the following fixups:
Nov 10 20:13:14 <lumag_> 1) fix in m62332 code
Nov 10 20:13:22 <lumag_> 2) move obj-y += backlight/ down
Nov 10 20:13:46 <lumag_> 3) in locomolcd_probe remove if (machine_is_poodle())
Nov 10 20:14:02 <lumag_> so call locomolcd_power(1) unconditionally on probe
Nov 10 22:21:36 <ant_home> lumag_: I've sent vid 3 after those changes
Nov 10 22:23:40 <ant_home> seems a bit a progress somehow...
Nov 10 22:24:23 <lumag_> So display is not garbled, but no "new" picture
Nov 10 22:25:07 <ant_home> less garbled but not 'cleared'
Nov 10 22:25:52 <ant_home> repeatable, now I always see the logo but is misplaced
Nov 10 22:27:09 <lumag_> Hmm. Which logo? OE logo or kernel tux?
Nov 10 22:27:33 <ant_home> is always the same...kexecboot-kernel, launched kernel, psplash
Nov 10 22:27:49 <ant_home> I show you how it is on poodle if you want
Nov 10 22:32:20 <lumag_> I'm asking because on your video I saw 'bad' OE psplash, kexecboot, your fingers and then kexecboot, kexecboot, kexecboot.
Nov 10 22:33:06 <lumag_> You say on poodle video is correct.
Nov 10 22:33:10 <lumag_> That is strange.
Nov 10 22:33:18 <lumag_> poodle and collie share locomolcd
Nov 10 22:35:26 <ant_home> poodle is much quicker to decompress, even with 32M ram
Nov 10 22:35:48 <ant_home> see video so you see what I expect from collie as well
Nov 10 22:36:31 <ant_home> detection takes long because of th ejffs2 mtd2, mtd3 is ubi
Nov 10 22:37:14 <lumag_> ant_home, do you see any screen changes after you press enter on collie? I don't see any on your video.
Nov 10 22:37:43 <ant_home> er.. iphone ate the last part of the video...
Nov 10 22:38:06 <ant_home> but no, there isn't any clear 'reset' like on poodle
Nov 10 22:38:33 <lumag_> What kernel config are you basing upon? OE?
Nov 10 22:38:47 <ant_home> yes
Nov 10 22:40:31 <lumag_> It really looks like sa1100fb is broken.
Nov 10 22:40:37 <lumag_> However I fail to see how it can be.
Nov 10 22:40:47 <ant_home> seems it works on h3600
Nov 10 22:40:54 <lumag_> Yes
Nov 10 22:41:02 <ant_home> w/out locomo
Nov 10 22:41:20 <lumag_> At least linusw said that he ported backlight/etc w/o any issues
Nov 10 22:41:42 <lumag_> locomolcd is also working
Nov 10 22:41:50 <lumag_> Hmm.
Nov 10 22:41:58 * lumag_ has an idea
Nov 10 22:42:05 <ant_home> locomo + pxa = ok
Nov 10 22:42:12 <ant_home> locomo + sa1100 = ko
Nov 10 22:42:57 <ant_home> or maybe just pxa vs. sa1100 framebuffer...
Nov 10 22:49:19 <lumag_> Would you mind adding #define DEBUG as the first line of sa1100fb.c and then grepping dmesg for sa1100-fb?
Nov 10 22:50:54 <lumag_> Ah, and btw: did you succeed building kernel w/o CPU_FREQ?
Nov 10 22:55:59 <ant__> should I change m62332 as well?
Nov 10 22:58:03 <lumag_> Yes.
Nov 10 22:58:09 <lumag_> All 3 workarounds + debug
Nov 10 22:58:18 <ant_home> ok
Nov 10 22:59:04 <lumag_> I'm really trying to understand what goes on with fb driver.
Nov 10 23:00:42 <lumag_> As I still did not implement sa1100 fb qemu emulation :(
Nov 10 23:02:54 <ant_home> just #define DEBUG
Nov 10 23:02:55 <ant_home>  ?
Nov 10 23:04:10 <ant_home> ah, ok, dev_dbg
Nov 10 23:04:24 <ant_home> building
Nov 10 23:05:16 <lumag_> I'm not a fan of 'dynamic_debug'/etc.
Nov 10 23:06:33 <ant_home> I've learned that with mtd
Nov 10 23:06:48 <ant_home> still scared by debugfs
Nov 10 23:07:17 <ant_home> at this point, gdb as you once told me ;)
Nov 10 23:07:33 <lumag_> I like debugfs
Nov 10 23:08:26 <lumag_>  /sys/kernel/debug/gpio, was my favourite for long debugging sessions
Nov 10 23:08:28 <ant_home> never spent enough time to learn it...
Nov 10 23:08:46 <lumag_> And /sys/kernel/debug/asoc for sound card issues
Nov 10 23:08:59 <ant_home> btw, there are 3 patches speeding build of kernel (hardlinks)
Nov 10 23:09:17 <ant_home> linux-yocto was taking 15-16 mins, let see now
Nov 10 23:16:07 <ant_home> built
Nov 10 23:19:42 <ant_home> well, nothing... maybe device debug is disabled.. checking
Nov 10 23:24:43 <ant_home> hm.. debugfs is mounted
Nov 10 23:28:29 <ant_home> root@collie:~# cat /sys/kernel/debug/gpio
Nov 10 23:28:30 <ant_home> GPIOs 0-27, gpio:
Nov 10 23:28:30 <ant_home>  gpio-1   (ac in               ) in  hi
Nov 10 23:28:30 <ant_home>  gpio-20  (main battery full   ) in  lo
Nov 10 23:28:30 <ant_home>  gpio-26  (main battery low    ) in  hi
Nov 10 23:28:30 <ant_home> GPIOs 28-39, sharp-scoop:
Nov 10 23:28:32 <ant_home>  gpio-28  (main charge on      ) out hi
Nov 10 23:28:34 <ant_home>  gpio-35  (flash Vpp enable    ) out lo
Nov 10 23:28:36 <ant_home> GPIOs 40-49, no-bus/ucb1x00, ucb1x00:
Nov 10 23:28:38 <ant_home>  gpio-47  (main battery        ) out lo
Nov 10 23:28:40 <ant_home>  gpio-48  (backup battery      ) out lo
Nov 10 23:28:42 <ant_home>  gpio-49  (main batte
Nov 10 23:29:17 <ant_home> ry temp   ) out lo
Nov 10 23:33:02 <ant_home> lumag: fwiw LCD (or backlight) is OFF on resume after suspend
Nov 10 23:39:04 <ant_home> eh.. DEBUG must be defined before...
Nov 10 23:39:15 <ant_home> ok, redoing
Nov 10 23:42:51 <lumag_> n/p
Nov 10 23:42:56 <lumag_> I'm really interested in dmesg
Nov 10 23:45:22 <ant_home> seems kernel build gained 25% speed
Nov 10 23:45:28 <ant_home> overall
Nov 10 23:45:45 <ant_home> 10 mins instead of 15-16
Nov 10 23:46:05 <ant_home> on my old quad
Nov 10 23:58:18 <ant_home> lumag_: http://pastebin.com/NcJV1Rp4
Nov 10 23:59:38 <lumag_> Didn't check register values (will do tomorrow), but it looks sane.
Nov 11 00:00:03 <ant_home> ok
Nov 11 00:00:36 <lumag_> In the dead end we can just do a git bisect :)
Nov 11 00:00:45 <ant_home> see the resume
Nov 11 00:00:45 <ant_home> collie login: root
Nov 11 00:00:46 <ant_home> root@collie:~# apm --suspend
Nov 11 00:00:46 <ant_home> PM: Syncing filesystems ... done.
Nov 11 00:00:46 <ant_home> Freezing user space processes ... (elapsed 0.01 seconds) done.
Nov 11 00:00:46 <ant_home> Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Nov 11 00:00:47 <ant_home> Suspending console(s) (use no_console_suspend to debug)
Nov 11 00:00:49 <ant_home> sd 0:0:0:0: [sda] Stopping disk
Nov 11 00:00:51 <ant_home> sa11x0-fb sa11x0-fb: backlight off
Nov 11 00:00:53 <ant_home> sa11x0-fb sa11x0-fb: Disabling LCD controller
Nov 11 00:00:55 <ant_home> sa11x0-fb sa11x0-fb: LCD power off
Nov 11 00:00:59 <ant_home> PM: suspend of devices complete after 825.581 msecs
Nov 11 00:01:01 <ant_home> PM: late suspend of devices complete after 2.907 msecs
Nov 11 00:01:03 <ant_home> PM: noirq suspend of devices complete after 2.626 msecs
Nov 11 00:01:05 <ant_home> PM: noirq resume of devices complete after 729.023 msecs
Nov 11 00:01:07 <ant_home> PM: early resume of devices complete after 2.343 msecs
Nov 11 00:01:09 <ant_home> sa11x0-fb sa11x0-fb: LCD power on
Nov 11 00:01:11 <ant_home> sa11x0-fb sa11x0-fb: Enabling LCD controller
Nov 11 00:01:13 <ant_home> sa11x0-fb sa11x0-fb: DBAR1: 0xc3ac0fe0
Nov 11 00:01:15 <ant_home> sa11x0-fb sa11x0-fb: DBAR2: 0xc3ad3c00
Nov 11 00:01:17 <ant_home> sa11x0-fb sa11x0-fb: LCCR0: 0x000000b9
Nov 11 00:01:19 <ant_home> sa11x0-fb sa11x0-fb: LCCR1: 0x0a1d1130
Nov 11 00:01:21 <ant_home> sa11x0-fb sa11x0-fb: LCCR2: 0x020000ef
Nov 11 00:01:23 <ant_home> sa11x0-fb sa11x0-fb: LCCR3: 0x00fffffe
Nov 11 00:01:25 <ant_home> sa11x0-fb sa11x0-fb: backlight on
Nov 11 00:01:29 <ant_home> ata1.00: configured for PIO0
Nov 11 00:01:31 <ant_home> sd 0:0:0:0: [sda] Starting disk
Nov 11 00:01:33 <ant_home> PM: resume of devices complete after 318.849 msecs
Nov 11 00:01:35 <ant_home> Restarting tasks ... done.
Nov 11 00:01:37 <ant_home> root@collie:~#
Nov 11 00:01:45 <lumag_> Still no picture on screen?
Nov 11 00:01:56 <lumag_> BTW: what will happen to screen if you do dd if=/dev/urandom of=/dev/fb0?
Nov 11 00:03:05 <ant_home> nothing after resume...I'll reboot
Nov 11 00:03:43 <ant_home> all is black even if backlight is on...
Nov 11 00:05:26 <ant_home> now after eboot all is white (building backlight at the end)
Nov 11 00:05:47 <ant_home> nothing happens on screen
Nov 11 00:07:40 <ant_home> hmm.. sa11x0-fb sa11x0-fb: dma period = 1372168 ps, clock = 0 kHz
Nov 11 00:07:46 <ant_home> 0 kHz ?
Nov 11 00:09:32 <lumag_> Heh.
Nov 11 00:09:35 <lumag_> cpu_freq in charge
Nov 11 00:09:50 <ant_home> ah, this is built w/out
Nov 11 00:10:22 <lumag_> No it was not.
Nov 11 00:10:34 <lumag_> At least from what I understand.
Nov 11 00:12:31 <ant_home> my bad..., maybe I didn't remove it from the .config but just from the Kconfig
Nov 11 00:12:41 <ant_home> s/maybe/surely/
Nov 11 00:12:52 <ant_home> it has been readded
Nov 11 00:14:16 <lumag__> sorry
Nov 11 00:14:30 <lumag__> had network outage
Nov 11 00:14:34 <ant_home> np, I'l ldo a last build and go
Nov 11 00:15:49 <lumag_> wait a minute.
Nov 11 00:16:46 <lumag_> No/
Nov 11 00:16:52 <lumag_> I will think about it
Nov 11 00:17:02 <lumag_> Maybe we really need to implement dram timings
Nov 11 00:17:20 <ant_home> ask linusw tomorrow
Nov 11 00:17:40 <ant_home> you guys can better talk each other ;)
Nov 11 00:18:07 <ant_home> I'm happy to monkey-build
Nov 11 00:18:27 <lumag_> ant_home, proper solution would be to read clock from cpu, rather than asking cpufreq for it,
Nov 11 00:18:33 <lumag_> I will think tomorrow.
Nov 11 00:18:42 <lumag_> Great that you have eyes to notice that.
Nov 11 00:29:26 <ant_home> afaik thesing hardcoded it
Nov 11 00:29:52 <ant_home> right when he introduced cpufreq for collie
Nov 11 00:30:01 <ant_home> strange eh
Nov 11 00:30:56 <ant_home> anyway, gn
Nov 11 00:30:59 <ant_home> and thx
Nov 11 00:31:04 <ant_home> bye
**** ENDING LOGGING AT Mon Nov 11 02:59:58 2013