From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9781] ti-sgx-km build on kernel >4.1
Date: Mon, 05 Feb 2018 16:46:03 +0000 [thread overview]
Message-ID: <bug-9781-163-ApHS144AJk@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9781-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9781
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|NEW |RESOLVED
--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
This really is an upstream problem. The Git repository at
http://git.ti.com/graphics/omap5-sgx-ddk-linux has newer versions, but the Git
history is a bit of a mess, making it difficult to know if the latest master
branch still applies to the SoCs ti-sgx-km currently supports.
Someone having access to HW and interested in TI platforms should look into
this. Could you submit a patch updating the ti-sgx-km to a newer version?
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2018-02-05 16:46 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
[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 [this message]
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=bug-9781-163-ApHS144AJk@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.