[linux-sunxi] Re: Updated os for Cubieboard 2

> I tried and failed with Fedora, see > https://ask.fedoraproject.org/t/install-fedora-in-a-cubieboard-2/18633 , > but I'm having problems because it doesn't boot. AFAIK, CB2 is fully supported by vanilla kernels (except for the onboard flash, I think), so there should be no problem booting any

[linux-sunxi] Re: [PATCH v10 00/15] Add Allwinner H3/H5/H6/A64 HDMI audio

>> Yay! > Note that this doesn't bring HDMI audio card just yet. Another driver will be > needed for that. That's what I suspected, but thanks for clarifying. >> Now, I wonder: will that make it easier to add support for HDMI-Audio for >> the A10/A20? > No, A10/A20 HDMI audio uses completely

[linux-sunxi] Re: [PATCH v10 00/15] Add Allwinner H3/H5/H6/A64 HDMI audio

>> This series add H6 I2S support and the I2S node missing to support >> HDMI audio in different Allwinner SoC. > Applied to >https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Yay! Now, I wonder: will that make it easier to add support for HDMI-Audio for the A10/A20?

[linux-sunxi] Re: Odd "jump" when playing music on A10 and A20

Stefan Monnier [2020-08-31 15:51:21] wrote: > Stefan Monnier [2020-08-21 13:18:33] wrote: >> Enable the display pipeline and HDMI output. > Hmm... it turns out this patch (appended below) introduces artifacts to > the audio output on my Mele A1000. Side note: I can avoid those

[linux-sunxi] Odd "jump" when playing music on A10 and A20

Stefan Monnier [2020-08-21 13:18:33] wrote: > Enable the display pipeline and HDMI output. Hmm... it turns out this patch (appended below) introduces artifacts to the audio output on my Mele A1000. It's the same artifacts that I had encountered two years ago on my Orange Pi mini which were a

[linux-sunxi] [PATCH] ARM: dts: sun4i: Enable HDMI support on the Mele A1000

Enable the display pipeline and HDMI output. Signed-off-by: Stefan Monnier --- arch/arm/boot/dts/sun4i-a10-a1000.dts | 25 + 1 file changed, 25 insertions(+) diff --git a/arch/arm/boot/dts/sun4i-a10-a1000.dts b/arch/arm/boot/dts/sun4i-a10-a1000.dts index 8692b11a83c3

[linux-sunxi] Help bringing up a new A10s board

