| 00:49.29 | *** join/#arm-netbook mysteryname (~mysteryna@14-202-9-167.tpgi.com.au) |
| 03:05.39 | *** join/#arm-netbook tekzilla (~jon@hmbg-5f77db18.pool.mediaWays.net) |
| 03:27.06 | *** join/#arm-netbook QingPei (~qingpei@61.191.41.175) |
| 03:57.29 | *** join/#arm-netbook QingPei1 (~qingpei@202.102.71.11) |
| 03:59.32 | *** part/#arm-netbook QingPei1 (~qingpei@202.102.71.11) |
| 06:02.03 | *** join/#arm-netbook Quarx (~Quarx@94.137.60.155) |
| 06:03.47 | *** join/#arm-netbook ceo16 (~asus@host5-35-dynamic.0-87-r.retail.telecomitalia.it) |
| 06:32.30 | *** join/#arm-netbook asus_ (~asus@host35-242-dynamic.8-87-r.retail.telecomitalia.it) |
| 07:03.49 | *** join/#arm-netbook asus__ (~asus@host121-26-dynamic.4-87-r.retail.telecomitalia.it) |
| 07:09.14 | *** join/#arm-netbook asus__ (~asus@host197-238-dynamic.9-87-r.retail.telecomitalia.it) |
| 07:48.08 | *** join/#arm-netbook asus__ (~asus@host189-247-dynamic.9-87-r.retail.telecomitalia.it) |
| 07:48.46 | *** join/#arm-netbook cheng (~cheng@214.48.48.60.kmr03-home.tm.net.my) |
| 07:49.03 | cheng | anyone manage to get i2c work in meleA1000? |
| 08:02.15 | *** join/#arm-netbook cat1 (~cat_x301@a91-152-66-200.elisa-laajakaista.fi) |
| 08:02.55 | hno | cheng, yes |
| 08:06.13 | cheng | hno: from rhombus-tech, i need to add R14/R15(jumper) to enable it? |
| 08:06.23 | cheng | what i2c-line is that on the eeprom? |
| 08:06.31 | cheng | as i saw it have i2c-0/1/2 |
| 08:08.45 | hno | no idea. have only tried talking to the pmu which is i2c connevted. |
| 08:10.03 | cheng | that's the i2c device already on the melea1000? |
| 08:10.06 | hno | and nowdays playing more with cubieboard & olinuxino where I/O functions are conveniently exposed on expansion pins. |
| 08:10.11 | hno | cheng, yes. |
| 08:12.40 | cheng | ok, thanks. i've work with what i have till i manage to get a cubieboard |
| 08:13.51 | hno | If you don't need HDMI then http://linux-sunxi.org/A13-OLinuXino is very nice for hacking. |
| 08:15.58 | cheng | too bad i need HDMI |
| 08:16.43 | cheng | would it be useful if i put device that i found on meleA1000 on net for other reference? |
| 08:37.13 | hno | cheng, please expand http://linux-sunxi.org/Mele_A1000 with your findings. |
| 08:37.19 | hno | what did you find? |
| 08:38.08 | cheng | i'm trying to scan any i2c device available on the board, |
| 08:38.41 | cheng | so far seems like on i2c-0, there is a device 0x34 (not too sure) |
| 08:38.54 | hno | 34 is the pmu |
| 08:39.03 | *** join/#arm-netbook gimli (~gimli@xbmc/staff/gimli) |
| 08:39.28 | cheng | but from the PMU(AXP209) datasheet, the device address is 0x68 |
| 08:42.35 | hno | That's because they include the read/write bit in the address there. |
| 08:42.43 | hno | 0x68 >> 1 == 0x34. |
| 08:43.02 | cheng | aiks...silly me..thanks.. |
| 08:44.26 | hno | Hm. why is so little info on A1000 on linux-sunxi? http://rhombus-tech.net/allwinner_a10/hacking_the_mele_a1000/ has plenty more info. |
| 08:46.02 | hno | there. link added. |
| 08:48.18 | cheng | cnx-software also have plenty of info on this device, i learn most stuff from there. |
| 08:50.11 | *** join/#arm-netbook rellla (~Thunderbi@p4FE562B4.dip0.t-ipconnect.de) |
| 08:52.22 | *** join/#arm-netbook popolon (~popolon@og-free.planet-service.fr) |
| 09:05.27 | *** join/#arm-netbook tzafrir_laptop (~tzafrir@local.xorcom.com) |
| 09:10.33 | discopig | sunxi is nice |
| 09:39.20 | *** join/#arm-netbook merbzt (~benjamin@c-94-255-220-30.cust.bredband2.com) |
| 09:56.45 | *** join/#arm-netbook avernos (~avernos@111.192.246.193) |
| 09:56.46 | *** join/#arm-netbook avernos (~avernos@unaffiliated/avernos) |
| 09:57.10 | *** join/#arm-netbook rellla1 (~Thunderbi@p5B078ADE.dip0.t-ipconnect.de) |
| 10:16.33 | *** join/#arm-netbook Marex (~Marex@2a01:430:d:0:2cc:6ff:fefc:db16) |
| 10:21.15 | oliv3r | anybody tried flashing anything with livesuit for linux? i keep getting the error 'invalid image' |
| 10:21.30 | oliv3r | do I need to copy some 'key' file or something frmo the windos version from the oem? |
| 10:21.48 | oliv3r | (the module is patched and loads fine as per patch i put on the ML) |
| 11:51.34 | *** join/#arm-netbook ibot (~ibot@rikers.org) |
| 11:51.34 | *** topic/#arm-netbook is EOMA: Embedded Open Modular Architecture - Don't ask to ask. Just ask! - http://elinux.org/Embedded_Open_Modular_Architecture/EOMA-68 - ML arm-netbook@lists.phcomp.co.uk - Logs http://ibot.rikers.org/%23arm-netbook or http://irclog.whitequark.org/arm-netbook/ - http://rhombus-tech.net/ |
| 12:06.37 | *** join/#arm-netbook dw4rf (~dw4rf@IGLD-84-229-15-146.inter.net.il) |
| 12:09.44 | *** join/#arm-netbook Yakuzzi (~za@ip-2-206-85-73.web.vodafone.de) |
| 12:16.05 | Yakuzzi | hey there, i just saw a good offer i think |
| 12:16.07 | Yakuzzi | http://zzkko.com/ainol-novo7-crystal-android-tablet.html |
| 12:16.32 | Yakuzzi | when i understand right there is a high propability that xbmc will run on it ? |
| 12:16.57 | Yakuzzi | due to the amlogic chipset ? |
| 12:24.56 | *** join/#arm-netbook QingPei (~qingpei@123.118.102.76) |
| 12:31.20 | *** join/#arm-netbook dw4rf (~dw4rf@IGLD-84-229-15-146.inter.net.il) |
| 12:47.10 | mnemoc | cat1: hi, does http://sprunge.us/hSDE let use rt8192cu on 3.4 on runtime? |
| 12:54.26 | *** join/#arm-netbook avernos (~avernos@111.192.246.193) |
| 12:54.27 | *** join/#arm-netbook avernos (~avernos@unaffiliated/avernos) |
| 12:57.50 | techn | mnemoc: what you think if we merge disp branch.. And leave code which causes green screen to #if 0 ? |
| 13:01.41 | techn | https://github.com/techn/linux-allwinner/blob/1b0a097e82c8b8b8ecc54754fdf7259728ea4a6d/drivers/video/sunxi/hdmi/aw/hdmi_core.c#L380 |
| 13:06.08 | *** join/#arm-netbook mano (~mano@117.201.172.41) |
| 13:07.43 | *** join/#arm-netbook Yakuzzi (~za@ip-2-206-85-73.web.vodafone.de) |
| 13:08.25 | *** join/#arm-netbook asus__ (~asus@host189-247-dynamic.9-87-r.retail.telecomitalia.it) |
| 13:16.41 | mnemoc | techn: if you have it narrowed, and works fine. sure |
| 13:36.35 | oliv3r | anybody tried the linux livesuit yet? I kept getting an error about invalid image, where as it worked fine in the windos version |
| 13:37.38 | mnemoc | it might rely in a newer packer tool. try to repack it in linux too |
| 13:38.01 | oliv3r | i used the one supplied by the oem of the tablet |
| 13:38.06 | oliv3r | is it 'safe' to unpack and repack? |
| 13:38.33 | mnemoc | i suppose |
| 13:48.19 | *** join/#arm-netbook popolon (~popolon@og-free.planet-service.fr) |
| 13:56.22 | *** join/#arm-netbook tuliom (~tuliom@186.214.48.149) |
| 14:06.03 | *** join/#arm-netbook Yakuzzi (~za@ip-2-206-85-73.web.vodafone.de) |
| 14:28.22 | *** join/#arm-netbook mikey_w (~mike@c-71-63-115-202.hsd1.va.comcast.net) |
| 14:28.39 | *** join/#arm-netbook n6pfk (~mike@c-71-63-115-202.hsd1.va.comcast.net) |
| 14:29.32 | *** part/#arm-netbook QingPei (~qingpei@123.118.102.76) |
| 14:33.18 | *** join/#arm-netbook wingrime (~alex@78.109.115.103) |
| 14:34.29 | wingrime | mnemoc: You can see patches that make work ts on my tablet https://github.com/wingrime/linux-allwinner |
| 14:34.53 | wingrime | but it need some Kconfig stuff... |
| 14:35.20 | wingrime | also I now fixed driver re insmod |
| 14:35.36 | wingrime | not make push yet |
| 14:36.42 | *** join/#arm-netbook Yakuzzi (~za@ip-2-206-85-73.web.vodafone.de) |
| 14:37.35 | mnemoc | wingrime: send them to the mailing list please |
| 14:38.23 | wingrime | push requests is possible ? |
| 14:38.50 | mnemoc | ML preferred |
| 14:39.08 | mnemoc | so the rest of the devs can comment |
| 14:40.12 | wingrime | give me link to you maillist |
| 14:40.30 | *** join/#arm-netbook Yakuzzi (~za@ip-2-206-85-73.web.vodafone.de) |
| 14:40.35 | mnemoc | http://linux-sunxi.org/Mailing_list |
| 14:41.01 | mnemoc | http://linux-sunxi.org/Submitting_patches |
| 14:41.54 | wingrime | ok I make some cleanup and think about it |
| 14:48.49 | *** join/#arm-netbook pwhalen (~paul@CPE001310360dac-CM78cd8ec9e405.cpe.net.cable.rogers.com) |
| 14:50.52 | *** join/#arm-netbook mikey_w (~mike@c-71-63-115-202.hsd1.va.comcast.net) |
| 14:51.06 | *** join/#arm-netbook n6pfk (~mike@c-71-63-115-202.hsd1.va.comcast.net) |
| 14:57.32 | techn | wingrime: have you tried latest codes.. there is already fix for some ts problem |
| 14:59.00 | techn | atleast it helped drachensun |
| 14:59.22 | cat1 | mnemoc: on rt8192cu -- never tried, I am using rtlwifi. |
| 15:00.56 | *** join/#arm-netbook rzk (~rzk@128-72-194-30.broadband.corbina.ru) |
| 15:01.46 | cat1 | mnemoc: though some dirty hacking is required there as well.. |
| 15:02.42 | mnemoc | it seems the only problem is that sanity check over a list which doesn't exist in 3.4's struct wake_lock |
| 15:02.44 | wingrime | techn:what commit? |
| 15:03.06 | techn | https://github.com/linux-sunxi/linux-sunxi/commit/b32a25f543e23503002ec2d4a164bca502df6868 |
| 15:10.33 | wingrime | techn: one bug fixed in goodix_touch but not in ft5x_ts |
| 15:10.52 | wingrime | +#define CTP_IRQ_NO (gpio_int_info[0].port_num) |
| 15:12.41 | wingrime | techn: see my github, dirty fix for now, but it working |
| 15:13.14 | mnemoc | https://github.com/linux-sunxi/linux-sunxi/blob/sunxi-3.0/drivers/input/touchscreen/goodix_touch.c#L105 |
| 15:13.32 | mnemoc | err |
| 15:14.04 | mnemoc | https://github.com/linux-sunxi/linux-sunxi/blob/sunxi-3.0/drivers/input/touchscreen/ft5x_ts.c#L114 .... uhm |
| 15:14.44 | wingrime | I have ts on INT11 |
| 15:15.14 | mnemoc | it seems I screwed up the merge |
| 15:16.12 | wingrime | but it not enough to make it working on my HW |
| 15:17.10 | wingrime | now I will look for resume/suspend bug with ts |
| 15:17.37 | mnemoc | wingrime: but please, to the ML |
| 15:17.45 | techn | wingrime: could you try if #define CTP_IRQ_NO (gpio_int_info[0].port_num) helps you.. changing hardcoded 21 to 11 is just moving the bug :/ |
| 15:18.45 | wingrime | I know this |
| 15:20.21 | mnemoc | is http://sprunge.us/JdCY?diff the only missing part? |
| 15:21.19 | wingrime | not only for make it work for me |
| 15:21.47 | mnemoc | can you compare it with the driver in the import-sunxi branch? |
| 15:22.04 | wingrime | https://github.com/wingrime/linux-allwinner/commit/4be7cd998cd76943fb06286138426b599214c031 |
| 15:22.51 | wingrime | I now make git clone for new place of code |
| 15:23.26 | mnemoc | also, make the commit mergable. not C++ comments, no "signatures", ... |
| 15:23.34 | mnemoc | no hardcoded values |
| 15:23.54 | mnemoc | but please compare it with the driver in import-sun5i branch to see what else I missed |
| 15:24.02 | mnemoc | now I can't look deeper on that |
| 15:24.27 | wingrime | ok, just wait |
| 15:25.41 | wingrime | also, WRN:L2357(drivers/usb/sun4i_usb/udc/sw_udc.c):ERR : dev->driver=0xc0790e8c, dev->gadget.speed=0 |
| 15:25.53 | wingrime | have you this flood? |
| 15:38.20 | wingrime | menmoc: you lost only interrupt http://pastebin.com/fRTcWwKG |
| 15:40.40 | wingrime | please fix this in git and I make patch that fix second bug |
| 15:42.40 | mnemoc | wingrime: ok. I'll commit the paste I showed before |
| 15:43.10 | *** join/#arm-netbook toxicpsion (~toxicpsio@h216-45-98-25.dynamic.platinum.ca) |
| 15:44.49 | wingrime | in my plaste reversive patch as you see |
| 15:45.00 | wingrime | it need inverce |
| 15:45.24 | mnemoc | http://sprunge.us/JdCY?diff |
| 15:47.33 | wingrime | prefect |
| 15:57.18 | mnemoc | wingrime: done |
| 15:59.08 | wingrime | thanks |
| 15:59.29 | mnemoc | thanks you for reporting it |
| 16:01.47 | wingrime | send patch over ML or pool-req ? |
| 16:01.53 | mnemoc | ML |
| 16:01.57 | wingrime | ok |
| 16:02.18 | *** join/#arm-netbook tzafrir_laptop (~tzafrir@local.xorcom.com) |
| 16:19.24 | *** join/#arm-netbook MMlosh (~MMlosh@2001:470:6f:23:ed2d:96f:9d79:b869) |
| 16:28.19 | *** join/#arm-netbook Yakuzza321 (~za@ip-109-40-153-175.web.vodafone.de) |
| 16:43.16 | techn | mnemoc: I figured out how to fix that problem.. much better solution ;) |
| 16:43.59 | mnemoc | \o/ |
| 16:44.06 | Yakuzza321 | does anyone got experience how easy it is to use an external bluetooth dongle on a mele with stockrom ? |
| 16:44.25 | Yakuzza321 | * stockrom ics 1.2 |
| 16:45.45 | mnemoc | techn: out_csc = 2; ???? |
| 16:45.48 | mnemoc | just that? |
| 16:46.36 | *** join/#arm-netbook rsalveti (~rsalveti@linaro/rsalveti) |
| 16:49.24 | techn | mnemoc: yes :) |
| 16:50.02 | techn | :D |
| 16:53.49 | *** join/#arm-netbook simosx (~simosx@ubuntu/member/simosx) |
| 16:55.50 | *** join/#arm-netbook merbzt (~benjamin@c-94-255-220-30.cust.bredband2.com) |
| 17:11.36 | *** join/#arm-netbook dw4rf (~dw4rf@bzq-79-179-142-245.red.bezeqint.net) |
| 17:29.16 | hno | Yakuzza321, no idea if bluetooth is at all enabled in Mele stock Android rom. |
| 18:03.19 | Yakuzza321 | which rom is recommendable at the moment, i have only one device and actually want to use it at an tv with cvbs input, so does there happen to be a rom where there might even be a uinput.ko for droidmote and bluetooth enabled ? |
| 18:03.41 | specing | what is a rom? |
| 18:04.05 | specing | Yakuzza321: ? |
| 18:04.16 | Yakuzza321 | the system image |
| 18:04.20 | specing | no. |
| 18:04.31 | specing | try again. What is a rom? |
| 18:04.57 | Yakuzza321 | you mean read only memory or what you mean ? |
| 18:05.27 | specing | That would be the correct definition |
| 18:05.49 | Yakuzza321 | but i used it interchangebly with the image i´d flash on the device |
| 18:05.56 | specing | And with this in mind, your question does not seem logical |
| 18:06.12 | specing | Why can't you just ask "which system image ...", then? |
| 18:07.46 | Yakuzza321 | good point, is there a system image in which almost all output features of my mele are covered ? |
| 18:07.59 | Yakuzza321 | sata,vga,cvbs,ethernet |
| 18:30.24 | *** join/#arm-netbook lkcl (~lkcl@host86-131-170-4.range86-131.btcentralplus.com) |
| 18:38.35 | hno | Yakuzza321, outputting what? |
| 18:40.32 | *** join/#arm-netbook rsalveti (~rsalveti@linaro/rsalveti) |
| 19:00.00 | toxicpsion | while on topic of mele... anyone figure out what unpopulated 13J1 (4pin by SATA) is connected to on a2000? |
| 19:02.33 | toxicpsion | my guess is one of the a10 USB hosts (since all 3 external USB come from GL850G)... opinions? |
| 19:17.10 | mnemoc | the otg header is behind the ethernet. and the other native usb host goes to the wifi |
| 19:17.26 | mnemoc | and those are the 3 native usbs the a10 has |
| 19:22.09 | *** join/#arm-netbook rsalveti_ (~rsalveti@linaro/rsalveti) |
| 19:24.25 | hno | toxicpsion, you mean the connector between sata and vga? |
| 19:24.55 | hno | my guess is something audio related. |
| 19:25.10 | hno | but have not traced it at all. |
| 19:28.19 | hno | toxicpsion, the fourth USB port from the HUB is the 6 pin header between SD & USB on the side. |
| 19:29.25 | hno | 12J4 is also unidentified. |
| 19:29.45 | toxicpsion | yea... i forgot about the wifi using one.... |
| 19:33.41 | toxicpsion | where's 12j4? my eyes are missing it :| |
| 19:34.04 | hno | 2 pin, next to SD |
| 19:35.00 | toxicpsion | connected to 17R6(unpopulated).... |
| 19:35.01 | hno | missing a resistor as well.' |
| 19:35.41 | oliv3r | i'm comparing christian troy's script.bin (wherever he may got it from) to the one the oem supplied; found some differences in values that is not on the fex guide wiki. things plike pll4/6_freq, storage_type, [card_burn_para] |
| 19:36.28 | toxicpsion | any idea what value that resistor should be? i'll throw a logic analyser on it. |
| 19:36.31 | oliv3r | anybody got a more detailed list of explainations? (i haven't started going through the file further then the top two sections, was going to look why I can't get into recovery mode with christian troy's script.bin any more (which seems odd) (this all for the momo9 clone) |
| 19:36.52 | hno | ppl frequencies are pretty obvious. |
| 19:37.38 | hno | those are clock frequencies for different I/O functions. And there is several ways to wire those two. |
| 19:39.51 | hno | I think storage_type is telling livesuit if it should use NAND or SD. Not sure. |
| 19:39.58 | oliv3r | I assume that since script.bin is generated by livesuit that one should be concidered 'best' for my board? anyhow, those where as an example, there's many more script.bin values that i don't know what should be used |
| 19:40.21 | hno | script.bin is generated in the image build process. Don |
| 19:40.26 | oliv3r | the entire [card_burn_para] section is 'new' with things like card_no, card_line, card_mode, sdc_d1 sdc_d0, sdc_clk, sdc_cmd, sdc_d? |
| 19:40.29 | hno | Don't think livesuit changes it. |
| 19:40.45 | *** join/#arm-netbook wingrime (~alex@78.109.115.103) |
| 19:40.56 | hno | Those are SD interface parameters for flashing to SD/eMMC. |
| 19:40.59 | oliv3r | ah, i thought livesuit dynamically sets up some things (like ram timings? i forgot allready whattt exactly it did) |
| 19:41.20 | oliv3r | 'card burn parameters' does make sense :) anyway, was just seeking an accurate list |
| 19:41.21 | hno | It does, but not in script.bin. Those parameters are stored in boot0 & boot1. |
| 19:41.27 | oliv3r | i'll add the valueees i find that aren't in the wiki to the wiki |
| 19:41.44 | oliv3r | and someone more knowledgable hopefully can enter them :) |
| 19:42.12 | hno | mnemoc, do you have the A13 fex guide? |
| 19:42.18 | oliv3r | i'll probably use the OEM script.bin as that one atleast allows me to get back into recovery mode :) |
| 19:42.36 | oliv3r | i was looking at the http://linux-sunxi.org/fex-guide |
| 19:42.51 | oliv3r | s/fex-guide/Fex-Guide/ |
| 19:43.52 | mnemoc | hno: the only difference i've noticed in A13 .fex files is the usage of port:power[0123] to refer to the AXP GPIOs |
| 19:44.13 | mnemoc | we have a short datasheet, but no "guides" |
| 19:45.33 | mnemoc | http://dl.linux-sunxi.org/A13/A13%20Datasheet%20-%20v1.12%20%282012-03-29%29.pdf |
| 19:46.24 | toxicpsion | hno: what's 11J1 (14pin @ front)? |
| 19:48.20 | mnemoc | jtag? |
| 19:49.06 | oliv3r | i'm actually just looking at [jtag_para] and if your really good, you could trace them back to PB14 PB15 PB16 and PB17 :p |
| 19:54.12 | simosx | I want to get mkbootimg for Ubuntu. Is https://gist.github.com/1087757 the only way? |
| 19:55.26 | mnemoc | simosx: that comes in the android sdk |
| 19:57.21 | simosx | mnemoc, it's part of the utils like adb and so on? that would be nice. |
| 19:58.13 | mnemoc | i get adb and fastboot from a ppa from linaro |
| 19:58.24 | mnemoc | but it doesn't include mkbootimg |
| 20:02.45 | *** join/#arm-netbook tzafrir_laptop (~tzafrir@bzq-218-155-148.cablep.bezeqint.net) |
| 20:04.52 | hno | toxicpsion, JTAG. |
| 20:05.58 | oliv3r | hmm, i don't know where this guy got his scripts.bin from, but it almost looks like he randomly enabled all sorts of thigns, or got it form a completly different device |
| 20:06.26 | oliv3r | it's supposed to be for tablets, but things like sata ports, ir ports etc etc are all enabled |
| 20:06.27 | hno | oliv3r, most script.bin:s are quite crappy. |
| 20:06.41 | oliv3r | yeah, i guess the one that is most trustworthy would be the vendor supplied one, right? |
| 20:06.45 | oliv3r | even though it's crappy :p |
| 20:06.49 | mnemoc | they just tweak the template |
| 20:06.59 | hno | they take the EVB one and modify it slightly for their device. |
| 20:07.04 | oliv3r | how important is pmu_battery_rdc/cap? |
| 20:07.32 | oliv3r | i think the android folks, 'chefs' they call them these days, just use a script.bin that comes from some device i guess |
| 20:08.22 | oliv3r | anyway, those battery values, the resitance and capicitance should come from 'some' test. I guess I can't test it so i'll just have to hope the oem put some sane values there :) |
| 20:08.40 | hno | The battery parameters should match the battery for charging and charge level to work right. |
| 20:08.59 | oliv3r | thats what i mean, unless i have some verified sources, the vendor values are the most likly ones |
| 20:09.11 | hno | yes |
| 20:09.22 | oliv3r | hmm, why does the wiki say: 'please read the documentaiton of the cell parameter test instruction) |
| 20:09.42 | hno | Because it's a copy-paste document. |
| 20:09.55 | oliv3r | ohh |
| 20:10.28 | hno | and annoyingly lacks reference to which chinese version the wiki one is based on. |
| 20:10.41 | simosx | mnemoc, I could not find 'makebootimg' in the Android SDK. Continuing with source. I need makebootimg to create images for the linux-allwinner source. |
| 20:10.51 | oliv3r | :S |
| 20:11.14 | mnemoc | simosx: wasn't it `mkbootimg` and not `makebootimg` ? |
| 20:11.21 | hno | there is a document on how to test the battery to get some of the parameters. |
| 20:11.33 | akaizen | how did empat0 get all those cedarx docs? |
| 20:11.35 | oliv3r | well, i went through script.fex but find nothing obvious as to why I can't enter recovery mode when flashing this stuff :S well, lets find out if the original script.bin works well :D |
| 20:11.50 | mnemoc | hno: maybe it was there initially and got "lost" on wikification? |
| 20:11.59 | mnemoc | in which case it would be in the history |
| 20:12.26 | simosx | mnemoc, sorry, you are right, it's 'mkbootimg' (not available in the Android SDK). |
| 20:13.30 | mnemoc | http://androidforums.com/international-gsm-galaxy-nexus-all-things-root/540134-mkbootimg-unpackbootimg.html <--- first google match for: mkbootimg android |
| 20:13.57 | hno | simosx, http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images |
| 20:14.09 | hno | another. |
| 20:15.59 | hno | feels yet another NIH syndrome in Android here.. Why couldn't they just use one of the existing multipart boot image formats? |
| 20:16.27 | mnemoc | https://github.com/Quarx2k/android_system_core/tree/ics/mkbootimg |
| 20:17.23 | oliv3r | so what is repsonsible for entering recovery mode, that could be overwritten with some android rom (which shouldn't write more then /system, /bootloader (nande iirc) |
| 20:17.43 | RaYmAn | There's also a 'standalone' variant of mkbootimg + a boot.img unpacker https://github.com/androidRoot/boottools |
| 20:17.51 | hno | oliv3r, u-boot iirc. But not playing with Android. |
| 20:18.20 | oliv3r | i just wanna have android 'properly' running on this tablet before playing with booting from uSD and more :) |
| 20:18.35 | oliv3r | just something decent to fallback on, as the vendor firmware is ... well really crap; and i don't trust vendor binaries :) |
| 20:18.45 | RaYmAn | oliv3r: on most devices, bootloader checks for key combo and for boot-recovery written to MISC partition (seperately) |
| 20:20.02 | oliv3r | and the bootloader (u-boot I guess?) checks the bootloader partition for extra info? (/dev/block/nanda) |
| 20:21.11 | oliv3r | so if the vendor firmware goes successfully into recovery mode, then flashing 'a' android rom 'that doesn't mess with /dev/nanda' should still mean that recovery mode can be entered normally? |
| 20:21.30 | oliv3r | i really have to read up on the whole android thing. where the kernel resides, how partitions are laid out |
| 20:21.52 | RaYmAn | the kernel+ramdisk resides on the two boot.img partitions |
| 20:21.55 | RaYmAn | iirc nandc and nandg |
| 20:22.27 | RaYmAn | nanda is iirc more for boot0/boot1/spl usage? |
| 20:22.37 | oliv3r | i would assume so |
| 20:22.44 | oliv3r | it contains script.bin among other thigns |
| 20:23.04 | oliv3r | some drv_de.drv, font files, 'magic.bin' |
| 20:23.12 | oliv3r | boot.axf and sprite.axf, boot.ini |
| 20:23.17 | oliv3r | some dirs |
| 20:23.38 | oliv3r | linux/u-boot.bin (THE uboot?) |
| 20:23.49 | oliv3r | linux/some bitmaps, linux/linux.ini |
| 20:23.49 | RaYmAn | yeah |
| 20:24.01 | oliv3r | ok check this |
| 20:24.21 | oliv3r | /dev/block/nanda/linux/linux.ini -> img_name = c:\linux\u-boot.bin |
| 20:24.30 | oliv3r | also logo_name = c:\linux\linux.bmp |
| 20:24.35 | oliv3r | how funny is that |
| 20:24.44 | RaYmAn | yeah *rolls eyes* |
| 20:24.57 | RaYmAn | allwinner-isms |
| 20:25.06 | oliv3r | is this used by something else? or are they retranslating those \'s internally |
| 20:25.23 | RaYmAn | it's boot0/boot1 that uses those inits afaik |
| 20:25.39 | RaYmAn | It appears to just be symbolic naming, e.g. c: -> nanda |
| 20:26.17 | oliv3r | so boot0/boot1 does some magic to translate c:\linux\u-boot.bin to nanda\linux\u-boot.bin? |
| 20:26.52 | oliv3r | well i assume boot0/boot1 is some lowlvl C code, probably using very basic 'open()' or maybe fopen() functions. |
| 20:27.10 | oliv3r | i haven't programmed for ages in win32, but i think even there you supply either both, or unix slashes? |
| 20:27.25 | oliv3r | in any case, they have to actually code those translations? |
| 20:28.27 | *** join/#arm-netbook ZaEarl_ (~malmrose@202.155.242.30) |
| 20:28.58 | oliv3r | also, and thid does actually quite bafle me; there's more interesting images in nanda\os_show. a 'melis[12].bmp' probably THE original template for the firmware? and wince[12].bmp! |
| 20:29.14 | oliv3r | winCE out of all things! |
| 20:30.27 | mnemoc | techn: can't c99-style struct initialization be used instead of each fb_para.foo one by one? { .foo = 1, ... } will zero anything else. with fb_para.foo you can always miss something |
| 20:30.36 | *** join/#arm-netbook ZaEarl__ (~malmrose@202.155.242.30) |
| 20:31.04 | techn | mnemoc: true. |
| 20:31.43 | mnemoc | that way you can also omit all those fields happy been 0 |
| 20:34.55 | mnemoc | techn: but I can merge the fixed version, and wait for the cleanup next |
| 20:35.19 | techn | yep.. fix/cleanup will go to tomorrow |
| 20:35.56 | mnemoc | i mean. do i merge what I've got now, or wait? |
| 20:38.17 | techn | wait.. I'll fix that tomorrow :) |
| 20:38.28 | mnemoc | ok |
| 21:05.08 | oliv3r | assuming i'd use vanilla linux on the device (with sunxi support obviously) how 'free' am I in partitioning choice? I assume nanda is required (by uboot/boot[01]), but what about nandb? nandc? nandc is for the kernel yes? Does it always _have_ to live there? I want to write up a quick partitioning table on the wiki |
| 21:07.33 | mnemoc | depends on the u-boot *file* in nanda |
| 21:07.53 | mnemoc | by default it reads the env from a partition and the kernel from another |
| 21:08.22 | mnemoc | but you can change it's env to load the kernel from nanda too |
| 21:08.58 | mnemoc | for the env itself, not sure what relocation options you have |
| 21:09.02 | oliv3r | so if i build my own u-boot, that directly loads my kernel from somewhere (must be a partition?) I could thus have 1 big partition for the rest? |
| 21:09.15 | oliv3r | well still working on understanding the partitions i have here |
| 21:09.32 | oliv3r | i see bootloader, env, boot, system, misc, recovery, cache, databk, UDISK atm for example |
| 21:10.07 | mnemoc | I use the first block of http://linux-sunxi.org/User:Alejandro_Mery/Notes to make nanda's u-boot load my test kernel |
| 21:11.02 | oliv3r | bootloader is for uboot/boot[01] i gather, env? boot probably holds the kernel and ramdisk; system obviously androids /system, misc, no idea, recovery is obviously CWM/recovery part, cache androi'ds cache, databk, not sure, i guess /data though; and UDISK would be the internal mass storage |
| 21:11.23 | oliv3r | *reading* |
| 21:11.25 | oliv3r | oh short note list :p |
| 21:12.21 | mnemoc | boot0/boot1 live outside the logical nand space, you can't access them |
| 21:12.46 | mnemoc | nanda is the vfat boot partition where u-boot lives in file form |
| 21:13.02 | mnemoc | env is a raw partition dedicated to u-boot's env |
| 21:13.25 | mnemoc | iirc the kernel is raw in nandd, but don't remmeber |
| 21:13.40 | mnemoc | but that can be fixed changing some lines in u-boot's env |
| 21:13.50 | mnemoc | like on that "note" |
| 21:14.43 | Turl | misc is a partition to signal stuff to the boot chain |
| 21:14.53 | Turl | eg 'boot in recovery mode' or 'boot into fastboot mode' |
| 21:15.04 | oliv3r | yeah you told me a few times (sorry for asking so many questionns here!) but i ment boot0 data, e.g. battery1.bmp etc |
| 21:15.50 | oliv3r | u-boot.bin IS u-boot right? basically, if BROM is the 'bios', nanda/linux/u-boot.bin is the MBR (to relate it to the PC way of thinking) |
| 21:16.01 | hno | battery1.bmp is not used by boot0. It's used by boot.axf I think. |
| 21:16.09 | oliv3r | actually, i'd think BROM is somethiiing before the bios, and boot0/1 is the bios |
| 21:16.25 | hno | There is no BIOS as such. |
| 21:16.39 | oliv3r | nono, i know, i'm just trying to relate it to my knowledge on how pc boots |
| 21:17.17 | hno | BROM i the boot rom embedded in the CPU, which loads boot code from SD0/NAND/SD2/SPI and also does FEL USB mode. |
| 21:17.18 | oliv3r | i guess any PC chip has some form of BROM that starts to execute the bios; so the BROM in the A10 executes boot0/1 which in turn run u-boot.bin from nand aa |
| 21:17.35 | oliv3r | yeah :) I wrote the page! (on the wiki) :p |
| 21:18.12 | mnemoc | here a "bios" is chomped in different apps |
| 21:18.54 | mnemoc | brom, (boot0/boot1) or SPL, u-boot, and linux itself |
| 21:19.40 | oliv3r | so boot0/boot1 reads the config file from nanda, which tells it where the bootloader lives (c:\linux\u-boot.bin) and takes it from there |
| 21:19.50 | hno | BROM loads boot0 / u-boot-spl. boot0 / u-boot-spl configures DRAM etc and then loads boot1 / u-boot. In case of boot1 it then loads script.bin, configures more of the hardware and loads boot.axf. boot.axf then loads boot.cfg (or whatever it's name) which tells it to load u-boot.bin. |
| 21:19.52 | oliv3r | then u-boot reads data from nandb (env) |
| 21:20.43 | mnemoc | nanda's u-boot. yes |
| 21:20.59 | oliv3r | so where recides uboot-spl? |
| 21:21.01 | mnemoc | our u-boot reads that from before the first partiton |
| 21:21.15 | oliv3r | hno: boot.ini probalby |
| 21:21.21 | hno | u-boot-spl is the u-boot equivalence of boot0. |
| 21:21.22 | mnemoc | u-boot spl at 8*1024 of the mmc |
| 21:21.57 | oliv3r | ah duh, of course, i should have known that, partition-table, uboot-spl, partition0 with uboot in it |
| 21:21.59 | hno | we have two different boot loader chains depending on which bootloader you use. |
| 21:22.28 | oliv3r | i'll let that all sink in a little more, and maybe write a page on the wiki about the boot chains |
| 21:22.30 | hno | allwinner boot0/boot1 or u-boot-spl. |
| 21:22.44 | oliv3r | and right now, we can only boot u-boot-spl via SD |
| 21:22.56 | hno | yes. |
| 21:23.01 | oliv3r | got it |
| 21:23.42 | hno | and u-boot-spl also do not know as much about the PMU and possibly other parts as boot1, but is all free software with full source available. |
| 21:24.21 | oliv3r | yeah, mnemoc told me a while ago, uboot-spl isn't as far as boot0, but should get there in time |
| 21:24.47 | hno | it should be pretty up to spee with boot0, but not boot1. |
| 21:24.49 | mnemoc | it's very close these days |
| 21:25.16 | hno | have not cared about batteries yet. |
| 21:25.43 | hno | none of my devices have a battery. |
| 21:27.08 | oliv3r | so i get nanda (uboot.bin and datafiles for boot*etc), nandb (env for uboot), nandc (boot, holds the kernel + ramdisk) then, nandd (system which is 'android' or whatever you configure it as, followed by nande (misc, which turl explained above, not sure why there's a partition required for this and how this works at all yet) and then the rest |
| 21:27.16 | oliv3r | i'll wikify that info as best as i can |
| 21:27.32 | hno | Plesae do. |
| 21:28.34 | hno | Another note about A10 documentation. It is imho not OK to copy material from the A10 User Guide. It's a restricted document. |
| 21:28.47 | oliv3r | one more thing, i have a boot.img to be written directly into nandc, it starts however with ANDROID! as it's magic signature |
| 21:29.34 | hno | boot.img is an android thing. |
| 21:29.58 | hno | u-boot uses other image formats. |
| 21:30.05 | oliv3r | in this case, it's what gets dumped to nandc |
| 21:30.16 | hno | In an Android setup yes. |
| 21:30.29 | oliv3r | ah ok |
| 21:30.47 | hno | You can repartition the NAND as you please. |
| 21:31.33 | hno | and also load kernel + initrd as u-boot images from files. |
| 21:31.59 | oliv3r | well a lot of A10 hardware usualy ocmes pre-installed with android, so some notes on default partition layout can be usefull |
| 21:32.06 | hno | just remember to keep "boot" partition reasonably intact if using boot0/boot1. |
| 21:33.57 | hno | and a smallish "env" partition if using allwinner u-boot. Beyond that partition as you please. |
| 21:34.16 | oliv3r | makes sense |
| 21:34.31 | oliv3r | i'll write a minimal partitioning chapter with that info sometime tomorrow |
| 21:35.15 | oliv3r | hmm, somehow a letter got lost in the alphabet. i'll have to dig deeper into that :S |
| 21:35.37 | mnemoc | Android/Partitions ? |
| 21:35.51 | oliv3r | i know for a fact that nandg is the recovery partition on my device. i've written CWM to it several times. however dmesg shows 'The 5 disk name = recovery' which is nandf |
| 21:35.59 | oliv3r | ah, better idea |
| 21:37.39 | hno | idea? |
| 21:37.41 | markvandenborre | oliv3r: you may also want to talk to Dimitar Gmishev |
| 21:38.00 | markvandenborre | he has managed to get Debian running from nand on an a13 based board |
| 21:38.23 | oliv3r | Android/partitions for the wiki location :p |
| 21:39.05 | simosx | mnemoc, hno: I eventually used a standalone repo (the one from github given above) to compile mkbootimg. Thanks to both. |
| 21:39.19 | mnemoc | if you are going to talk about android/sunxi partiotions, yes |
| 21:39.39 | mnemoc | simosx: quarkx's? |
| 21:39.42 | oliv3r | mnemoc: did and done :) |
| 21:39.53 | mnemoc | :) |
| 21:41.26 | *** join/#arm-netbook tuliom (~tuliom@186.214.48.149) |
| 21:41.47 | simosx | mnemoc, this one, https://github.com/work4blue/unpack-mkbootimg |
| 21:42.48 | mnemoc | ok |
| 21:43.06 | oliv3r | great scots! i figured out why CWM and CM10 won't boot. I think somewhere, someone somehow swapped recovery and /data partitons, so my /data is only 15MiB! atleast i know what to fix now :D |
| 21:43.10 | hno | oliv3r, what does u-boot say? Mine says http://fpaste.org/3sSA/ |
| 21:44.07 | oliv3r | http://fpaste.org/1tPv |
| 21:44.10 | oliv3r | but taht's not from u-boot |
| 21:44.14 | oliv3r | that's from dmesg/kernel |
| 21:44.31 | hno | this one is from u-boot. |
| 21:44.58 | hno | but probably the same in dmesg. NAND driver is mostly the same in u-boot and kernel. |
| 21:45.31 | mnemoc | the filesystem can be smaller |
| 21:45.48 | hno | mnemoc, what? |
| 21:46.18 | mnemoc | in the android images they generate filesystem images of a given size |
| 21:46.22 | mnemoc | and then dump it |
| 21:46.25 | hno | yes. |
| 21:46.27 | mnemoc | ignoring the real partition size |
| 21:46.52 | mnemoc | as a result you can have a 16MB filesystem in a 2GB partition... |
| 21:47.05 | hno | not sure the data partition is included in images. But maybe it is. |
| 21:48.39 | Turl | oliv3r: did you device come with gingerbread on it? |
| 21:48.54 | Turl | oliv3r: I recall reading GB A10 devices had a different partition layout |
| 21:50.10 | oliv3r | it came with android 4.0.3 |
| 21:50.19 | oliv3r | and they have an update for android 4.0.4 (both livesuit images) |
| 21:50.37 | Turl | oliv3r: https://raw.github.com/allwinner-dev-team/android_device_allwinner_zatab/jellybean/recovery.fstab |
| 21:50.40 | oliv3r | but they changed something with the partitions, not only size, but also order |
| 21:50.59 | Turl | most A10 devices have that layout on the link there ^ |
| 21:51.05 | oliv3r | i'm installing 4.0.3 to make a quick dmesg dump of partitinos, then install 4.0.4 stock to do the same to compare |
| 21:51.17 | oliv3r | gimme 10 minutes and i'll give you a paste of both what i have :) |
| 21:51.26 | oliv3r | but they deffo changed the sizes |
| 22:04.06 | oliv3r | i'll fpaste it tomorrow :p |
| 22:04.10 | oliv3r | bed time now :) |
| 22:04.48 | mnemoc | hno: btw, my cubie still halts on spl on reboot. yours doesn't? |
| 22:08.08 | hno | Don't boot the cubie that often. Usually test stuff on the A13 via JTAG. |
| 22:08.49 | hno | does it also halt on reboot from u-boot? Or only from kernel? |
| 22:10.19 | hno | oliv3r, remember to select to format the flash. If not existing partitioning layout is kept which may give unexpected results. |
| 22:10.50 | hno | mnemoc, does it print the SPL header and then silently dies? |
| 22:11.10 | mnemoc | it used to die on MMC: |
| 22:11.17 | mnemoc | now it's after the greeting |
| 22:11.28 | mnemoc | i suppose still on the same place |
| 22:11.38 | mnemoc | just that boot device detection code changed |
| 22:12.02 | hno | Many small things changed. Now the greeting is very early, even before DRAM. |
| 22:13.00 | hno | How reproducible is it? |
| 22:13.21 | mnemoc | 100% |
| 22:13.29 | mnemoc | in the mele it's like 50% |
| 22:13.32 | hno | every time you reboot? |
| 22:13.35 | mnemoc | yes |
| 22:14.05 | hno | Same SD card in both? |
| 22:14.34 | mnemoc | no, one SD per device, one ttl/usb dongle per device |
| 22:16.30 | hno | Hm. You don't get MMC: now? |
| 22:16.52 | Turl | fuu, forgot to merge next_mali when building with cpufreq for zatab :P |
| 22:17.09 | mnemoc | hno: only: U-Boot SPL 2012.10-rc3-04244-gfa4a874-dirty (Oct 13 2012 - 16:47:06) |
| 22:17.37 | mnemoc | Turl: does next_mali work well in android? |
| 22:17.55 | Turl | mnemoc: yeah, I've been using it since I created the branch :x |
| 22:18.03 | mnemoc | :) |
| 22:18.56 | Turl | that's like 2 months ago *hint* :P |
| 22:19.07 | mnemoc | Turl: not my call |
| 22:19.28 | Turl | techn: what's holding next_mali from merging? |
| 22:20.06 | hno | Hm... odd, I don't get MMC: either. |
| 22:20.47 | Turl | hm, wtf |
| 22:21.01 | Turl | it still doesn't work and on boot the screen does all weird glitches |
| 22:21.10 | Turl | with the uboot(?) splash |
| 22:21.27 | hno | mnemoc, so yes, it's most likely dying at the same place as before. Just different output. |
| 22:21.52 | hno | hadn't noticed the MMC: output is removed in rc3. |
| 22:22.53 | mnemoc | good thing is that same happens (not 100% but often) on the mele too. so jtag could be used ;-) |
| 22:23.28 | Turl | nevermind, I suck |
| 22:23.35 | Turl | I pushed the kernel and not the modules ~.~ |
| 22:23.41 | mnemoc | Turl: :) |
| 22:23.58 | mnemoc | make an script to do so for you. write once, works always |
| 22:25.02 | Turl | there, it works |
| 22:25.10 | Turl | it still does the fugly glitches though |
| 22:25.13 | Turl | wonder what's causing those |
| 22:25.21 | Turl | they weren't there before |
| 22:27.51 | Turl | hno: the cpufreq stuff is on my github if you want to test/review before I send it to the ML |
| 22:28.49 | Turl | I need to clean up the patches and organize it better, and I noticed I commited a defconfig by mistake too together with some other stuff |
| 22:35.50 | hno | mnemoc, try enabling SUNXI_MMCDBG in drivers/mmc/sunxi_mmc. |
| 22:35.53 | hno | .c |
| 22:38.22 | mnemoc | http://dpaste.com/813681/ <--- first boot |
| 22:39.11 | hno | mnemoc, isn't that from u-boot and not spl? |
| 22:39.46 | mnemoc | oops |
| 22:40.12 | hno | Should be mostly the same, but... |
| 22:40.18 | mnemoc | http://dpaste.com/813683/ <--- spl, first boot |
| 22:40.39 | *** join/#arm-netbook mysteryname (~mysteryna@14-202-9-167.tpgi.com.au) |
| 22:41.12 | *** join/#arm-netbook ZaEarl_ (~malmrose@202.155.242.30) |
| 22:44.28 | *** join/#arm-netbook ibrah (~chatzilla@212.49.88.98) |
| 22:44.54 | mnemoc | hno: and early death on reboot |
| 22:45.00 | mnemoc | U-Boot SPL 2012.10-rc3-04245-g77f7322-dirty (Oct 15 2012 - 00:36:44) |
| 22:45.00 | mnemoc | [mmc]: init mmc 0 resource |
| 22:46.14 | mnemoc | but i have to go to take a nap know. good night |
| 22:53.11 | *** join/#arm-netbook ZaEarl_ (~malmrose@202.155.242.30) |
| 22:57.14 | hno | mnemoc, that's odd. There is no I/O until after "init mmc 0 clock and io". Only preparation of data structures. |
| 23:04.39 | hno | But hmm... that data is in DRAM not SRAM. Wonder if that's a good idea. |
| 23:05.06 | *** join/#arm-netbook itamarjp (~itamar@189-015-124-078.xd-dynamic.ctbcnetsuper.com.br) |
| 23:05.06 | *** join/#arm-netbook itamarjp (~itamar@fedora/itamarjp) |
| 23:37.56 | Turl | https://plus.google.com/u/0/+Linux/posts/iBvjvyovDCA arm multiplatform on rc1 :) |
| 23:38.57 | *** join/#arm-netbook bsdfox (~Bob@c-71-197-83-152.hsd1.ca.comcast.net) |
| 23:38.57 | *** join/#arm-netbook bsdfox (~Bob@unaffiliated/bsdfox) |