mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: balbes-150@yandex.ru (Oleg)
To: linus-amlogic@lists.infradead.org
Subject: S805/S812 Device Tree upstreaming (was: Testing.)
Date: Mon, 15 May 2017 15:12:57 +0300	[thread overview]
Message-ID: <939ef72d-a4e5-7535-2252-d607158bd0fe@yandex.ru> (raw)
In-Reply-To: <CAFBinCA__tiW03VrMzbfAFUOkKY1VoZG=OK7BNfZyfm05HOLng@mail.gmail.com>


> get a copy of:
> - dmesg output
> - /sys/kernel/debug/gpio
> - /proc/interrupts
> - /proc/iomem

I received the necessary data from LebreELEC (this system now I have eMMC).
Let me know if you need to receive this data always from Android.

https://yadi.sk/d/deis2Z023JAiyE

>
> I'm using an initrd from Arch Linux ARM (from their ARMv7 multi-platform image).
> however, I found another missing kernel config option yesterday: you
> also need to enable CONFIG_COMMON_CLK_PWM
> once you enable that you should be able to see /dev/mmcblk1p[0-9] with
> all the partitions from your SD card
>
> I was also able to reproduce the kernel crash you reported last week.
> it seems to go away when enabling CONFIG_DEBUG_SPINLOCK in the kernel
> config - but I will create a separate thread about this (as I suspect
> that there may be some memory corruption along with a race condition
> somewhere)
>
>
> Regards,
> Martin
Hi Martin

Good news. Using the sources Your latest kernel (20170513) and amendments
in the config of the kernel I was able to run on Tronsmart MXIII Plus 
(s812).
By the way, in the source for Your kernel I had to make one small change 
to comment
out the in /arch/arm/mach-meson/Makefile a build of platsmp.
Thanks for the support. Now I have the ability
to run basic system on the device and test will be easier.

  reply	other threads:[~2017-05-15 12:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-14 21:07 Martin Blumenstingl
2017-05-15 12:12 ` Oleg [this message]
2017-05-15 14:45   ` Oleg
2017-05-15 20:29     ` Martin Blumenstingl
2017-05-16  9:05       ` Oleg
2017-05-20 16:59         ` Martin Blumenstingl
2017-05-21  8:57           ` S805/S812 Device Tree upstreaming Oleg
2017-05-21 18:17             ` Martin Blumenstingl
2017-05-22 12:12               ` Oleg
2017-05-25 15:56                 ` Martin Blumenstingl
2017-05-26  7:29                   ` Oleg
2017-10-01  7:22                   ` Oleg
2017-10-01 13:28                     ` Martin Blumenstingl
2017-10-01 18:24                       ` Oleg
  -- strict thread matches above, loose matches on Subject: below --
2017-05-08 20:10 S805/S812 Device Tree upstreaming (was: Testing.) Martin Blumenstingl
2017-05-09 13:14 ` Oleg
2017-05-11  9:54 ` Oleg
2017-05-13  9:03   ` Martin Blumenstingl
2017-05-13 19:25     ` Oleg
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
     [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: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

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=939ef72d-a4e5-7535-2252-d607158bd0fe@yandex.ru \
    --to=balbes-150@yandex.ru \
    --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®