[linux-sunxi] Re: A10 versus A20 , gtkperf result.
On Sunday, March 23, 2014 1:33:15 PM UTC-4, Rajesh Mallah wrote: > > Hi , > > I use gtkperf to get an idea of 2D graphics performance. > > the A20 based Mele M3 completes in 19secs > the A10 based Cubieboard1 completes in 32 secs. > > both using fbturbo xorg driver . > > Is that much difference expected or does it needs to > be _further_ investigated ? please lemme know. > > Regds > mallah. > > You haven't provided nearly enough information for anyone to possibly comment on the results. What versions of the kernel did you use? What linux disto? What (if any) Mali version? Did you use the A20 Mali driver that supports the MP2? What CPU clock speeds? What DRAM clock speeds? What MBUS clock speeds? Did you run gl2mark? -- 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 3.4] sunxi:axp20x: Enable internal thermal monitoring
On Sunday, March 16, 2014 12:22:58 PM UTC-4, Alejandro Mery wrote: > > Hi, > > On 11/03/14 05:31, Patrick Wood wrote: > > > > > > On Sunday, March 9, 2014 10:13:08 AM UTC-4, Alejandro Mery wrote: > > > > > > > > On 09/03/14 13:09, Olliver Schinagl wrote: > > > Mnemoc, > > > > > > have you checked and merged this yet? > > > > thanks for the reminder. it fails to compile when hwmon is m > > > > like on sun7i_defconfig: > > LD .tmp_vmlinux1 > > drivers/built-in.o: In function `axp20_init_chip': > > > /srv/build/amery/allwinner/linux-sunxi/3.4/drivers/power/axp_power/axp20-mfd.h:149: > > > > > > undefined reference to `hwmon_device_register' > > drivers/built-in.o: In function `axp_mfd_remove': > > > /srv/build/amery/allwinner/linux-sunxi/3.4/drivers/power/axp_power/axp-mfd.c:368: > > > > > > undefined reference to `hwmon_device_unregister' > > make[1]: *** [.tmp_vmlinux1] Error 1 > > make: *** [sub-make] Error 2 > > > > build_sun7i/.config:CONFIG_AXP_HWMON=y > > build_sun7i/.config:CONFIG_HWMON=m > > > > in most defconfigs hwmon is n, should I y/y them on all defconfigs? > can > > it be fixed to support hwmon=m? > > > > > > Try this: > > > > diff --git a/drivers/power/axp_power/Kconfig > > b/drivers/power/axp_power/Kconfig > > index 66aa6ac..4e942a9 100644 > > --- a/drivers/power/axp_power/Kconfig > > +++ b/drivers/power/axp_power/Kconfig > > @@ -38,7 +38,7 @@ config AXP_CHGCHANGE > > config AXP_HWMON > > depends on HWMON > > - bool "Enable the internal thermal monitoring support of AXP20X > > chips" > > + tristate "Enable the internal thermal monitoring support of > > AXP20X chips" > > default y > > endif # !AW_AXP > > yes, that solved the problem. what about defconfig? m/m? y/y? > > regards, > Alejandro Mery > Well, my preference is y/y, but I don't know if anyone else feels that way. Pat -- 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: How to boot from onboard eMMC ?
Did you search for emmc in linux-sunxi? When I did, many topics popped up. On Sunday, March 16, 2014 1:24:52 AM UTC-4, rova wrote: > > Hi, > I have a board(A20) with an onboard eMMC. Booting from external SD is > successful. The onboard eMMC can be found as mmcblk0, i can't boot from the > eMMC. > I have tried to modify the board.c(add #define CONFIG_MMC_SUNXI_SLOT 2), > compile the u-boot and dd to eMMC, but it also doesn't work. > I wonder how to boot from eMMC? Please help me. > > Thanks. > -- 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 3.4] sunxi:axp20x: Enable internal thermal monitoring
On Sunday, March 9, 2014 10:13:08 AM UTC-4, Alejandro Mery wrote: > > > > On 09/03/14 13:09, Olliver Schinagl wrote: > > Mnemoc, > > > > have you checked and merged this yet? > > thanks for the reminder. it fails to compile when hwmon is m > > like on sun7i_defconfig: >LD .tmp_vmlinux1 > drivers/built-in.o: In function `axp20_init_chip': > /srv/build/amery/allwinner/linux-sunxi/3.4/drivers/power/axp_power/axp20-mfd.h:149: > > > undefined reference to `hwmon_device_register' > drivers/built-in.o: In function `axp_mfd_remove': > /srv/build/amery/allwinner/linux-sunxi/3.4/drivers/power/axp_power/axp-mfd.c:368: > > > undefined reference to `hwmon_device_unregister' > make[1]: *** [.tmp_vmlinux1] Error 1 > make: *** [sub-make] Error 2 > > build_sun7i/.config:CONFIG_AXP_HWMON=y > build_sun7i/.config:CONFIG_HWMON=m > > in most defconfigs hwmon is n, should I y/y them on all defconfigs? can > it be fixed to support hwmon=m? > > Try this: diff --git a/drivers/power/axp_power/Kconfig b/drivers/power/axp_power/Kconfig index 66aa6ac..4e942a9 100644 --- a/drivers/power/axp_power/Kconfig +++ b/drivers/power/axp_power/Kconfig @@ -38,7 +38,7 @@ config AXP_CHGCHANGE config AXP_HWMON depends on HWMON - bool "Enable the internal thermal monitoring support of AXP20X chips" + tristate "Enable the internal thermal monitoring support of AXP20X chips" default y endif # !AW_AXP -- 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] [A10] Getting u-boot onto freshly partitioned Nand for booting Linux
Oh, I see it is uart1. Did you build uboot to use uart1 for 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] [A10] Getting u-boot onto freshly partitioned Nand for booting Linux
Is your serial debug port on uart0? -- 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] [A10] Getting u-boot onto freshly partitioned Nand for booting Linux
Looks to me like this is loading script.bin and uImage from nanda. -- 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] Building Olinuxino-A10-Lime using Yocto - not booting
Which kernel are you using? HDMI is only supported in 3.4. -- 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/groups/opt_out.
Re: [linux-sunxi] [PATCH] arch/arm/mach-sun7i/pm/standby/mem_printk.c used non-const char arrays. However gcc 4.6.3 likes to replace these by calls to memcpy. memcpy doesn't exist in the kernel. Havin
On Wednesday, March 5, 2014 5:55:50 PM UTC-5, Alejandro Mery wrote: > > > On 05/03/14 16:14, Andreas Baierl wrote: > > Hi Alejandro, > > this patch breaks building because it's not applied as Danny sent it :) > > yes, I couldn't "apply" it because of ^Ms... but compiled fine for me > > I'm kind of lost on why is `const char foo* =` instead of `const char > foo[] =`. > This has to do with how arrays vs. pointers are initialized by the compiler at runtime. A pointer like char *p (or const char *p) is initialized by simply setting its value to the address of some string in the data area. An automatic array (on the stack) has storage that must be initialized with the actual contents of the string every time the function is called; memcpy is one way to do this. But if memcpy isn't available because libc isn't available > can you show the error? > > These should all be declared "const char *" not "const char ...[]" Pat -- 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/groups/opt_out.
Re: [linux-sunxi] Re: How to decide NAND boot address?
fatload nand 0 kernel_address kernel_file Note that my u-boot is based on a heavily-modified version of the one used by android. On Wednesday, March 5, 2014 10:10:03 PM UTC-5, hunter hu wrote: > > Hi Pat, > > I was not be able to get serial port access yet, work in progress. > > Regarding the syntax, what are the correct ones? > > thanks, > -Hunter > > On Wednesday, March 5, 2014 8:51:22 PM UTC-6, Patrick Wood wrote: >> >> That's not the right syntax for file access. Don't you have a serial port >> you can get boot logs from? > > -- 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/groups/opt_out.
Re: [linux-sunxi] Re: How to decide NAND boot address?
That's not the right syntax for file access. Don't you have a serial port you can get boot logs from? -- 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/groups/opt_out.
[linux-sunxi] Re: How to decide NAND boot address?
This version of uboot loads the entire partition into RAM, not the uImage
file. You need a modified uboot that can be set up more like the one
that's used on SD cards: http://www.cubieforums.com/index.php?topic=511.0
Pat
On Monday, March 3, 2014 4:00:55 PM UTC-5, hunter hu wrote:
>
> Thanks Patrick,
>
> Does this mean I don't need to change the default 5000 at all?
>
> My intention is to load Linux instead of Android from NAND and following
> this sunxi wiki: http://linux-sunxi.org/Installing_to_NAND.
>
> What changes need to be made in the uboot env besides the /dev/nandd ->
> /dev/nandb?
>
> -Hunter
>
> On Monday, March 3, 2014 2:45:21 PM UTC-6, Patrick Wood wrote:
>>
>> That's not the nand read address; that's the RAM address where the nand
>> read command stores data read from nand. The last argument (boot,
>> recovery) is the nand partition name where it's reading data.
>>
>> This is how an android kernel+initrd is loaded.
>>
>> On Monday, March 3, 2014 2:42:17 PM UTC-5, hunter hu wrote:
>>>
>>> Hi All,
>>>
>>> I am trying to boot from NAND, and using Allwinner lichee-dev branch, in
>>> the sun5i_a13.h header, there is a section of hard coded environment setup
>>> like this:
>>>
>>> 81 #define CONFIG_EXTRA_ENV_SETTINGS \
>>> 182 "bootdelay=3\0" \
>>> 183 "bootcmd=run setargs boot_normal\0" \
>>> 184 "console=ttyS0,115200\0" \
>>> 185 "nand_root=/dev/nandd\0" \
>>> 186 "mmc_root=/dev/mmcblk0p4\0" \
>>> 187 "init=/init\0" \
>>> 188 "loglevel=8\0" \
>>> 189 "setargs=setenv bootargs console=${console} root=${nand_root}" \
>>> 190 "init=${init} loglevel=${loglevel}\0" \
>>> 191 "boot_normal=nand read 5000 boot; boota 5000\0" \
>>> 192 "boot_recovery=nand read 5000 recovery; boota 5000\0" \
>>> 193 "boot_fastboot=fastboot\0"
>>>
>>> My question is: how do I find the nand read address of my own instead of
>>> default 5000?
>>>
>>> My nand-part on the tablet looks like:
>>>
>>> 9 mbr: version 0x0100, magic softw311
>>> 10 2 partitions
>>> 11 partition 1: class = DISK, name = boot, partition
>>> start =32768, partition size =52768 user_type=0
>>> 12 partition 2: class = DISK, name = root, partition
>>> start =85536, partition size = 15479264 user_type=0
>>>
>>> Is that the start of nandb which is 85536 x 512 = 43794432 ?
>>>
>>> I also need to change /dev/nandd to /dev/nandb because I boot from the
>>> second partition /dev/nandb, correct?
>>>
>>> Any hints are greatly appreciated,
>>>
>>> Cheers,
>>> -Hunter
>>>
>>>
--
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/groups/opt_out.
[linux-sunxi] Re: How to decide NAND boot address?
That's not the nand read address; that's the RAM address where the nand
read command stores data read from nand. The last argument (boot,
recovery) is the nand partition name where it's reading data.
This is how an android kernel+initrd is loaded.
On Monday, March 3, 2014 2:42:17 PM UTC-5, hunter hu wrote:
>
> Hi All,
>
> I am trying to boot from NAND, and using Allwinner lichee-dev branch, in
> the sun5i_a13.h header, there is a section of hard coded environment setup
> like this:
>
> 81 #define CONFIG_EXTRA_ENV_SETTINGS \
> 182 "bootdelay=3\0" \
> 183 "bootcmd=run setargs boot_normal\0" \
> 184 "console=ttyS0,115200\0" \
> 185 "nand_root=/dev/nandd\0" \
> 186 "mmc_root=/dev/mmcblk0p4\0" \
> 187 "init=/init\0" \
> 188 "loglevel=8\0" \
> 189 "setargs=setenv bootargs console=${console} root=${nand_root}" \
> 190 "init=${init} loglevel=${loglevel}\0" \
> 191 "boot_normal=nand read 5000 boot; boota 5000\0" \
> 192 "boot_recovery=nand read 5000 recovery; boota 5000\0" \
> 193 "boot_fastboot=fastboot\0"
>
> My question is: how do I find the nand read address of my own instead of
> default 5000?
>
> My nand-part on the tablet looks like:
>
> 9 mbr: version 0x0100, magic softw311
> 10 2 partitions
> 11 partition 1: class = DISK, name = boot, partition
> start =32768, partition size =52768 user_type=0
> 12 partition 2: class = DISK, name = root, partition
> start =85536, partition size = 15479264 user_type=0
>
> Is that the start of nandb which is 85536 x 512 = 43794432 ?
>
> I also need to change /dev/nandd to /dev/nandb because I boot from the
> second partition /dev/nandb, correct?
>
> Any hints are greatly appreciated,
>
> Cheers,
> -Hunter
>
>
--
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/groups/opt_out.
Re: [linux-sunxi] how to flash android in NAND without phonixsuite ..
This from his boot log indicatees that boot1 was found, loaded, and started up okay: Succeed in loading Boot1. Jump to Boot1. [ 0.150] boot1 version : 2.0.0 -- 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/groups/opt_out.
[linux-sunxi] Re: how to flash android in NAND without phonixsuite ..
You're missing the boot partition. Read this: http://www.cubieforums.net/index.php/topic,511.0.html And this: http://cubieforums.net/index.php?topic=511.msg2408#msg2408 On Thursday, February 20, 2014 1:00:08 AM UTC-5, Puneet B wrote: > > Hi all, > > I am using A20 humming bird board. > > i want to boot android from NAND. > > i booted android from sd card successfully. > > i want to know boot0 and boot1 , is it common for all A20 board. > > and to which sector i need to flash this. > > Regards > Punith > -- 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/groups/opt_out.
[linux-sunxi] [PATCH 3.4] sunxi: prevent mali drivers from building every time
This patch was suggested to prevent the mali drivers from rebuild
every time the modules are built. It simply creates symlinks to
sources used by both ump.ko and mali.ko so that their objects are built
in separate directories; otherwise, there is a ping-pong effect between
the ump.ko objects and mali.ko objects overwriting each other.
Signed-off-by: Patrick Wood
---
drivers/gpu/mali/ump/Kbuild |2 +-
drivers/gpu/mali/ump/linux/mali_osk_atomics.c |1 +
drivers/gpu/mali/ump/linux/mali_osk_locks.c |1 +
drivers/gpu/mali/ump/linux/mali_osk_math.c|1 +
drivers/gpu/mali/ump/linux/mali_osk_memory.c |1 +
drivers/gpu/mali/ump/linux/mali_osk_misc.c|1 +
6 files changed, 6 insertions(+), 1 deletion(-)
create mode 12 drivers/gpu/mali/ump/linux/mali_osk_atomics.c
create mode 12 drivers/gpu/mali/ump/linux/mali_osk_locks.c
create mode 12 drivers/gpu/mali/ump/linux/mali_osk_math.c
create mode 12 drivers/gpu/mali/ump/linux/mali_osk_memory.c
create mode 12 drivers/gpu/mali/ump/linux/mali_osk_misc.c
diff --git a/drivers/gpu/mali/ump/Kbuild b/drivers/gpu/mali/ump/Kbuild
index 01355f5..62380fa 100644
--- a/drivers/gpu/mali/ump/Kbuild
+++ b/drivers/gpu/mali/ump/Kbuild
@@ -12,7 +12,7 @@
# Change this to use a different config.h
CONFIG ?= os_memory_64m
-UDD_FILE_PREFIX = ../mali/
+UDD_FILE_PREFIX =
# set the SVN_REV to ${MALI_RELEASE_NAME} due to ARM using subversion
SVN_REV := $(MALI_RELEASE_NAME)
diff --git a/drivers/gpu/mali/ump/linux/mali_osk_atomics.c
b/drivers/gpu/mali/ump/linux/mali_osk_atomics.c
new file mode 12
index 000..d37aa82
--- /dev/null
+++ b/drivers/gpu/mali/ump/linux/mali_osk_atomics.c
@@ -0,0 +1 @@
+../../mali/linux/mali_osk_atomics.c
\ No newline at end of file
diff --git a/drivers/gpu/mali/ump/linux/mali_osk_locks.c
b/drivers/gpu/mali/ump/linux/mali_osk_locks.c
new file mode 12
index 000..f4c33be
--- /dev/null
+++ b/drivers/gpu/mali/ump/linux/mali_osk_locks.c
@@ -0,0 +1 @@
+../../mali/linux/mali_osk_locks.c
\ No newline at end of file
diff --git a/drivers/gpu/mali/ump/linux/mali_osk_math.c
b/drivers/gpu/mali/ump/linux/mali_osk_math.c
new file mode 12
index 000..e8a59cd
--- /dev/null
+++ b/drivers/gpu/mali/ump/linux/mali_osk_math.c
@@ -0,0 +1 @@
+../../mali/linux/mali_osk_math.c
\ No newline at end of file
diff --git a/drivers/gpu/mali/ump/linux/mali_osk_memory.c
b/drivers/gpu/mali/ump/linux/mali_osk_memory.c
new file mode 12
index 000..0e5e8c8
--- /dev/null
+++ b/drivers/gpu/mali/ump/linux/mali_osk_memory.c
@@ -0,0 +1 @@
+../../mali/linux/mali_osk_memory.c
\ No newline at end of file
diff --git a/drivers/gpu/mali/ump/linux/mali_osk_misc.c
b/drivers/gpu/mali/ump/linux/mali_osk_misc.c
new file mode 12
index 000..750aa9d
--- /dev/null
+++ b/drivers/gpu/mali/ump/linux/mali_osk_misc.c
@@ -0,0 +1 @@
+../../mali/linux/mali_osk_misc.c
\ No newline at end of file
--
1.7.9.5
--
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/groups/opt_out.
[linux-sunxi] Re: [PATCH 3.4] sunxi: Unbreak broken CedarX userland software (2GB phys->bus issue)
On Tuesday, February 11, 2014 2:11:59 PM UTC-5, Siarhei Siamashka wrote: > > The commit 1e205f75658cb0cf3addc28ddaa9912ca9ce14e8 happened to > break broken CedarX media players on the systems with 2GB of RAM > (Cubietruck). The problem is that some CedarX userland code (used > in VLC and XBMC together with proprietary blobs) already feeds > bus addresses to the sunxi disp ioctls, while physical addresses > are expected there. The open source libvdpau-sunxi does not have > such bugs. > > This patch avoids phys->bus conversion if the address passed to > the __phys_to_bus macro is already obviously a bus address. > > While the right solution would be to hunt down and fix all the > userland offenders, this may be difficult in practice. For example > when dealing with Android images and trying to provide a drop-in > kernel replacement for them. > > Signed-off-by: Siarhei Siamashka > > --- > arch/arm/plat-sunxi/include/plat/memory.h | 18 +- > 1 file changed, 17 insertions(+), 1 deletion(-) > > diff --git a/arch/arm/plat-sunxi/include/plat/memory.h > b/arch/arm/plat-sunxi/include/plat/memory.h > index 42a4afa..3a94fe6 100644 > --- a/arch/arm/plat-sunxi/include/plat/memory.h > +++ b/arch/arm/plat-sunxi/include/plat/memory.h > @@ -30,7 +30,23 @@ > /* default ATAG_MEM size */ > #define MEM_SIZE(512*1024*1024) > > -#define __phys_to_bus(x) ((x) - PLAT_PHYS_OFFSET) > +/* > + * HACK: if 'x' argument is lower than PLAT_PHYS_OFFSET in the > '__phys_to_bus' > + * macro (which is incorrect by itself), then we know that > something is > + * wrong. Most likely 'x' is already a bus address (result of a > conversion > + * of some physical address belonging to the first 1GB of DRAM). > Not much > + * harm is done if we just keep it as-is instead of wrapping around > into > + * the 0xC000-0x range. The typical offenders are the > CedarX > + * userland wrappers around proprietary blobs, which mess up the > address > + * arithmetics and may introduce an arbitrary address offset (this > offset > + * is a multiple of 0x4000). As we have little control over the > blobs > + * used in Android, this hack may workaround some issues for the > users > + * of the systems with 2GB of RAM (the adverse effects of a > multiple of > + * 0x4000 address calculation bugs only show up on such > systems). > + */ > + > +#define __phys_to_bus(x) ((u32)(x) < PLAT_PHYS_OFFSET ? (x) : \ > + (x) - > PLAT_PHYS_OFFSET) > #define __bus_to_phys(x) ((x) + PLAT_PHYS_OFFSET) > > #endif > -- > 1.8.3.2 > > Works for me on a 2GB CT. Acked-by: Patrick Wood -- 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/groups/opt_out.
Re: [linux-sunxi] Re: Unable to play 720p video in Ubuntu
And if you're not running this in an xterm, you need to set DISPLAY=:0 in your environment (or somesuch -- whatever name the Xorg driver used to set up the X display). On Tuesday, February 4, 2014 11:28:37 AM UTC-5, Roman Mamedov wrote: > > On Tue, 4 Feb 2014 02:35:26 -0800 (PST) > Puneet B > wrote: > > > Exiting... (End of file) > > root@localhost:/libvdpau-sunxi# > > You are running the media player as 'root', but are you logged into Xorg > also > as 'root' (which would be uncommon and not recommended)? > > If not, then 'root' will not have access to a local display by default, > since > it is a different user. > > So ensure the media player runs from the same user as Xorg. > > -- > With respect, > Roman > -- 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/groups/opt_out.
[linux-sunxi] Unable to play 720p video in Ubuntu
You don't need Mali for video decode. See these: http://linux-sunxi.org/CedarX http://linux-sunxi.org/Cedrus http://linux-sunxi.org/XBMC -- 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/groups/opt_out.
Re: [linux-sunxi] Re: How to port ubuntu in my A20 board.
These distros all do not have any getty running on the serial port. The virtual terminals should be working, or you can add a /etc/init/ttyS0.conf. -- 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/groups/opt_out.
[linux-sunxi] [PATCH 3.4] sunxi:axp20x: Enable internal thermal monitoring
Enable the internal thermal monitoring support of AXP20X chips
Cherry-picked from:
https://github.com/cubieboard/linux-sunxi/commit/e4144b3ce62b1d7014fee36b84bc65c812469822
Creates the sysfs file temp1_input in the sunxi-i2c tree that reports the
AXP's temperature in degrees C.
According to the AXP202's datasheet, this port outputs a 12-bit value
where 0x000 == -144.7C and 0xfff == 264.8C in 0.1 degree C increments.
Signed-off-by: LABBE Corentin
Signed-off-by: Hans de Goede
Signed-off-by: Patrick Wood
---
drivers/power/axp_power/Kconfig |5 ++
drivers/power/axp_power/axp-mfd.c |7 +++
drivers/power/axp_power/axp20-mfd.h | 112 +++
include/linux/mfd/axp-mfd.h |7 +++
4 files changed, 130 insertions(+)
diff --git a/drivers/power/axp_power/Kconfig b/drivers/power/axp_power/Kconfig
index 039679f..b76f517 100644
--- a/drivers/power/axp_power/Kconfig
+++ b/drivers/power/axp_power/Kconfig
@@ -36,4 +36,9 @@ config AXP_CHGCHANGE
bool "AXP charging current set when suspend\resume\shutdown"
default y
+config AXP_HWMON
+ depends on HWMON
+ bool "Enable the internal thermal monitoring support of AXP20X chips"
+ default y
+
endif # !AW_AXP
diff --git a/drivers/power/axp_power/axp-mfd.c
b/drivers/power/axp_power/axp-mfd.c
index 9af0257..cfa894a 100644
--- a/drivers/power/axp_power/axp-mfd.c
+++ b/drivers/power/axp_power/axp-mfd.c
@@ -363,6 +363,13 @@ static int __devexit axp_mfd_remove(struct i2c_client
*client)
pm_power_off = NULL;
axp = NULL;
+#ifdef CONFIG_AXP_HWMON
+ if (chip->itm_enabled == 1) {
+ hwmon_device_unregister(chip->hwmon_dev);
+ sysfs_remove_group(&client->dev.kobj, &axp20_group);
+ }
+#endif
+
axp_mfd_remove_subdevs(chip);
kfree(chip);
return 0;
diff --git a/drivers/power/axp_power/axp20-mfd.h
b/drivers/power/axp_power/axp20-mfd.h
index 1c7a41b..214856e 100644
--- a/drivers/power/axp_power/axp20-mfd.h
+++ b/drivers/power/axp_power/axp20-mfd.h
@@ -22,6 +22,83 @@
#include "axp-rw.h"
+#ifdef CONFIG_AXP_HWMON
+
+#include
+#include
+#include
+
+static struct axp_mfd_chip *axp20_update_device(struct device *dev);
+
+static ssize_t
+show_temp(struct device *dev, struct device_attribute *devattr, char *buf)
+{
+ struct sensor_device_attribute *attr = to_sensor_dev_attr(devattr);
+ struct axp_mfd_chip *data = axp20_update_device(dev);
+ if (attr->index == 1)
+ return sprintf(buf, "264800\n");
+ if (attr->index == 2)
+ return sprintf(buf, "-144700\n");
+ return sprintf(buf, "%d\n", data->temperature * 100);
+}
+
+
+static SENSOR_DEVICE_ATTR(temp1_input, S_IRUGO, show_temp, NULL, 0);
+static SENSOR_DEVICE_ATTR(temp1_max, S_IRUGO, show_temp, NULL, 1);
+static SENSOR_DEVICE_ATTR(temp1_min, S_IRUGO, show_temp, NULL, 2);
+
+static struct attribute *axp20_attributes[] = {
+ &sensor_dev_attr_temp1_input.dev_attr.attr,
+ &sensor_dev_attr_temp1_min.dev_attr.attr,
+ &sensor_dev_attr_temp1_max.dev_attr.attr,
+ NULL
+};
+
+static const struct attribute_group axp20_group = {
+ .attrs = axp20_attributes,
+};
+
+
+/*
+ * * function that update the status of the chips (temperature)
+ * */
+static struct axp_mfd_chip *axp20_update_device(struct device *dev)
+{
+ struct i2c_client *client = to_i2c_client(dev);
+ struct axp_mfd_chip *data = i2c_get_clientdata(client);
+ int err;
+ u8 high, low;
+
+ mutex_lock(&data->lock);
+
+ if (time_after(jiffies, data->last_updated + HZ * 2)
+ || !data->valid) {
+ dev_dbg(&client->dev, "Updating axp20 data\n");
+ /* AXP202 datasheet page 25, 0x000 means -144.7,
+* 0xfff means 264.8, 4096 steps of 0.1 degress */
+ err = __axp_read(client, 0x5E, &high);
+ if (err) {
+ dev_err(dev, "AXP Error while reading high\n");
+ high = 0;
+ }
+
+ err = __axp_read(client, 0x5F, &low);
+ if (err) {
+ dev_err(dev, "AXP Error while reading low\n");
+ low = 0;
+ }
+
+ data->temperature = -1447 + ((high << 4) + (low && 0x0F));
+ data->last_updated = jiffies;
+ data->valid = 1;
+ }
+
+ mutex_unlock(&data->lock);
+ return data;
+}
+
+#endif
+
static int __devinit axp20_init_chip(struct axp_mfd_chip *chip)
{
@@ -33,6 +110,9 @@ static int __devinit axp20_init_chip(struct axp_mfd_chip
*chip)
POWER20_INTSTS3, 0xff, POWER20_INTSTS4, 0xff,
POWER20_INTSTS5, 0xff };
int err;
[linux-sunxi] [PATCH 3.4] sunxi-hdmiaudio: Enable 32-bit audio
The original modifications for this patch originate from some custom
changes made to the 3.3 Android kernel by huangxin at allwinnertech.com.
The A10/A20 DMA engine for HDMI audio only supports 16 or 32-bit
transfers. The documentation says 16, 20, and 24 bits, but I have not
been able to get 24-bit audio, ether 3-bytes (PCM_FMTBIT_24_3LE) or
4-bytes (PCM_FMTBIT_24_LE) to work.
This patch removes the non-working PCM formats, PCM_FMTBIT_S18_3LE
and PCM_FMTBIT_S20_3LE, and PCM_FMTBIT_S24_LE and adds suppor for
32-bit HDMI audio (PCM_FMTBIT_S32_LE). It's possible that other 32-bit
formats, like PCM_FMTBIT_U32_LE or PCM_FMTBIT_FLOAT_LE might work, but
couldn't be tested.
This patch was tested with 24-bit and 32-bit .wav files and the ALSA
"plughw" plugin (for upconverting the 24-bit audio files to 23-bits)
with aplay -v to verify that the target format was S32_LE.
Signed-off-by: Patrick Wood
---
drivers/video/sunxi/hdmi/drv_hdmi.c |6 ++
drivers/video/sunxi/hdmi/hdmi_core.c| 30 +--
drivers/video/sunxi/hdmi/hdmi_core.h|1 +
include/linux/drv_hdmi.h|1 +
sound/soc/sunxi/hdmiaudio/sndhdmi.c | 16 +-
sound/soc/sunxi/hdmiaudio/sunxi-hdmiaudio.c |6 --
sound/soc/sunxi/hdmiaudio/sunxi-hdmipcm.c |3 ++-
7 files changed, 53 insertions(+), 10 deletions(-)
diff --git a/drivers/video/sunxi/hdmi/drv_hdmi.c
b/drivers/video/sunxi/hdmi/drv_hdmi.c
index a8d3cef..283d2ae 100644
--- a/drivers/video/sunxi/hdmi/drv_hdmi.c
+++ b/drivers/video/sunxi/hdmi/drv_hdmi.c
@@ -208,6 +208,12 @@ static __s32 Hdmi_Set_Audio_Para(hdmi_audio_t *audio_para)
if (!audio_para)
return -1;
+ if (audio_para->sample_bit != audio_info.sample_bit) {
+ if (hdmi_state >= HDMI_State_Audio_config)
+ hdmi_state = HDMI_State_Audio_config;
+ audio_info.sample_bit = audio_para->sample_bit;
+ }
+
if (audio_para->sample_rate != audio_info.sample_rate) {
audio_info.sample_rate = audio_para->sample_rate;
change = audio_info.audio_en;
diff --git a/drivers/video/sunxi/hdmi/hdmi_core.c
b/drivers/video/sunxi/hdmi/hdmi_core.c
index c1c4c9c..a6dd01f 100644
--- a/drivers/video/sunxi/hdmi/hdmi_core.c
+++ b/drivers/video/sunxi/hdmi/hdmi_core.c
@@ -580,8 +580,14 @@ __s32 audio_config(void)
return 0;
if (audio_info.channel_num == 1) {
- /* audio fifo rst and select ddma, 2 ch 16bit pcm */
- writel(0x, HDMI_AUDIO_UNKNOWN_0);
+ if (audio_info.sample_bit == 32) {
+ /* audio fifo rst and select ddma, 2 ch 32bit pcm */
+ writel(0x000e, HDMI_AUDIO_UNKNOWN_0);
+ } else {
+ /* audio fifo rst and select ddma, 2 ch 16bit pcm */
+ writel(0x, HDMI_AUDIO_UNKNOWN_0);
+ }
+
/* ddma,pcm layout0 1ch */
writel(0x, HDMI_AUDIO_LAYOUT);
writel(0x76543200, HDMI_AUDIO_UNKNOWN_1);
@@ -592,8 +598,14 @@ __s32 audio_config(void)
writel(0x, HDMI_AUDIO_INFOFRAME + 8);
writel(0x, HDMI_AUDIO_INFOFRAME + 12);
} else if (audio_info.channel_num == 2) {
- /* audio fifo rst and select ddma, 2 ch 16bit pcm */
- writel(0x, HDMI_AUDIO_UNKNOWN_0);
+ if (audio_info.sample_bit == 32) {
+ /* audio fifo rst and select ddma, 2 ch 32bit pcm */
+ writel(0x000e, HDMI_AUDIO_UNKNOWN_0);
+ } else {
+ /* audio fifo rst and select ddma, 2 ch 16bit pcm */
+ writel(0x, HDMI_AUDIO_UNKNOWN_0);
+ }
+
/* ddma,pcm layout0 2ch */
writel(0x0001, HDMI_AUDIO_LAYOUT);
writel(0x76543210, HDMI_AUDIO_UNKNOWN_1);
@@ -604,8 +616,14 @@ __s32 audio_config(void)
writel(0x, HDMI_AUDIO_INFOFRAME + 8);
writel(0x, HDMI_AUDIO_INFOFRAME + 12);
} else if (audio_info.channel_num == 8) {
- /* audio fifo rst and select ddma, 2 ch 16bit pcm */
- writel(0x, HDMI_AUDIO_UNKNOWN_0);
+ if (audio_info.sample_bit == 32) {
+ /* audio fifo rst and select ddma, 2 ch 32bit pcm */
+ writel(0x000e, HDMI_AUDIO_UNKNOWN_0);
+ } else {
+ /* audio fifo rst and select ddma, 2 ch 16bit pcm */
+ writel(0x, HDMI_AUDIO_UNKNOWN_0);
+ }
+
/* ddma,pcm layout1 8ch */
writel(0x000f, HDMI_AUDIO_LAYOUT);
writel(0x76543210, HDMI_AUDIO_UNKNOWN_1);
diff --git a/drivers/video/sunxi/hdmi
Re: [linux-sunxi] 24-bit Audio Isn't Working
I've just submitted the patch. Pat On Monday, January 27, 2014 7:33:07 AM UTC-5, turk...@gmail.com wrote: > > On Friday, January 17, 2014 9:16:18 PM UTC+4, George Ioakimedes wrote: > > We're getting closer. I was able to meet briefly with Allwinner at CES > and they are helping us now. We are very close now I think and with some > luck we may solve this over the weekend. > > Hi George. Could you manage to get 24-bit audio? > > Regards, > Ali > > -- 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/groups/opt_out.
[linux-sunxi] How to port ubuntu in my A20 board.
You can start with a base linaro or ubuntu armhf rootfs like this: https://wiki.linaro.org/Platform/DevPlatform/Rootfs or this: http://cdimage.ubuntu.com/ubuntu-core/releases/13.10/release/ Once you untar them you can use apt-get to install more packages. -- 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/groups/opt_out.
Re: [linux-sunxi] Re: How to test wifi in A20.
On Thursday, January 23, 2014 7:31:22 AM UTC-5, Olliver Schinagl wrote: > > > > On 23-01-14 13:21, Puneet B wrote: > > Hi Patrick, > > > > Actually i compiled bcmdhd as a driver not as a module. > > > > because if i compiled as a module and try to insert it > > > > i am getting fallowing error. > > > > modprobe: FATAL: Could not load > > /lib/modules/3.4.75-1-g9cfbbed/modules.dep: No such file or > directory > looks like you forgot to run depmod -a or didn't make modules_install > > > > > > Do you think this will be problem? > modules.dep informs modprobe about module order and dependencies; so > yeah, could be. > There's no reason why this driver won't work when compiled directly into the kernel instead of as a module; however, if you don't get your module building steps correct now, you'll never be able to build any modules and modprobe them. Pat -- 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/groups/opt_out.
[linux-sunxi] Re: How to test wifi in A20.
On Saturday, January 18, 2014 12:14:39 AM UTC-5, Puneet B wrote: > > Hi Patrick, > > Thanks for your reply. > > Actually i tried with 3.3 kernel also. > > Here is my logo: > > > I haven't looked at this device in the 3.3 kernel, but the 3.4 kernel from cubietech has these modifications to support the Cubietruck's ap6210: https://github.com/cubieboard/linux-sunxi/commit/aff95a2fc4192f72c9ff33abfd17144e25773c5a, and they are known to work in the CT's distros. > > Can you tell why down_timeout is not returning 0. > Here i am attaching schematic of my board. > I have this device working on the Cubietruck with the 3.4 kernel. In order to get it to work on a different board, you'll need to set up the script.bin to enable the mmc port it's attached to. On the CT, the chip is hooked up to mmc3, so its script.fex looks like this: [mmc3_para] sdc_used = 1 sdc_detmode = 4 sdc_buswidth = 4 sdc_cmd = port:PI04<2><1><2> sdc_clk = port:PI05<2><1><2> sdc_d0 = port:PI06<2><1><2> sdc_d1 = port:PI07<2><1><2> sdc_d2 = port:PI08<2><1><2> sdc_d3 = port:PI09<2><1><2> sdc_det = sdc_use_wp = 0 sdc_wp = sdc_isio = 1 sdc_regulator = "none" You'll also need to specify the gpio that's used for enabling it. On the CT, it's PH09, and the fex entry looks like this: ap6xxx_wl_regon = port:PH09<1><0> I'm afraid you're going to have to read the schematics yourself or get support for it from hummingbird. > Should i use 3.4 from > https://github.com/cubieboard/linux-sunxi > > > or 3.3 kernel for problem solving. > If you're building a kernel for a linux distro and not android, the 3.4 kernel is a better choice, since many people have the wifi working now with this kernel and different distros, and we're not really keen on answering questions about the 3.3 kernel anymore. If you're building a kernel for android, I don't know, 'cause I don't build android. > Pat > Kindly tell me how to solve the wifi issue. > > Regards > Punith > > > > > > > -- 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/groups/opt_out.
[linux-sunxi] Re: How to test wifi in A20.
On Friday, January 17, 2014 2:54:45 AM UTC-5, Puneet B wrote:
>
> Hi,
>
> While tracing problem i found below issue.
>
> i am getting error in log as:
>
> [4.780261] [dhd_module_init] get wl_host_wake gpio failed
>
> The code is from here:./
>
> vim linux-sunxi/drivers/net/wireless/bcmdhd/dhd_linux.c +4396
>
> if (gpio_request(WL_HOST_WAKE_DEF_GPIO, "wl_host_wake")) {
> pr_warning("[%s] get wl_host_wake gpio failed\n",
> __FUNCTION__);
> wl_host_wake = -1;
> return -1;
> }
>
> Which means some gpio error:
>
> In script for wifi:
> ap6xxx_wl_regon = port:PH09<1><0>
> ap6xxx_wl_host_wake = port:PH10<0><0>
> ap6xxx_bt_regon = port:PB05<1><0>
> ap6xxx_bt_wake = port:PI20<1><0>
> ap6xxx_bt_host_wake = port:PI21<0><0>
> ap6xxx_lpo = port:PI12<4>
>
>
> For ap6xxx_wl_host_wake , i check by making high and low but error is
> same.
>
> Can any one tell why that error is, Is it because of some gpio pins or
> something else went wrong?
>
> Regards
> Punith
>
> The problem is that the stock bcmdhd driver doesn't know how to toggle the
allwinner gpios to turn on the chip. Cubietech made some changes for that
to drivers/net/wireless/bcmdhd/dhd_custom_gpio.c, which is meant by
Broadcom to be customized to different boards (thus the "custom" in the
name). It could all be abstracted pretty easily in the 3.4 linux-sunxi
kernel, except for a few new calls to sunximmc_rescan_card made after power
off and power on (probably not needed after the power off).
The mainline kernel abstracts this stuff much better than 3.4, so
backporting might not be so easy.
Pat
--
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/groups/opt_out.
Re: [linux-sunxi] [PATCH u-boot-sunxi] ARM: sunxi: get script.bin file name from env
Even in mainline, I see no reason to not to access the dtb file through an env variable (I haven't checked to see, perhaps it is). -- 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/groups/opt_out.
[linux-sunxi] Re: Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support
Use the latest code. This device was added with this commit: 9cfbbed3b2b098774b04553843d2f4092b8f7fe8 from this patch: https://groups.google.com/forum/#!topic/linux-sunxi/oMmB72S8qzQ On Tuesday, January 14, 2014 9:35:16 AM UTC-5, Nelson Grodzicki wrote: > > Just realized that the WiFi adaptor is RTL8188etv which has a different > vendor id (0179). > Perhaps I need to modify the .ko driver which is set for RTL8188eu. > How do I do that the easy way ?? > Thanks -- > Nelson > > > 2014/1/13 Nelson Grodzicki > > >> Hi, >> so far this is what I got from dmseg >> [10947.177718] sw_usb_enable_hcd: usbc_num = 1 >> [10947.182129] usbcore: registered new interface driver rtl8188eu >> >> Will see.. >> >> Thanks >> >> >> >> >> 2014/1/13 > >> >> понедельник, 13 января 2014 г., 17:43:25 UTC+4 пользователь Nelson >>> Grodzicki написал: >>> > Still internal WiFi does not want to show up ... >>> what 'dmesg' out after 'modprobe 8188eu' ? >> >> >> > -- 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/groups/opt_out.
[linux-sunxi] Re: [PATCH u-boot-sunxi] ARM: sunxi: get script.bin file name from env
No other comments?
On Thursday, January 9, 2014 12:49:28 AM UTC-5, Patrick Wood wrote:
>
> All the other files can be overridden by env settings, what's so
> special about script.bin?
>
> Use the "script" env variable instead of hard-coding script.bin
> everywhere; still defaults to "script.bin", but can be overridden
> from uEnv.txt or boot.scr.
>
> Signed-off-by: Patrick Wood
> ---
> include/configs/sunxi-common.h |7 ---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/include/configs/sunxi-common.h
> b/include/configs/sunxi-common.h
> index 2c86a8e..a0c41ac 100644
> --- a/include/configs/sunxi-common.h
> +++ b/include/configs/sunxi-common.h
> @@ -213,6 +213,7 @@
> "kernel=uImage\0" \
> "bootenv=uEnv.txt\0" \
> "bootscr=boot.scr\0" \
> +"script=script.bin\0" \
> "loadbootscr=" \
>"fatload $device $partition $scriptaddr ${bootscr}" \
>" || " \
> @@ -231,19 +232,19 @@
>"if "\
> "bootpath=/boot/" \
> " && " \
> -"ext2load $device $partition 0x4300
> ${bootpath}script.bin" \
> +"ext2load $device $partition 0x4300 ${bootpath}${script}"
> \
> " && " \
> "ext2load $device $partition 0x4800 ${bootpath}${kernel}"
> \
>";then true; elif " \
> "bootpath=/" \
> " && " \
> -"fatload $device $partition 0x4300 script.bin" \
> +"fatload $device $partition 0x4300 ${script}" \
> " && " \
> "fatload $device $partition 0x4800 ${kernel}" \
>";then true; elif " \
> "bootpath=/" \
> " && " \
> -"ext2load $device $partition 0x4300
> ${bootpath}script.bin" \
> +"ext2load $device $partition 0x4300 ${bootpath}${script}"
> \
> " && " \
> "ext2load $device $partition 0x4800 ${bootpath}${kernel}"
> \
>";then true; else "\
> --
> 1.7.9.5
>
>
--
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/groups/opt_out.
[linux-sunxi] Re: help with NAND access of A20 based MELE M5
What do you mean by "enable flash storage"? Enable how? -- 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/groups/opt_out.
Re: [linux-sunxi] [PATCH u-boot-sunxi] ARM: sunxi: get script.bin file name from env
On Thursday, January 9, 2014 1:54:58 PM UTC-5, Arokux wrote: > > On Thu, Jan 9, 2014 at 6:26 PM, Patrick Wood > > > wrote: > > > > > > On Thursday, January 9, 2014 10:53:40 AM UTC-5, Arokux wrote: > >> > >> On Thu, Jan 9, 2014 at 6:49 AM, Patrick Wood > wrote: > >> > All the other files can be overridden by env settings, what's so > >> > special about script.bin? > >> > > >> > Use the "script" env variable instead of hard-coding script.bin > >> > everywhere; still defaults to "script.bin", but can be overridden > >> > from uEnv.txt or boot.scr. > >> > > >> > Signed-off-by: Patrick Wood > >> > >> Hm.. why do you think it has the chance to make its way into mainline > >> u-boot? > >> > >> A. > > > > > > Oops, sorry, you're right. This should have been for sunxi only. > Should I > > resubmit with a new subject? > > As far as I know u-boot-sunxi is going to be mainlined some time and > there is no sunxi specific branch. > > A. > > Well, when it is mainlined, sunxi-common.h will have to change anyway, as script.bin isn't used by the mainline kernel. So unless mainlining is going to occur really soon, I don't see the problem with this patch. -- 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/groups/opt_out.
Re: [linux-sunxi] [PATCH u-boot-sunxi] ARM: sunxi: get script.bin file name from env
On Thursday, January 9, 2014 10:53:40 AM UTC-5, Arokux wrote: > > On Thu, Jan 9, 2014 at 6:49 AM, Patrick Wood > > > wrote: > > All the other files can be overridden by env settings, what's so > > special about script.bin? > > > > Use the "script" env variable instead of hard-coding script.bin > > everywhere; still defaults to "script.bin", but can be overridden > > from uEnv.txt or boot.scr. > > > > Signed-off-by: Patrick Wood > > > Hm.. why do you think it has the chance to make its way into mainline > u-boot? > > A. > Oops, sorry, you're right. This should have been for sunxi only. Should I resubmit with a new subject? -- 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/groups/opt_out.
[linux-sunxi] [PATCH u-boot-sunxi] ARM: sunxi: get script.bin file name from env
All the other files can be overridden by env settings, what's so
special about script.bin?
Use the "script" env variable instead of hard-coding script.bin
everywhere; still defaults to "script.bin", but can be overridden
from uEnv.txt or boot.scr.
Signed-off-by: Patrick Wood
---
include/configs/sunxi-common.h |7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/include/configs/sunxi-common.h b/include/configs/sunxi-common.h
index 2c86a8e..a0c41ac 100644
--- a/include/configs/sunxi-common.h
+++ b/include/configs/sunxi-common.h
@@ -213,6 +213,7 @@
"kernel=uImage\0" \
"bootenv=uEnv.txt\0" \
"bootscr=boot.scr\0" \
+ "script=script.bin\0" \
"loadbootscr=" \
"fatload $device $partition $scriptaddr ${bootscr}" \
" || " \
@@ -231,19 +232,19 @@
"if "\
"bootpath=/boot/" \
" && " \
- "ext2load $device $partition 0x4300 ${bootpath}script.bin" \
+ "ext2load $device $partition 0x4300 ${bootpath}${script}" \
" && " \
"ext2load $device $partition 0x4800 ${bootpath}${kernel}" \
";then true; elif " \
"bootpath=/" \
" && " \
- "fatload $device $partition 0x4300 script.bin" \
+ "fatload $device $partition 0x4300 ${script}" \
" && " \
"fatload $device $partition 0x4800 ${kernel}" \
";then true; elif " \
"bootpath=/" \
" && " \
- "ext2load $device $partition 0x4300 ${bootpath}script.bin" \
+ "ext2load $device $partition 0x4300 ${bootpath}${script}" \
" && " \
"ext2load $device $partition 0x4800 ${bootpath}${kernel}" \
";then true; else "\
--
1.7.9.5
--
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/groups/opt_out.
Re: [linux-sunxi] Re: A good SD card image for A10-OLinuXino-Lime?
An on a different note, not to make things more difficult: the cpufrequtils package from ubuntu (at least this version: cpufrequtils_008-1_armhf.deb) installs an init.d startup file called cpufrequtils that sets the default governor to... you guessed it -- ondemand. This is easily overridden by putting GOVERNOR=performance in the file /etc/default/cpufrequtils, but requires people to know that this is needed. On Sunday, January 5, 2014 9:50:24 PM UTC-5, Siarhei Siamashka wrote: > > On Mon, 6 Jan 2014 06:39:38 +0600 > Roman Mamedov > wrote: > > > On Mon, 6 Jan 2014 00:00:00 +0200 > > Siarhei Siamashka > wrote: > > > > > A better solution is to really ramp up the CPU to the maximum clock > > > speed if we have some external power source connected (ACIN or VBUS). > > > Adhering to the "principle of least surprise", it makes sense to fork > > > the "ondemand" governor with some new name and make it the default. > > > > A new governor (and a platform-specific one, no less) is unlikely to > ever be > > mainlined. > > It's a bit too early to talk about mainlining. We need to solve the > problem at hand before planning too far ahead. I proposed this > particular solution with the upgrade path for sunxi-3.4 in mind. > > Also I don't pretend to know much about power management. But the > current default cpufreq performance is simply unacceptable and > something has to be done about it. Enough is enough. > > > Try mainlining those "fantasy" or "interactive", you'll more likely > > be laughed out of the building politely pointed to all the > tunables > > of "ondemand", some of which I just listed in my other E-Mail. > > Well, it is the primary responsibility of the kernel to provide an > efficient way to use the hardware. If the kernel fails to handle > this efficiently for any reasons, then it is doing a poor job and > needs to be improved. > > And the kernel is indeed always evolving. New things are being > introduced whenever they are justified. And for example, do you > remember things like hyper-threading or turbo boost? Why haven't > those dudes been laughed out of the building politely > asked to design the hardware so that it plays nice with the existing > kernel without any need to introduce anything new? > > But why am I even explaining these obvious things? > > > If you *really* want to react to power events, there is no reason a > userspace > > program can't change max/min_frequency of the ondemand governor, or even > > switch between ondemand and performance as the power situation allows; > it could > > be either a daemon or a oneshot script called from udev(?), if changes > are only > > required on plugging/unplugging of power source. In fact I think there > should > > be something like that already (designed for laptops). > > AFAIK on the x86 laptops at least part of this functionality is handled > by the BIOS and ACPI. Which makes them a little bit different from ARM > hardware. > > In any case, I don't like the idea of forcing the userland to take > special care of sunxi specific power management when this can be better > done in the kernel. How the hell are you going to package it for many > different linux distributions? > > -- > Best regards, > Siarhei Siamashka > -- 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/groups/opt_out.
Re: [linux-sunxi] Re: A good SD card image for A10-OLinuXino-Lime?
On Sunday, January 5, 2014 7:13:06 PM UTC-5, Roman Mamedov wrote: > > On Sun, 5 Jan 2014 16:01:20 -0800 (PST) > Patrick Wood > wrote: > > > Also, my experience with performance on the A10 devices over the last > two > > years has shown me that ondemand is a really terrible governor, as it > > doesn't boost the CPU frequency unless utilization has been high over an > > extended period > > This is easily tunable via knobs mentioned at > http://linux-sunxi.org/Cpufreq > > Specifically you want to reduce the up_threshold, in the example on that > page > the frequency will be boosted as soon as the CPU utilization even touches > 25%. > Not "high over extended period", is it? And then if an issue arises that > it > drops back too quickly, that can be tuned by changing > sampling_down_factor. > Yes, but most people don't bother to read that. In fact, most people don't know about the cpu governors; they just complain about performance. The default settings for ondemand are obviously poor for non-battery use. Also, none of these knobs helps boot times. > > > so even programs that are CPU bound don't cause it to > > switch if they spend just a little time reading or writing data. > > Set io_is_busy to 1, and even time spent reading or writing data (in > iowait) > will count as "CPU load" for the purposes of frequency switching. > See comment above. > > > interactive is much better at increasing the CPU clock even on > relatively > > small changes in demand. > > My guess is that people tend to invent crazy new obscure governors mostly > because they didn't spend any time reading documentation for the existing > ones > (and how to properly configure them for the usage scenario at hand). > See comment above. The current default governor (ondemand) and/or its default settings need to be changed. Pat > > -- > With respect, > Roman > -- 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/groups/opt_out.
Re: [linux-sunxi] Re: A good SD card image for A10-OLinuXino-Lime?
On Sunday, January 5, 2014 5:00:00 PM UTC-5, Siarhei Siamashka wrote:
>
> On Wed, 1 Jan 2014 20:03:35 -0800 (PST)
> Patrick Wood > wrote:
>
> > On Wednesday, January 1, 2014 5:54:20 PM UTC-5, Siarhei Siamashka wrote:
> > > I myself still see no good reason for using any governor other than
> > > "performance" when running with a wall connected power plug. Poor
> > > default cpufreq behaviour is a major performance pitfall for
> > > inexperienced users and it totally kills desktop responsiveness.
> > >
> > > We may introduce a new customized cpufreq governor and set it by
> > > default. The users can always change the cpufreq settings to whatever
> > > they want.
> > >
> > > Moreover, as a temporary solution, I would probably even advocate
> > > setting the "performance" cpufreq governor for linux-sunxi kernels
> > > by default (for the linux defconfigs). Do we have many tablet users,
> > > who are running linux instead of android and also need good battery
> > > life (have no usb ports or chargers nearby for providing power)?
> >
> > I believe that a minimum setting of 408MHZ with the "interactive"
> governor
> > works quite well. This governor raises the CPU clock much faster than
> > ondemand, and 408MHz seems to be a spot where the SoC will power down a
> lot
> > of blocks when idle.
>
> Is this just a speculation? Or some kind of research has been done?
>
It was based on the comments in this commit:
47d3b18876571835f0fce7b7b8125110713e30fc
Also, my experience with performance on the A10 devices over the last two
years has shown me that ondemand is a really terrible governor, as it
doesn't boost the CPU frequency unless utilization has been high over an
extended period, so even programs that are CPU bound don't cause it to
switch if they spend just a little time reading or writing data.
interactive is much better at increasing the CPU clock even on relatively
small changes in demand.
> What we know for sure is that the current cpufreq defaults ("ondemand"
> for sun4i and "fantasy" for sun7i) are responsible for really poor
> performance. Note that sun4i and sun7i are defaulting to different
> governors for some unknown reason.
>
> And there is one more source of inconsistency. The range of allowed CPU
> frequencies and their voltages can be configured in fex files for
> each device/board individually. For example, compare cubieboard2 and
> cubietruck fex files:
>
> https://github.com/linux-sunxi/sunxi-boards/blob/36a6f268b69afde7/sys_config/a20/cubieboard2.fex#L957
>
>
> https://github.com/linux-sunxi/sunxi-boards/blob/36a6f268b69afde7/sys_config/a20/cubietruck.fex#L944
>
> The minimum CPU clock frequency for the cubieboard2 is set to 400MHz.
> And for cubietruck the lowest limit is 60MHz. This means that the
> "fantasy" governor on cubieboard2 will run the idle system at 384MHz,
> but on cubietruck that would be supposedly 60MHz. Funny, isn't it?
>
> This is a big freaking mess.
>
No argument there.
>
> > Also, perhaps the minimum setting should be 1GHz at boot time and not
> > dropped until the UI is up and running, since this affects the overall
> boot
> > speed by quite a bit, and that's the first impression any user gets of a
> > distro -- how long it takes to get my login prompt or splash screen.
>
> Does it mean that currently the "ondemand" / "fantasy" / "interactive"
> governors are also responsible poor boot time? That's one more reason
> to do something about this.
>
I don't know about fantasy, but I do know that boot times are faster with
interactive than ondemand given the same 60 MHz minimum clock frequency
setting (based on the boot log time stamps); boot times don't change much
switching from interactive to performance.
>
> I tried to look into this stuff and run some tests on cubieboard2 and
> cubietruck using the current stage/linux-sunxi-3.4 branch.
>
> As Michal Suchanek mentioned earlier in this thread, we have AXP209
> power management chip. And it has some interesting registers (REG 00H
> and REG 01H):
> http://linux-sunxi.org/AXP209#REG_00H:_Power_input_status
> The values of these registers are exposed to the userspace via
> /sys/devices/platform/sunxi-i2c.0/i2c-0/0-0034/axp20_regs
> AXP209 also has IRQs for the notifications about plugging/removing
> different power sources: ACIN (power plug), VBUS (miniusb) and LiPo
> battery. So looks like the hardware mostly provides all that we need.
>
> Now the results of
Re: [linux-sunxi] [PATCH] wireless:rtl8188eu: add usb id for rtl8188etv
On Thursday, January 2, 2014 4:43:27 PM UTC-5, Luc Verhaegen wrote: > > On Thu, Jan 02, 2014 at 12:51:27PM -0800, Patrick Wood wrote: > > Searching for "0x0179" on this list shows this is the third time this > > exact patch has been submitted. Since this is something that's > > already in the upstream code, I don't see why it was never applied. > > Ouch :( > +1 Pat -- 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/groups/opt_out.
Re: [linux-sunxi] FOSDEM 2014, what do we want
On Wednesday, January 1, 2014 8:13:12 AM UTC-5, Tim Fletcher wrote: > > On 01/01/14 13:06, Oliver Schinagl wrote: > > Hey list, > > > > as you should remember, I applied for FOSDEM and got accepted. As I'm > > working on the presentation, I am curious what you guys think others > > would be interested in hearing about. > > > > So please, pretend this is a blank slate, and suggest whatever should be > > mentioned during FOSDEM and I will try to take that into account. > > I think that a lot of people aren't aware of how far the sunxi project > has come towards making the allwinner SoCs well supported and part of > the main line kernel. I know I wasn't aware of it until I read Rich's > blog post about the cubietruck and KVM. > > Being able to point people towards a few good cheap boards they can get > Linux up and running on quickly and easily would help too. Too many (to > my mind) of the postings on the debian-arm list are about bodging debian > onto ancient arm5 devices. > > I think you should put up a slide or two comparing the AW SoCs with other low-cost, high-integration ARM SoCs out there, like Rockchip, Broadcom, AMLogic, and maybe Freescale. Include things like HW features, current level of FOS support (or lack thereof) for IP blocks, level of kernel support (or lack thereof) from the manufacturer, status of reverse-engineered blocks, etc. Also include a "high-end" SoC like Tegra or OMAP as a reference. Rhombus Tech has some useful information comparing different SoCs. -- 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/groups/opt_out.
[linux-sunxi] [PATCH] wireless:rtl8188eu: add usb id for rtl8188etv
Searching for "0x0179" on this list shows this is the third time this exact patch has been submitted. Since this is something that's already in the upstream code, I don't see why it was never applied. -- 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/groups/opt_out.
Re: [linux-sunxi] Re: A good SD card image for A10-OLinuXino-Lime?
On Wednesday, January 1, 2014 5:54:20 PM UTC-5, Siarhei Siamashka wrote: > > I myself still see no good reason for using any governor other than > "performance" when running with a wall connected power plug. Poor > default cpufreq behaviour is a major performance pitfall for > inexperienced users and it totally kills desktop responsiveness. > > We may introduce a new customized cpufreq governor and set it by > default. The users can always change the cpufreq settings to whatever > they want. > > Moreover, as a temporary solution, I would probably even advocate > setting the "performance" cpufreq governor for linux-sunxi kernels > by default (for the linux defconfigs). Do we have many tablet users, > who are running linux instead of android and also need good battery > life (have no usb ports or chargers nearby for providing power)? > > I believe that a minimum setting of 408MHZ with the "interactive" governor works quite well. This governor raises the CPU clock much faster than ondemand, and 408MHz seems to be a spot where the SoC will power down a lot of blocks when idle. Also, perhaps the minimum setting should be 1GHz at boot time and not dropped until the UI is up and running, since this affects the overall boot speed by quite a bit, and that's the first impression any user gets of a distro -- how long it takes to get my login prompt or splash screen. -- 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/groups/opt_out.
Re: [linux-sunxi] fails to get TouchScreen ft5x_ts working on CB2/A20
I'm thinking you may need to remove the "IRQF_TRIGGER_FALLING |" for the A20. On Tuesday, December 31, 2013 8:49:18 AM UTC-5, Carlo Caione wrote: > > On Tue, Dec 31, 2013 at 11:35 AM, > > wrote: > > Hi, > > > > Upon branch pat-3.4.43 (based on sunxi-3.4), I got touchscreen > ft5406(9.7 > > inch ctp) working on my CB1/A10. But I can't do it on my CB2/A20. > > > > dmesg shows: > > [ 68.884468] ft5x_ts_probe begin=. > > [ 68.888515] touch panel gpio addr: = 0xf0154800 > > [ 68.892489] ft5x_ts_probe : client->addr = 56. > > [ 68.895990] ft5x_ts_probe : client->addr = 56. > > [ 68.904922] input: ft5x_ts as > > /devices/platform/sunxi-i2c.1/i2c-1/1-0038/input/input4 > > [ 68.911271] ctp_set_irq_mode: config gpio to int mode. > > [ 68.917188] ctp_set_irq_mode, 225: gpio_int_info, port = 8, port_num > = 7. > > [ 68.928675] INTERRUPT CONFIG > > [ 68.934752] setting trigger mode 2 for irq 60 failed > > (gic_set_type+0x0/0xd8) > > [ 68.952622] ft5x_ts 1-0038: ft5x_ts_probe: request irq failed > > > The problem is that apparently GIC in not able to cope with IRQs with > type different from IRQ_TYPE_LEVEL_HIGH and IRQ_TYPE_EDGE_RISING. See: > > http://lxr.missinglinkelectronics.com/linux/drivers/irqchip/irq-gic.c#L202 > > Try to change the interrupt type in the DTS to type 1 or 4. > > Best, > > -- > Carlo Caione > -- 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/groups/opt_out.
Re: [linux-sunxi] Sun8i (A23) spotted in the wild.
The boot_clock in the .fex file is given as 1008. On Friday, December 20, 2013 8:46:32 PM UTC-5, Runzhong Yi wrote: > > It could be possible since A23 can run as high as 1.8Ghz. If the core > run as 1650MHz then this mean the dram clock is 1/3 of the core clock. > > 2013/12/21 Patrick Wood >: > > Am I reading the fex file correctly? The DRAM is running at 552 MHz? > > > > > > On Friday, December 20, 2013 9:08:07 AM UTC-5, Luc Verhaegen wrote: > >> > >> On Thu, Dec 19, 2013 at 12:32:24AM +0100, Luc Verhaegen wrote: > >> > I tried to order myself one of those cheap Q88 tablets with an A13 > just > >> > now. Big was my surprise when i got it and popped it open, as i was > >> > staring at an A23. > >> > > >> > Bad news all round really: > >> > * fully locked down android, no root, no adb. I will give another > root > >> > exploit a try tomorrow. > >> > * our fel utility does not work. > >> > * we of course have no code for u-boot or linux yet. > >> > * nothing on the serial port. > >> > > >> > This device is a really serious GPL violator. They even went as far > as > >> > removing all open source licenses from the About section under > android > >> > settings. > >> > > >> > What we do know: > >> > * two obvious serial pads (which are not sending out anything atm) > >> > * it tries to boot off SD when a likely candidate is there > >> > * it has a 3.4.39 kernel, and the /proc/config.gz was world readable > >> > (this is where the string sun8i was found). > >> > * HW is an A23 which is a bga, with an AXP223 companion > >> > > >> > Board picture is available at the device page: > >> > http://linux-sunxi.org/Ippo_q8h > >> > > >> > Luc Verhaegen. > >> > >> In the meantime, adb access has been figured out and the device has > been > >> rooted. All is documented on the page. > >> > >> script.bin has been fetched, and is available from: > >> http://dl.linux-sunxi.org/users/libv/ippo_q8h/ > >> > >> 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...@googlegroups.com . > > For more options, visit https://groups.google.com/groups/opt_out. > -- 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/groups/opt_out.
Re: [linux-sunxi] Sun8i (A23) spotted in the wild.
Am I reading the fex file correctly? The DRAM is running at 552 MHz? On Friday, December 20, 2013 9:08:07 AM UTC-5, Luc Verhaegen wrote: > > On Thu, Dec 19, 2013 at 12:32:24AM +0100, Luc Verhaegen wrote: > > I tried to order myself one of those cheap Q88 tablets with an A13 just > > now. Big was my surprise when i got it and popped it open, as i was > > staring at an A23. > > > > Bad news all round really: > > * fully locked down android, no root, no adb. I will give another root > > exploit a try tomorrow. > > * our fel utility does not work. > > * we of course have no code for u-boot or linux yet. > > * nothing on the serial port. > > > > This device is a really serious GPL violator. They even went as far as > > removing all open source licenses from the About section under android > > settings. > > > > What we do know: > > * two obvious serial pads (which are not sending out anything atm) > > * it tries to boot off SD when a likely candidate is there > > * it has a 3.4.39 kernel, and the /proc/config.gz was world readable > > (this is where the string sun8i was found). > > * HW is an A23 which is a bga, with an AXP223 companion > > > > Board picture is available at the device page: > > http://linux-sunxi.org/Ippo_q8h > > > > Luc Verhaegen. > > In the meantime, adb access has been figured out and the device has been > rooted. All is documented on the page. > > script.bin has been fetched, and is available from: > http://dl.linux-sunxi.org/users/libv/ippo_q8h/ > > 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/groups/opt_out.
