From: eric miao <eric.y.miao@gmail.com>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: linux-fbdev-devel@lists.sourceforge.net,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: pxafb: Is it actually working in 2.6.21?
Date: Fri, 08 Jun 2007 08:33:28 +0800 [thread overview]
Message-ID: <4668A3D8.1090204@gmail.com> (raw)
In-Reply-To: <1181261560.30600.15.camel@localhost.localdomain>
Richard Purdie wrote:
> On Fri, 2007-06-08 at 01:18 +0200, Hans-Jürgen Koch wrote:
>> In the last few days, I desperately tried to make pxafb work on a 2.6.21
>> vanilla kernel. All I got so far is some white and black blur on my display.
>> I asked for help on the linux-arm-kernel mailing list, but though friendly
>> and competent people answered my request, it still doesn't work.
>>
>> So, I'd like to know if pxafb in 2.6.21 is actually working for somebody
>> with a similar setup.
>
> pxafb works for me on the Spitz (PXA270 based) machine in 2.6.21.
Also, pxafb works for me on the Mainstone (PXA270) and Lubbock (PXA255)
in 2.6.21.
- eric
> Regards,
>
> Richard
>
>
> -------------------------------------------------------------------
> List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
> FAQ: http://www.arm.linux.org.uk/mailinglists/faq.php
> Etiquette: http://www.arm.linux.org.uk/mailinglists/etiquette.php
>
-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
FAQ: http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette: http://www.arm.linux.org.uk/mailinglists/etiquette.php
next prev parent reply other threads:[~2007-06-08 0:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 23:18 pxafb: Is it actually working in 2.6.21? Hans-Jürgen Koch
2007-06-08 0:12 ` Richard Purdie
2007-06-08 0:33 ` eric miao [this message]
2007-06-08 0:24 ` Antonino A. Daplas
2007-06-08 0:31 ` Antonino A. Daplas
2007-06-08 7:45 ` Hans-Jürgen Koch
2007-06-12 15:53 ` [SOLVED] " Hans-Jürgen Koch
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=4668A3D8.1090204@gmail.com \
--to=eric.y.miao@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=rpurdie@rpsys.net \
/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).