IRC log for #arm-netbook on 20120929

00:00.02*** join/#arm-netbook xenoxaos (~xenoxaos@developers.archlinuxarm.org)
00:56.49*** join/#arm-netbook zewelor (~x@89-78-93-36.dynamic.chello.pl)
01:52.24*** join/#arm-netbook Hexxeh (u1532@gateway/web/irccloud.com/x-fmkixslykoclzxdz)
01:52.37*** join/#arm-netbook steev (u1383@gentoo/developer/steev)
02:46.53*** join/#arm-netbook tekzilla (~jon@hmbg-4d06d437.pool.mediaWays.net)
04:10.25*** join/#arm-netbook calris (~calris@d110-32-174-6.sbr801.nsw.optusnet.com.au)
04:50.21*** join/#arm-netbook newbie (~kvirc@220-136-76-173.dynamic.hinet.net)
04:52.33*** join/#arm-netbook Quarx (~Quarx@94.137.56.184)
05:54.17*** join/#arm-netbook steev (u1383@gentoo/developer/steev)
06:30.48*** join/#arm-netbook jlj (~jlj@109-104-24-9.customers.ownit.se)
06:44.44*** join/#arm-netbook robws (~robws1@38.99.170.111)
07:07.40*** join/#arm-netbook gimli (~gimli@xbmc/staff/gimli)
07:46.30*** join/#arm-netbook mSquare (~selvan@122.178.254.228)
08:06.08*** join/#arm-netbook rvalles (~rvalles@unaffiliated/rvalles)
08:08.39*** join/#arm-netbook rellla (~Thunderbi@p5B078046.dip0.t-ipconnect.de)
08:19.59techn_WarheadsSE: chmod your /dev/ump
08:21.59techn_or if you have done so.. try with that buf2 patch
08:33.10*** join/#arm-netbook jlj (~jlj@109-104-24-9.customers.ownit.se)
08:41.03*** join/#arm-netbook popolon (~popolon@og-free.planet-service.fr)
08:48.22*** join/#arm-netbook MMlosh (~MMlosh@2001:470:6f:23:99fc:20ff:5a87:7724)
09:25.25*** join/#arm-netbook rellla (~Thunderbi@p4FE5606E.dip0.t-ipconnect.de)
09:45.28*** join/#arm-netbook lkcl (~lkcl@host86-131-170-4.range86-131.btcentralplus.com)
09:47.41*** join/#arm-netbook rvalles (~rvalles@unaffiliated/rvalles)
09:53.33*** join/#arm-netbook cheng (~cheng@175.137.64.110)
10:04.43*** join/#arm-netbook plan_b (~plan_b@ip-80-226-24-3.vodafone-net.de)
10:09.00techn_mnemoc: this can be removed? wip/allwinner-v2.6.36-android/disp :)
10:11.50mnemoctechn_: ok
10:12.19techn_what I noticed that there is only one hack to supress crash
10:12.47mnemocyes
10:12.50mnemocdone
10:14.37techn_how about these? /allwinner/amery/lichee-v2.6.36-dev, /amery/linux-2.6.36-sun4i ?
10:15.12mnemoctechn_: we still need the 2.6.36 ref for sun3i
10:15.47techn_ok
10:15.51RaYmAnit also really doesn't matter much whether you delete the branch or not (Except for the github ui)
10:15.58mnemocbut I can rename them if the "amery" prefix bothers you
10:16.24mnemocRaYmAn: eventually orphan heads get removed
10:16.52mnemocand that implies losing data
10:17.01techn_mnemoc: no.. I'm just cleaning my own repo.. and trying to find out valid branches
10:18.18techn_RaYmAn: you can force compress which removes dead head's
10:18.48RaYmAnsure
10:18.50techn_mnemoc: how about 3.3 branches? :)
10:19.22mnemoctechn_: there is work from steev there
10:19.38mnemoctechn_: which i don't want to trash until it's ported to 3.4
10:20.09mnemocbut they are also part of our "attic"
10:23.07RaYmAnperhaps it's time to consider making a github "organisation" to put the "official repos" on, e.g. u-boot and kernel? then the more experimental can stay at amery and hno repos?
10:24.09mnemoci would love too... but I fear about broken links
10:24.41mnemocI still get people forking my uboot repo regarless the big warnings asking them to use hno's
10:24.55RaYmAnso clean it out? :P
10:25.05mnemochno's is a fork of mine
10:25.13mnemocno clue how will github react
10:25.26RaYmAnit won't affect anything
10:25.35RaYmAnyou can delete your repo and hno's will be unaffected.
10:25.51mnemoci thought they were linked
10:26.14RaYmAnmm ,probably behind the scenes - but I'm 100% that github does the right thing
10:27.57RaYmAnit would be chaos if all forks went haywire if original repo was broken
10:28.42mnemocfair point
10:29.21RaYmAnbut rather than deleting, it would probably be better to remove all content and and make sure to link on to the proper repo
10:29.32RaYmAnso you don't break http links to it :)
10:29.44mnemocthat sounds like a good idea
10:34.35cat1is it only me who gets this error http://sprunge.us/IXPP while compiling recent linux-sunxi-3.4? note that CONFIG_RTL8192CU_SW=m is used instead of mainstream driver.
10:36.01mnemoccat1: yes, the driver is bound to android stuff deprecated in their 3.4 branch
10:36.15mnemocwe can either fix the driver, or trash it
10:37.04cat1mnemoc: yeah, once we get rtlwifi working with fw :)
10:37.24cat1actually i do not really remember, maybe that was working with 3.4..
10:37.28cat1but i doubt..
10:37.35mnemocwe should move the usb_wifi_para handling into proper power management
10:37.45mnemoccat1: try it ;-)
10:38.01cat1mnemoc: but the problem i have seems not to be realted to pm
10:38.41techn_mnemoc: could there be used kernel's own usb suspend logic?
10:40.11mnemoccat1: it's not
10:40.34mnemoccat1: but the reason for that driver to exist and be used instead of mainline is [usb_wifi_para] support
10:40.50mnemocwhich enable/disable the usbc if the wifi module is loaded/unloaded
10:41.00mnemocto save power
10:41.56cat1mnemoc: ok, marked for the future :) anyway, the thing is that i am really annoyed by the fact that network connectivity is missing to the target..
10:42.24mnemocdisable CONFIG_RTL8192CU_SW
10:42.45cat1mnemoc: it is not fun :)
10:42.57mnemoc:)
10:43.31cat1the real fun is to get mainline stuff working.
10:44.28mnemocbut fixing the fw problem on the mainline driver in 3.6 doesn't add value to sunxi =)
10:45.00cat1mnemoc: actually it does as i suspect it does not work in 3.4 too!
10:45.18cat1will figure it out soon as i am preparing 3.4 for testing
10:46.53mnemoc:)
10:47.31cat1btw, yesterday took 4g modem for trial, results are good so far http://speedtest.net/result/2208940981.png
10:48.12techn_cat1: nice.. looks good alternative for adsl
10:50.10techn_http://www.speedtest.net/result/2209808481.png <= 20/1 adsl result
10:50.22cat1techn_: aha, the only problem is that my house is located on the coverage boundary, so only 2bars on strength indicator :) dunno if it will cause any connection stability issues.
10:50.59cat1techn_: yeah, i still have nokia paid adsl line -- restults are proximately in the same range as yours.
10:51.31cat1techn_: but soon it will be terminated so i am looking for alternatives.
10:51.41techn_cat1: external antenna would help?
10:52.08cat1techn_: maybe, but i wont bother unless i experience real problems.
10:52.49techn_repo size went from 800MB to 600MB with aggressive gc :)
11:06.20*** join/#arm-netbook aaribaud (~aaribaud@2a01:e35:2eb9:20:250:43ff:fe01:dc73)
11:06.39rz2ktechn_: could you please write step-by-step manual about how you got es2gears working, I've tested clean install on r2p4 with latest buf2 patch, I have same errors and black screens. tested both in-kernel and modules for hdmi/lcd/disp stuff.
11:07.00rz2kwe have same config.h
11:07.03*** join/#arm-netbook silentaa (~silentaa@2a01:e35:2eb9:20:250:43ff:fe01:dc73)
11:08.30techn_rz2k: I compiled everythink like in the wiki.. except I didn't run autoreconf -vi command.. if I remember correctly
11:09.22rz2kyes, autoreconf fails r2p4 setup because ARM guys was too lazy to write working configuration, so they've supplied output from autoconf in package.
11:10.20mnemocinstead of "instructions" we should provide patch
11:12.08techn_I have to leave.. back in 2 hours :(
11:12.20rz2ktechn_: could you try clean install of r2p4 with kernel from -v2 + your buf2 patch and everything like in wiki? I believe you've did something that I miss.
11:13.24rz2k+ using your default script.bin, for instance, script.bin from mele-vga package from dl.linux-sunxi.org has different clock_div than my default one.
11:16.55*** join/#arm-netbook RITRedbeard (~redbeard@c-68-37-165-37.hsd1.nj.comcast.net)
11:18.50*** join/#arm-netbook orly_owl (~david@unaffiliated/orly-owl/x-3167833)
11:19.18*** join/#arm-netbook strong (~strong@86.108.10.58)
11:35.23*** part/#arm-netbook strong (~strong@86.108.10.58)
11:39.49*** join/#arm-netbook jlj (~jlj@109-104-24-9.customers.ownit.se)
11:56.40*** join/#arm-netbook penguin42 (~dg@tu006.demon.co.uk)
12:02.28*** join/#arm-netbook orly_owl (~david@unaffiliated/orly-owl/x-3167833)
12:11.19*** join/#arm-netbook orly_owl (~david@unaffiliated/orly-owl/x-3167833)
12:26.17*** join/#arm-netbook orly_owl (~david@unaffiliated/orly-owl/x-3167833)
12:46.14*** join/#arm-netbook chz_ (~chz@27.26.47.156)
12:58.42*** join/#arm-netbook orly_owl (~david@unaffiliated/orly-owl/x-3167833)
13:06.59*** join/#arm-netbook Quarx (~Quarx@94.137.56.184)
13:19.08techn_back
13:24.44captainiglooi'm trying to use nand-part of sunxi-tools
13:24.55captainigloobut i'm not able to get my nand back :(
13:25.07captainigloosomebody already uses it ?
13:26.50mnemocafter repartitioning you might need to reboot
13:26.59mnemoci doubt the changes are taken immediately
13:27.21captainiglooyeah but they seems not to be taken at all
13:27.35mnemocyou have /dev/nand, right?
13:27.40captainiglooyes
13:27.57mnemocuhm
13:27.59captainigloohttp://pastebin.ca/2229559
13:28.33captainiglooi'm trying to create a 16MB partitions, and a nand2 as 128MB
13:28.48captainiglooi put size in bytes
13:29.45mnemocthe tool itself skips nanda
13:29.58mnemocyou might need to patch it to let you modify it
13:31.51captainigloohum
13:32.57captainigloonandA is the first partition
13:33.05captainiglooand contains the "mbr" ?
13:34.11plan_bjust enter:    nand-part  /dev/nand  'nand2 134217728'
13:34.36captainigloosame error
13:34.55captainigloohttp://pastebin.ca/2229560
13:35.16captainiglooif someone give the first 1024 bytes of nand , i could maybe recover the mbr ?
13:35.36captainigloowith dd
13:42.16*** join/#arm-netbook hipboi (~hipboi@27.42.88.119)
13:48.20*** join/#arm-netbook RITRedbeard (~redbeard@c-68-37-165-37.hsd1.nj.comcast.net)
14:05.10*** join/#arm-netbook plan_b (~plan_b@ip-80-226-24-13.vodafone-net.de)
14:07.00*** join/#arm-netbook orly_owl (~david@unaffiliated/orly-owl/x-3167833)
14:09.17mnemoccaptainigloo: nanda is the boot partition, 16MB vfat. the partitions table comes before
14:09.59captainigloomnemoc: plan_b send me the first 2048 bytes of the /dev/nand device
14:10.20mnemoccaptainigloo: fixed the problem?
14:10.20captainiglooit seems that partition 0 which is actually nandA begin at offset 2048
14:10.29captainigloomnemoc: i'm waiting for the file :)
14:11.17plan_bjust a moment .. my internet connections is unstable at the moment
14:12.06mnemocplan_b: try https://filetea.me .... it's anonimous and not-storing
14:14.04plan_b44% done
14:14.04plan_bso sloooowwww at the moment
14:14.18captainigloofor 2048 bytes ?!
14:14.45plan_b65%
14:15.01mnemoccome one
14:15.04mnemocon
14:15.08captainiglooit's less thant 2 ip packets :)
14:15.08mnemoc2k??
14:15.32plan_bI'm not at home at the moment ... no dsl
14:15.33mnemocplan_b: dd if=/dev/nand of=head.bin bs=2048 count=1
14:16.00plan_b96%
14:16.09*** join/#arm-netbook QingPei (~qingpei@114.241.177.202)
14:16.31mnemocplan_b: you are uploading something wrong
14:16.47mnemocplan_b: it's impossible it takes you over 2 seconds to upload such file
14:17.00mnemoceven if you connect to the internet using a cotton thread
14:17.49RaYmAnmaybe if it's by carrier pidgeon :D
14:18.07RaYmAnrfc1149 as it were
14:18.08RaYmAn:P
14:18.12Turlthis is how I repartitioned my tablet
14:18.14Turl/sbin/yes | /tmp/nand-part /dev/block/nand 'env 4096' 'boot 65536' 'system 716800' 'data 2265088' 'misc 2048' 'recovery 65536' 'cache 262144' 'UDISK 27713536'
14:18.32Turlymmv
14:18.33mnemocTurl: captainigloo corrupted his nanda
14:18.42mnemocnand-part doesn't touch that one
14:19.21Turlif it's corrupted, it's livesuit time :P
14:19.21plan_bhttps://filetea.me/t1se9c1f
14:19.36Turlunless you wanna boot with an sdcard with a minimal linux and fix it
14:19.49plan_bmk5sum bd089df81f028767bd1a9994ce1ab36e
14:19.52Turlyou'd need a nanda backup for that though
14:22.04captainigloohttp://pastebin.ca/2229572
14:22.07captainiglooseems better !
14:22.11captainiglooplan_b: thanks :)
14:22.44plan_bbut your nanda will be empty ... do you have a backup
14:23.05captainigloothere is one on amery's github repo
14:23.11plan_bok
14:23.30Turlcaptainigloo: the 'stock' nanda won't boot anything with that partition disposition though
14:23.45captainiglooah and after a reboot i get /dev/nanda and /dev/nandb
14:23.49captainiglooTurl: why ?
14:24.22Turlcaptainigloo: because it's configured to boot an android boot.img from a boot partition which you clearly lack
14:24.43captainigloowhat's configured ?
14:24.49Turlthe uboot on it
14:25.01captainigloohum
14:25.32plan_bcaptainigloo, what happens if you "mount /dev/nanda  /mnt"
14:25.52plan_bwithout a reboot
14:26.40captainigloo/dev/nanda is not formated
14:26.49plan_bok
14:27.17plan_bI could upload my nanda backup ... will be online in about 2 weeks
14:27.21plan_b;)
14:27.23captainigloolol
14:29.16captainigloorh i don't have mkfs on my system !
14:30.42Turlwhat are you using to format this stuff captainigloo?
14:31.03captainiglooi think about using mkfs.vfat to format /dev/nanda
14:31.10captainiglooand put the boot files on it
14:31.24Turlyeah that should be ok
14:31.35Turlbut you say you don't have mkfs.vfat?
14:32.11captainiglooyeaj i'm building it
14:34.10TurlCWM has probably everything you'd ever need and more, might come in handy to have a sdcard with it to do these kind of things captainigloo
14:34.18Turlhttp://linux-sunxi.org/CWM_on_a_SDCard
14:37.37mnemoc:o
14:42.37captainiglooTurl: i don't know what CWM is, but it's what i try to do
14:43.03captainiglooa bootable sdcard to recovery my mele if it crashes or something goes wrong
14:43.27captainigloobut i'm using a minimal linux distro
15:06.27*** join/#arm-netbook revident (~scott@fw.ss.org)
15:19.37*** part/#arm-netbook hipboi (~hipboi@27.42.88.119)
15:21.55*** join/#arm-netbook QingPei (~qingpei@114.241.177.202)
15:26.27captainigloook it works
15:26.50captainigloomy nand works again
15:26.58Turlcaptainigloo: CWM means ClockworkMod Recovery
15:27.26Turlit's an android recovery
15:27.40Turlit's main use is flashing android roms, but you can use adb shell on it
15:27.48captainiglooah ok, i already use it to flash my htc desire
15:27.49techn_new mali libs here http://linux-sunxi.org/Mali400
15:27.53Turland it has a crapton of useful tools
15:28.08captainigloook
15:28.22Turltechn_: r3p1 for android? :P
15:28.31techn_rz2k: I need to go now.. sorry could manage to get things running with r2p4.. Some other linking problems
15:29.00techn_Turl: mali400-gles20-gles11-linux-x11-ump-no_monolithic
15:30.15techn_r3p0
15:30.16rz2kI will try that right now, thanks techn_
15:30.33cat1techn_: second, what is kernel part for it?
15:30.36captainiglooarmhf ?
15:31.00rz2kcaptainigloo: TARGET_SYSTEM=gcc-arm-linux-gnueabihf
15:31.33rz2kcat1: https://github.com/amery/linux-allwinner/tree/wip/linux-sunxi-3.0/next_mali
15:31.36techn_cat1: next_mali
15:31.44cat1techn_: ah, ok, tnx!
15:32.00techn_thank Tom :)
15:32.12cat1techn_: thanks, Tom! ;D
15:32.44captainigloothere is no way to have a softfp version ?
15:32.59techn_but gotta go to party :D
15:33.26captainigloohave a nice party :)
15:41.31*** join/#arm-netbook vgrade2 (~martinbro@cpc2-nrte22-2-0-cust128.8-4.cable.virginmedia.com)
15:41.58*** join/#arm-netbook drachensun (~drachensu@142.196.83.182)
15:43.37mnemoctechn_: please send a mail to linux-sunxi announcing it :)
15:44.59*** join/#arm-netbook vgrade (~martinbro@cpc2-nrte22-2-0-cust128.8-4.cable.virginmedia.com)
15:48.12Turlhttp://marcin.juszkiewicz.com.pl/2012/09/28/lets-take-a-look-at-arm-boards-again/
15:51.30Turl69USD i.MX6 boards :p
15:51.47mnemocmade from the buggy chips
15:52.08Turlpossibly
15:52.32Turlwasn't the bug power management only though?
15:52.39mnemocthe fixed chips just started selling last month
15:52.45mnemocyes
15:53.07captainigloothere is a i.MX6 board at only 69$ ?
15:53.21mnemocdev boards is a nice way of getting rid of those buggy chips
15:53.56Turlshipment starts end of nov 2012 mnemoc
15:53.57Turlso it might as well have the fixed ones
15:53.58Turlcaptainigloo: http://www.wandboard.org/
15:54.42rmwangboard
15:54.52captainigloointerresting
16:00.25plan_b$89 for two cores
16:02.12captainiglooi bet on 109$ for 4 cores when it will be out :)
16:04.01*** join/#arm-netbook popolon (~popolon@og-free.planet-service.fr)
16:15.54L84Supperthe price difference between the single and four core imx was only around $15
16:17.20L84SupperMCIMX6S5DVM10AA i.MX 6Solo Consumer  - 1GHz w/ VPU&GPU ~$11
16:17.45L84SupperMCIMX6D5EYM12AB i.MX 6Dual Consumer Ext. Temp – 1.2GHz w/ VPU&GPU ~$23
16:18.07L84SupperMCIMX6Q5EYM12AB i.MX 6Quad Consumer Ext. Temp – 1.2GHz w/ VPU&GPU ~$29
16:18.28L84SupperMCIMX6Q5EYM10AB i.MX 6Quad Consumer Ext. Temp - 1GHz w/ VPU&GPU ~$26
16:18.55plan_bQuad 1.2 GHz would be nice
16:19.14penguin42http://boundarydevices.com/products/sabre-lite-imx6-sbc/ is neat
16:20.04penguin42more expensive (note the $199 from November) but nice stuff; 1GB, PCIe, SATA, GBe
16:26.42rz2kI was thinking about making imx6q board for self education or university paper, but didnt find any data about when imx6q will go out for minor customers and when documents like reference designs will be available.
16:27.12rz2k"q4 2012" doesnt say anything because it is already q4 2012.
16:27.45penguin42not until Monday it isn't!
16:43.32penguin42Turl: What's interesting about the wandboard is it's modular with the CPU/RAM etc on a separate board; with a creative commons defined interface (EDM)
17:06.01*** join/#arm-netbook RITRedbeard (~redbeard@c-68-37-165-37.hsd1.nj.comcast.net)
17:07.41*** join/#arm-netbook gimli_ (~gimli@xbmc/staff/gimli)
17:12.37*** join/#arm-netbook popolon (~popolon@og-free.planet-service.fr)
17:26.28*** join/#arm-netbook mikey_w (~mike@c-71-63-115-202.hsd1.va.comcast.net)
17:26.46*** join/#arm-netbook n6pfk (~mike@c-71-63-115-202.hsd1.va.comcast.net)
17:28.59*** join/#arm-netbook ssvb (~ssvb@212.16.98.80)
17:38.56*** join/#arm-netbook ceo16 (~asus@host153-22-dynamic.4-87-r.retail.telecomitalia.it)
17:53.40drachensunhas anyone tried to get a tablet camera working?
17:54.02drachensunI can load the camera driver but I'm not sure whats needed after that
18:13.45lkclpenguin42: yeah... it looks great, until you realise that it's designed for purely factory-install purposes *only*.  just like the qseven-standard. you can't do anything with an EDM module, without a matching breakout PCB.
18:18.57Turllkcl: same with EOMA-68 too?
18:19.25Turldrachensun: it uses video4linux from what I recall
18:22.02*** join/#arm-netbook RITRedbeard (~redbeard@c-68-37-165-37.hsd1.nj.comcast.net)
18:22.40lkclTurl: no.  EOMA-68 re-purposes PCMCIA.  you can stick an EOMA-68 CPU Card in your top pocket without damage.
18:23.09lkclok, that's assuming it's inside a PCMCIA metal shield of course, rather than being straight off an engineer's R&D lab desk
18:23.46lkclEOMA-68 is designed for mass-volume end-user purposes [with a case on] as well as for factory-install purposes [with the case off]
18:24.09Turlah, I see what you mean now
18:24.23lkclyeah.
18:24.29Turlyou could stick some shielding on top of EDM too I guess
18:24.33Turlor make a carrying case
18:24.45lkclplus, unfortunately, just like in the q-seven standard, many of the interfaces are "optional".
18:24.56lkcldid i ever tell you the story about the development of the X-25 standard?
18:25.10lkclit's quite a simple one.
18:25.13TurlI don't think you did :)
18:25.17lkcl:)
18:25.21lkclahh, allow me :)
18:25.27TurlX-25 reminds me of X-28, any relation?
18:25.33Turl(alarm system)
18:25.44lkclthe X-25 standard is similar to RS-232 - it was what the JANET network ran on.
18:26.14lkclit's 9 pins, and it has (had) a hardware line dedicated to "interrupt", and it had a "Tx" clock line.
18:26.28*** join/#arm-netbook revident (~scott@76.10.173.74)
18:26.49lkclbut, *just in case* someone forgot to honour the hardware "interrupt" line, they put "software interrupt" into the serial data stream
18:26.57lkclno, sorry - it only had a "Rx" clock line.
18:27.22lkclanyway - because it had both hardware and software interrupt, *everyone* had to support software interrupt
18:27.35lkclthus, the hardware interrupt line was *utterly* useless.
18:27.37*** join/#arm-netbook jlj (~jlj@109-104-24-9.customers.ownit.se)
18:27.45Turlheh
18:27.54lkclwhich is a total waste of a pin, esp. when it could have been used as a "Tx" clock line
18:28.34drachensunTurl: yeah I figured out the drivers needed from looking at the android but I'm getting crashes in videobuf_core now
18:28.47lkclso instead of a $2 cable like in RS232, you had to have a $7 box generating a Tx clock to *both* parties, with a $3 power supply!
18:28.58drachensunI'm looking for 'low hanging fruit' features to fix up right now
18:29.13lkclyou see the point i'm making - which is that you must NOT have "optional features" in a hardware standard?
18:29.54lkclif you do have options, they must be negotiable over the bus lines.
18:30.06lkcle.g. USB2 has speed-negotiation... but done in hardware.
18:30.29lkclSATA has speed-negotiation... all the way from 150mbits/sec up to 3gbits/sec... but that's done over the *same* 4 wires
18:30.36lkclethernet as well.
18:30.56lkclEDM, unfortunately, makes many of its interfaces optional
18:31.06Turldrachensun: on kernel?
18:31.11lkclthat immediately to me is a red flag
18:31.48Turllkcl: any optional features on EOMA-68? :)
18:32.27drachensunTurl: when I used fswebcam to try to read from the camera the kernel driver videobuf_core is crashing
18:33.13drachensunI'm installing another v4l program now to see if maybe thats all it is
18:33.49Turlit shouldn't crash even if it's a bad v4l program :)
18:34.59lkclTurl: nnnope :)
18:35.10lkcli learned the lesson of X-25 :)
18:35.33drachensunheh yeah I guess not
18:35.40drachensunit was checking for working resolutions
18:35.57drachensunand I'm thinking maybe the first resolutions just aren't supported
18:38.03*** join/#arm-netbook RITRedbeard (~redbeard@c-68-37-165-37.hsd1.nj.comcast.net)
18:41.51penguin42lkcl: How 'factory only' is EDM? What makes it any worse than a so-dimm?
18:43.39lkclpenguin42: it's exactly the same factory-only usefulness for all those form-factors.  MXM, SO-DIMM, EDM, Q-Seven.
18:43.54penguin42lkcl: In that case, I don't see the problem
18:44.09penguin42lkcl: Plenty of people carry SO-DIMMs around, fit them in their own laptops etc
18:44.20lkclyou only have to think, "would a module of standard X survive my grandma putting it in the top pocket of her best nylon-polyester dress?"
18:44.38penguin42lkcl: But why is that important for EOMA?
18:44.46lkclpenguin42: think "grandma".  does grandma carry around SO-DIMMs and fit them into her laptop?
18:45.08penguin42lkcl: No, grandma carries around a system with an HDMI port on
18:45.11lkclpenguin42: because we're expecting the volumes to be somewhere around a million a month or greater
18:45.20penguin42lkcl: That's way less than SO-DIMM
18:45.26lkclpenguin42: exactly.  an EOMA-68 CPU Card has an HDMI port.
18:45.45penguin42lkcl: No, my point is what is granny going to do with her EOMA?
18:45.56penguin42lkcl: Why wouldn't she just carry her tablet around?
18:46.07lkclpenguin42: i was underestimating.  GW's capacity is... even into numbers bigger than i can appreciate
18:46.44penguin42lkcl: Seriously, that EDM stuff looks like exactly what is needed
18:47.15lkclpenguin42: yes.  good question.  granny's tablet breaks.  little johnny (her 8-year-old tech support) tells her to take the EOMA-68 CPU Card out and bring it over to his mum's house.
18:47.34penguin42lkcl: No he doesn't, little jonny tells her to bring her tablet over
18:47.41rmrz2k, what am I missing?    mali_exa.h:27:21: fatal error: ump/ump.h: No such file or directory
18:47.59lkclor, granny takes it back to the store when it's broken, takes the EOMA-68 CPU Card out and she puts it in her handbag.
18:48.10penguin42lkcl: No, Granny takes the tablet back
18:48.30penguin42lkcl: The differential between the card and the object it's part enough has to be large enough to justify the difference
18:48.41lkclpenguin42: sorry, you don't get it.  if you don't get it, i'm not going to spend a lot of time explaining.
18:49.31penguin42lkcl: Sorry, I don't; I see the point in making stuff modular, I don't get the reason to make it more robust for that type of app
18:49.42*** join/#arm-netbook RITRedbeard (~redbeard@c-68-37-165-37.hsd1.nj.comcast.net)
18:52.19lkclpenguin42: if you're going to argue with the envisaged scenarios without listening, there's no point in me trying to explain, is there.
18:53.01penguin42lkcl: Apologies, I seriously don't mean to be like that; I don't see what I haven't listened to
18:53.51lkclpenguin42: the point is that anything that's removable *will* be hit or damaged by the average person.
18:54.41lkclpenguin42: if there's even a 1% returns rate on items that are sold in quantities of 100 million, that's still a loss of a million units.
18:55.07lkclin the mass-volume retail sector, typically the profits are below 1%.
18:55.10penguin42lkcl: OK, so I'm trying to understand why the SO-DIMM doesn't hit that problem?
18:55.39lkclit does hit that problem.  it's not protected from damage through static, is it?
18:55.46lkclor from being dropped
18:55.54lkclor poked at with a sharp implement
18:56.11lkclor peoples' fingers pressing against the connector and getting oil on it
18:56.14penguin42lkcl: Yep, so laptops are still mostly sold with SO-DIMMs in - so why do they survive?
18:56.35lkclbecause the average person DOES NOT DO THE INSTALL, do they?
18:57.02lkclwhat's the average lifecycle on removal and insertion of an SO-DIMM memory module?
18:57.09penguin42lkcl: I'd guess 10
18:57.16lkclit'll be about once every.... 5 years.
18:57.53lkclwhereas we're anticipating EOMA-68 modules to be inserted/removed on a similar order as USB
18:58.05penguin42lkcl: OK, but why do you want EOMA to be installed/removed more often - I want to understand why granny would want to do this
18:58.14lkclSO-DIMM sockets have a lifecycle of about .... something like 25 cycles *total*.
18:58.19lkclbecause they can.
18:58.25lkclgranny might not
18:58.50lkclbut a professional who has an EOMA-68-compliant Digital SLR Camera, as well as an EOMA-68-compliant smartphone
18:58.52lkcland tablet
18:58.54lkcland laptop
18:59.00lkcland 30in LCD monitor at work
18:59.05lkcland a games console at home
18:59.26lkclthey might end up inserting/removing their EOMA-68 CPU Cards up to 10 times a *day*
18:59.36penguin42lkcl: OK, I hadn't seen that use of it
19:00.14lkclyeah - it's like... the potential here is *huge*.  it covers virtually every mass-volume electronics system you can think of, in the world.
19:00.38lkclwith the exception of the hard-core gaming industry, the high-end server market, high-end / real-time video editing industry
19:01.19lkcland ... err... i run out of examples where EOMA-68 could not be used.  oh yeah: portable watches :)
19:01.33penguin42and music players
19:01.36lkcli'm not going to wear a device of 86x54 mm on my wrist :)
19:02.16lkcltrue.  yes.  music players... well..... you think, we used to have walkmans and so on.... 86x54 is credit-card-sized... but... yeah
19:02.22lkclpeople now expect them to be usb-stick-sized
19:02.29penguin42lkcl: and I think mobiles are now probably below it
19:02.51lkcljust about, yes.  although some smartphones have to have larger screens.
19:02.59drachensunpeople still buy ipods, how big are those now?
19:03.02lkcland esp. the smartphones with keyboards
19:03.05drachensunstill phone sized I think
19:03.17lkclipods?  ooo, they're about the size of Compact Flash.
19:03.25lkclwhich is why i drew up EOMA-CF as well
19:03.34lkclbut, we'll get to that later
19:04.08penguin42lkcl: Right, so I hadn't seen your vision of that before which is why I couldn't see that before - the challenge then which I'm not too sure of is whether the market is really there; people carry the SD card between there tablet/tv/camera/laptop, or use their mobile as the module
19:04.42lkclpenguin42: sorry!
19:05.23drachensuncost cost cost, I think consumers would see the benefit of "I want the latest camera with 2123123 MP but this one is less because it uses my old cameras processor board"
19:05.24lkclpenguin42: yeah, some people aren't going to "grok" the various combinations
19:05.50penguin42lkcl: That argument is much better than 'servicing' argument; because 8 year old jonny probably can change an SO-DIMM
19:05.57Turldrachensun: you're likely to need a new processor to process the extra MPs anyway
19:06.04lkclbut that's ok - there are benefits for the factories, SoC vendors etc. etc. as well which gives them some incentive to make them
19:06.31lkclpenguin42: there's an article coming out in a couple of weeks
19:07.55drachensunTurl: maybe not a perfect example, but in a lot of consumer electronics pieces don't change generation to generation, except the processing
19:09.13penguin42lkcl: It's interesting though how uses change; the SD card and the mobile are now to some extent getting used as the module; people can carry their data around between all their devices; and I think on iphone 5 Apple have put a high bandwidth interface which I expect them to push that idea further (wtf they didn't use the thunderbolt or USB-3 I don't get, or is it actually a thunderbolt derivative)
19:10.09Turldrachensun: I really can't think of a single example :|
19:11.13*** join/#arm-netbook techn (~quassel@a91-152-35-60.elisa-laajakaista.fi)
19:13.35drachensunwell I just noticed there is a videobuf2-core driver
19:13.38drachensunmaybe that is what I need
19:15.49lkclpenguin42: apple have a different kind of agenda.  compliance with e.g. EU regulations on industry standards such as the USB charger/audio connector standard ain't high on their list....
19:16.22penguin42lkcl: Right, but their move to higher bandwidth interfaces I suspect is the interesting one to watch
19:18.02captainiglooI build my own kernel, git://github.com/amery/linux-allwinner.git branch allwinner-v3.0-android-v2 with arch/arm/config/sun4i_defconfig
19:18.16hnocaptainigloo, good.
19:18.16captainigloobut it freezez just after loading kernel in uboot
19:18.30hnothat's not good.
19:18.34captainigloo:)
19:18.43lkclpenguin42: yeahhh, they have the funds to create entire eco-systems, amortising the R&D and tooling across the cost of the devices, but still pushing up the overall unit price
19:18.56hnocaptainigloo, what device do you have?
19:19.08captainiglooi compare mine with the one in nightly build hw pack
19:19.11captainigloomele a2000
19:19.37lkclwhereas we're re-using stuff that's just borderline obselete, using decade-old lowest common denominator interfaces.  radically different approach!
19:19.43hnothe nightly build should be a sun4i_defconfig build as well.
19:19.59captainiglooit seems there is a diff in load adress and entry point of the uboot format
19:20.06captainigloofile uImage
19:20.07captainigloouImage: u-boot legacy uImage, Angstrom/3.0.42/allwinner-a10, Linux/ARM, OS Kernel Image (Not compressed), 4018700 bytes, Sat Sep 29 10:40:32 2012, Load Address: 0x20008000, Entry Point: 0x20008000, Header CRC: 0x18E011A8, Data CRC: 0x3424C34B
19:20.17hnothat do not look right.
19:20.24penguin42lkcl: Yeh I worry about that
19:20.26captainigloothis one is mine
19:20.50captainiglooram begins at 0x4000000 right ?
19:20.54hnoyes
19:21.22captainiglooi can't find where this value is used
19:21.33hnoand kernel load & entry point should be 0x40008000,
19:21.51captainiglooit should be passed during the mkimage step
19:21.58hnoram begins at 0x40000000 (one zero more)
19:22.13captainiglooyeah sorry 0x4000 0000
19:23.10hnoIt's set in arch/arm/mach-sun4i/Makefile.boot
19:23.22hnono idea where your build got 0x20008000 from.
19:24.38captainigloozreladdr-$(CONFIG_ARCH_SUN4I):= 0x40008000
19:24.49captainiglooit's the content of my Makefile.boot
19:25.08captainiglools
19:25.10captainiglooouch sorry
19:26.07hnoIs that uImage from the kernel build process, or created separately by your build environment=
19:26.09hno?
19:26.38captainigloomy build environment use the stanadrt kernel build process
19:27.10captainiglooi'm using openembedded btw
19:27.19hnoWhat's in arch/arm/boot/?
19:27.51captainigloobootp  compressed  Image  install.sh  Makefile  uImage  zImage
19:28.06hnoand the uImage there has 0x20008000 as address?
19:28.14captainiglooand file uImage shows Entry Point at 0x20008000
19:28.22captainiglooyes
19:28.25hnostrange
19:29.41captainiglooah , the script which generate the uImage has fixed ENTRYPOINT at 20008000
19:29.54captainiglooit's in openembedded
19:30.10captainigloodinally it's maybe not following the kernel build process
19:30.17captainigloo:)
19:31.45hnoobviously not entirely following process.
19:35.42captainiglooit seems i need to declare UBOOT_ENTRYPOINT and UBOOT_LOADADDRESS into my hardware configuration file ...
19:35.51captainigloomake sense
19:36.28mnemochno: I can't get wip/unified-aw to tell anything in the uart :<
19:36.44hnoNothing?
19:36.56mnemocnothing at all
19:37.52hnook. Thanks for trying. Will dig into it in detail.
19:39.37mnemochno: would it make sense to try sunxi again?
19:39.47mnemocwill the generated dram_para
19:39.52mnemocwith*
19:42.08hnomnemoc, sunxi do not have dram_para for sun4i, only sun5i.
19:42.56mnemocok
19:44.18captainigloohuhu, i finally get my squashfs image running on nand !
19:44.21hnodo it work on the A13?
19:44.30captainigloothanks guys :D
19:45.18rmhttp://www.kickstarter.com/projects/adapteva/parallella-a-supercomputer-for-everyone/
19:52.12mnemochno: I might have another problem.... sunxi used to greet and halt, now it doesn't show anything either
19:55.36hnook
19:58.07mnemocmeh, powercycling the board instead of playing with the button worked. sunxi now greets again
19:58.15mnemocback to unified-aw
19:59.35mnemocvery strange thing. on reboot it skips the uSD
20:00.37mnemochno: same, no greeting from a fresh unified-aw on my cubie
20:00.42hnook
20:00.46mnemocwill try the a13
20:00.57hnowould be great.
20:04.44mnemochno: btw, this was my intention http://sprunge.us/IeLe?diff
20:07.31mnemocand was going to add an equivalent call to init the PMU when called
20:07.41mnemocwith [target] values
20:07.48hnoOk.
20:08.02hnoThe SUN5I values are for Olinuxino A13.
20:08.13hnoAnd the original SUN4I ones are Mele.
20:08.59mnemocok
20:08.59hnoAh, density on the 1GB cubieboard should be 4096, not 2048.
20:09.20hnoand size 1024.
20:09.40mnemocbut might that cause it to not greet at all?
20:09.49hnounlikely.
20:10.10hnoshould run fine with too small density & size.
20:45.43mnemochno: it seems to be PMU related, in both (a13 olinuxino and cubieboard) with plugging the board with a card made of unified-aw there is no reaction in uart AND the power button does nothing at all
20:46.10mnemocafter pressing reset, boots fine from NAND
20:49.17mnemocwith the uSD still connected
20:49.35captainigloodid you already get this kind of error with nand driver :
20:49.38captainigloohttp://pastebin.ca/2231521
20:50.56captainigloothis log is better, i launch nand-part, and i get error, the second time it's ok
20:51.00captainigloohttp://pastebin.ca/2231532
20:51.27mnemocuh
20:52.32mnemoccaptainigloo: you should really reflash it
20:52.52captainiglooyep but i need windows ?
20:53.16mnemocunfortunatelly yes
20:53.31captainiglooi try to launch LiveSuit with wine but it doens't work
20:53.46captainiglooi have macos, linux, android
20:53.51captainigloobut no windows :(
20:54.17hnophoenixcard might work better, but probably not.
20:55.09captainigloowhere could i find the phonix card ?
20:55.14TurlI cannot see the logs :<
20:55.24Turlcaptainigloo: it's generated with a windows software
20:55.30captainigloo:'(
20:55.52Turlcaptainigloo: can you paste your logs somewhere else? :< pastebin.ca doesn't work for me
20:56.14captainigloo.com is ok ?
20:56.38captainigloohttp://pastebin.com/xh6snxMp
20:57.01mnemochttp://sprunge.us/ rules
20:57.23Turlyeah .com is ok as long as it doesn't show me a captcha :P
20:59.44Turlweird stuff captainigloo, never seen anything like that :/
21:00.04captainiglooo:/
21:00.42captainigloothat's really strange
21:00.54captainiglooi relaunch again, an now there is no problem
21:01.02captainiglooat least when i launch nand-part
21:02.33captainigloook now my mele is completely instable
21:03.04captainiglooouach
21:04.43Turlah, you have a mele?
21:04.49Turlthere's a dd-able phoenixcard somewhere
21:05.51captainiglooabout the nand partitions
21:06.02captainiglooi need to align the partitions ?
21:07.56hnomnemoc, A13 Olinuxuni should not differ between sunxi and wip/unified-aw. Ifthere is a difference then I goofed up something.
21:08.21Turlcaptainigloo: http://lundman.net/ftp/mele/Mele_HTPC_Android_4.0_V1.ddimg.bin.bz2
21:08.31Turldownload, uncompress and dd to a sdcard, then boot your mele with it
21:08.32captainiglooTurl: hehe, i just find this linnk !
21:09.10Turlif you have uart you should be able to follow the install process there
21:09.23captainiglooyep, thanks !
21:09.42mnemochno: i'll test pristine sunxi on the a13 olinuxino now
21:10.16*** join/#arm-netbook avernos (~avernos@111.194.214.45)
21:10.17*** join/#arm-netbook avernos (~avernos@unaffiliated/avernos)
21:16.12mnemochno: sunxi/sun5i booted just fine
21:18.26hnoYes.. unified-aw seems dead.
21:18.34hnolets see where.
21:32.28captainiglooTurl: ok ICS is booting now;), and nand seems to be ok
21:33.16Turl:)
21:33.51mnemoccaptainigloo: and now nand-part works fine?
21:36.45*** join/#arm-netbook pwhalen (~paul@CPE001310360dac-CM78cd8ec9e405.cpe.net.cable.rogers.com)
21:39.54*** join/#arm-netbook cat1 (~cat_x301@a91-152-66-200.elisa-laajakaista.fi)
21:40.19hnomnemoc, ok, found one copy-paste bug which caused internal dram bus clock to not enable.. guess that may have some impact.
21:41.11mnemoc:)
21:47.51hnoU-Boot SPL 2012.10-rc1-00830-gb88d9f5-dirty (Sep 29 2012 - 23:42:18)
21:47.52hnoMMC:
21:48.13hnolooks better.
21:48.18mnemoc:)
21:48.28mnemocpush the fix please
21:48.45rmwhat's with that problem where U-boot SPL refuses to see MMC on one MK802
21:48.56mnemoctechn: there is a thread about edid in the cubieboard list which desperately needs you :)
21:49.05rmany hope it's been fixed by something recently? should I retry?
21:49.25mnemocisn't that fixed with a clock factor change?
21:50.30rmI thought clock factor was fixing something else, i.e. that instability and kernel crashes
21:50.48mnemocah, ok. never mind
21:51.03hnomnemoc, pushed.
21:51.05*** join/#arm-netbook ssvb (~ssvb@212.16.98.80)
21:52.10hnorm, there is reports about u-boot-mmc not liking some SD cards, probably a timeout issue where it doesn't wait long enought for the card to come online.
21:52.22mnemocrootwait ?
21:52.38mnemocmeh. need to sleep
21:52.39hnono, earlier when u-boot tries to access the mmc.
21:53.23rmI mean this http://permalink.gmane.org/gmane.comp.hardware.netbook.arm/4203
21:53.45hnonot planning to look into MMC issues until PMU support is implemented.
21:53.52*** join/#arm-netbook calris (~calris@d110-32-174-6.sbr801.nsw.optusnet.com.au)
21:54.16hnorm, yes that.
21:55.08rmalso this is with 3 or 4 different cards, but consistently on one MK802 out of three
21:55.38mnemochno: `fexc -O uboot` now makes an struct pmu_para made out of [target]
21:56.19hnorm, could also be the PMU issue, if it's a newer MK802 with PMU. Running the CPU under voltage gives all kinds of wierd errors.
21:56.27mnemocstill only a proof of concept obviusly, output needs to match uboot needs
21:57.01hnomnemoc, plus that more and more boards will come with empty parameters.
21:57.47hnoluckily rand, bus, io, density and size can all be determined by visually inspecting the board.
21:58.10mnemoclivesuit uses sys_config, so there must be "good defaults" we can adopt
21:58.11hnos/rand/rank/
21:58.39hnomnemoc, livesuit is said to autodetect memory layout these days.
21:58.55mnemocdoesn't believe in magic
21:59.18mnemocit could trial and error
21:59.35hnoIt's supposedly one of the big things with the A13 push as it makes the same image run on many different boards.
21:59.54hnoofcourse it's trial and error.
22:00.06mnemocso NULL fields would mean "detect"?
22:00.08hnobut some educated trial & error.
22:00.11hnoyes.
22:00.34mnemocdo I turn those into... 0xffffffff ?
22:00.40hnono idea what phoenixcard does.
22:00.58hnothe code I have do not do any autodetection.
22:01.40mnemocyet :)
22:02.06hnohave not planned to implement any autodetection.
22:02.45mnemoc:)
22:03.20hnobut guess we will need to deal with this one way or another as information is unavailable.
22:03.29hnoto users-
22:04.13mnemocthinking in "the users" if we can't trust script.bin, and "good defaults" are not possible... a fel tool to dump the boot1 header?
22:04.30mnemockind of sucks :|
22:05.09mnemocanother way is to keep an archive of trustworthy $board.fex files
22:06.48mnemoclike the chips thing in the SDK, but corrected to not assume livesuit will do it's thing
22:06.49hnoWell. there isn't really that many different DRAM configurations. So a little guide based on number of chips, type of chips and cpu model helps filling in the gaps.
22:07.49hnobut having corrected fex files helps a lot.
22:08.54mnemochno: cubieboard + unified-aw (with board_cubieboard.c) worked :)
22:08.58hnolivesuit misdetects the A13 Olinuxino configuration btw.
22:09.18mnemocbut... DRAM:  1 KiB
22:09.33hnoEh. Right. Wrong scale ther.
22:10.03mnemochttp://sprunge.us/OYQB?diff
22:11.34hnois missing mele.
22:12.02hnothe sun4i config you deleted.
22:12.28mnemocyes
22:12.49mnemocbut without a CONFIG_ ruling this I can't really start making a collection yet
22:14.19hnoMemory size fix pushed.
22:14.49mnemochttp://sprunge.us/YEaI <--- now with mele
22:15.12hnobut don't try that meminfo with MALI enabled.
22:16.06hnomnemoc, better.
22:17.41hnoI also have another dram.c based on toms code, but much more work to merge that and rewrite to seinsible parameterized code than to switch to the allwinner code.
22:18.14mnemocbtw, that board_mele.c is made from the stock script.bin, not from the code I deleted
22:18.54hnoshould not differ. Does it?
22:19.03mnemocdidn't check :p
22:19.41mnemocDRAM:  1 GiB
22:19.45mnemoc\o/
22:20.15hnoYes, but clock speed probably isn't very good.
22:20.58mnemoci'll start playing with the kernel here tomorrow... with mali disabled
22:21.46hnomaybe possible to use cpufreq to switch to better speeds, that do reprogram the PMU. But don't know. There is more voltage settings than just the core.
22:22.02mnemoc:(
22:22.45mnemocmaybe setting the default governor to performance can make an early reclocking?
22:23.41hnoyou can try. But I would prefer to get the PMU under control before trying higher clocks.
22:23.58mnemocfair enough
22:24.43hnobut on the other hand most A10 devices seem fine with default voltages for some strange reason.
22:25.49hnoI do have PMU TWI traces, but then realized the trace is a warm trace with the PMU already configured. Need to redo the trace at cold boot.
22:26.39hnoThe third access is reading a non-default value of a user defined register (4 bytes of user defined usage, preserved by PMU as long as there is at least backup power)
22:34.11captainigloomnemoc: nand-part works again
22:34.28mnemoc\o/
22:34.33captainigloo:)
22:34.45captainigloobut i don't understand what it says
22:35.15captainigloohttp://pastebin.com/2tjFFXhU
22:35.25captainigloopartition1, i guess it's nanda
22:35.36captainigloosorry partition0
22:35.45captainigloopartition size is 32768
22:35.49hnoyes.
22:35.52captainigloobut 32768 what ?
22:36.12hnokb IIRC. nanda is very small.
22:36.21captainiglooah !
22:36.22hnoor is it blocks?
22:36.26captainigloono
22:36.41captainigloomount /dev/nanda /mnt/nanda
22:36.45captainigloodf -h
22:37.00captainigloo/dev/nanda               16.0M      6.5M      9.5M  41% /mnt/nanda
22:37.05captainiglooit's 16MB
22:37.48mnemocyes, 512b blocks
22:37.54mnemocB
22:38.19captainiglooah ok
22:38.50captainiglooit's maybe why i fucked up my partition table earlier ;)
22:39.05captainiglooi was sure it's in bytes :D
22:41.28mnemoc:)
22:41.32mnemocgoing to sleep
22:41.34mnemocgood night
22:41.38captainigloogn
23:15.52*** join/#arm-netbook Thomas42 (~Thomas42@static.105.236.9.5.clients.your-server.de)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.