Re: [linux-sunxi] Nintendo NES runs on Allwinner R16
2016-11-06 16:42 GMT+03:00 Icenowy Zheng : > > The only hackable interface found is re-solder a NAND ;-) It has testpads on PCB, so there is hope for FEL and UART. Nintendo most likely flashes NAND using standard and known Allwinner's ways, I would be surprised to see if there is something unusual. -- 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] Guideline for Xen on Cubietruck
2016-06-20 12:16 GMT+03:00 dlbp : > Hello to everybody! > Hi, > I have a Cubietruck and i need to setup an hypervisor Xen. > I need to mount all system on a SD card and i don't want touch the NAND > memory. > > Are there some guidelines fot this aim?? > Read the Xen wiki: http://wiki.xen.org/wiki/Xen_ARMv7_with_Virtualization_Extensions/Allwinner It has links to these guides: https://mirage.io/wiki/xen-on-cubieboard2 http://www.sourcediver.org/blog/2014/06/19/running-arch-linux-arm-with-xen-on-cubieboard-2/ If I remember correctly, this did work around 2014, I had cubietruck running Xen for couple weeks. > > Thanks > BR, Dmitriy Beykun -- 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] random decryption errors with sun4i-ss on dm-crypt
2016-02-17 16:39 GMT+03:00 : > Hi > Hello, > > Any suggestions? > Please, use the scripts/get_maintainer.pl script to get the maintainers of driver you have problems with and notify them about the bug. Author of sun4i-ss might not read this mailing list. Best Regards, Dmitriy Beykun -- 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] A20: move from kernel 3.4.10x to 4.2.x - will MALI work?
2015-09-23 7:04 GMT+03:00 Siarhei Siamashka : > > > 2. Somebody needs to adapt the Mali kernel driver to sunxi >hardware. It is not too difficult and I can do this myself >or provide some assistance. But I don't feel very motivated >at the moment :-) > 4. Everyone needs to understand that a patched kernel would >be required (to add the Mali driver and also update the >dts/dtsi files with the description of Mali hardware). > > example of patched mali sources for DT support and mainline is here https://github.com/tobiasjakobi/linux-odroid/commits/odroid-4.0.y/drivers/gpu/arm/mali https://github.com/tobiasjakobi/linux-odroid/blob/odroid-4.0.y/arch/arm/boot/dts/exynos4412-odroid-common.dtsi#L673 > -- > Best regards, > Siarhei Siamashka BR, Dmitriy Beykun -- 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] Banana pi BPI-M2 uboot 2015-7 and kernel 4.1.6 test
2015-08-28 14:09 GMT+03:00 lion wang : > github: https://github.com/bpi-sinovoip > Is there any chance for this to stop? https://github.com/BPI-SINOVOIP/BPI-Kernel4.0/commits/master/linux-4.0.2 https://github.com/BPI-SINOVOIP/BPI-Mainline-kernel/commits/master You've uploaded your presumably fixed 4.x kernel, but without any previous commits made to it. Doing things like this make figuring out what you've changed there very hard. Please, don't delete original .git/ from the kernel, make branches and proper commits. BR, Dmitriy Beykun -- 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] CedarXPlayer IStreamSource issue
2015-08-27 13:51 GMT+03:00 Dharmesh Patel : > Hello, > Hello, > > I have requirement to play WiFi display stream through native GPU renderer > player(CedarXPlayer) instead NUPlayer in Android. > This mailing list is mainly about native linux on sunxi devices. > I have tried it with CedarXPlayer but got "cedar demuxer open error" error > message. > Can anyone help me to resolve the issue? > > Error Log:- > > D/cedarx_demux( 1293): cedarx_demux_create: 0x0 > E/DemuxStreammingSource_Component( 1293): cedar demuxer open error > E/CDX_Player( 1293): 3.create demux error! -1 > > Note:- I am working on allwinner a20 based custom board running on Android. > Contact your devboard manufacturer/Allwinner for Android BSP support. -- 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] CSR8510 A10 BLE dongle driver for A20 humming board
2015-08-12 8:55 GMT+03:00 Nithin Chakravarthy : > here kernel log > <6>usb 5-1: new full-speed USB device number 2 using sw-ohci > <3>bluetooth: exports duplicate symbol baswap (owned by kernel) > [ 94.643972] bluetooth: exports duplicate symbol baswap (owned by kernel) > <3>bluetooth: exports duplicate symbol baswap (owned by kernel) > [ 94.661251] bluetooth: exports duplicate symbol baswap (owned by kernel) > > whats is meant by "exports duplicate symbol baswap (owned by kernel)"? > Means exactly what is said - some module tries to export symbol that was already exported. > how can i solve this > Use kernel and modules that do not clash with each other. Compile and use https://github.com/linux-sunxi/linux-sunxi/tree/stage/sunxi-3.4 (read wiki http://linux-sunxi.org/Linux_Kernel) > > When I tried to insert bfusb.ko module. I got some error > [ 273.895355] bluetooth: exports duplicate symbol baswap (owned by kernel) > FATAL: Error inserting btusb > (/lib/modules/3.4.61+/kernel/drivers/bluetooth/btusb.ko): Invalid module > format > > > You are trying to insert module that was not meant to be used with your "3.4.61+". You should never try to insert modules from different kernel versions unless you really know what you are doing. -- 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] CSR8510 A10 BLE dongle driver for A20 humming board
2015-08-11 17:13 GMT+03:00 Nithin Chakravarthy : > Hi, > Hi, > Is there any way to configure BLE device. > BLE works okay only with modern kernels (3.18+). Before that it had many problems starting from missing/wrongly implemented features ending with soft lockups. -- 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] openwrt finally released for sunxi
2015-06-24 22:31 GMT+03:00 Zoltan HERPAI : > Dmitriy B. wrote: > >> 2015-05-25 10:54 GMT+03:00 Benjamin Henrion > zoo...@gmail.com>>: >> >> Openwrt is finally released for sunxi: >> >> https://downloads.openwrt.org/chaos_calmer/15.05-rc1/sunxi/generic/ >> >> We had to wait because otherwise there were only daily builds >> available. >> >> If you use it, feel free to report bugs. >> >> >> 1) Cubietruck defconfig seems to miss something needed for onboard >> broadcom to power up. >> Anyone got success running its wifi? >> 2) A20 boards device trees seem to include cryptodev, which was proven to >> have HW bug on all Allwinner SoCs, fixed in A83. grep linux-sunxi mailing >> list for answers from Kevin in crypto hw acceleration patch threads. Does >> the version of crypto driver included in openwrt have updated patch? Since >> we have 3.1x here with patches from 4.x backported, this issue might be >> easily missed. >> >> Apart from Cubietruck, I've got ok results from A10 boards, nothing >> seriously frustrating, almost everything works out of the git build. >> > Hi Dmitriy, > > 1) I don't have a cubietruck so this wasn't tested - IIRC it was left off > where brcmfmac would've needed the SDIO code built as well. Patches are > most welcome. :) > > If brcmfmac SDIO is selected, driver can see the chip, but can't load the firmware - its missing from openwrt firmware packages. When I added brcmfmac43362-sdio.bin by hand from linux-firmware.git driver couldnt load the firmware, probably missing patches from upstream for brcm43362 support or some sunxi SDIO work from Hans. > 2) I'll check this one, can't recall the exact series, probably it was a > v4 or a v5, based off the timestamps. The last one I saw around the crypto > driver is the v9 patchset, is that the one You're referring to? > Yes, see Priit Laes answer. > > Thanks, > Zoltan H > > Best Regards, Dmitriy Beykun -- 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] openwrt finally released for sunxi
2015-05-25 10:54 GMT+03:00 Benjamin Henrion : > Openwrt is finally released for sunxi: > > https://downloads.openwrt.org/chaos_calmer/15.05-rc1/sunxi/generic/ > > We had to wait because otherwise there were only daily builds available. > > If you use it, feel free to report bugs. > 1) Cubietruck defconfig seems to miss something needed for onboard broadcom to power up. Anyone got success running its wifi? 2) A20 boards device trees seem to include cryptodev, which was proven to have HW bug on all Allwinner SoCs, fixed in A83. grep linux-sunxi mailing list for answers from Kevin in crypto hw acceleration patch threads. Does the version of crypto driver included in openwrt have updated patch? Since we have 3.1x here with patches from 4.x backported, this issue might be easily missed. Apart from Cubietruck, I've got ok results from A10 boards, nothing seriously frustrating, almost everything works out of the git build. > > This is based on a 3.18 lts kernel. > > -- > Benjamin Henrion > FFII Brussels - +32-484-566109 - +32-2-4148403 > "In July 2005, after several failed attempts to legalise software > patents in Europe, the patent establishment changed its strategy. > Instead of explicitly seeking to sanction the patentability of > software, they are now seeking to create a central European patent > court, which would establish and enforce patentability rules in their > favor, without any possibility of correction by competing courts or > democratically elected legislators." > > -- > 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. > Best Regards, Dmitriy Beykun -- 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: openwrt finally released for sunxi
2015-05-27 12:57 GMT+03:00 Dmitriy B. : > 2015-05-27 12:31 GMT+03:00 Juan Font : > >> Hi, >> >> > Hi, > > >> I'm trying to build it for Cubietruck (make image PROFILE=Cubietruck) >> using the ImageBuilder ( >> https://downloads.openwrt.org/chaos_calmer/15.05-rc1/sunxi/generic/OpenWrt-ImageBuilder-15.05-rc1-sunxi.Linux-x86_64.tar.bz2) >> but it seems to have problems when looking for uboot: >> >> Downloading file:packages/base/kmod-pppox_3.18.11-1_sunxi.ipk. >> Installing uboot-envtools (2014.10-2) to root... >> Downloading file:packages/base/uboot-envtools_2014.10-2_sunxi.ipk. >> Unknown package 'uboot-sunxi'. >> Installing uboot-sunxi-Cubietruck (2015.01) to root... >> Downloading file:packages/base/uboot-sunxi-Cubietruck_2015.01_sunxi.ipk. >> Installing uci (2015-04-09.1-1) to root... >> Downloading file:packages/base/uci_2015-04-09.1-1_sunxi.ipk. >> Configuring kmod-scsi-core. >> Configuring kmod-ata-sunxi. >> Configuring opkg. >> Configuring kmod-nls-base. >> Configuring kmod-usb-core. >> ... >> ... >> Configuring ip6tables. >> Configuring uboot-sunxi-Cubietruck. >> Configuring ppp-mod-pppoe. >> Collected errors: >> * opkg_install_cmd: Cannot install package uboot-sunxi. >> Makefile:129: recipe for target 'package_install' failed >> make[2]: *** [package_install] Error 255 >> make[2]: Leaving directory >> '/home/mads/juanfont/isg/OpenWrt-ImageBuilder-15.05-rc1-sunxi.Linux-x86_64' >> Makefile:100: recipe for target '_call_image' failed >> make[1]: *** [_call_image] Error 2 >> make[1]: Leaving directory >> '/home/mads/juanfont/isg/OpenWrt-ImageBuilder-15.05-rc1-sunxi.Linux-x86_64' >> Makefile:178: recipe for target 'image' failed >> make: *** [image] Error 2 >> >> >> >> Any idea? >> > > Can confirm, have exactly the same error. Going to try to build from > source. > Building from source helps, I've got working system. If you have archlinux as a build machine, you need to apply https://patchwork.ozlabs.org/patch/475983/ > > >> >> Thanks, >> >> Juan >> >> >> On Monday, May 25, 2015 at 9:54:11 AM UTC+2, Benjamin Henrion wrote: >>> >>> Openwrt is finally released for sunxi: >>> >>> https://downloads.openwrt.org/chaos_calmer/15.05-rc1/sunxi/generic/ >>> >>> We had to wait because otherwise there were only daily builds available. >>> >>> If you use it, feel free to report bugs. >>> >>> This is based on a 3.18 lts kernel. >>> >>> -- >>> Benjamin Henrion >>> FFII Brussels - +32-484-566109 - +32-2-4148403 >>> "In July 2005, after several failed attempts to legalise software >>> patents in Europe, the patent establishment changed its strategy. >>> Instead of explicitly seeking to sanction the patentability of >>> software, they are now seeking to create a central European patent >>> court, which would establish and enforce patentability rules in their >>> favor, without any possibility of correction by competing courts or >>> democratically elected legislators." >> >> > Best Regards, > Dmitriy Beykun > > Best Regards, Dmitriy Beykun -- 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: openwrt finally released for sunxi
2015-05-27 12:31 GMT+03:00 Juan Font : > Hi, > > Hi, > I'm trying to build it for Cubietruck (make image PROFILE=Cubietruck) > using the ImageBuilder ( > https://downloads.openwrt.org/chaos_calmer/15.05-rc1/sunxi/generic/OpenWrt-ImageBuilder-15.05-rc1-sunxi.Linux-x86_64.tar.bz2) > but it seems to have problems when looking for uboot: > > Downloading file:packages/base/kmod-pppox_3.18.11-1_sunxi.ipk. > Installing uboot-envtools (2014.10-2) to root... > Downloading file:packages/base/uboot-envtools_2014.10-2_sunxi.ipk. > Unknown package 'uboot-sunxi'. > Installing uboot-sunxi-Cubietruck (2015.01) to root... > Downloading file:packages/base/uboot-sunxi-Cubietruck_2015.01_sunxi.ipk. > Installing uci (2015-04-09.1-1) to root... > Downloading file:packages/base/uci_2015-04-09.1-1_sunxi.ipk. > Configuring kmod-scsi-core. > Configuring kmod-ata-sunxi. > Configuring opkg. > Configuring kmod-nls-base. > Configuring kmod-usb-core. > ... > ... > Configuring ip6tables. > Configuring uboot-sunxi-Cubietruck. > Configuring ppp-mod-pppoe. > Collected errors: > * opkg_install_cmd: Cannot install package uboot-sunxi. > Makefile:129: recipe for target 'package_install' failed > make[2]: *** [package_install] Error 255 > make[2]: Leaving directory > '/home/mads/juanfont/isg/OpenWrt-ImageBuilder-15.05-rc1-sunxi.Linux-x86_64' > Makefile:100: recipe for target '_call_image' failed > make[1]: *** [_call_image] Error 2 > make[1]: Leaving directory > '/home/mads/juanfont/isg/OpenWrt-ImageBuilder-15.05-rc1-sunxi.Linux-x86_64' > Makefile:178: recipe for target 'image' failed > make: *** [image] Error 2 > > > > Any idea? > Can confirm, have exactly the same error. Going to try to build from source. > > Thanks, > > Juan > > > On Monday, May 25, 2015 at 9:54:11 AM UTC+2, Benjamin Henrion wrote: >> >> Openwrt is finally released for sunxi: >> >> https://downloads.openwrt.org/chaos_calmer/15.05-rc1/sunxi/generic/ >> >> We had to wait because otherwise there were only daily builds available. >> >> If you use it, feel free to report bugs. >> >> This is based on a 3.18 lts kernel. >> >> -- >> Benjamin Henrion >> FFII Brussels - +32-484-566109 - +32-2-4148403 >> "In July 2005, after several failed attempts to legalise software >> patents in Europe, the patent establishment changed its strategy. >> Instead of explicitly seeking to sanction the patentability of >> software, they are now seeking to create a central European patent >> court, which would establish and enforce patentability rules in their >> favor, without any possibility of correction by competing courts or >> democratically elected legislators." > > Best Regards, Dmitriy Beykun -- 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] sunxi-kms driver
2015-04-10 23:04 GMT+03:00 David Lanzendörfer : > Hi > I'm right now building a KMS driver using the HDMI interface as primary > connector Nice, Are you doing this while working at Allwinner? Whats the status of the driver and are you planning to make it to mainline? (though, looking at code, that will take time - there are disp/osal leftovers all over the place). Also copyright like this looks weird: " * Copyright (C) 2015-2020 Allwinner Technology Co., Ltd." Living in the future? :) Best Regards, Dmitriy Beykun -- 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] r3p2 version of the Mali driver A20
2015-03-18 11:36 GMT+03:00 Siarhei Siamashka : > On Tue, 17 Mar 2015 18:14:59 -0700 (PDT) > "@lex" wrote: > > > Hi, > > > > I would like to have r3p2 version of the Mali driver for my cb2, and i > have > > followed the sunxi-linux instructions and ended up with r3p0. > > The r3p0 mali driver should provide you with a functional OpenGL ES > implementation. > > > i have found the tutorial to use the recent mali r3p2 but i am not sure > how > > to proceed. > > I am using sunxi-linux kernel 3.4.103 but i don`t know if it has r3p2 > mali > > driver, can someone help how to get r3p2 compiled? > > > > And how to get mali-r3p2-support branch of the xf86-video-fbturbo xorg? > > > > Appreciate any help. > > The r3p0 and r3p2 mali binary blobs are a little bit buggy. Moreover, > they are buggy in different ways and require different sets of > workarounds. "Officially" supporting them both would be an extra > hassle. Moving exclusively to r3p2 is not totally painless either. > There needs to be a very good reason to do this work. > > Any chances to test r4pX and r5p0 coming from ODROID community? > -- > Best regards, > Siarhei Siamashka Best Regards, Dmitriy Beykun -- 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: Directions for video engine support (CedarX)
2015-03-16 20:22 GMT+03:00 Simos Xenitellis : > > It should be possible to retrofit the libvdecodec.so/libvencoder.so > libraries > (found on https://github.com/allwinner-zh) into an existing Android image > Those *.so are armhf linux native. Android is armel linux with bionic. -- 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] Observations about the Neal Peacock PengPod1000 Tablets
2015-02-19 20:20 GMT+03:00 Siarhei Siamashka : > nobody has any idea what > you are talking about and what this "Neal Peacock PengPod1000" > device might possibly look like. PengPod had own wiki in 2012 where all info was located. Thats why users can't get help now. By hardware it is a rebadged A10 device, so it is easy to run anything there. -- 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] Communication with Allwinner
2015-02-15 21:25 GMT+03:00 Felipe Sanches : > What are the violation claims? Is it documented somewhere so that I can > learn more about the issue? > http://linux-sunxi.org/GPL_Violations -- 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: DMAEngine and audio support on A20
Been thinking to bring this up for a long time ago. So here we go. > These days, we're three of us doing some work, including fixing > existing bugs, maintaining the code, etc. > > That, and I'm not sure that focusing on a five years old SoCs while > ignoring any new SoC is the right policy. linux-sunxi did that with > the A31, look at where it is now. > I don't see thousands of A31 boards users eagerly waiting for mainline. > Sure, the A10 works > great. How many A10-based devices went out last year? > Support is about having a active userbase, not new devices everyday. > BUT, it's true that we still have a partial support for the older > SoCs. There's still no display support, no audio support. And anyone > is very welcome to contribute or help in that effort. > > But unless you're giving us our paycheck, you don't get to order us > what to work on and what not. > Honestly, this approach is very wrong on many levels (don't ask why) and please, speak on behalf of free-electrons only, if you have paycheck from them. No one is ordering you anything, this is a public ML about linux for sunxi, and Stefan expressed his point of view as a A10/A20 user. Maybe some one will pick up Turl's work. > But there's also two things to consider: > - People with A31/A23/A80 have no other alternative than the > Allwinner kernel. Do we really want to leave these users out in > the cold? I don't. > These people chose that way by buying those and you (and F-E) are not going to provide same level of feature coverage in mainline anyways (because NDAs for some of the new IPs, PVR, very short lifecycle of the SoC and etc.). > - Adding a new SoC support is pretty cheap And sort of useless without thousands of human hours figuring out new SoC. Best Regards, Dmitriy Beykun -- 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: RKM MK80
2014-12-11 15:39 GMT+03:00 Vladimir Komendantskiy : > Ditmar, > > I don't have the device yet and I'm evaluating it's usability for > development. > Sorry to disappoint you, but if you are going to use it for production development or something with commercial value, please contact Allwinner directly and order yourself BSP support & A80 Optimus devboard. You can also try to contact Merrii guys, I had some experience with them. Don't try to use available on the market consumer devices as devkits, especially, when using such modern SoCs like A80. IIRC, linux-sunxi support for A80 is sort of limited and implemented only in mainline kernel, 3.4 wont be updated for A80 because of huge differences in new AW BSPs with our legacy 2011-ish code. If you just want to play with A80 SoC, buy one of the A80 Optimus board clones from pcduino, merrii, cubietech and etc. They provide some basic bsp and images. -- 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] Availability of A80 boards to developers
> > I have the impression that Eva assumed we knew each other's efforts as she > mentioned something about "commits" which I did not understand at the time. > No idea if its connected, but Cubietech guys sent linux-sunxi boards two times, cb2 and ct, but that was more than half a year ago. Also don't forget that wild lkcl might appear and Eva might still think that rhombus-tech = linux-sunxi. -- 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] sunxi-3.4: sunxi_nand problem with Hynix H27UCG8T2BTR 8GB NAND
2014-08-08 16:09 GMT+04:00 Arnd Gronenberg : > Hello Dmitriy, > > thanks for the detailed reply! You are welcome. It is still in development, here you can check latest branch >> https://github.com/bbrezillon/linux-sunxi/commits/sunxi-nand-pre-v4-fixed >> > Which modules / options should I enable? Standard MTD/NAND/UBI/UBIFS things and nand-sunxi driver. Config options: MTD MTD_NAND MTD_NAND_SUNXI MTD_UBI UBIFS_FS > Where may I find the special kernel patch? Will it honour the existing bad > blocks? Comment https://github.com/bbrezillon/linux-sunxi/blob/sunxi-nand-pre-v4-fixed/drivers/mtd/nand/nand_base.c#L3274 and next line with goto statement (sorry I dont have my IRC logs/kernels around for proper diff). You will still have your "real" bad blocks, but the ones marked by mistake because of differences in OOB between mainline and sunxi-nand from 3.4 will be no longer marked bad. Then you will be able to use MTD aware file systems like UBI/UBIFS. I know the list of bad blocks from initial load of sunxi-nand... > Current driver will scan NAND on each boot for badblocks anyway, so knowledge from old sunxi-nand is useless and also old sunxi-nand had an offset in numbering, so bad block numbers are not equal to ones in the mainline driver, which counts them by MTD standards > I assume that flash_erase is the stock version from mtd-utils (from > http://www.linux-mtd.infradead.org/). Yes, also use UBI/UBIFS tools from there. > -- > > Arnd Gronenberg, a...@gronenberg.com, DJ9PZ / AB2QP > Best Regards, Dmitriy Beykun -- 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] sunxi-3.4: sunxi_nand problem with Hynix H27UCG8T2BTR 8GB NAND
2014-08-04 1:43 GMT+04:00 Arnd Gronenberg : Hello, > > Question: Does it make sense to fix sunxi_nand for sunxi-linux 3.4? If you want to run android, then yes. > How is this code implemented in the current mainline linux? It is still in development, here you can check latest branch https://github.com/bbrezillon/linux-sunxi/commits/sunxi-nand-pre-v4-fixed Be prepared to see bugs, like ubifs dying after a reboot and badblocks appearing out of nowhere (false positive ones, of course). Also OOB structure is completely incompatible with old sunxi_nand OOB and you will need to #flash_erase /dev/mtdX 0 0 -N at least once with a special kernel patch (not included in the branch above), otherwise, new mtd driver will detect all blocks marked as bad. I'm adding Boris to CC, talk to him if you want to discuss/test mainline driver. I think it is matter of couple more testing iterations to get it finally working. > If there is interest to fix sunxi_nand, I may have a look at the required > changes... There is (android users), but right now for a system not related to multimedia, you can run mainline just fine, so there is more interest in having a proper mainlined mtd driver, than sunxi_nand. Anyway, if you have tested patches for sunxi_nand, feel free to send them here. > -- > > Arnd Gronenberg, a...@gronenberg.com, DJ9PZ / AB2QP Best Regards, Dmitriy Beykun -- 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: A20 boot0/boot1 info
2014-07-23 19:46 GMT+04:00 Ivan Kozic : > > Still I'd be quite interested in trying out this WiP NAND uboot - do you > know from which repo can I fetch the source/binaries? Maybe it's time that > I get familiar with uboot... > Here are latest versions from Yuq. Boris Brezillon also tried to do this on mainline linux, search for discussion somewhere around, it was not long ago. u-boot https://github.com/yuq/u-boot-sunxi/commits/sunxi-current linux https://github.com/yuq/sunxi-nfc-mtd/commits/master Just dont get your hopes up, Yuq tested this only on his board which had interesting target - ~10MB Qt application launching as /sbin/init, also you might have different NAND and have different parameters (timings, blocksize, etc.). If I remember correctly, his u-boot generates .img ready for livesuit with help of bunch of custom scripts, these will also need modification. Best Regards, Dmitriy Beykun -- 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] Booting SPI serial flash in A13
2014-06-12 13:30 GMT+04:00 Henrik Nordström : > ons 2014-06-11 klockan 23:42 -0700 skrev Nohee Park: > > I have to use the SPI serial flash boot mode in A13. > > Is there the SPI serial flash boot mode implemented int A13 ? > > Th A13 supports SPI boot, but we do not have a known working SPI boot > loader to store on the SPI flash. > What about this one a13_source_1.5.tar.gz/a13_source_1.5/source/lichee/tools/pack/chips/sun5i/eGon/storage_media/spinor/boot0.bin ? it is from dragon .img packer that comes with a13_source_1.5.tar.gz that was distributed by some german company last year. Looks like you can select spinor in dragon config files. Regards > Henrik Best Regards, Dmitriy Beykun -- 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: Booting 3.15 kernel on Cubietruck
2014-05-24 7:57 GMT+04:00 jonsm...@gmail.com : > Can anyone verify for me that serial console has ever worked on the > A20 device tree kernels? Am I looking for breakage or has console > never worked at all? > I ran mainline on my cubietruck couple months ago. Had some problems with booting up (had absolutely no serial output even with earlyprintk and kernel crashed somewhere in between), had to use Hans's defconfig and u-boot settings. With them, everything worked (except occasional hangs after 6-7 hours compiling stuff, but I think that had something to do with MBUS and memory, for example, running 4x linpacks for half a day would crash it 100%). Also, if I remember correctly, PSU that I used running cubietruck on 3.4 did not handle it running mainline, cubietruck hang after 10-15 minutes of hard load, after throwing out the phone charger I've used as a PSU for cubietruck and using an old ATX PSU, that problem was gone. -- 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] State of MTD driver
2014-05-06 21:08 GMT+04:00 Stefan Monnier : > I remember discussion of an MTD driver for sunxi a while back. > I can't find it in sunxi-devel, tho. Is it only available for > sunxi-3.4, or is there a branch for this MTD driver that works on newer > (DT-based) kernels? > Boris Brezillon developed such driver from the sources of 3.4 one. I added him to cc. He tested it on Cubietruck board. You can check it out there http://lists.infradead.org/pipermail/linux-mtd/2014-March/052550.html and as cc to our mailing list (use search). I think driver got stuck before mainline because of the trouble of getting needed MTD framework changes pushed/tested. Best Regards, Dmitriy Beykun -- 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] DirectFB has poor performance in A10?
2014-04-12 14:02 GMT+04:00 Jacky Lau : > Hi, all. I run a DirectFB program on an AllWinner A10 board (1GHz with > 512MB 16bit RAM). My program is simple, it display a window and show a RGBA > png image(800x480). But the program cost about 2.5 seconds from create > window to show the image. The performance is very poor. Is it normal? > Try to search around the mailing list for Allwinner DirectFB G2D patches, IIRC someone used them with buildroot environment, but that was long ago (year+). With G2D you might be able to get better results. Best Regards, Dmitriy Beykun -- 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: Allwinner joins Linaro Digital Home Group, commits to open source chip support
> > That is not in the category of "what Linaro does". The code written at > Linaro is open and open lists discuss it. How do I discuss it when I cant even run it? > It is the vendor pushing > those NDAs, not Linaro. Joining Linaro is not going to automatically > change Allwinner's position on keeping Cedar source secret. Do we > even know for sure if Allwinner has the ability to open source it and > that Cedar is free from a third party licensing mess. > Cedar is described well enough right now at linux-sunxi and if Linaro wants - they will try to use that. If not - we will see another implementation of unusable kernelside V4L2 dec/enc with userspace part that is distributed by NDAs (look at Coda/Samsung MFC/whatever is kicking there right now. For MFC it took couple months to get it running well enough with XBMC for Exynos4). BTW, Hisilicon has never been open source friendly so why did you buy > their stuff? > I'm happy with my android there. But, its just the fact that HiSilicon spend time and money on getting mainline and 3.10.x android kernels that bothers me. Why cant I use it? No, lets say different, for exactly *who* it was made opensource? For a nice line in press release "we are now opensource"? "Not usable" - that is the picture of Linaro that I mean here as a HiSilicon device owner. Sorry if it sounds too raw, but thats the facts. :) Hope it will be different for Allwinner. By any way you slice it, I believe Allwinner joining Linaro will > improve their software offerings, not hurt them. Actually, If you had experience working with Linaro, could you please hint there that we could enjoy CSI drivers for A1x/A20, since you had/have a project in that field? As I said - everything simple was already done, even ARM PSCI is working with help from ARM employee. But things like kernelside Cedar, CSI and other multimedia stuff is missing http://linux-sunxi.org/Linux_mainlining_effort#Left_to_be_done It would be nice for Linaro to start from there, and not with rewriting what is already done. -- 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: Allwinner joins Linaro Digital Home Group, commits to open source chip support
> > Besides, why can't linux-sunxi cooperate with the Linaro people? > Everything Linaro does is on open mailing lists and servers Because its not. Try to find reference manuals for latest Exynos, HiSilicon K3V2 and other Linaro members SoCs and try to join the development, send a patch there (hint: you wont be able to. Because: NDAs, strict userlist and zero documentation). -- 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: Allwinner joins Linaro Digital Home Group, commits to open source chip support
> > For quite a few of the linaro member companies, this is really just > another consortium. They dispatch some fluff "engineers" that are > usually not too useful anywhere else, and then pat themselves on the > back that they are now actively doing the "open source" thing as well. Linaro is completely useless if company decides to go "sort of opensource/we-don't-care-about-you". Recent example is Huawei's daughter, HiSilicon joining Linaro - you cant use Linaro hisi kernel anywhere, there is just no public devices that can run it. I'm saying this as an owner of a tablet on HiSilicon K3V2. HiSilicon got their mainline and android kernel working - but no one, except themselves, can use it because u-boot/x-loader sources are closed and zero usage manuals provided. Plus Huawei got into "securityboot/drm" thing android hype and locked the bootloaders - to get the unlock code for fastboot you need to know someone from Huawei or wait 2-3 weeks for support answer (some times, they dont get what you want and you need to write two or three times until they figure out and send your request properly). Imagine what happens when 2k users of K3V2 tablets will request drm-off. I, of course, could spent a week with an osc probe seeking for UART on 45+ testpoints on my tablets 5mil pcb and then infinite amount of time figuring out their bootsequence, patch x-loader and launch it and it will probably work, but seriously, why just they don't start with basic plan/reference documentation of what they are doing and how to test/help? That is "typical Linaro" picture for me right now, and I do not expect anything interesting out of Allwinner either. I bet they will push crappy sun8i/sun9i support and couple missing drivers (as everything simple is already done) and then forget about it... Lets just hope we will not see our code with copyrights removed. > Allwinner joining linaro will only reduce Allwinners > active contributions to linux-sunxi in future. Even more - Allwinner joining Linaro will lead to less interest from other guys like Free-Electrons/RedHat. -- 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.
> > > but once i boot i got struck here. > > <6>Freeing init memory: 212K > [6.629097] Freeing init memory: 212K > <6>Write protecting the kernel text section c0008000 - c07d2000 > [6.638421] Write protecting the kernel text section c0008000 - c07d2000 > <30>systemd-udevd[165]: starting version 204 > <4>init: plymouth main process (78) killed by ABRT signal > <4>init: plymouth-splash main process (202) terminated with status 2 > <4>init: failsafe main process (225) killed by TERM signal > <4>init: plymouth-stop pre-start process (303) terminated with status 1 > You have no console or output because you are launching empty ubuntu-core, which is a minimalistic package consisting of what you need to install packages with chroot environment. It is not made to be an end user system. Mount this rootfs with your PC, chroot there and install atleast package "ubuntu-minimal". For more info, google manuals for ubuntu-core, there are plenty, both for x86 and ARM. If you don't want to make your own ubuntu from scratch with ubuntu-core as a base, just grab any latest Linaro http://releases.linaro.org/latest/ubuntu/saucy-images and have fun with everything already set up. Best Regards, Dmitriy Beykun -- 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: help with NAND access of A20 based MELE M5
2014/1/14 Rajesh Mallah > > In Android the flash is recognized as mmcblk0 . > That means that this is not a NAND flash. It is eMMC flash connected to one of the SD ports. You dont need NAND flash controller to use eMMC. -- 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: Probe deferral on AXP driver
> > [2.105938] i2c /dev entries driver > [2.114206] config i2c gpio with gpio_config api > [2.122210] incomplete xfer (0x20) > [2.129422] axp_mfd 0-0034: failed reading at 0x03 > [2.137781] [AXP20-MFD] try to read chip id failed! > [2.147226] axp_mfd: probe of 0-0034 failed with error -70 > [2.156546] i2c i2c-0: Invalid probe address 0x00 > [2.164426] I2C: i2c-0: AW16XX I2C adapter > [2.173834] i2c i2c-1: Invalid probe address 0x00 > [2.181672] hub 1-1:1.0: USB hub found > [2.188584] I2C: i2c-1: AW16XX I2C adapter > [2.196185] hub 1-1:1.0: 4 ports detected > [2.204120] i2c i2c-2: Invalid probe address 0x00 > [2.211998] I2C: i2c-2: AW16XX I2C adapter > [2.219840] [ccu-err] clk_enable: invalid handle > [2.228848] i2c i2c-3: Invalid probe address 0x00 > [2.236737] I2C: i2c-3: AW16XX I2C adapter > [2.244633] [ccu-err] clk_enable: invalid handle > [2.254376] i2c i2c-4: Invalid probe address 0x00 > [2.262184] I2C: i2c-4: AW16XX I2C adapter Yes, that is rather interesting, AXP fails in your log. You have something wrong with I2C bus, are you sure that you have everything right in script.bin? I'm talking about these parameters, I2C muxing https://github.com/linux-sunxi/sunxi-boards/blob/master/sys_config/a20/cubieboard2.fex#L122 addr/id for AXP https://github.com/linux-sunxi/sunxi-boards/blob/master/sys_config/a20/cubieboard2.fex#L895 Also, CSI driver wants these parameters of AXP to be working: https://github.com/linux-sunxi/sunxi-boards/blob/master/sys_config/a20/cubieboard2.fex#L516 Thats why it throws error. I'm linking cubieboard because it is in known working state, as I understand, you have your own custom board. -- 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: Probe deferral on AXP driver
2014/1/11 jonsm...@gmail.com > I am testing a beta armhf build from Allwinner for h.264 encoder. If > you are interested let me know, not > clear that it is working well enough yet for public consumption. > Awesome, thanks for working on armhf! You should probably post that to the encoder thread around here. -- 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: Probe deferral on AXP driver
> All three of those are Y on 3.4.75. Still getting the probe deferral > message. > Interesting, I had the exactly same deferrals when I accidentally started AXP and PSU stuff before loading the I2C drivers. In this situation you will have AXP throwing error and exiting/leaving everything with incomplete constraints. Then other AXP dependent drivers like CPUFreq have problems with setting the desired voltages. -- 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] A20 dram applied to A10
2014/1/11 > accidentally found that A20 *dram.c can work with A10 > No news here, dram controllers are the same, please dont try to run dramc settings from one board on another without checking out original script.bin's from manufacturer, you can accidentially setup it so that it will work, but you will have unstable system, for example, really cheap boards have low end DDR3s, they will not run on 400+MHz, or run and hang on high load. If you are interested in other similarities within sunxi family, checkout the pdf manuals around the wiki and this page http://linux-sunxi.org/Used_IP_cores Best Regards, Dmitriy Beykun -- 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: ethernet is not working...
> ... and to [emac_para] section : > emac_power = port:PH15<1><0> We do not know the schematics of Puneet's board, this can be plain wrong. Please, try not to guess the solution if you do not know all the details about the target device. Best Regards, Dmitriy Beykun -- 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: Probe deferral on AXP driver
2014/1/10 jonsm...@gmail.com > I see this in dmesg so maybe power is not my problem. > > <4>[1.617154] regulator_init_complete: axp20_buck3: incomplete > constraints, leaving on > <4>[1.617506] regulator_init_complete: axp20_buck2: incomplete > constraints, leaving on > <4>[1.617853] regulator_init_complete: axp20_ldo4: incomplete > constraints, leaving on > <4>[1.618198] regulator_init_complete: axp20_ldo3: incomplete > constraints, leaving on > <4>[1.618542] regulator_init_complete: axp20_ldo2: incomplete > constraints, leaving on > <4>[1.618886] regulator_init_complete: axp20_ldo1: incomplete > constraints, leaving on > Do you have I2C support built-in or as a module? You should have this built-in: CONFIG_I2C=y CONFIG_AW_AXP=y CONFIG_I2C_SUNXI=y to get rid of 'incomplete constraints' errors. Also, on latest 3.4 kernel you should have i2c_sunxi default to 'y', maybe you are checking out really old hash, probably, because sunxi-bsp submodule was not updated. Best Regards, Dmitriy Beykun -- 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] [RFC PATCH 8/9] ARM: dt/sunxi: add NFC pinctrl pin definitions
>
> + nand_cs0_pins_a: nand_cs@0 {
>
> + nand_rb0_pins_a: nand_rb@0 {
>
If I remember correctly, sun4i and sun7i have 8 CS pins and 2 RB pins,
shouldnt those be all defined in this patch? Correct me if I'm wrong.
Best Regards,
Dmitriy Beykun
--
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] [RFC PATCH 0/9] mtd: nand: add sunxi NAND Flash Controller support
2014/1/8 Boris BREZILLON > Hello, > > This series add the sunxi NFC support with up to 8 NAND chip connected. > I'm still in the early stages drivers development and some key features are > missing, but it's usable (I tested it on the cubietruck board). > Hello Boris, Thanks for working on NAND controller support, I was thinking about doing the non-DMA version of Yuq's driver for mainline testing, but didn't have time to do it. First, I want to ask about performance, did you have time to make some measurements for NAND-flavored file systems like UBIFS/etc. ? Info about this will be really interesting to know, how it will perform using the soft_bch and no DMA available. Second, did you encounter any problems with badblock scan and oob areas usage? When I was poking around the Yuq's driver I found couple bugs there that I could not avoid, for example, badblock bug was that on the end of any NAND chip 4 or 5 blocks were always non-readable after write and standard badblock detection didn't detect that right, I was forced to manually shrink my MTD area so it wont use those blocks at the end. And third, what about the SPL area and possibilities of pure NAND boot? Yuq's driver had the nand1k things to work this around. Here's what's missing: > - HW ECC support > - DMA support > - HW randomization support > - many more improvements Any plans on implementing these? Especially, HW ECC/HW random? If I remember correctly, random was broken in Yuq's driver, even though he tried to use it exactly like in the allwinner's sources. And last question, do you plan to implement community 3.4 kernel support? If your version has no bugs with badblocks/oob it could be used as an alternative to what we have on 3.4 (the ugly block layer). Thanks again for working on this subject, hope we will soon see a full NAND MTD boot on our sunxi devices. Best Regards, Dmitriy Beykun -- 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] LVDS LCD no clock
2014/1/7 TsvetanUsunov > LVDS works, but as I reported a month ago LVDS driver is buggy > Thanks for rapid answer, but could you clarify, what kernel do you use? Our community one, or Allwinner SDK Android? -- 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] LVDS LCD no clock
Interesting detail is, OLIMEX now sells LVDS panel https://www.olimex.com/Products/OLinuXino/A20/A20-LCD15.6/ http://olimex.wordpress.com/2013/12/09/new-product-in-stock-monster-lvds-15-6-lcd-for-a20-olinuxino/ They claim that it works with A20-OLinuXino-MICRO. -- 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: New sunxi-next tree with usb (ehci only), hs timers, and other stuff.
2013/12/31 Hans de Goede
>
> I've just pushed my latest work to:
> https://github.com/linux-sunxi/linux-sunxi/commits/sunxi-devel
>
> Which I'm currently maintaining and is the tree to use if you want to
> follow upstream
> sunxi development.
>
> Try comparing the sun7i-a20.dtsi and sun7i-a20-cubietruck.dts files there
> with the ones
> you're using. Maybe there is some other change there too, or maybe somehow
> just having
> something extra in the dtb (making it larger) mysteriously fixes things ?
>
> Regards,
>
> Hans
>
> p.s.
>
> I'm going AFK till 2014, see you then, and happy new year.
Hans,
After downloading everything again and recompiling, I think I figured out
where the culprit is: its the fdt loading and mangling by PSCI. Check this
commit
https://github.com/jwrdegoede/u-boot-sunxi/commit/a5cc529a6126cedab52899375fdd10733e2e5456
This
code emits the things needed for PSCI to work, and without them even if you
have PSCI in kernel, you will have -38 on second CPU bringup.
Next, I tried disabling "appended fdt to zImage" (CONFIG_ARM_APPENDED_DTB)
option in the kernel and I got interesting results: my kernel stopped
booting. This means that it does not read mangled fdt from u-boot, instead
it was reading appended raw fdt without PSCI nodes emited.
I also checked if it is an ATAG issue by adding "chosen { bootargs =
"<...>"; };" to my fdt to check wether it is booting but without console
output - but no luck here too.
Could you please show us all your boot envorinoment and, especially, fdt
related things? I think we have a little problem here with default u-boot
env not ready for fdt loading.
Best Regards,
Dmitriy Beykun
p.s.: Happy New Year to you too.
--
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.
