From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9781] New: ti-sgk-km build on kernel >4.1
Date: Tue, 28 Mar 2017 21:37:51 +0200 [thread overview]
Message-ID: <20170328213751.5098434e@free-electrons.com> (raw)
In-Reply-To: <bug-9781-163@https.bugs.busybox.net/>
Lothar,
Since you initially submitted the ti-sgx-km package, could you have a
look at the below bug report, and see if you could provide a patch?
Thanks a lot!
Thomas
On Mon, 27 Mar 2017 13:31:28 +0000, bugzilla at busybox.net wrote:
> https://bugs.busybox.net/show_bug.cgi?id=9781
>
> Bug ID: 9781
> Summary: ti-sgk-km build on kernel >4.1
> Product: buildroot
> Version: unspecified
> Hardware: Other
> OS: Linux
> Status: NEW
> Severity: normal
> Priority: P5
> Component: Other
> Assignee: unassigned at buildroot.uclibc.org
> Reporter: sbenoit at brioconcept.com
> CC: buildroot at uclibc.org
> Target Milestone: ---
>
> The ti-gfx-km will not find the dmac function when building.
> Since the prototype has changed file/folder since version higher than 4.1. We
> need to patch the ocfunc.c file and add
>
>
> 54a55,57
> > #if (LINUX_VERSION_CODE >= KERNEL_VERSION(4,1,0))
> > #include <../mm/dma.h>
> > #endif
>
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-28 19:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 13:31 [Buildroot] [Bug 9781] New: ti-sgk-km build on kernel >4.1 bugzilla at busybox.net
2017-03-28 19:37 ` Thomas Petazzoni [this message]
[not found] ` <9521dc83-a6f0-a495-884b-dbd3119deb7d@gmail.com>
2017-05-07 14:10 ` Thomas Petazzoni
2017-03-28 20:30 ` [Buildroot] [Bug 9781] ti-sgx-km " bugzilla at busybox.net
2018-02-05 16:46 ` bugzilla at busybox.net
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=20170328213751.5098434e@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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.