From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH resend] directfb: add support for davinci gfx driver
Date: Sun, 06 May 2012 13:40:57 +0200 [thread overview]
Message-ID: <87mx5la65y.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4FA6601A.60203@mind.be> (Arnout Vandecappelle's message of "Sun, 06 May 2012 13:27:22 +0200")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
>> For some odd reason, I don't see the davincifb.h file in the directfb
>> tarball, but it IS in git:
>>
>> http://git.directfb.org/?p=core/DirectFB.git;a=tree;f=gfxdrivers/davinci;h=f0bd9ad6add6164f3a5e953d4eed4056315a2be2;hb=ab0d779e85cec22c7c2e7b8b6b1976049b1ba0f1
>>
>> Is it working for you? If so, how?
Arnout> davincifb.h is the kernel header file which contains the
Arnout> davinci-specific interfaces. Unfortunately the davinci stuff
Arnout> doesn't get upstreamed, so you need a davinci-specific fork
Arnout> like git://arago-project.org/git/projects/linux-davinci.git
Arnout> I thought I tested it with davinci-specific kernel headers,
Arnout> but I can't find the output anymore and I can't reproduce it...
Arnout> One solution would be to add includethe davincifb.h file with
Arnout> a buildroot patch. However, I don't have a davinci board
Arnout> anymore so I can't even test if it works.
Arnout> Therefore, I prefer to revert the patch.
Ok, if nobody else thinks otherwise then I'll revert.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-05-06 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-28 16:50 [Buildroot] [PATCH resend] directfb: add support for davinci gfx driver Arnout Vandecappelle
2012-05-01 20:02 ` Peter Korsgaard
2012-05-05 9:05 ` Peter Korsgaard
2012-05-06 11:27 ` Arnout Vandecappelle
2012-05-06 11:40 ` Peter Korsgaard [this message]
2012-05-15 19:58 ` Peter Korsgaard
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=87mx5la65y.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.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 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.