All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Gutierrez <kuyurix@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] ti-gfx: bump to version 5_01_00_01
Date: Thu, 27 Feb 2014 17:08:33 -0300	[thread overview]
Message-ID: <CA+kK6Wt1obEVFsk_G_RPrhn6ViVxXVRq11JvT3mrqW0dQUWuCA@mail.gmail.com> (raw)
In-Reply-To: <87vbw2dmqi.fsf@dell.be.48ers.dk>

Hi Peter, all

Ehh, but the newclkapi patch no longer applies:
>
> Applying ti-gfx-newclkapi.patch using patch:
> patching file GFX_Linux_KM/services4/system/omap3630/sysutils_linux.c
> Hunk #1 FAILED at 153.
> Hunk #2 FAILED at 167.
> Hunk #3 FAILED at 233.
> Hunk #4 FAILED at 246.
> Hunk #5 succeeded at 540 (offset 166 lines).
> Hunk #6 FAILED at 444.
> Hunk #7 FAILED at 490.
> 6 out of 7 hunks FAILED -- saving rejects to file
> GFX_Linux_KM/services4/system/omap3630/sysutils_linux.c.rej
> Patch failed!  Please fix ti-gfx-newclkapi.patch!
> make: *** [/home/peko/source/buildroot/
> output/build/ti-gfx-5_01_00_01/.stamp_patched] Error 1
>
> Could you please send a patch to fix it?
>

I wonder if we need to apply that patch?

All I can say that SGX version works great on BBB(ti-kernel 3.12 using
beaglebone_defconfig)

Regards,
Marcelo




2014-02-26 10:31 GMT-03:00 Peter Korsgaard <peter@korsgaard.com>:

> >>>>> "Peter" == Peter Korsgaard <jacmet@uclibc.org> writes:
>
> >>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
>  >> Marcelo, All,
>  >> On 2014-02-13 18:38 +0000, kuyurix at gmail.com spake thusly:
>  >>> From: Marcelo Gutierrez <kuyurix@gmail.com>
>  >>>
>  >>> Signed-off-by: Marcelo Gutierrez <kuyurix@gmail.com>
>
>  >> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
>
>  >> Notes:
>
>  >> - The version pointed to by Spencer was 5.00.x, and was a beta
>  >> version, and only contained the hardfp variant. The version in
>  >> this patch is 5.01.x, is not marked as beta, and contains both
>  >> the hardfp and softfp variants.
>
>  >> - With 4.10.x and before, the *_$(TI_GFX_VERSION).bin archive would
>  >> contain a huge load of stuff we did not need, and was roughly
>  >> 1.7GiB big. But with 5.01.x, this file is now back to a more
>  >> acceptable size, roughly 140MiB (although it still contains way
>  >> much more than we need).
>
>  > Sounds good. Committed to next, thanks both.
>
> Ehh, but the newclkapi patch no longer applies:
>
> Applying ti-gfx-newclkapi.patch using patch:
> patching file GFX_Linux_KM/services4/system/omap3630/sysutils_linux.c
> Hunk #1 FAILED at 153.
> Hunk #2 FAILED at 167.
> Hunk #3 FAILED at 233.
> Hunk #4 FAILED at 246.
> Hunk #5 succeeded at 540 (offset 166 lines).
> Hunk #6 FAILED at 444.
> Hunk #7 FAILED at 490.
> 6 out of 7 hunks FAILED -- saving rejects to file
> GFX_Linux_KM/services4/system/omap3630/sysutils_linux.c.rej
> Patch failed!  Please fix ti-gfx-newclkapi.patch!
> make: ***
> [/home/peko/source/buildroot/output/build/ti-gfx-5_01_00_01/.stamp_patched]
> Error 1
>
> Could you please send a patch to fix it?
>
> I also see that 5_01_01_01 is out:
>
>
> http://tigraphics.blogspot.be/2014/02/1q-2014-linux-graphics-sdk-release.html
>
> --
> Bye, Peter Korsgaard
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140227/f9743bad/attachment.html>

      reply	other threads:[~2014-02-27 20:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 18:38 [Buildroot] [PATCH 1/1] ti-gfx: bump to version 5_01_00_01 kuyurix at gmail.com
2014-02-13 22:03 ` Spenser Gilliland
2014-02-13 22:50   ` Marcelo Gutierrez
2014-02-14  9:57     ` Peter Kuemmel
2014-02-14 11:03       ` Peter Kuemmel
2014-02-14 16:02         ` Marcelo Gutierrez
2014-02-14 16:11           ` Peter Kuemmel
2014-02-14 16:22             ` Marcelo Gutierrez
2014-02-23 19:31 ` Yann E. MORIN
2014-02-23 19:56   ` Peter Korsgaard
2014-02-26 13:31     ` Peter Korsgaard
2014-02-27 20:08       ` Marcelo Gutierrez [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=CA+kK6Wt1obEVFsk_G_RPrhn6ViVxXVRq11JvT3mrqW0dQUWuCA@mail.gmail.com \
    --to=kuyurix@gmail.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.