They started with low-cost board and the target audience was hobbyists,
amateurs, and students.
They have or had really good products and high quality, so they switched to
high-end boards and different target audiences, and that awkward board
format.
Ohh, not saying rpi format is good.. :)
And
Oops, sorry for the noise. Unmuting some controls were enough to get the
sound.
I get noise with aplay -D sysdefault:CARD=0
/usr/share/sounds/alsa/Front_Right.wav but works after installing Gnome!
On Wednesday, July 8, 2020 at 3:50:02 PM UTC-3, @lex wrote:
>
> Post was inncompçlete
:42 PM UTC-3, @lex wrote:
>
> Hi ChenYu,
>
> Card is detected and ALSA mixer controls are enabled but no sound output
> to Jack (not even noise) only HDMI out ..
> I have Kernel 5.7 with the i2s patches applied and is now up to date.
> Using CLI only. Could be just ALSA mixer m
m
# CONFIG_SND_SEQ_DUMMY is not set
# CONFIG_SND_SEQUENCER_OSS is not set
CONFIG_SND_SEQ_MIDI_EVENT=m
CONFIG_SND_SEQ_MIDI=m
CONFIG_SND_SEQ_VIRMIDI=m
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_DRIVERS=y
CONFIG_SND_DUMMY=m
CONFIG_SND_ALOOP=m
CONFIG_SND_VIRMIDI=m
# CONFIG_SND_MTPAV is not set
# CONFIG_SND
Thank you
On Wednesday, July 8, 2020 at 3:45:42 PM UTC-3, @lex wrote:
>
> Hi ChenYu,
>
> Card is detected and ALSA mixer controls are enabled but no sound output
> to Jack (not even noise) only HDMI out ..
>
Hi,
Can anyone point to a linux-next kernel with working sound output Jack,
5.7 linux-next...? Pine64+.
BR
--
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
Hi,
Just a question, i have been testing this on Pine64+ and NanoPi A64, both
play sound too fast when tested with:
aplay -D sysdefault:CARD=0 /usr/share/sounds/alsa/Front_Right.wav
The same setup works fine with Kernel 5.4 and 5.5 but not with 5.7.
Any clue what i am missing?
BR,
@lex
D25,PD26 and
PD27 pins?
panel {compatible = "panel-lvds";width-mm = <>;
height-mm = <>;pinctrl-names = "default";pinctrl-0 =
<_enable_pin _lvds0_pins>;
pinctrl-1 = <_enable_pin _lvds1_pins>;
enable-
Hi Andrey,
Thank you for sharing your work.
I can remember 2 channel was needed for the 1920x1080 res. in fact the
panel is 17"
I need to find the fex files, must be somewhere here... :)
I will try with your kernel and see what i get. Busy weekend ahead...
I will post the results.
BR
Hi Andrey,
I have a couple of 15" LCDs (different makers) with Cubieboard A20 (kernel
3.4) i would like to test your implementation if possible.
Can you share a kernel tree with your code and where should i change the
timings for each Panel?
BR
@lex
On Wednesday, February 12, 2020 at 7:
Hi,
Yesterday i left the board running overnight with the *htop *to gather some
health info, today i got the error below, i don't have a battery attached.
* Kernel running: 5.8.4
* htop running (user application)
* the board was idle
What could trigger this?
BR,
@lex
Kernel message
to investigate it, but does not seem to
be related to the issue.
BR
@lex
On Friday, January 10, 2020 at 12:02:44 PM UTC-3, @lex wrote:
>
> Hi Clément,
>
> [image: backligth.png]
> I can confirm that the patch fixed the issue (just need to run for a day
> to make it does not br
Hi Clément,
I can still see some diff from what i have working in 5.4.8. Maybe this is
redundant and not necessary. Anyway, I will test it soon.
BR,
@lex
--- /arm/ubuntu/nanopi-a64-linux-next/linux-next/drivers/gpu/drm/sun4i/
sun6i_mipi_dsi.h
+++ /arm/ubuntu/nanopi-a64-linux-next/linux-5.4.8
Hi Clément,
Sure, i will try to apply the MIPI-DSI patch to linux-next, but i see there
are a lot of changes to be made and this can take some time.
I will report back when i get the results.
Thanks,
@lex
On Thursday, January 9, 2020 at 8:33:13 PM UTC-3, Clément Péron wrote:
>
> H
Clément,
It usually crashes while changing the LCD backlight.
Not sure it is related, but some time later the board enters in a sleep
mode and shutdown itself (don't resume from that). Screen saver and power
savings are disabled.
BR,
@lex
[image: changing_backlight.png]
On Thursday, January
Hi Clément,
Looks like Kernel 5.5 will be affected too.
Thank you.
BR,
@lex
On Thursday, January 9, 2020 at 2:03:43 PM UTC-3, Clément Péron wrote:
>
> Hi @lex,
>
> On Thu, 9 Jan 2020 at 16:51, @lex >
> wrote:
> >
> > Just adding some info, 5.3.y has th
Just adding some info, 5.3.y has the same issue.
On Thursday, January 9, 2020 at 9:55:54 AM UTC-3, @lex wrote:
>
> I asked this because i have not touched the pwm-sun4i driver code, Only
> the MIPI-DSI on top of 5.4.8.
>
> On Thursday, January 9, 2020 at 9:25:11 AM UTC-3, @lex wro
I asked this because i have not touched the pwm-sun4i driver code, Only the
MIPI-DSI on top of 5.4.8.
On Thursday, January 9, 2020 at 9:25:11 AM UTC-3, @lex wrote:
>
> Thank you Vasily for the explanation.
>
> Is this a known bug or i have possibly introduced it while patching t
_get_rate() while holding a spinlock and clk_get_rate() may
> sleep.
>
> It's a bug in pwm-sun4i driver.
>
> On Wed, Jan 8, 2020 at 4:19 PM @lex >
> wrote:
> >
> > I am doing some experiments with LCD7" with the kernel 5.4.8 and
> occasionally i get
+0x1a0/0x1e0
[67634.614312] bad: scheduling from the idle thread!
Regards,
@lex
--
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-sunx
: /sys/devices/virtual/thermal/thermal_zone1/temp: Invalid argument
On Tuesday, July 30, 2019 at 10:55:09 AM UTC-3, @lex wrote:
>
> I was just thinking about the resolution of the values, shouldn't it be
> something like 42000 and not only 42 for the thermal throttling to occu
I was just thinking about the resolution of the values, shouldn't it be
something like 42000 and not only 42 for the thermal throttling to occur?
Any thoughts?
On Tuesday, July 30, 2019 at 10:13:57 AM UTC-3, @lex wrote:
>
> Clément,
>
> You are right.
> The formula now gives s
think it is working.
Thank you!
Regards,
@lex
On Tuesday, July 30, 2019 at 5:18:37 AM UTC-3, Clément Péron wrote:
>
> Hi Alex,
>
> On Tue, 30 Jul 2019 at 01:15, @lex >
> wrote:
> >
> > Clément,
> >
> > I gave it a try but still something missing.
&g
clocks = < CLK_BUS_THS>, < CLK_THS>;
clock-names = "ahb", "ths";
};
Regards,
@lex
On Sunday, July 28, 2019 at 5:44:31 PM UTC-3, Clément Péron wrote:
>
> On Sun, 28 Jul 2019 at 22:21, Clément Péron > wrote:
> >
> > Hi Alex,
> >
&g
Thu, 25 Jul 2019 at 22:01, @lex >
> wrote:
> >
> > Thank you for the info.
> >
> > Almost there, i get negative values for the temp, still something
> missing or wrong.
>
> This mean that the calibration data are wrong.
>
> I don't know where the
gt; clock-names = "ahb", "ths";
> };
On Thursday, July 25, 2019 at 4:28:07 PM UTC-3, Clément Péron wrote:
>
> Hi Alex,
>
> On Thu, 25 Jul 2019 at 19:12, @lex >
> wrote:
> >
> > Hi Clément,
> >
> > No. i did not read
Hi Clément,
No. i did not read the R40 manual until now, Base address: 1c24c00
But how to find the correct interrupt number and the correct Mapping in the
Manual? What should o look for?
Thanks for the answer.
@lex
On Wednesday, July 24, 2019 at 1:46:47 PM UTC-3, @lex wrote:
>
> Hi,
Hi,
I am trying to get the thermal readout to work on bpi m2 ultra using the
same setup from the H3 without success.
i get:
[ 802.038807] thermal thermal_zone0: failed to read out thermal zone (-16)
Anyone have this working or have a fix for this?
This is what i am using:
ths:
Another interesting thing is that a read here the RTC issue and some
workaround for that.
I do not anything wrong with RTC (yet) with this DTS, maybe i misunderstood
what the problem is or was just lucky!?
On Sunday, January 13, 2019 at 7:51:06 PM UTC-2, @lex wrote:
>
> Ok, the sound
Ok, the sound seems to be fixed. The thermal thing is still a mystery to
me. I would need to see if someone has it working.
On Sunday, January 13, 2019 at 5:10:16 PM UTC-2, @lex wrote:
>
> Sounds good. I think i'd better restart with linux-next as a reference.
>
> On Sunday, Janu
Sounds good. I think i'd better restart with linux-next as a reference.
On Sunday, January 13, 2019 at 4:51:20 PM UTC-2, CodeKipper wrote:
>
> On Sun, 13 Jan 2019 at 18:42, @lex >
> wrote:
> >
> > Hmm, i thought you would know about the wrong size, or where to look
Thanks
On Sunday, January 13, 2019 at 12:48:43 PM UTC-2, CodeKipper wrote:
>
> On Sun, 13 Jan 2019 at 13:35, @lex >
> wrote:
> >
> > Hi Marcus,
> > Thank you for the input.
> >
> > The patch seems to be verbatim.
> > The message is clear ab
anuary 13, 2019 at 7:10:41 AM UTC-2, CodeKipper wrote:
>
> s
> s
>
> On Sat, 12 Jan 2019 at 20:33, @lex >
> wrote:
> >
> > I've tried to apply this patch in a hope to get the thermal sensor
> working but things got hairy, can anyone please e
-a64-nanopi-a64.dtb: Warning
(thermal_sensors_property): /thermal-zones/gpu1-thermal:thermal-sensors:
property size (8) too small for cell size 2
On Friday, January 11, 2019 at 6:38:05 PM UTC-2, @lex wrote:
>
> Hi,
> I am running stable kernel 4.20.1 on NanoPi A64 with the li
Hi,
I am running stable kernel 4.20.1 on NanoPi A64 with the linux-sunxi
community patches and it works really well thanks for the hard work however
i am struggling to get the sound card (any) detected and the upper USB
receptacle is not working (for some reason).
Regarding the USB upper slot
back-ported the driver. Bluetooth is now working on both boards
(bpi-m2-zero and nanoPi Air)
On Sunday, November 18, 2018 at 9:51:10 PM UTC-2, @lex wrote:
>
> Hi,
> I am trying to enable Bluetooth on bpi-m2-zero and nanopi-air on kernel
> 4.20.0-rc2 but i get kernel Tainted when
Hi,
I am trying to enable Bluetooth on bpi-m2-zero and nanopi-air on kernel
4.20.0-rc2 but i get kernel Tainted when rfkill-gpio is loaded.
Can anyone pinpoint what is wrong with this and how to fix it?
[ 224.360665] rfkill_gpio rfkill_bt: sunxi-bt device probe.
[ 224.385774] rfkill_gpio
These are my
changes: https://gist.github.com/avafinger/40e7751f5d8e8fbe0225e3ad4c5da0bf
On Thursday, March 8, 2018 at 10:57:13 AM UTC-3, @lex wrote:
>
> Ok, will test Ondřej and your branch. This can take some time, I think
> this weekend I can build and test both.
>
> But t
ev_mode_unlocked)
>> from [] (drm_fb_helper_set_par+0x30/0x60)
>
> [ 58.906273] [] (drm_fb_helper_set_par) from []
>> (drm_fb_helper_hotplug_event.part.11+0xa8/0xb0)
>
> [ 58.906353] [] (drm_fb_helper_hotplug_event.part.11) from
>> [] (drm_helper_hpd_irq_event+0xf0/0xfc)
&g
Just for the record, bootlog without the patch looks better:
https://gist.github.com/avafinger/840c3e7743ead085f3c1f16bf10eaadc
On Wednesday, March 7, 2018 at 7:17:42 PM UTC-3, @lex wrote:
>
> Hi Jernej,
>
> Unfortunately, this patch did not fix the issue, unless I did something
>
UTC-3, Jernej Škrabec wrote:
>
> Hi,
>
> Dne sreda, 07. marec 2018 ob 21:30:42 CET je @lex napisal(a):
> > ops, i mean turning ON.
> >
> > On Wednesday, March 7, 2018 at 5:26:59 PM UTC-3, @lex wrote:
> > > Hi,
> > >
> > >
Hi Jernej,
Yes, I missed the warning and the code was without that patch, I think this
will fix another issue I have when the monitor is still blank for the first
login message.
I will apply the fix and check again.
Thank you.
BR,
@lex
On Wednesday, March 7, 2018 at 5:39:10 PM UTC-3
ops, i mean turning ON.
On Wednesday, March 7, 2018 at 5:26:59 PM UTC-3, @lex wrote:
>
> Hi,
>
> Turning HDMI monitor during boot or after complete boot kernel shows the
> following error:
>
> [ 14.842605] [] (unwind_backtrace) from []
> (show_stack+0x10/0x14)
> [
Have you tried to port it (JPEG encoder) to H3?
On Thursday, November 24, 2016 at 10:20:38 AM UTC-2, Milos Ladni wrote:
>
> Hello,
>
> This is yet another Proof of Concept analogue TV decoder (TV-IN) and
> hardware accelerated H264-JPEG encoder with VEISP scaling for sunxi.
> This example
Can anyone please explain what is the rule of the actuator device on the
VFE (Video Front End driver)?
I have got this message:
[VFE_ERR]Error registering v4l2 act subdevice!
The actuator is configured this way in FEX file:
vip_dev0_act_used= 1
vip_dev0_act_name= "vm149c_act"
I am working on OV5640 to get the best fps i can on 1920x1080 preview mode.
After a lot of trial and errors i got somewhat near 15 fps, actually ~10
fps when rendering on screen.
If i set the timings to 30 fps i get the following error:* [VFE]cs/isp
reset after csi/isp interrupt timeout!*
I
00 Rosimildo DaSilva
> <rosi...@gmail.com > wrote:
> > I will try in a few weeks.
> >
> > I am going on a business trip for 2 wks, and when I get back I will
> > try it. The way it is now, it is very easy to use ffmpeg, but you
> > have to use scripts to pipe
; > On Sat, Mar 12, 2016 at 7:37 PM, @lex <alex@gmail.com >
> wrote:
> >> You are right, i changed the input format to NV12 on GuvcView and got
> lower
> >> CPU usage (250%) and Temp ~75C.
> >> I does not help much overall.
> >
> >
- | \
>$ROOT_DIR/videoenc -i - -k 2 -r 25 -b 1024 -s 1280x720 -o
> /tmp/out1.h264
> ;;
>
> R
>
> On Saturday, March 12, 2016 at 4:55:57 PM UTC-6, @lex wrote:
>>
>> Inspired by so many good arguments on USB uvc cameras i decided to te
gt; Interval: Discrete 0.200s (5.000 fps)
> Size: Discrete 320x240
> Interval: Discrete 0.033s (30.000 fps)
> Interval: Discrete 0.050s (20.000 fps)
> Interval: Discrete 0.067s (15.000 fps)
> Interval: Discrete 0.100s (10.000 fps)
> Interval: Discrete 0.200s (5
the sound with image you need HW encoding.
This is my 2 cents.
@lex
On Saturday, March 12, 2016 at 5:36:08 PM UTC-3, Jon Smirl wrote:
>
> On Sat, Mar 12, 2016 at 3:01 PM, Rosimildo DaSilva <rosi...@gmail.com
> > wrote:
> > Jon,
> > Thanks for yours always inf
/ 15.00 on a sbc board and another $ 100.00 is
only viable if you don't want to mess with software.
* No tinkering, no learning and no solution for the upcoming Allwinner new
devices going this route.
So, guys lets's get back to work, the fight is not over yet.
@lex
On Friday, March 11, 2016
Can you please tell me the idVendor and idProduct for this camera?
On Friday, March 11, 2016 at 8:08:21 PM UTC-3, @lex wrote:
>
> Err... That was new to me. Without researching how do you grab video from
> this generic driver how good this camera performs?
>
> On Friday, March 1
Seems to be a nice camera, but that depends on your kernel version.
There is no support for SN9C291 OV9712 on kernel v3.4.39.
And no support on odroid-3.8.30 on my U3 also.
Don't know about armbian legacy kernel version, but i don't expect there
will be support also.
On Friday, March 11, 2016 at
Thank you Rosimildo!
I will try it out and see how i can glue it to a 'C' program, if you don't
mind being asked very basic questions.
Don't get me wrong but why you choose C++? I will take some time to port it
to C.
Anyways thanks for the hard work.
@lex
On Friday, March 11, 2016 at 9:32:09
others to have
a look, fix, suggest, contribute as you wish in a hope it can do something
useful.
And sorry for the monolithic way of programming, it was just easier for me
to get it compiled.
https://github.com/avafinger/jepocx
@lex
--
You received this message because you are subscribed
at all but we need
a lot of bandwith.
If you have spare time and are willing to get this done i can arrange to
send you a Opi one or Opi PC, what do you think?
I hope the child has not been born dead already!
@lex
On Friday, February 12, 2016 at 8:48:48 PM UTC-2, Manuel Braga wrote:
>
>
Considering my level of skill, i believe getting a workable sample without
memory leaks first would benefit also this new cheap HW that is coming.
Cheap HW, cheap (or a good) camera and a working HW encoding engine would
be more attractive to advanced developers and give a reason to the good
this working
with A20,A10,A83T.
Is any way i could check if /dev/cedar_dev is working properly?
if you need further info, please ask.
@lex
On Wednesday, December 30, 2015 at 3:18:49 PM UTC-2, John S wrote:
>
> "@lex" <alex@gmail.com > wrote:
> > I am trying to
gt;
> Basically two thing are missing:
>
> a) The "DEVICES" code are missings
> b) Memory Allocators are missing ( ION and/or SUNXI_MEM )
>
> Unless AW really does something to fix it, it is useless the code.
>
>
> R
>
>
> On Wednesday, December 30,
imple task? or even share
a YUV sample image that works with the demo?
@lex
--
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
I have r3p0 working fine.
I just had my final try on this:
http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread=53=5#firstpost
I finally gave up and followed your advice.
BR,
@lex
On Tuesday, September 1, 2015 at 6:09:19 AM UTC-3, Siarhei Siamashka wrote:
>
> On Thu, 26 Mar 2
I contacted him and asked for the SDK/BSP, he replied to wait for about a
week, that was two weeks ago. So i guess they are still cleaning up some
things and are closer to release it.
On Tuesday, April 28, 2015 at 3:59:55 AM UTC-3, Simos Xenitellis wrote:
On Tue, Apr 28, 2015 at 1:29 AM,
Simos,
Is it possible to get the latest Mali binaries (for developers) from
Allwinners?
Say r4p0 or r5p0?
@lex
On Thursday, March 26, 2015 at 11:39:40 AM UTC-3, Simos Xenitellis wrote:
On Thu, Mar 26, 2015 at 11:40 AM, Siarhei Siamashka siarhei@gmail.com
javascript: wrote:
On Wed
When i said the last hope i meant to get the binaries for the r4p0 from
Allwinners (or perhaps from Cubietech).
It is not legally to use it from ODROID.
On Thursday, March 26, 2015 at 7:08:54 AM UTC-3, Siarhei Siamashka wrote:
On Wed, 25 Mar 2015 05:26:08 -0700 (PDT)
@lex alex@gmail.com
On Monday, March 23, 2015 at 3:09:00 PM UTC-3, Siarhei Siamashka wrote:
On Mon, 23 Mar 2015 08:13:46 -0700 (PDT)
@lex alex@gmail.com javascript: wrote:
On Monday, March 23, 2015 at 10:51:17 AM UTC-3, Siarhei Siamashka wrote:
On Thu, 19 Mar 2015 05:04:33 -0700 (PDT)
@lex alex
.
The *real* problem is i want to have linux all the bells and whistles
Android have for this platform, my bad.
But..but..but why you so upset? I did not want to start a war, was just a
question.
Kind Regards,
@lex
On Monday, March 23, 2015 at 10:51:17 AM UTC-3, Siarhei Siamashka wrote:
On Thu
Thank you all,
So, the last hope is what Siarhei Siamashka is suggesting? Any chance this
will happen?
BR,
@lex
On Thursday, March 19, 2015 at 8:42:32 AM UTC-3, Henrik Nordström wrote:
ons 2015-03-18 klockan 06:17 -0700 skrev @lex:
I have looked into ODROID r4p0 blobs and headers and did
I have looked into ODROID r4p0 blobs and headers and did not find any EULA,
perhaps it is kept with the sources?
Would be great to catch up with them.
On Wednesday, March 18, 2015 at 9:59:04 AM UTC-3, @lex wrote:
Sorry if i replied the recipients.
If there is an EULA, would i find it when i
Sorry if i replied the recipients.
If there is an EULA, would i find it when i install the binaries on their
SBC?
On Tuesday, March 17, 2015 at 10:14:59 PM UTC-3, @lex wrote:
Hi,
I would like to have r3p2 version of the Mali driver for my cb2, and i
have followed the sunxi-linux
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.
@lex
--
You received this message because you are subscribed to the Google Groups
linux-sunxi group.
To unsubscribe from this group
71 matches
Mail list logo
