Re: [linux-sunxi] linux-sunxi/u-boot-sunxi is no longer supported, time to switch to upstream u-boot
Hi, On 10-01-15 21:38, Jens Thiele wrote: Hans de Goede hdego...@redhat.com writes: [...] Note that when used with a 3.19 kernel + this patch: https://github.com/jwrdegoede/linux-sunxi/commit/d1b7faa5c69ef1ad52b739aa88cd803e08955360 This will also give you video out support while using an upstream kernel. just tested - and it works :-) what's missing: - touchscreen doesn't work (not sure why) Likely because the upstream kernel does not yet have a driver for it. - dpms / switch lcd off (seems like this is expected with simplefb) Correct, this is expected with simplefb. Regards, Hans -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] Inet K970,A20,linux-sunxi -- nand driver kernel panic
Hi everyone,
the boot log shows a very unhappy nand driver.
--
[0.682894] Division by zero in kernel.
[0.689714] [c001540c] (unwind_backtrace+0x0/0x12c) from [c03d41f8]
(Ldiv0+0x8/0x10)
[0.696123] [c03d41f8] (Ldiv0+0x8/0x10) from [c047351c]
(get_cmu_clk+0x30/0x40)
[0.703360] [c047351c] (get_cmu_clk+0x30/0x40) from [c047354c]
(set_nand_clock+0x20/0x80)
[0.710497] [c047354c] (set_nand_clock+0x20/0x80) from [c09b2bb4]
(nand_init+0x68/0x1c4)
[0.717906] [c09b2bb4] (nand_init+0x68/0x1c4) from [c0008698]
(do_one_initcall+0x114/0x16c)
[0.725577] [c0008698] (do_one_initcall+0x114/0x16c) from [c09979f8]
(kernel_init+0x190/0x228)
[0.733160] [c09979f8] (kernel_init+0x190/0x228) from [c000f7ec]
(kernel_thread_exit+0x0/0x8)
[0.736507] [NAND] nand driver version: 0x2 0x9
[0.742146] [SCAN_ERR] search nand physical architecture parameter failed!
[0.744506] [NAND]init_blklayer fail
--
Apparently, this happens in drivers/block/sunxi_nand/nfd/nand_blk.c:1107
--
#ifndef USE_SYS_CLK
__u32 get_cmu_clk(void)
{
__u32 reg_val;
__u32 div_p, factor_n;
__u32 factor_k, factor_m;
__u32 clock;
reg_val = *(volatile unsigned int *)(0xf1c2 + 0x20);
div_p= (reg_val 16) 0x3;
factor_n = (reg_val 8) 0x1f;
factor_k = ((reg_val 4) 0x3) + 1;
factor_m = ((reg_val 0) 0x3) + 1;
clock = 24 * factor_n * factor_k/div_p/factor_m;
return clock;
}
--
From this code, since factor_m 0, it is div_p being zero.
The related Android log lines are:
--
4[1.651812] nand_init,line:1400
4[1.651837] [NAND]nand driver, init.
4[1.651852] [NAND] nand driver(A20) version: 0x2, 0x12, data: 20130627
1522
4[1.651863] [NAND] nand clk request start
4[1.651898] [NAND] nand clk request ok!
4[1.651999] [NAND DMA] request dma success
4[1.652011] [NAND DMA] set fulldone_cb success
4[1.652410] nand interrupt register ok
4[1.652426] [NAND] get nand_good_block_ratio from script: 870
4[1.652506] [NAND DMA] start dma*
--
Since the driver mentions explicitly '(A20)', I might be running
an unsuited driver. Is this a known A20 issue or particular to
my installation? Instead using CONFIG_NAND, should I better
give CONFIG_NAND_TEST a shot?
The A20 handbook does not mention the register, but
./arch/arm/plat-sunxi/include/plat/platform.h:182 has a
#define SW_VA_CCM_IO_BASE 0xf1c2,
and finally relates to CCM_PLL5_CFG this via
http://linux-sunxi.org/Clock_Control_Module#Timer_Registers
where it is cited as being A10 material.
But even if it is A10-only material, something appears to be fishy
either the code or the wiki page:
| CCM_PLL5_P 16:17 Read/Write 0x00
|0x00 = 1
|0x01 = 2
|0x02 = 3
|0x03 = 4
| PLL5 external factor P
Here, 0x00 is perfectly legal and the above code should read IMO
|div_p= ((reg_val 16) 0x3) + 1;
But perhaps I'm reading this wrong.
Kind regards,
Lars
--
You received this message because you are subscribed to the Google Groups
linux-sunxi group.
To unsubscribe from this group and stop receiving emails from it, send an email
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Inet K970,A20,linux-sunxi -- nand driver kernel panic
On Sun, 2015-01-11 at 12:55 +0100, Lars Doelle wrote:
Hi everyone,
the boot log shows a very unhappy nand driver.
What kernel version?
--
[0.682894] Division by zero in kernel.
[0.689714] [c001540c] (unwind_backtrace+0x0/0x12c) from
[c03d41f8] (Ldiv0+0x8/0x10)
[0.696123] [c03d41f8] (Ldiv0+0x8/0x10) from [c047351c]
(get_cmu_clk+0x30/0x40)
[0.703360] [c047351c] (get_cmu_clk+0x30/0x40) from
[c047354c] (set_nand_clock+0x20/0x80)
[0.710497] [c047354c] (set_nand_clock+0x20/0x80) from
[c09b2bb4] (nand_init+0x68/0x1c4)
[0.717906] [c09b2bb4] (nand_init+0x68/0x1c4) from [c0008698]
(do_one_initcall+0x114/0x16c)
[0.725577] [c0008698] (do_one_initcall+0x114/0x16c) from
[c09979f8] (kernel_init+0x190/0x228)
[0.733160] [c09979f8] (kernel_init+0x190/0x228) from
[c000f7ec] (kernel_thread_exit+0x0/0x8)
[0.736507] [NAND] nand driver version: 0x2 0x9
[0.742146] [SCAN_ERR] search nand physical architecture
parameter failed!
[0.744506] [NAND]init_blklayer fail
--
Apparently, this happens in
drivers/block/sunxi_nand/nfd/nand_blk.c:1107
--
#ifndef USE_SYS_CLK
__u32 get_cmu_clk(void)
{
__u32 reg_val;
__u32 div_p, factor_n;
__u32 factor_k, factor_m;
__u32 clock;
reg_val = *(volatile unsigned int *)(0xf1c2 + 0x20);
div_p= (reg_val 16) 0x3;
factor_n = (reg_val 8) 0x1f;
factor_k = ((reg_val 4) 0x3) + 1;
factor_m = ((reg_val 0) 0x3) + 1;
clock = 24 * factor_n * factor_k/div_p/factor_m;
return clock;
}
--
From this code, since factor_m 0, it is div_p being zero.
The related Android log lines are:
--
4[1.651812] nand_init,line:1400
4[1.651837] [NAND]nand driver, init.
4[1.651852] [NAND] nand driver(A20) version: 0x2, 0x12, data:
20130627 1522
4[1.651863] [NAND] nand clk request start
4[1.651898] [NAND] nand clk request ok!
4[1.651999] [NAND DMA] request dma success
4[1.652011] [NAND DMA] set fulldone_cb success
4[1.652410] nand interrupt register ok
4[1.652426] [NAND] get nand_good_block_ratio from script: 870
4[1.652506] [NAND DMA] start
dma*
--
Since the driver mentions explicitly '(A20)', I might be running an
unsuited driver. Is this a known A20 issue or particular to my
installation? Instead using CONFIG_NAND, should I better
give CONFIG_NAND_TEST a shot?
The A20 handbook does not mention the register, but
./arch/arm/plat-sunxi/include/plat/platform.h:182 has a
#define SW_VA_CCM_IO_BASE 0xf1c2,
and finally relates to CCM_PLL5_CFG this via
http://linux-sunxi.org/Clock_Control_Module#Timer_Registers
where it is cited as being A10 material.
But even if it is A10-only material, something appears to be fishy
either the code or the wiki page:
CCM_PLL5_P 16:17 Read/Write 0x00
0x00 = 1
0x01 = 2
0x02 = 3
0x03 = 4
PLL5 external factor P
Here, 0x00 is perfectly legal and the above code should read IMO
div_p= ((reg_val 16) 0x3) + 1;
But perhaps I'm reading this wrong.
Kind regards,
Lars
--
You received this message because you are subscribed to the Google Groups
linux-sunxi group.
To unsubscribe from this group and stop receiving emails from it, send an email
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] [PATCH] Mainline U-boot -- Tristan Auron Planet 1 tablet
On Sat, Jan 10, 2015 at 05:02:58PM +0100, Lars Doelle wrote: Hi Luc, thank you for reviewing the device description so throughout. I'll work through your comments doing my best to make the description confirm to your standards. This is an Inet K970??, and like all inet devices this is very often rebadged. Referring to some of your notes [[Inet K970]]: As described in the wiki page, please fire up android, and find out the last 1-2 letters, which usually are tied to a given display size and wifi module, and use this name everywhere instead. I broke the Android partition while probing ft5x_ts prior starting the device description, so I could not report the Android's bits anymore. Meanwhile I restored the image. Anyway, if you mean the 'Build number', its in the wiki page now, saying: A20_K9701_K9701L2B_1210239.20121030 Otherwise I'm not clear, to what you might refer to by last 1-2 letters. Ok, let's keep the name at K970 for now, perhaps no other K970 devices will turn up. The K970 can be found on aliexpress though. Another point you notices, is the Wifi part. If possible, please reread what i wrote there: 1) The first link is IMO a proper reference to the relevant Wifi section. Yes and no. The way i changed it makes it conform to the other devices, and, it is more future proof, meaning that you will not have to go revisit when the wifi page changes, or the status of this driver changes. 2) The second link refers to a patch making the third USB-head going, to which the RTL8723AU, which is USB-device is connected. So it was not in the fex. If I did something wrong activating it this way, I like know about it. Nobody has so far gone and created a bluetooth page. For the OTG, state is as described. W.r.t. OTG the only note on the [[USB]] page is: On an Hackberry and A20-based tablet (with a single OTG USB port) the main sunxi-3.4 branch kernel (as of 22 Nov 2013) with default defconfig settings also seems to leave USB devices without power. This can be fixed by enabling the Inventra Highspeed Dual Role Controller in Device Drivers - USB Support and selecting the Allwinner Platform Glue option. By saying This is standard A20 stuff. Move to the USB page., do you mean I should not use this options? Otherwise I could file a proper report of the state. Yes, this is specific to the A20 SoC. All A20 based devices have OTG issues as the A20 - sunxi codebase otg port was not complete. For the last points, uart and pictures, this basically a matter of equipment. As this is the first time for me dealing with small electronics and I to check whether my probes and soldering stuff are sharp enough for this purpose. Contrary to the other Inet board pictures in the wiki, i could not locate any writings on the board indicating the uart on the first examination. Thus almost certainly, I'll have to probe them. Get a good board picture. The picture of the board on the inet site very clearly shows the uart pins. Most of the pictures have been taken free-hand though with some support with the flash deactivated causing them to become blurry. I'm looking to get a tripod, perhaps this will do better. For the same reason, I did not yet publish a detailed picture of the board and its chips. Try multiple passes for focussing correctly, and try supporting your elbows. Thanks for sticking with this. This could be another solidly supported and properly documented device. Luc Verhaegen. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] HDMI Module on the A80
One thing to note is that when writing on 0x03d0 the values do not change - so perhaps it is half alive'? When I play with 0x060005a8 (AHB2 module reset control) I switch between seeing zeros or the strange values: 03d0: 13131313 bfbfbfbf 03d00010: [zeros from here and on..] in* both cases I cannot write* on this module (unlike the debe for example). besides that I turned on all the gate and reset registers and nothing changes at 0x03d0 or 0x0300.. Raanan On Wednesday, January 7, 2015 at 3:34:13 PM UTC+2, RFat wrote: Hi Hans, Thanks for the suggestion. I believe that if indeed the HDMI module is located at 0x03d0 then it belongs to the AHB2. I did play with its gate and reset registers and indeed the BE1 and LCD1 appear and disappear and so also the very few values in 0x03d0: 03d0: 13131313 bfbfbfbf 03d00010: [zeros from here and on..] As I said, setting 03d0 or 03d4 to zero does not affect the HDMI transmission in u-boot (which shows an allwinner logo). These values do not make any sense, do they? I did another search in the memory of 0x0300 till 0x03ff looking for hdmi-ish values (such as 1079 and 1919) and could not find them, as if the HDMI module is not there (however, being at this address range is the most sensible place since I think it should belong to AHB2 like the rest of the display modules). You mentioned adb / adp which ones are those? BTW: I checked the options of ahb0 that Vladimir suggested and searched for the module at 0x01c16000 but this is all zeros. This used to be the address in the A20 and there seem to be many changes since. The A80 memory map describe this address as TS Config registers http://linux-sunxi.org/index.php?title=A10/TSaction=editredlink=1 Transport Stream controller (DVB) which is not hdmi as far as I understand. Why the heck this is so hidden in this soc... Thanks Raanan On Monday, January 5, 2015 10:50:10 AM UTC+2, Hans de Goede wrote: Hi, On 05-01-15 09:19, RFat wrote: Thanks for the reply, but I can't see how that can be the case since this address range is filled with zeros when the hdmi is active (both in case of the ubuntu and the u-boot - I am reading these physical addresses). Any other idea? The registers no longer need to be accessed after setting up the hdmi encoder, so chances are that the adb / adp gate for the hdmi controller is closed, causing all reads to return 0. First ensure all the clk gates, and resets, etc. are set up properly before trying to dump the hdmi encoder registers. Regards, Hans -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Inet K970,A20,linux-sunxi -- nand driver kernel panic
On Sunday, January 11, 2015 14:59:24 Siarhei Siamashka wrote: To workaround problems in older sunxi-3.4 kernels, [...] Hmm, sorry that I still have to sort myself. I was using the 'sunxi-3.4' branch, which is flagged being 'PREFERED' in the [[Linux_Kernel]]. The patch you're referring me to appears to be in branch 'stage/sunxi-3.4', not mentioned in the wiki. To avoid bringing up obsolete issues, is that the branch should I use when working with 'current' linux-sunxi? Kind regards, Lars -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] [PATCH] Mainline U-boot -- Tristan Auron Planet 1 tablet - ( bluetooth )
- Original Message - From: Lars Doelle lars.doe...@on-line.de Sent: Saturday, 10 January 2015, 18:03 Subject: Re: [linux-sunxi] [PATCH] Mainline U-boot -- Tristan Auron Planet 1 tablet Getting bluetooth more properly going is on my list, and I'll gladly put my findings on the wiki. Bluetooth (AP6210) is also on my list (but it's a long list). A few links I have bookmarked if they are any help to you: 3.4 kernel: - http://linux-sunxi.org/Cubietruck/Bluetooth - http://archlinuxarm.org/forum/viewtopic.php?f=33t=7253 - Got bluetooth working on Cubietruck - proof of concept Mainline: - http://linux-sunxi.org/User_talk:Sehraf - Sehraf did some research a few months ago, conclusion was a problem with the set up of the clock -https://github.com/wens/linux/commit/b3df2aa9dfb48d58ee590c9686dfc0e3946de5fc - ARM: dts: sun7i: add bluetooth module to CubieTruck DTS Regards, Al -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] Disable Console on UART (A20 - Sunchip_SDK-758)
Hello, Like to know how can I disable the UART port on the island, leaving free for other use. My Device - http://linux-sunxi.org/Sunchip_SDK-758 I've done the adjustment in .FEX and UEnv.txt but the console is always linked to UART port (PB22, PB23) My Script.fex [uart_para0] uart_used = 0 uart_port = 0 uart_type = 2 uart_tx = port:PB2221defaultdefault uart_rx = port:PB2321defaultdefault [uart_para1] uart_used = 1 uart_port = 1 uart_type = 2 uart_tx = port:PB2221defaultdefault uart_rx = port:PB2321defaultdefault My UEnv.txt removed the lines related to console -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] U-Boot 2015 by jwrdegoede Erro compile
Hi, On 11-01-15 19:58, Ezaul Zillmer wrote: [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote origin] url = https://github.com/jwrdegoede/u-boot-sunxi.git fetch = +refs/heads/*:refs/remotes/origin/* [branch sunxi-wip] remote = origin merge = refs/heads/sunxi-wip make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- Cubieboard2_config make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- CC drivers/spi/spi.o LD drivers/spi/built-in.o LD drivers/usb/eth/built-in.o LD drivers/usb/gadget/built-in.o CC drivers/usb/host/ehci-hcd.o drivers/usb/host/ehci-hcd.c: Na função ‘submit_int_msg’: drivers/usb/host/ehci-hcd.c:1401:2: erro: too few arguments to function ‘create_int_queue’ drivers/usb/host/ehci-hcd.c:1150:1: nota: declarado aqui make[1]: ** [drivers/usb/host/ehci-hcd.o] Erro 1 make: ** [drivers/usb/host] Erro 2 Thanks for the report, I've just done a forced push fixing this, please updare your checkout. Regards, Hans -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] U-Boot 2015 by jwrdegoede Erro compile
[core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote origin] url = https://github.com/jwrdegoede/u-boot-sunxi.git fetch = +refs/heads/*:refs/remotes/origin/* [branch sunxi-wip] remote = origin merge = refs/heads/sunxi-wip make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- Cubieboard2_config make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- CC drivers/spi/spi.o LD drivers/spi/built-in.o LD drivers/usb/eth/built-in.o LD drivers/usb/gadget/built-in.o CC drivers/usb/host/ehci-hcd.o drivers/usb/host/ehci-hcd.c: Na função ‘submit_int_msg’: drivers/usb/host/ehci-hcd.c:1401:2: erro: too few arguments to function ‘create_int_queue’ drivers/usb/host/ehci-hcd.c:1150:1: nota: declarado aqui make[1]: ** [drivers/usb/host/ehci-hcd.o] Erro 1 make: ** [drivers/usb/host] Erro 2 -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
A20-OLinuXino-MICRO + A13-LCD10TS and mainline kernel (Was: Re: [linux-sunxi] linux-sunxi/u-boot-sunxi is no longer supported, time to switch to upstream u-boot)
Hans de Goede hdego...@redhat.com writes: On 10-01-15 21:38, Jens Thiele wrote: what's missing: - touchscreen doesn't work (not sure why) Likely because the upstream kernel does not yet have a driver for it. thought it is sun4i-ts and that it is already in mainline, but will have to take a look... greetings, jens -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] Re: Infrared Remote Control (sunxi-ir)
Hello, I remember the code in 3.4. Authors do decoding manually instead of using kernel decoders. I think it is possible to use them. I've made some effort to push sunxi ir driver into mainline linux kernel, here is the main file: https://github.com/torvalds/linux/blob/master/drivers/media/rc/sunxi-cir.c. I think it is possible to backport the changes, but I am outside of my country for 3 mounts. Best, Alexander Bersenev суббота, 10 января 2015 г., 7:12:32 UTC+5 пользователь tkg написал: I think the current sunxi-ir driver only decodes the NEC protocol. In my case I have one of the dual core android tv player device similar to: http://linux-sunxi.org/YBKJ_A20 I have made a debian linux sd card using the 3.4 sunxi kernel and I had success reading the original remote that came with the box and also various cheap remotes usually found in car players. See for instance the remote from here: http://docs.cubieboard.org/tutorials/cb1/customization/wireless_music_box If the driver is loaded properly you should be able to find an eventX link for it in /dev/input/eventX where X varies but it should be similar to what you had in the dmesg log. A simple test to see if you have any keys recognized you could run: cat /dev/input/eventX | hexdump and start pressing keys from your remote. If you do not get any output then either your remote is not using the NEC protocol or the decoder might be listening on the wrong pins. I saw you have ir0_rx = port:PB042defaultdefaultdefault in your script.fex file but have you actually converted that file to a binary one and made it available so that the U-boot loader can load it? Again, in my case, I needed the script.bin file generated for my debian build as mentioned in here: http://linux-sunxi.org/Manual_build_howto All the best, tkg -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] A31s chipset support
Hi Siarhei, On Wed, Dec 31, 2014 at 11:39 AM, Siarhei Siamashka siarhei.siamas...@gmail.com wrote: On Mon, 3 Nov 2014 09:52:03 +1100 Julian Calaby julian.cal...@gmail.com wrote: Hi All, On Mon, Sep 29, 2014 at 3:23 PM, Siarhei Siamashka siarhei.siamas...@gmail.com wrote: On Thu, 18 Sep 2014 09:36:55 +1000 Julian Calaby julian.cal...@gmail.com wrote: Hi, Earlier this year, HP released the following three tablets: (Australian store links due to the specifications listing the SoC's name) HP 7 Plus: http://h20386.www2.hp.com/AustraliaStore/Product.aspx?pdetail=P333853 HP 8: http://h20386.www2.hp.com/AustraliaStore/Product.aspx?pdetail=P327832 HP 10 Plus: http://h20386.www2.hp.com/AustraliaStore/Product.aspx?pdetail=P339093 All of which appear to be based around the A31s SoC. As they're pretty cheap for a big name brand's tablets, I'm planning to obtain one. Has anyone else laid hands on any A31s devices yet? And if so, has any work started on supporting them? I bought a 7 Plus over the weekend, and apart from dismal battery life it's a significant improvement on my crappy A10 tablet (iNet 3FBT in a Kogan Agora) The Android install on it feels just like my partner's Asus TF300. The battery life is not great in my A31s based MSI Primo81 tablet, but not bad either. It can stay idle for many days on a single battery charge, and lasts enough hours (have not measured it, but maybe more than 6?) when it is actively used. Watch for WLAN power consumption, maybe try to disable it altogether to see if the battery life improves significantly. The excessive waste of power may be a purely software issue. I believe the poor battery life is due to it being an ex-demonstrator (which is part of why I bought it, _very_ cheap for retail.) Given that it's only connectivity option is WiFi and 90% of what I do on my tablet requires internet, disabling WiFi isn't really an option. It appears to be a disguised version of Allwinner's 4.2.2 (Jellybean) Android version as there's a couple of little details that remind me of my A10 tablet: The most obvious is the notifications for plugging, mounting and removing USB devices or microSD cards are very basic. More subtle is that if you hold either of them diagonally by one of their top corners, angled 45 degrees away from you, they do something weird: the Agora can't figure out it's orientation, the 7 Plus emits a long string of key presses that confuse Google Play Store. Well, discussing the usability of the stock Android firmware is not the primary topic of interest in this mailing list ;-) But thanks for sharing your experience. I made these points more to describe the quirks of the stock Android as it shares a lot of them with Android on my other tablet which is definitely Allwinner's version. Another little quirk is that the WiFi is inconsistently called WLAN or WiFi. Processor: QuadCore-A7 Model Number: HP 7 Plus Android Version: 4.2.2 Kernel Version: 3.3.0 zhangaiguo@SzExdroid10 #44 Tue Mar 25 14:15:51 CST 2014 Build Number: 1.1.5_WW-ILEX-13 Shockingly, it can mount thumb drives connected through an OTG cable to the micro-USB port. This is pretty normal and expected from any hardware. In my limited experience, this is the first Android device I've come across that has OTG support out of the box. My A10 tablet has a dedicated host port, my phone has hardware OTG support, but it's disabled in all but the latest custom ROMs and my partner's tablet lacks a micro-USB port. Frustratingly, it can't decide if the volume down button is a back button or not. It's also not pre-rooted. My MSI Primo81 was also not pre-rooted. And it took a bit of effort to search various Android community forums for a working method to root it. If you'd be so kind as to share which method you used and where you got it, I'd be most grateful. Every method I've tried has failed to the point where I'm thinking about whether it's possible to make a tool that roots devices using FEL / FES mode. I also have started considering to get an Allwinner based tablet since a couple of weeks ago. So far all my devices are just various development boards and one Mele TV box, which is not very different from a development board in terms of features. The first attempt was a failure. I tried to buy a relatively cheap 10 no-name tablet (but with HDMI and 1GB of RAM), which was advertised as Allwinner A20 by the seller. But it turned out to be in fact using an Actions ATM7029B SoC with a quad-core Cortex-A5 CPU (disguised as Leopard Gen.I CPU core). Big disappointment! And a total loss of trust in this method of obtaining hardware. Though even if the SoC was the right one, the build quality leaves a lot to be desired and the screen is just horrible (colors and viewing angles). Maybe other people had better experience, but I'm not going this route again. So now I'm also trying the big name
Re: [linux-sunxi] Re: [PATCH v2 01/11] clk: sunxi: Add mod0 and mmc module clock support for A80
On Mon, Jan 12, 2015 at 10:39 AM, Chen-Yu Tsai w...@csie.org wrote: On Thu, Jan 8, 2015 at 5:38 PM, Maxime Ripard maxime.rip...@free-electrons.com wrote: On Sat, Dec 20, 2014 at 08:43:27PM +0800, Chen-Yu Tsai wrote: That looks a lot like the A10 MMC clock. What's changing? only the data to feed to the factors setup code? That's correct. Only the mux width in the data fed to the setup code and the lock differ. The hardware can work with the a10 mod0 code, but it won't recover from cases where someone writes to the upper bits of the mux, since it doesn't know about them. I'd very much prefer if we could factorise that code then. I was hoping to not have to extend sunxi-factors-clk any more. But yes, I can add mux_width and mux_table fields to factors_data. OK. This was not what I meant to say at all. I've generalized sun4i_a10_mmc_setup() in the next version. ChenYu -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: A20-OLinuXino-MICRO + A13-LCD10TS and mainline kernel (Was: Re: [linux-sunxi] linux-sunxi/u-boot-sunxi is no longer supported, time to switch to upstream u-boot)
I am also trying to get the touchscreen working (olimex 4.3 Inch display works fine, thanks!) I tried using the driver in the mainline kernel which I suppose was posted first here: https://groups.google.com/forum/#!topic/linux-sunxi/DzcsAsvmrcM Any reason why this should not work (Olimex A20-Micro for me)? Thanks, Jens Am Sonntag, 11. Januar 2015 21:26:23 UTC+1 schrieb Jens Thiele: Hans de Goede hdeg...@redhat.com javascript: writes: On 10-01-15 21:38, Jens Thiele wrote: what's missing: - touchscreen doesn't work (not sure why) Likely because the upstream kernel does not yet have a driver for it. thought it is sun4i-ts and that it is already in mainline, but will have to take a look... greetings, jens -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: [PATCH v2 01/11] clk: sunxi: Add mod0 and mmc module clock support for A80
On Thu, Jan 8, 2015 at 5:38 PM, Maxime Ripard maxime.rip...@free-electrons.com wrote: On Sat, Dec 20, 2014 at 08:43:27PM +0800, Chen-Yu Tsai wrote: That looks a lot like the A10 MMC clock. What's changing? only the data to feed to the factors setup code? That's correct. Only the mux width in the data fed to the setup code and the lock differ. The hardware can work with the a10 mod0 code, but it won't recover from cases where someone writes to the upper bits of the mux, since it doesn't know about them. I'd very much prefer if we could factorise that code then. I was hoping to not have to extend sunxi-factors-clk any more. But yes, I can add mux_width and mux_table fields to factors_data. ChenYu -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