Still not having any success with my reko-smartbox. I compared my config files (the DTS and the file in `configs`) with those of the other A10s boards supported, and consulted my fex file to try and figure out which pins should be used where. I have now a file which seems reasonable to me (given

[linux-sunxi] Re: Installation procedure for mainline U-Boot

> $ ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- make savedefconfig > This command will create defconfig file. Could you take a look at my recent post on "Submitting new A10s board" and answer there, since I think it will clarify what is my problem. Stefan -- You received this message

[linux-sunxi] Re: Installation procedure for mainline U-Boot

> i am not sure where is the issue but here are my tips how i built new > mainline u-boot few months ago... > https://linux-sunxi.org/Mainline_U-Boot > Install additional packages: > $ apt-get install swig python-dev python3-dev > Build HowTo: > $ git clone git://git.denx.de/u-boot.git > $ git

[linux-sunxi] Installation procedure for mainline U-Boot

http://linux-sunxi.org/Bootable_SD_card says that to install U-Boot coming wither from mainline of legacy should be done with: dd if=u-boot-sunxi-with-spl.bin of=${card} bs=1024 seek=8 [ except for U-Boot v2013.07 or earlier. ] But when I build U-Boot from the mainline's `master` branch, I

[linux-sunxi] Re: Submitting new A10s board

Back in 2013, I wrote: > I just received a box that's externally like a Mini-X, but with an A10s > inside. It's sold as a "Reko mk801" > (http://dx.com/p/reko-mk801-android-4-0-4-mini-pc-google-tv-player-w-antenna-1gb-ram-4gb-rom-av-hdmi-blue-208095). > It has 1024MB of RAM (at least > I see 4

[linux-sunxi] Re: [PATCH v2] arm64: dts: allwinner: h6: orangepi-3: Add eMMC node

Question: > OrangePi 3 can optionally have 8 GiB eMMC (soldered on board). Because > those pins are dedicated to eMMC exclusively, node can be added for both > variants (with and without eMMC). Kernel will then scan bus for presence > of eMMC and act accordingly. Is it just me or would this kind

[linux-sunxi] Re: [PATCH 1/3] media: cedrus: Properly signal size in mode register

> Do you know if we have a way to report some estimation of the maximum supported > fps to userspace? It would be useful to let userspace decide whether it's a > better fit than software decoding. Even if the fps ends up too low for the player's taste, I can't imagine why software decoding would

[linux-sunxi] Re: [RFC PATCH] drivers: ata: ahci_sunxi: Increased SATA/AHCI DMA TX/RX FIFOs

> Increasing the SATA/AHCI DMA TX/RX FIFOs (P0DMACR.TXTS and .RXTS) from > default 0x0 each to 0x3 each gives a write performance boost of 120MB/s > from lame 36MB/s to 45MB/s previously. Read performance is about 200MB/s > [tested on SSD using dd bs=4K count=512K]. Such a simple patch to fix

Reboot and audio on Orange Pi mini (was: [linux-sunxi] Re: [PATCH v3 0/9] Stop AXP from crashing when enabling LDO3)

> Well, f you have the hardware, then there's only one way to find out: > > 1) Apply patchset > 2) Add following into boards defconfig: > CONFIG_AXP_ALDO3_INRUSH_QUIRK=y > 3) If it still fails to reboot, add following > CONFIG_AXP_ALDO3_VOLT_SLOPE_08=y Hmm... I tried it and it worked: it now

[linux-sunxi] Re: [PATCH v3 0/9] Stop AXP from crashing when enabling LDO3

> When powering up an AXP209, the default value for LDO3 output is > enabled. This works fine. However if for whatever reason, LDO3 is > disabled, for example by OS during reboot and u-boot enables LDO3 > again, the PMIC shuts down (without setting an interrupt) causing the > board to hang.

[linux-sunxi] Re: [PATCH v3 6/9] power: axp209: Add support for voltage rate control on LDO3

> + Increases the voltage by 1.6 mV per uS until the final voltage has > + been reached. Note that the scaling is in 25 mV steps and thus > + the slew rate in reality is about 25 mV/31.250 uS. [...] > + Increases the voltage by 0.8 mV per uS until the final voltage has > + been

[linux-sunxi] Re: [PATCH 01/15] ARM: dts: sun8i-a33: Remove heading 0 in video-codec unit address

> This cosmetic change removes the heading 0 in the video-codec unit ^ I think you meant "leading 0" (this applies to the title as well, and to the other patch for H3 as well). Stefan -- You received this message because you are subscribed to

[linux-sunxi] Re: [PATCH 9/9] [DO NOT MERGE] drm/sun4i: rgb: Add 5% tolerance to dot clock frequency check

> it might also break some panels that currently work and won't now, Could you give a scenario where this happens? My reading of the patch says that it should only cause the display to be ON in more circumstances (i.e. in cases where it previously would stay OFF because of MODE_CLOCK_LOW or

[linux-sunxi] Re: Odd "jump" when playing music on A20

to the Orange Pi mini. I'm currently running with the 4.18 kernel using the DTS from 4.16, which circumvents the problem by disabling the sun4i-drm (which then falls back on simple-framebuffer, IIUC). Stefan Stefan Monnier writes: >> Could you try to revert the sigma delta patch?  >

Re: [linux-sunxi] Re: Odd "jump" when playing music on A20

> Could you try to revert the sigma delta patch?  > > git revert de34485 > > Or try to set cpufreq on performance govenor. Bisecting gave me the following culprit: commit e3dd25ae0a910b77d049a8cda586a17d8661689d Author: Stefan Monnier Date: Fri Feb 16 15:5

[linux-sunxi] Re: Using sun4i-drm on a BananaPi

[...] > I've compiled the mainline 4.15rc2 kernel with the patch below for the > bananapi's DTS (ported from the patch that was applied for the > cubietruck), but when I boot the sun4i-drm module is not loaded. Duh! Of course, I didn't `make dtbs`, so I ended up still using the old DTB without

[linux-sunxi] Re: Using sun4i-drm on a BananaPi

> sun4i-drm is the overall DRM driver, but each separate component in > the display pipeline has its own module as well. If you look at your > config above you'll see DRM_SUN4I_HDMI, DRM_SUN4I_BACKEND. However > if you have the modules installed correctly the kernel should be > able to load them

[linux-sunxi] Using sun4i-drm on a BananaPi

I've compiled the mainline 4.15rc2 kernel with the patch below for the bananapi's DTS (ported from the patch that was applied for the cubietruck), but when I boot the sun4i-drm module is not loaded. My kernel config is based on that Debian's, with most things compiled as modules: % grep -i

[linux-sunxi] Re: [PATCH v8] drm/sun4i: hdmi: Implement I2C adapter for A10s DDC bus

> Thanks for your work on this, I've queued it in 3.14. > It will appear in my branches and next as soon as 3.13-rc1 is out. I presume you meant "4." instead of "3." above, Stefan -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To

[linux-sunxi] Re: A33 Suspend

> I updated the instructions on the wiki to update the commit tag. You > shouldn't need to switch branches if the commit tag is correct. It looks > like the old commit tag disappeared. I tested with the new commit tag on > sina-a33 and it appears to work. (make sure to use correct u-boot config

[linux-sunxi] Re: [PATCH 10/15] drm/sun4i: tcon: Switch mux on only for composite

>> + if (encoder->encoder_type == DRM_MODE_ENCODER_TVDAC) >> + val = 1; >> + else >> + val = 0; Isn't this better written as val = (encoder->encoder_type == DRM_MODE_ENCODER_TVDAC); -- Stefan -- You received this message because you are

[linux-sunxi] Re: [PATCH 0/15] drm: sun4i: Add support for the HDMI controller

> Here is an attempt at getting the HDMI controller running. > This HDMI controller is found on a number of old Allwinner SoCs (A10, A10s, > A20, A31). Thank you thank you thank you. Stefan "I need it on the A20, so we're not quite there yet, but it's great to see

[linux-sunxi] Re: [PATCH RFC] drm/sun4i: rgb: Add 5% tolerance to dot clock frequency check

> So we're back to where we started. What is a reasonable tolerance to set in > the driver if we don't know the tolerances of the panel? Can you manually fudge the min/max settings from the guessed timing to which you apply a 5% tolerance? IOW, the 5% tolerance is not in the driver's code but in

[linux-sunxi] Re: [PATCH 4/8] drm/sun4i: add support for sun8i DE2 mixers and display engines

> drivers/gpu/drm/sun4i/Kconfig | 8 + > drivers/gpu/drm/sun4i/Makefile | 1 + > drivers/gpu/drm/sun4i/sun4i_crtc.c | 6 +- > drivers/gpu/drm/sun4i/sun4i_drv.c | 38 +++- > drivers/gpu/drm/sun4i/sun4i_drv.h | 1 + > drivers/gpu/drm/sun4i/sun4i_layer.c | 92 ++-- >

[linux-sunxi] Re: Whither the DRM driver for A20?

> It works, but IIRC noone has submitted device patches to mainline (or > noone has bothered to update Wiki). > > Some work with A20 Olinuxino Lime and Micro: > https://github.com/net147/linux/branches Hmm... so looking briefly at those patches, it seems that it indeed reuses the display engine

[linux-sunxi] Whither the DRM driver for A20?

I was very happy several months ago to see a preliminary patch that added a DRM driver for the A10/A20. But when I look at http://linux-sunxi.org/Linux_mainlining_effort the status of DRM support for A20 says "Nobody works on it, but it should be compatible with already done drivers". Oddly

[linux-sunxi] Re: OpenFirmare / OpenBoot for A13

>> PS: Even tho the cards are "old/small" they're much larger than the >> U-Boot they hold, so I have a slight feeling of "waste". > A SPI Flash can work without wasting a lot. So I heard, indeed. But I don't have any SPI Flashes lying around, don't know of any friends who have some, and I

[linux-sunxi] Re: OpenFirmare / OpenBoot for A13

> The reason why i wish to use this one is that i'm actually looking towards > having the A13 being able to boot gnu/linux from usb hard disk and or usb > cd/dvd as if it were a powermac, a sun machine or an olpc. FWIW, my A20 machines boot this way, using U-Boot: I use an old/small (μ)SD card

[linux-sunxi] Re: [PATCH v9 0/2] sun4i-codec: Add Line-In, FM-In, Mic 2, Capture Source, Differential Line-In

> - rename "Line-In" to "Line". Curious: why? Stefan -- 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

[linux-sunxi] Re: Problems with Orange Pi mini

> Can you try if that works: > echo b > /proc/sysrq-trigger > That's the hardcore version of "reboot" which does wait any process to > nicely terminate, including filesystems. I just tried it, but it doesn't work either: the machine just hangs there. Stefan PS: FWIW, in this "frozen

[linux-sunxi] Problems with Orange Pi mini

I recently noticed two problems with my Orange Pi mini running Debian's stock 4.6.0-1-armmp kernel: - Reboot doesn't work. I think this has been the case "for ever", but I just noticed that it's still the same (in the last few months I never rebooted this machine, so I didn't notice the

[linux-sunxi] Mainline under Debian!

Just a little thank you note: with the introduction of the 4.6 kernels in Debian testing, I can finally use stock kernels on all my little ARM boxes (used as NAS-style servers, so all based on A20). [ With 4.4 I could use the stock kernels already, but I still needed a hand-built DTB to use the

[linux-sunxi] Re: sunxi_usb_udc

> Hello! I am trying to create my own USB gadget based on sunxi_usb_udc and > GadgetFS. I can't find any details about sunxi_usb_udc and after successful > startup detection I am unable to get data sent by host side. How can > I proceed?. IIUC, sunxi_usb_udc is the driver used in Allwinner's

[linux-sunxi] Re: Reliability of A20 boards

> My cubietruck with battery and Samsung HDD has been up for 79 days using > this power supply: BTW, by "reliability" I don't mean "time between reboots" but "time before hardware failure". So far my experience with sunxi hardware running 24/7 (mostly used as NAS) has been rather mixed: -

Re: [linux-sunxi] Unreliable boot on Mele-A2000

> So this happens right after spinning up the disk, which is the > moment when the disk uses significantly more power then during > normal operation. Actually, according to the noises I hear, the spin up happens about 1 or 2 seconds before getting to the "Found U-Boot script /boot.scr" message

Re: [linux-sunxi] Unreliable boot on Mele-A2000

>> But this last step often fails with timeouts or bad CRC checksums or >> other errors (the exact errors vary from time to time).  I'd estimate >> that the boot succeeds about 1/3 of the time. > Could you post some logs on how it fails? Here's one example (hand-copied, so may include some

[linux-sunxi] Re: Unreliable boot on Mele-A2000

> Could you post some logs on how it fails? For some reason my UART<->USB adapter doesn't want to cooperate (it is getting long in the tooth), so while I wait to receive the new one, I'll have to hand-copy it from the HDMI output. Will do that tomorrow when I'll get a chance to reboot the

[linux-sunxi] Reliability of A20 boards

I like to use A20 boards for little NAS-style servers, because of their very low power consumption. But so far I'm not impressed w.r.t reliability (large part of the problem being to get a reliable enough power adapter, it seems). So, I'm looking for recommendations for an A20 board (with SATA)

[linux-sunxi] Unreliable boot on Mele-A2000

I recently took out an old Mele-A2000 and set it up with an HDD connected (an old 120GB 2.5" laptop drive) via SATA to boot into Debian. Things mostly work correctly, except that the early boot is unreliable. More specifically: - I use a recent U-Boot (v2016.05) compiled with default flags for

[linux-sunxi] Re: CedarX Encoder Demo

> I have added "V4l2" sources to the CedarX encoder demo. > This is basically the "Camera" sources from AW demo that was around for > A20... IOW a complete waste of time. I'd encourage you instead to work with the Cedrus library, which has the philosophical/ethical advantage of being Free

[linux-sunxi] Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users

>>> Why does dmaengine need to wait? Can you explain that [...] > I see 2 possible reasons why waiting till checking for drq can help: Any chance something similar is causing the "max 50MB/s" limit on SATA transfers for A10/A20? Stefan -- You received this message because you are

[linux-sunxi] Re: random decryption errors with sun4i-ss on dm-crypt

> Thanks, I installed your cryptotest suite including your new lukstest > tool and ran some tests on a Banana Pi tonight. The results were all > good. After a first successful run of lukstest, I modified the script > and increased the sample size by a factor of 100 (and the image file, > too).

[linux-sunxi] Re: allwinner-zh/media-codec demo

> He is looking for an Encoder and libvdpau-sunxi providers a decoder > functionality. > I don't think there is any RE encoder code, except this stupidity that AW > released, very incomplete. There is a PoC of a H264 encoder, but that is > not available for anything beyond A10/A20, I guess. I

[linux-sunxi] Re: allwinner-zh/media-codec demo

Don't waste your time with allwinner-zh/media-codec. Try and use the libvdpau-sunxi instead. It needs a lot of work, but at least it's cleaner and will benefit more people in the long run. Stefan > "@lex" == @lex writes: > Hi, > I am trying to make the

[linux-sunxi] Re: Rotated video playback on A20

> Can you give advice on how to approach this? Is it at all possible to do > rotation with the CedarX driver? I'd recommend you try it with the libvdpau-sunxi since it's at least a code base that is amenable to improvements. Stefan -- You received this message because you are

Re: [linux-sunxi] Re: Rotated video playback on A20

> the video engine is able to rotate the video while decoding, but its not > possible to export this feature with vdpau. > vdpau doesn't provide the information that it needs a rotated video at > decoding time, but only later at render time. You would have to look > into the future to do rotate at

[linux-sunxi] Re: [PATCH] ARM: dts: sun7i: Add dts file for the lamobo-r1 board

> The lamobo-r1 board, sometimes called the BPI-R1 but not labelled as such > on the PCB, is meant as a A20 based router board. As such the board comes > with a built-in switch chip giving it 5 gigabit ethernet boards, and it > has a large empty area on the pcb with mounting holes which will fit a

[linux-sunxi] Re: [PATCH sunxi-tools 2/2] fel: Enable MMU on Allwinner-H3

> When the CPU clock speed is set to 480 MHz by the U-Boot SPL, ^^^ You mean MBUS? > the performance improvement for 'sunxi-fel write' transfers > to DRAM is ~95 KB/s -> ~510 KB/s. > When the CPU clock speed is set to 1008 MHz by the U-Boot SPL, > the performance improvement for

[linux-sunxi] Re: audio codec: input/output error from aplay if "Pre-Amplifier DAC" and "Pre-Amplifier Mute" are off

> AFAIK this is the behavior of ALSA. If there's no valid output path > for the default soundcard/route, it'll block instead of just dropping > output. Can't say if this is the "correct" behavior though. You should > probably ask the ALSA maintainers. I guess the main issue (which is

Re: [linux-sunxi] Re: audio codec: input/output error from aplay if "Pre-Amplifier DAC" and "Pre-Amplifier Mute" are off

>> I guess the main issue (which is sunxi-specific) is that the default >> settings of sunxi's mixer should enable an output path. > Yes. Hans already raised the issue. This is a userspace setting, which > is in alsa-lib and not part of kernel proper. > See https://lkml.org/lkml/2015/9/30/867

[linux-sunxi] Re: [PATCH] ARM: dts: sun7i: Enable audio codec on pcDuino

BTW, I've been using successfully the same additions in sun7i-a20-bananapi.dts and sun7i-a20-orangepi-mini.dts. Stefan > "Hans" == Hans de Goede writes: > From: Jelle van der Waa > Enable the on-chip audio codec > Signed-off-by: Jelle van

[linux-sunxi] Re: [PATCH 00/19] drm: Add Allwinner A10 display engine support

> The current code only assumes that there is a single instance of all > the controllers. It also supports only the RGB and Composite > interfaces. Sorry for the offtopic question, but: you seem to have spent a fair bit of time on PAL/NTSC support. In my own little world, devices using those

[linux-sunxi] Re: Is this mailing list dead?

> I'm asking here questions about linux-sunxi and didn't get any answers at > all. Do you really expect an answer in less than an hour? On which planet do you live? Stefan -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To

[linux-sunxi] Re: Help to find "SUNXI USB2.0 Dual Role Controller support" in menuconfig?

> However, in current menuconfig (of sunxi) Which kernel are you using? 3.4 or mainline? Stefan -- 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] Re: [PATCH v2] ARM: dts: sunxi: Add regulators for LeMaker BananaPi

> @Maxime: How should we handle this? In its current form, the patch applies > only to the BananaPi dts by overriding the inherited opp from the SoC dtsi. > In an earlier discussion, it was said that this can be done, even though it > might not be the most elegant approach. But then again, I think

[linux-sunxi] Re: Allwinner A20 SMP issue

> We are trying to port Windows CE on to Marsboard (A20). So why are you asking here rather than asking Allwinner? Stefan -- 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

Re: [linux-sunxi] Re: U-boot fails to read my SD cards

=> load mmc 0 0x4400 uImage ** ext4fs_devread read error - block >>> Bummer, so can you read uImage from this card using the Linux kernel >>> once booted ? >> Yes, > Can you try my sunxi-wip branch? This one has some fixes which > might fix this. Indeed, I just tried it and it was

[linux-sunxi] Re: U-boot fails to read my SD cards

=> load mmc 0 0x4400 uImage ** ext4fs_devread read error - block >>> Bummer, so can you read uImage from this card using the Linux kernel >>> once booted ? >> Yes, > Can you try my sunxi-wip branch? This one has some fixes which > might fix this. I'll try it as soon as I get back to

[linux-sunxi] Re: U-boot fails to read my SD cards

= load mmc 0 0x4400 uImage ** ext4fs_devread read error - block Bummer, so can you read uImage from this card using the Linux kernel once booted ? Yes, Stefan -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from

Re: [linux-sunxi] Re: U-boot fails to read my SD cards

IIUC there's a general sentiments that most SD cards are crap (and indeed mine are all oldcheap), but I find it striking that they work everywhere *except* for U-boot reading a large file. What sunxi board(s) are you using ? I have a Mele A2000, a pair of cheap mini-x style a10s box, a

[linux-sunxi] Re: U-boot fails to read my SD cards

IIUC there's a general sentiments that most SD cards are crap (and indeed mine are all oldcheap), but I find it striking that they work everywhere *except* for U-boot reading a large file. What sunxi board(s) are you using ? I have a Mele A2000, a pair of cheap mini-x style a10s box, a

[linux-sunxi] Re: [PATCH v8] dma: sun4i: Add support for the DMA engine on sun[457]i SoCs

Applied with subsystem name fixed Yay! Stefan -- 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

[linux-sunxi] U-boot fails to read my SD cards

With my recent effort to move all my remaining 3.4 machines to (almost)mainline, I saw a strange pattern: Many of the SD cards I have can't be read by U-boot. Yet, they work fine elsewhere. More specifically, more than half of the SD cards I've tried show the following behavior: - I can put

[linux-sunxi] Re: [RFC] ARM: dts: sunxi: Add regulators and board-specific operating points for LeMaker BananaPi

IMHO for a common maximum opp that's a good approach. But for the lowest frequency setting, it would seem more logical to me, to raise the voltage to a point where all boards will run fine with them, unless those boards cannot handle the frequency regardless of the higher voltage. I generally

[linux-sunxi] Re: Further Allwinner misbehaviour.

It is time to extend the negative marketing campaign to some of Allwinners customers, and truly hit Allwinner where it hurts. While I do think that a large-scale boycott could really make a change here and force Allwinner to release code and comply with licenses, I also think that the

[linux-sunxi] Re: TRRS on Banana Pro and Orange Pi

No idea about Orange Pi. But if you can confirm the Banana Pro's pinout it would help if you add this stuff to http://linux-sunxi.org/Banana_Pro#Tips.2C_Tricks.2C_Caveats Thanks. I can't confirm it yet, but I added the corresponding info on that page. Stefan -- You received this

[linux-sunxi] TRRS on Banana Pro and Orange Pi

The new SBCs seem to all be moving to using a TRRS connector for combined composite+audio output. That makes a fair bit of sense, but the lack of standard makes it unclear which cable to use. Could someone comment on the mutual compatibility between these board and other systems (e.g. the new

[linux-sunxi] [OFFTOPIC] Why use USB over SDIO

While comparing the OrangePi Mini and the Banana Pro, I noticed that the Banana Pro connects its wifi chip via SDIO whereas the OrangePi Mini uses a USB connection. My naive understanding is that the BananaPro choice is better since the A20 already provides the SDIO connection, whereas the

[linux-sunxi] Re: [OFFTOPIC] Why use USB over SDIO

Newer wifi is too fast for USB 2.0. For example 5Ghz or 11ac. Hard to believe. I never managed to go any further than 5MB/s over wifi (in real-life usage), so in my world 30MB/s is still a long way ahead. But in any case, this argues in favor of SDIO, which again makes me wonder why the

[linux-sunxi] Re: [OFFTOPIC] Why use USB over SDIO

https://linux-sunxi.org/Banana_Pro contains a link to the schematics at the bottom of the page. Thanks! Stefan -- 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

[linux-sunxi] Re: [OFFTOPIC] Why use USB over SDIO

Top end 11AC will do 175MB/s = 1.4Gb/s Right, but has anyone actually seen anywhere near that bandwidth in real life? E.g. I haven't even been able to get past 3MB/s with 11n at home. This said, the SDIO info I found seem to say that it only reaches 200Mb/s. But cheaper enough to pay for the

[linux-sunxi] ERROR: sun4i_usb_phy_set_squelch_detect [drivers/usb/musb/sunxi.ko] undefined

That's the error I get when I tried to compile Hans's sunxi-wip branch with CONFIG_USB_MUSB_SUNXI=m CONFIG_PHY_SUN4I_USB=m If I change them to =y the compilation error doesn't show up (haven't tried to change only one of the two). Stefan -- You received this message because you

[linux-sunxi] Re: Trying 4.1 on a Mele-A2000

I have compered our configs and I think you should try to enable these modules. One of them should resolve your issue. CONFIG_REGULATOR_DEBUG=y CONFIG_REGULATOR_VIRTUAL_CONSUMER=y CONFIG_REGULATOR_USERSPACE_CONSUMER=y CONFIG_PWM_SUN4I=y Indeed, after enabling those 4, my ethernet is now

[linux-sunxi] Re: testing sunxi-codec on Cubieboard A10

Right the patches for the Mele A1000 where still floating around on the list, I've picked them up now and added them to my sunxi-wip branch, so you may want to give things another try copying the relevant bits from the sun4i-a10-a1000.dts file to the sun4i-a10-cubieboard.dts one. I just tried

[linux-sunxi] Re: testing sunxi-codec on Cubieboard A10

71af6414aad688cf901a4b6e1aaa0076e467c01f commit fb3ae87c7e8cba95d6b1b993923b53367fe3949c Author: Stefan Monnier monn...@iro.umontreal.ca Date: Tue Oct 7 22:04:27 2014 -0400 Fix up sun4i-a10.dtsi to match sun7i-as0.dtsi diff --git a/arch/arm/boot/dts/sun4i-a10.dtsi b/arch/arm/boot/dts/sun4i

[linux-sunxi] Re: Trying 4.1 on a Mele-A2000

Having the whole .config and all the boot logs would help, but did you enable CONFIG_MDIO_SUN4I? Hmm... so it turned out that yes, that was enabled. And, comparing with Jarosław's .config I don't see anything that rings a bell. For the record, here's my dmesg and my .config. Stefan

[linux-sunxi] Re: tv-in documentation from allwinner?

the lack of parts (DVB tuners) that can feed a TS to the A20 so no proper integration with a DVB linux subsystem has been done. Oh, I missed the fact that the onboard part only does the TS part. If you need an external tuner, then indeed it's probably not worth the trouble. Stefan

[linux-sunxi] Re: tv-in documentation from allwinner?

There is quite a bit of documentation on the MPEG-TS part. And some people have been looking into writing a driver, but lack of commonly available hardware to develop on slows things down. I suspect that lack of driver for that part is also a reason for the lack of boards that provide access

[linux-sunxi] Re: Banana R1 router german article

http://www.pc-magazin.de/ratgeber/banana-pi-r1-router-anleitung-openwrt-bananian-3021511.html Anyone has ever tested this router? I heard they had problems to make the BCM switch working properly. Someone ported the BCM switch driver to mainline:

[linux-sunxi] Re: [PATCH 0/2] sun4i spi dma support

So is the dmaengine going to get anywhere Depends if someone pushes it or not, IIUC. Stefan -- 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] Re: [PATCH 0/3] Using SPI NOR flah on sunxi.

The SPI driver returns an error when more than 64 bytes are transferred at once due to lack of DMA support. Have you tried the dmaengine patch and make the SPI driver use it? Stefan -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To

[linux-sunxi] Re: A20 DMA engine patch and GMAC

When SATA uses it's own DMA code this could explain why writing to SATA disk is up to 5 times slower than reading. I don't see why. The SATA code in mainline for Allwinner uses the same code (including DMA) as used on many other platforms, AFAIK. But yes, I'm also very curious why SATA write

[linux-sunxi] Re: Devices naming consistency in U-Boot, Linux, sunxi-boards and the linux-sunxi wiki

I can think of a couple of exceptions which might resolve that (based around device name includes vendor or is clearly linked to a specific vendor) but TBH I think if there are loads of exceptions then the benefits of the cleanups is watered down somewhat. Agreed. I'm not sure it's terribly

[linux-sunxi] Re: sunxi-kms driver

Also copyright like this looks weird: * Copyright (C) 2015-2020 Allwinner Technology Co., Ltd. Living in the future? :) I'm granting all the copyright to my newly written code to Allwinner so no... It's 2015 and the copyright goes 5 years... Am I wrong? ^^' Yes, you're wrong: the copyright

[linux-sunxi] Re: HDCP support in sunxi for A20

further only in encrypted form. How is that a denial for freedom? Surely, you are not saying that proprietary content should never be transmitted using any open source product. Open Source doesn't really care about Freedom, indeed, but Free Software does. Stefan -- You received

[linux-sunxi] Re: HDCP support in sunxi for A20

I working on a pretty basic STB model, where proprietary content needs to be downloaded and played on tv. Its a requirement to encrypt the content :( ( i know hdcp gets a lot of hate, but such is the nature of the beast) I think if you're implementing such Freedom-denying code, you'd be

[linux-sunxi] Re: Allwinner strips symbols from latest cedar binaries.

My vote is to completely forget about any CedarX binary releases from Allwinner, and focus on the reverse engineered driver. Nothing good is likely to come from the Allwinner binary driver. To continue discussions about the binary driver only makes things worse for everyone involved.

[linux-sunxi] Re: Annoucement about Allwinner's CedarX Software Licensing

Recently, there have been some questions about CedarX's software licensing. To clear up any misconceptions about Allwinner's support and respect for the open source community, the CedarX media codec framework is now released with full open source code under the LGPL license. Everyone can get

[linux-sunxi] Re: Directions for video engine support (CedarX)

The way I understood all these was that there are short-term and long-term goals for better support with the video engine. As an end user, I think that having mainline support (not just for the kernel, but the rest of the stack as well) for something like Kodi (nee XBMC) would be great. Ever

[linux-sunxi] Re: Directions for video engine support (CedarX)

I'm interested in this as well. When I've tried manually mounting in Android they still fail. It looks like the data coming off is still in a format the software can't take. Does someone have step by step instructions for Android? Additionally to mounting, I think it is necessary to perform

[linux-sunxi] Re: [RFC] Serial number on sunxi devices

if necessary truncate the SID somehow. Or hash it, Stefan -- 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

[linux-sunxi] Re: sunxi otg usb code for mainline (wip) available now

I'm happy to report that after a lot of poking at the Allwinner musb code I've it working reliable in both host and peripheral mode, as well as automatically switching between the 2 depending on which cable gets plugged. Yay! Stefan -- You received this message because you are

[linux-sunxi] Re: Communication with Allwinner

What are the violation claims? Is it documented somewhere so that I can learn more about the issue? http://linux-sunxi.org/GPL_Violations BTW, most of those are violations in Allwinner's SDK/kernel, whereas most of the code that gets integrated into mainline is actually different, AFAICT

[linux-sunxi] Re: Allwinner A20 SMP Issue

Though this is not related to Linux, I hope to get your expertise support to solve a A20 related issue. We are trying to port Windows C E on to Marsboard (A20). Now, that's new. Why don't you ask the vendor? Or better: why don't you first release the Windows CE code as Free Software so we

  1   2   >