mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Boaz Ben-David <boaz.bd@wellsense-tech.com>
To: "marc@cpdesign.com.au" <marc@cpdesign.com.au>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>,
	Itai Raab <itai.raab@wellsense-tech.com>
Subject: Re: iMX35 3stack framebuffer problem
Date: Tue, 8 Mar 2011 09:03:55 +0200	[thread overview]
Message-ID: <39A4B204C321D34DA3490E3B119D5A6C68C006F8A4@SBS2008.wellsense.local> (raw)
In-Reply-To: <201103081635.29082.marc@cpdesign.com.au>

Yes, I am using the freescale kernel unfotunately.
Do you know of some way to fix this (a patch for the freescale kernel
maybe)?

Thanks,

Boaz.


On Tue, 2011-03-08 at 16:35 +1100, Marc Reilly wrote:
> On Tuesday, March 08, 2011 03:35:10 am Boaz Ben-David wrote:
> > Hi,
> > 
> > When using the iMX35 freescale 3stack we are having some issues with the FB
> > driver. On device boot we enable the fb using "fb0.enable=1" and then try
> > to boot the kernel from nand. The problem is that after the kernel is
> > loaded to RAM and extracted the board hangs. If we do not init the fb0
> > device but simply boot the kernel it works fine. Trying "fb0.enable=0"
> > before booting also did not help.
> > Did anyone encounter this issue yet or are we doing something wrong?
> 
> Are you using the freescale kernel? It doesn't handle loading the IPU driver 
> if the IPU has been enabled previously.. (an IRQ fires before all the driver 
> structures have been initialized and crashes)
> 
> Cheers,
> Marc
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2011-03-08  7:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07 16:35 Boaz Ben-David
2011-03-08  5:35 ` Marc Reilly
2011-03-08  7:03   ` Boaz Ben-David [this message]
2011-03-08  7:10     ` Baruch Siach
2011-05-29  6:08       ` Boaz Ben-David
2011-05-29  6:33         ` Baruch Siach
2011-05-29  7:14           ` Boaz Ben-David
2011-05-29  7:28             ` Baruch Siach
2011-10-09  7:10               ` Boaz Ben-David
2011-10-10  4:44                 ` Baruch Siach
2011-10-11  6:40                   ` Boaz Ben-David
2011-10-11  6:54                     ` Robert Schwebel
     [not found]                       ` <4E93E8CB.1040504@wellsense-tech.com>
2011-10-11  6:59                         ` Boaz Ben-David
2011-10-11  7:01                         ` Baruch Siach
2011-10-11  7:06                         ` Robert Schwebel

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=39A4B204C321D34DA3490E3B119D5A6C68C006F8A4@SBS2008.wellsense.local \
    --to=boaz.bd@wellsense-tech.com \
    --cc=barebox@lists.infradead.org \
    --cc=itai.raab@wellsense-tech.com \
    --cc=marc@cpdesign.com.au \
    /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