From: Fawad Lateef <fawadlateef@gmail.com> To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, kernelnewbies@kernelnewbies.org Subject: Suggestions needed for resolving DT issues between kernel 3.10 and 4.4 Date: Mon, 3 Apr 2017 10:38:53 +0200 [thread overview] Message-ID: <CAGgoGu6=44fsZ_m8tk3FHXR-FDjRgY9bCn9xXkXic64v1Mg6_Q@mail.gmail.com> (raw) Hi, I am facing some issues with device-trees (I am fairly new to them) and need some pointers about how to approach below problem: I got some I.MX6Q based hardware (some custom made whose hardware details are unknown to me). Hardware shipped with 3.10.53 kernel with full sources and everything is working on it Trying to get one of the recent kernel working on it (linux-4.4, from linux-linaro-stable with rt patches). I can compile the kernel and boot into it using 3.10.xx kernel compiled DTB but getting Warning at boot-time "Outdated DT detected, suspend/resume will NOT work" and few main hardware components not working (mainly ethernet(s) - 1 out of 4 ports working though, MTD/NAND (for u-boot environment)) So I looked into compiling the DTS (from 3.10 kernel) for 4.4 and managed to get it compiled. Now no warning of outdated DT _but_ still hardware components not working. I was assuming that as hardware is still same for both kernel 3.10 and 4.4, so it should work, but seems like something in DT is off for 4.4 kernel. Any help and suggestions will be good enough for me to look into above issue. Thanks and regards, -- Fawad Lateef
WARNING: multiple messages have this Message-ID (diff)
From: fawadlateef@gmail.com (Fawad Lateef) To: kernelnewbies@lists.kernelnewbies.org Subject: Suggestions needed for resolving DT issues between kernel 3.10 and 4.4 Date: Mon, 3 Apr 2017 10:38:53 +0200 [thread overview] Message-ID: <CAGgoGu6=44fsZ_m8tk3FHXR-FDjRgY9bCn9xXkXic64v1Mg6_Q@mail.gmail.com> (raw) Hi, I am facing some issues with device-trees (I am fairly new to them) and need some pointers about how to approach below problem: I got some I.MX6Q based hardware (some custom made whose hardware details are unknown to me). Hardware shipped with 3.10.53 kernel with full sources and everything is working on it Trying to get one of the recent kernel working on it (linux-4.4, from linux-linaro-stable with rt patches). I can compile the kernel and boot into it using 3.10.xx kernel compiled DTB but getting Warning at boot-time "Outdated DT detected, suspend/resume will NOT work" and few main hardware components not working (mainly ethernet(s) - 1 out of 4 ports working though, MTD/NAND (for u-boot environment)) So I looked into compiling the DTS (from 3.10 kernel) for 4.4 and managed to get it compiled. Now no warning of outdated DT _but_ still hardware components not working. I was assuming that as hardware is still same for both kernel 3.10 and 4.4, so it should work, but seems like something in DT is off for 4.4 kernel. Any help and suggestions will be good enough for me to look into above issue. Thanks and regards, -- Fawad Lateef
next reply other threads:[~2017-04-03 8:39 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-04-03 8:38 Fawad Lateef [this message] 2017-04-03 8:38 ` Suggestions needed for resolving DT issues between kernel 3.10 and 4.4 Fawad Lateef 2017-04-03 8:54 ` Fawad Lateef 2017-04-03 8:54 ` Fawad Lateef 2017-04-04 11:11 ` Fawad Lateef 2017-04-04 11:11 ` Fawad Lateef 2017-04-05 6:24 ` Mulyadi Santosa
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='CAGgoGu6=44fsZ_m8tk3FHXR-FDjRgY9bCn9xXkXic64v1Mg6_Q@mail.gmail.com' \ --to=fawadlateef@gmail.com \ --cc=kernelnewbies@kernelnewbies.org \ --cc=linux-kernel@vger.kernel.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.