From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: "Hiremath, Vaibhav" <hvaibhav@ti.com>
Cc: Daniel Mack <zonque@gmail.com>, "Nori, Sekhar" <nsekhar@ti.com>,
Jason Kridner <jkridner@gmail.com>,
Tony Lindgren <tony@atomide.com>,
"Hilman, Kevin" <khilman@ti.com>, Paul Walmsley <paul@pwsan.com>,
"Hernandez, Carlos" <ceh@ti.com>,
"Maupin, Chase" <chase.maupin@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Kridner, Jason" <jdk@ti.com>
Subject: Re: Current state of AM33xx patches
Date: Mon, 02 Jul 2012 14:56:39 +0200 [thread overview]
Message-ID: <4FF19A87.4040602@visionsystems.de> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A83EA5FC0F@DBDE01.ent.ti.com>
Am 29.06.2012 19:43, schrieb Hiremath, Vaibhav:
> On Fri, Jun 29, 2012 at 19:24:04, Yegor Yefremov wrote:
>> Am 28.06.2012 17:09, schrieb Daniel Mack:
>>> On 27.06.2012 14:13, Hiremath, Vaibhav wrote:
>>>
>>>> Just to clarify from AM335x perspective,
>>>>
>>>> In case of AM335x, since the patches and complete BasePort support is still
>>>> not present in the Mainline (neither in Linus's tree not in linux-omap), you
>>>> need to use my Repo (https://github.com/hvaibhav: Closely follows linux-
>>>> omap/master) in order to test something on BeagleBone platform.
>>> Great, that is the information I've been looking for.
>>>
>>> Your am335x-upstream-staging branch works for me on a custom AM335x
>>> based board using a custom DT config.
>>>
>>> I'll dig through the sources and come back once I know which parts are
>>> missing.
>> Do you have LCD screen attached? I need a functioning framebuffer driver. So far if I start x-server I get various errors:
>>
>> (EE) FBDEV(0): internal error: miCreateDefColormap failed in FBDevScreenInit()
>>
> Did you get a chance to dig on this? Do you have further level of details
> from driver perspective? Which IOCTL is failing here? What is return value?
Sorry for the noise. The driver is working now. It was a software issue introduced by the latest Buildroot version. But the FB_BLANK patch is still valid, it removes nasty warnings.
Best regards,
Yegor
WARNING: multiple messages have this Message-ID (diff)
From: yegor_sub1@visionsystems.de (Yegor Yefremov)
To: linux-arm-kernel@lists.infradead.org
Subject: Current state of AM33xx patches
Date: Mon, 02 Jul 2012 14:56:39 +0200 [thread overview]
Message-ID: <4FF19A87.4040602@visionsystems.de> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A83EA5FC0F@DBDE01.ent.ti.com>
Am 29.06.2012 19:43, schrieb Hiremath, Vaibhav:
> On Fri, Jun 29, 2012 at 19:24:04, Yegor Yefremov wrote:
>> Am 28.06.2012 17:09, schrieb Daniel Mack:
>>> On 27.06.2012 14:13, Hiremath, Vaibhav wrote:
>>>
>>>> Just to clarify from AM335x perspective,
>>>>
>>>> In case of AM335x, since the patches and complete BasePort support is still
>>>> not present in the Mainline (neither in Linus's tree not in linux-omap), you
>>>> need to use my Repo (https://github.com/hvaibhav: Closely follows linux-
>>>> omap/master) in order to test something on BeagleBone platform.
>>> Great, that is the information I've been looking for.
>>>
>>> Your am335x-upstream-staging branch works for me on a custom AM335x
>>> based board using a custom DT config.
>>>
>>> I'll dig through the sources and come back once I know which parts are
>>> missing.
>> Do you have LCD screen attached? I need a functioning framebuffer driver. So far if I start x-server I get various errors:
>>
>> (EE) FBDEV(0): internal error: miCreateDefColormap failed in FBDevScreenInit()
>>
> Did you get a chance to dig on this? Do you have further level of details
> from driver perspective? Which IOCTL is failing here? What is return value?
Sorry for the noise. The driver is working now. It was a software issue introduced by the latest Buildroot version. But the FB_BLANK patch is still valid, it removes nasty warnings.
Best regards,
Yegor
next prev parent reply other threads:[~2012-07-02 12:56 UTC|newest]
Thread overview: 102+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 9:28 Current state of AM33xx patches Daniel Mack
2012-06-11 9:28 ` Daniel Mack
2012-06-11 13:51 ` Jason Kridner
2012-06-11 13:51 ` Jason Kridner
2012-06-11 14:21 ` Hernandez, Carlos
2012-06-11 14:21 ` Hernandez, Carlos
2012-06-18 8:15 ` Hiremath, Vaibhav
2012-06-18 8:15 ` Hiremath, Vaibhav
2012-06-21 13:50 ` Daniel Mack
2012-06-21 13:50 ` Daniel Mack
2012-06-25 18:17 ` Daniel Mack
2012-06-25 18:17 ` Daniel Mack
2012-06-26 11:42 ` Sekhar Nori
2012-06-26 11:42 ` Sekhar Nori
2012-06-27 12:13 ` Hiremath, Vaibhav
2012-06-27 12:13 ` Hiremath, Vaibhav
2012-06-28 15:09 ` Daniel Mack
2012-06-28 15:09 ` Daniel Mack
2012-06-29 13:54 ` Yegor Yefremov
2012-06-29 13:54 ` Yegor Yefremov
2012-06-29 17:43 ` Hiremath, Vaibhav
2012-06-29 17:43 ` Hiremath, Vaibhav
2012-07-02 12:56 ` Yegor Yefremov [this message]
2012-07-02 12:56 ` Yegor Yefremov
2012-06-29 17:33 ` Hiremath, Vaibhav
2012-06-29 17:33 ` Hiremath, Vaibhav
2012-06-29 18:34 ` Daniel Mack
2012-06-29 18:34 ` Daniel Mack
2012-06-29 18:47 ` Hiremath, Vaibhav
2012-06-29 18:47 ` Hiremath, Vaibhav
2012-06-30 2:11 ` Paul Walmsley
2012-06-30 2:11 ` Paul Walmsley
2012-06-30 9:33 ` Daniel Mack
2012-06-30 9:33 ` Daniel Mack
2012-07-04 10:07 ` Paul Walmsley
2012-07-04 10:07 ` Paul Walmsley
2012-07-04 10:50 ` Hiremath, Vaibhav
2012-07-04 10:50 ` Hiremath, Vaibhav
2012-07-04 11:22 ` Daniel Mack
2012-07-04 11:22 ` Daniel Mack
2012-07-05 17:45 ` N, Mugunthan V
2012-07-05 17:45 ` N, Mugunthan V
2012-07-23 6:30 ` Daniel Mack
2012-07-23 6:30 ` Daniel Mack
2012-07-23 16:36 ` N, Mugunthan V
2012-07-23 16:36 ` N, Mugunthan V
2012-07-26 14:52 ` Daniel Mack
2012-07-26 14:52 ` Daniel Mack
2012-07-26 15:00 ` Koen Kooi
2012-07-26 15:00 ` Koen Kooi
2012-07-26 15:58 ` Daniel Mack
2012-07-26 15:58 ` Daniel Mack
2012-07-26 16:09 ` Koen Kooi
2012-07-26 16:09 ` Koen Kooi
2012-07-26 17:46 ` Daniel Mack
2012-07-26 17:46 ` Daniel Mack
2012-07-31 19:29 ` Koen Kooi
2012-07-31 19:29 ` Koen Kooi
2012-08-02 15:30 ` Daniel Mack
2012-08-02 15:30 ` Daniel Mack
2012-08-02 15:37 ` Koen Kooi
2012-08-02 15:37 ` Koen Kooi
2012-08-02 17:19 ` Daniel Mack
2012-08-02 17:19 ` Daniel Mack
2012-08-02 19:56 ` Daniel Mack
2012-08-02 19:56 ` Daniel Mack
2012-08-02 20:20 ` Koen Kooi
2012-08-02 20:20 ` Koen Kooi
2012-08-03 10:17 ` N, Mugunthan V
2012-08-03 10:17 ` N, Mugunthan V
2012-08-03 5:25 ` N, Mugunthan V
2012-08-03 5:25 ` N, Mugunthan V
2012-06-11 14:15 ` Vaibhav Hiremath
2012-06-11 14:15 ` Vaibhav Hiremath
2012-06-23 13:03 ` Domenico Andreoli
2012-06-23 13:03 ` Domenico Andreoli
2012-06-27 12:07 ` Hiremath, Vaibhav
2012-06-27 12:07 ` Hiremath, Vaibhav
2012-06-27 18:31 ` Paul Walmsley
2012-06-27 18:31 ` Paul Walmsley
2012-06-27 19:01 ` Hiremath, Vaibhav
2012-06-27 19:01 ` Hiremath, Vaibhav
2012-06-27 19:12 ` Paul Walmsley
2012-06-27 19:12 ` Paul Walmsley
2012-06-27 19:21 ` Hiremath, Vaibhav
2012-06-27 19:21 ` Hiremath, Vaibhav
2012-06-27 19:37 ` Paul Walmsley
2012-06-27 19:37 ` Paul Walmsley
2012-06-27 20:00 ` Paul Walmsley
2012-06-27 20:00 ` Paul Walmsley
2012-06-27 20:56 ` Hiremath, Vaibhav
2012-06-27 20:56 ` Hiremath, Vaibhav
2012-06-27 21:13 ` Paul Walmsley
2012-06-27 21:13 ` Paul Walmsley
2012-06-27 21:44 ` Paul Walmsley
2012-06-27 21:44 ` Paul Walmsley
2012-06-29 14:20 ` Mark Jackson
2012-06-29 14:20 ` Mark Jackson
2012-06-29 17:56 ` Hiremath, Vaibhav
2012-06-29 17:56 ` Hiremath, Vaibhav
2012-07-02 8:04 ` Mark Jackson
2012-07-02 8:04 ` Mark Jackson
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=4FF19A87.4040602@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--cc=ceh@ti.com \
--cc=chase.maupin@ti.com \
--cc=hvaibhav@ti.com \
--cc=jdk@ti.com \
--cc=jkridner@gmail.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=paul@pwsan.com \
--cc=tony@atomide.com \
--cc=zonque@gmail.com \
/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 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.