From: arnaud.patard@rtp-net.org (Arnaud Patard (Rtp))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] i.MX51 Framebuffer support
Date: Thu, 23 Dec 2010 21:45:23 +0100 [thread overview]
Message-ID: <87wrn09q1o.fsf@lechat.rtp-net.org> (raw)
In-Reply-To: <87ipymun54.fsf@macbook.be.48ers.dk> (Peter Korsgaard's message of "Wed, 22 Dec 2010 11:17:59 +0100")
Peter Korsgaard <jacmet@sunsite.dk> writes:
Hi,
>>>>>> "Arnaud" == Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org> writes:
>
> Arnaud> Sascha Hauer <s.hauer@pengutronix.de> writes:
> Arnaud> Hi,
>
> >> The following series adds i.MX51 framebuffer support based on the
> >> IPUv3. It is not perfect but I decided it is good enough to open it
> >> for a wider audience and collect first reviews. I tested this on a
> >> babbage board using both outputs (VGA/DVI) with different
> >> resolutions up to 1680x1050 and different colour depths. I also
> >> tested it on one custom board using a fixed display setting.
>
> Arnaud> After adding code to my efika sb machine file and your patchset, I've
> Arnaud> seen the light. Err, no. It was a penguin and a login prompt. I guess
> Arnaud> it means your patchset is working here.
>
> Cool. Care to submit that machine file support?
Yes, I will (of course) but ... I'd like to see the usb issues I found
fixed because they're the only way to get usb on the sb and without usb,
you have no network, no keyboard, no way to connect any external device,
which makes the sb pretty useless. In the mean time, you can use my
patchset once I've added the fb support in it.
Arnaud
next prev parent reply other threads:[~2010-12-23 20:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 10:48 [PATCH v2] i.MX51 Framebuffer support Sascha Hauer
2010-12-20 10:48 ` [PATCH 1/9] ARM i.MX51: Add ipu clock support Sascha Hauer
2010-12-20 10:48 ` [PATCH 2/9] ARM i.MX51: rename IPU irqs Sascha Hauer
2010-12-20 10:48 ` [PATCH 3/9] Add a mfd IPUv3 driver Sascha Hauer
2011-01-03 15:42 ` Sascha Hauer
2011-01-07 12:08 ` Samuel Ortiz
2011-01-31 8:20 ` Sascha Hauer
2011-02-01 10:51 ` Samuel Ortiz
2011-02-01 10:59 ` Sascha Hauer
2011-02-01 11:44 ` Samuel Ortiz
2011-02-01 11:51 ` Russell King - ARM Linux
2011-02-01 12:07 ` Arnaud Patard (Rtp)
2011-02-01 12:51 ` Sascha Hauer
2011-02-01 16:47 ` Uwe Kleine-König
2011-02-01 14:03 ` Samuel Ortiz
2010-12-20 10:48 ` [PATCH 4/9] fb: export fb mode db table Sascha Hauer
2010-12-20 10:48 ` [PATCH 5/9] Add i.MX5 framebuffer driver Sascha Hauer
2010-12-20 10:48 ` [PATCH 6/9] ARM i.MX51: Add IPU device support Sascha Hauer
2010-12-20 10:48 ` [PATCH 7/9] ARM i.MX5: Allow to increase max zone order Sascha Hauer
2010-12-20 10:48 ` [PATCH 8/9] ARM i.MX5: increase dma consistent size for IPU support Sascha Hauer
2010-12-20 10:48 ` [PATCH 9/9] ARM i.MX51 babbage: Add framebuffer support Sascha Hauer
2010-12-20 12:35 ` arden jay
2010-12-22 7:56 ` [PATCH v2] i.MX51 Framebuffer support Arnaud Patard (Rtp)
2010-12-22 10:17 ` Peter Korsgaard
2010-12-23 20:45 ` Arnaud Patard (Rtp) [this message]
2011-01-05 13:04 ` Julien Boibessot
2011-01-06 9:42 ` Russell King - ARM Linux
2011-01-14 9:17 ` Julien Boibessot
2011-01-06 10:23 ` Sascha Hauer
2011-01-06 10:32 ` Peter Horton
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=87wrn09q1o.fsf@lechat.rtp-net.org \
--to=arnaud.patard@rtp-net.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).