public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: linux@johnea.net
To: linux-omap@vger.kernel.org
Subject: Re: Which git to clone for testing prior to submitting bugs?
Date: Fri, 28 Sep 2012 12:46:04 -0700	[thread overview]
Message-ID: <5065FE7C.9070503@johnea.net> (raw)
In-Reply-To: <CAOCHtYg3zrqO+3Rk6P8K7iit7uO9g4_YHQ870TXbmuEPZEyQ0Q@mail.gmail.com>

On 09/28/2012 12:18 PM, Robert Nelson wrote:
> Ah, so looking at the config, ARCH switched to omapdrm... It kinda
> works in v3.5.x, but i'd wait till a few more releases...
>
> So, based on that config, they have both "CONFIG_FB_OMAP2" and
> "CONFIG_DRM_OMAP" enabled.. That's a no-no...
>
> CONFIG_DRM_OMAP
> http://cateee.net/lkddb/web-lkddb/DRM_OMAP.html
> depends on: ( CONFIG_DRM&&  ! CONFIG_CONFIG_FB_OMAP2 )&&  (
> CONFIG_ARCH_OMAP2PLUS )
>
> Option 1: Stay with omapfb
>
> CONFIG_FB_OMAP2=m ->  CONFIG_FB_OMAP2=y
> disable: CONFIG_DRM_OMAP
>
> Option 2: Go Experimental route with omapdrm
>
> CONFIG_DRM_OMAP=m
> CONFIG_DRM_OMAP_NUM_CRTCS=1
>
> disable: CONFIG_FB_OMAP2
>
>> >  Attached are config.gz from running system and gz'd complete dmesg output
>> >  (hope attachments are OK on the list).
>> >
>> >  There's another 3.5.4 build scheduled on the panda build farm this
>> >  afternoon. If you have any config modification suggestions, they'd be very
>> >  gratefully received.
> Also, if your running that config on pre-es (omap4430) panda's..
> CONFIG_OMAP4_ERRATA_I688=y&   CONFIG_ARCH_HAS_BARRIERS=y
>
> and save your self some debugging time...;)
>
> Regards,
>
> -- Robert Nelson http://www.rcn-ee.com/

Thanks Robert!

I passed along to the distro devs to include in today's build.

I'll follow up once I'm running the new version...

johnea

  reply	other threads:[~2012-09-28 19:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-27 17:19 Which git to clone for testing prior to submitting bugs? linux
2012-09-27 18:25 ` Robert Nelson
2012-09-27 18:56   ` linux
2012-09-27 18:55     ` Felipe Balbi
2012-09-27 19:17       ` Tony Lindgren
2012-09-27 19:27     ` Robert Nelson
2012-09-27 19:39       ` Robert Nelson
2012-09-27 20:16         ` linux
2012-09-27 20:41           ` Robert Nelson
2012-09-28 18:49             ` linux
2012-09-28 19:18               ` Robert Nelson
2012-09-28 19:46                 ` linux [this message]
2012-10-01 14:57                   ` johnea
2012-10-01 16:50                     ` Robert Nelson
2012-10-01 16:57                       ` linux
2012-10-01 21:16                         ` linux

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=5065FE7C.9070503@johnea.net \
    --to=linux@johnea.net \
    --cc=linux-omap@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: 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