From: raptorsds@googlemail.com (raptorsds)
To: linus-amlogic@lists.infradead.org
Subject: Testing.
Date: Sat, 27 May 2017 20:06:18 +0200 [thread overview]
Message-ID: <d9abdffc-f9d4-84e7-cc4d-135c2f15c5ae@googlemail.com> (raw)
In-Reply-To: <CAFBinCD9iJzMLDLF8avyvWF6X9iBGcfdJNuHy9jpfnQ00EZKyg@mail.gmail.com>
Am 27.05.2017 um 18:08 schrieb Martin Blumenstingl:
> On Sat, May 27, 2017 at 4:57 PM, raptorsds <raptorsds@googlemail.com> wrote:
>> Hi Martin
>>
>>> Hi Tobias,
>>>
>>> On Thu, May 25, 2017 at 8:35 PM, Tobias Baumann
>>> <017623705678@o2online.de> wrote:
>>>> hi martin
>>>>
>>>> oleg (balbes150) from armbian forum told me you could need some help
>>>>
>>>> iam new to linux but i can test images and files for you
>>>>
>>>> my system OTT M8S Clone TVBox with S812 8GBRom 2GB RAM RTL8723BS WIFI BT
>>>> Combo HDMI 2xUSB
>>>>
>>>> ( run as server for USB Printer and Sane server for canon scanner)
>>>>
>>>> at the moment i use the armbian unbuntu rom from oleg with 3.10.99 kernel
>>>> (14 04 2017 ) with working wifi usb and internet also i could run a
>>>> successful test the 4.11 kernel
>>> disclaimer: I cannot really help with Amlogic's 3.10/3.14 kernel
>>
>> But maybe than i can help by 4.11 kernel test for older devices
> you need to be aware of the fact that my kernel patches are experimental.
> what you get is:
> - one CPU core at the frequency set by the bootloader
> - maybe USB (Oleg has problems with it while it works for me)
> - maybe ethernet (again, Oleg has problems while it works for me)
> - SD card
> - front LED
>
> basically everything else is broken (wifi, CPU cores 2-4, cpu frequency
> scaling, etc.). I even managed to corrupt u-boot when I was testing my
> NAND driver.
>
> what "older" devices do you have? and do you have access to the serial
> console of these devices?
Yes Serial console only my s812 box ,
>>>> my project now is to control the front LED
>>> what are you trying to control exactly?
>>
>> red = stop
>> blue = boot/start
>> red/blue (maybe dimming) = run
>> blinking = update (maybe)
> let me explain how where the LED is controlled currently:
> - red LED turns on automatically (probably because it's wired to VCC)
> when the device is powered on
> - u-boot turns on the blue LED
> - (kernel boots)
> - the kernel can now control the LED partially (as explained in my
> previous mail, you can only set the "mix" between red and blue - you
> can't turn it off)
>
> so with another kernel you can only change the LED color from the
> point on where the kernel is started. you'll have no control over it
> (without additional work on the u-boot side) for the first seconds
> after powering on the device.
ok thank you for your explanation , it would be great when after kernelk
boot (maybe inside rc.local) the LED will have a color change
>>>> but there is a problem oleg send my the dts for led but without gpio .
>>> my m8s.dts doesn't use a GPIO because the LED is connected to
>>> GPIO_TEST_N which can also be controlled by one of the PWM controllers
>>> (this allows dimming the LED to a certain level, but in my case the
>>> LED is a dual-color LED with blue and red: the further you reduce the
>>> brightness of the (blue) LED the more you see of the red one -> if you
>>> turn off the blue LED it turns red)
>>
>> I though " GPIO_TEST_N " was a placeholder . I havent any trigger at
>> /sys/class/leds , how can i controll PWM for LED
> are you testing this on a 3.10/3.14 kernel or on a kernel with my
> patches? I think the Amlogic kernel does not use the kernel's LED
> framework, so the LEDs are not exposed in /sys/class/leds
> if it's one of my kernels (I think Oleg has compiled some images with
> them) then please post the kernel log (dmesg)
yes i use 3.10.99 kernel from the image from oleg with a dtb files with
your Led infos about "gpio test n"
i also found a older info about system LED
https://lists.freebsd.org/pipermail/freebsd-arm/2015-February/010126.html
there is a info about gpio ao 13
i send you a private mail with my dmesg with oleg dts file with led line
>>>> maybe you can assist
>>>>
>>>> thanks Tobias
>>>>
>>>> PS: i am from Germany so i am more comfortable and faster in german
>>>>
>>>>
>>>> ---
>>>> Diese E-Mail wurde von Avast Antivirus-Software auf Viren gepr?ft.
>>>> https://www.avast.com/antivirus
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> linux-amlogic mailing list
>>>> linux-amlogic at lists.infradead.org
>>>> http://lists.infradead.org/mailman/listinfo/linux-amlogic
>>> _______________________________________________
>>> linux-amlogic mailing list
>>> linux-amlogic at lists.infradead.org
>>> http://lists.infradead.org/mailman/listinfo/linux-amlogic
>>
next prev parent reply other threads:[~2017-05-27 18:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 6:37 Testing Oleg
2017-05-07 16:38 ` Testing Martin Blumenstingl
2017-05-07 17:36 ` Testing Oleg
2017-05-07 18:05 ` Testing Martin Blumenstingl
2017-05-07 18:55 ` Testing Oleg
[not found] ` <e7eb7d12-8fa8-5507-5d7b-53ef9ce3e300@yandex.ru>
2017-05-07 18:59 ` Testing Martin Blumenstingl
2017-05-07 19:09 ` Testing Oleg
2017-05-07 20:22 ` Testing Martin Blumenstingl
2017-05-07 20:44 ` Testing Oleg
2017-05-07 20:46 ` Testing Martin Blumenstingl
2017-05-07 20:53 ` Testing Oleg
2017-05-07 20:57 ` Testing Oleg
2017-05-07 21:08 ` Testing Martin Blumenstingl
2017-05-07 21:23 ` Testing Oleg
2017-05-07 21:30 ` Testing Martin Blumenstingl
2017-05-08 9:42 ` Testing Oleg
2017-05-08 11:47 ` S805/S812 Device Tree upstreaming (was: Testing.) Andreas Färber
2017-05-12 7:03 ` Testing Oleg
2017-05-25 18:35 ` Testing Tobias Baumann
2017-05-27 14:15 ` Testing Martin Blumenstingl
2017-05-27 14:57 ` Testing raptorsds
2017-05-27 16:08 ` Testing Martin Blumenstingl
2017-05-27 18:06 ` raptorsds [this message]
2017-05-27 18:18 ` Testing Martin Blumenstingl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d9abdffc-f9d4-84e7-cc4d-135c2f15c5ae@googlemail.com \
--to=raptorsds@googlemail.com \
--cc=linus-amlogic@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®