All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingmar Sittl <ingmar.sittl@elektrobit.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: no display output on LVDS with i.mx6Q Sabre SDB and dora
Date: Mon, 14 Apr 2014 15:33:03 +0200	[thread overview]
Message-ID: <534BE38F.6070003@elektrobit.com> (raw)
In-Reply-To: <CAOMZO5B=yZZHvwz9rWcrHN_BX0HKNrYSSTFHNxKbe=9Y8Zn7ow@mail.gmail.com>

On 14.04.2014 15:20, Fabio Estevam wrote:
> On Mon, Apr 14, 2014 at 9:40 AM, Ingmar Sittl
> <ingmar.sittl@elektrobit.com> wrote:
>
>> Starting kernel ...
>>
>> Uncompressing Linux... done, booting the kernel.
>> Linux version 3.0.35-4.1.0+yocto+gbdde708 (dev@linux-8w3x.site) (gcc version
>> 4.8.1 (GCC) ) #1 SMP PREEMPT Fri Apr 11 12:24:20 CEST 2014
>> CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
>> CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
>> Machine: Freescale i.MX 6Quad/DualLite/Solo Sabre-SD Board
>> Memory policy: ECC disabled, Data cache writealloc
>> CPU identified as i.MX6Q, silicon rev 1.1
> Probably not related to the LVDS issue, but could you try this on a
> rev 1.2 instead?
>
> 3.0.35 4.1.0 does not officially support rev 1.1.
>

unfortunately all of our Sabre SDB boards are rev 1.1. If this is no longer 
supported, we would stay on LTIB.


  reply	other threads:[~2014-04-14 13:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 12:40 no display output on LVDS with i.mx6Q Sabre SDB and dora Ingmar Sittl
2014-04-14 13:20 ` Fabio Estevam
2014-04-14 13:33   ` Ingmar Sittl [this message]
2014-04-14 13:35     ` Fabio Estevam
2014-04-14 13:32 ` Daiane Angolini
2014-04-14 13:35   ` Ingmar Sittl
2014-04-14 13:43     ` Fabio Estevam
2014-04-14 13:47       ` Ingmar Sittl

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=534BE38F.6070003@elektrobit.com \
    --to=ingmar.sittl@elektrobit.com \
    --cc=festevam@gmail.com \
    --cc=meta-freescale@yoctoproject.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 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.