Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] nvidia-tegra23: new package
Date: Wed, 19 Nov 2014 22:42:58 +0100	[thread overview]
Message-ID: <20141119214258.GB3779@free.fr> (raw)
In-Reply-To: <546C4ACA.6030008@sensefly.com>

Nicolas, All,

On 2014-11-19 08:46 +0100, Nicolas Serafini spake thusly:
> Le 18. 11. 14 21:22, Yann E. MORIN a ?crit :
> >Nicolas, All,
> >
> >On 2014-11-05 16:52 +0100, Nicolas Serafini spake thusly:
> >>This patch adds a new package for all libraries, drivers and codecs
> >>provided by Nvidia Linux 4 Tegra release 16.4.0.
> >
> >I'm already working on a package for the Nvidia blobs for i386 and
> >x86_64, so I think your submision could fit in that effort.

> This patch was only for Tegra2 and Tegra3 but it's possible to integrate
> blobs for Tegra 4 and Tegra K1 too. It was my idea in a future patch update.

Yes, let's start simple, and build from there.

> All binaries and docs can be found here
> https://developer.nvidia.com/linux-tegra
> 
> Let me know if I can help you for the tegra part.

Yup, I do not have access to a Tegra device, so I'll rely on you for
testing.

However, I already noticed something we can improve with that patch:
trim it down to a reasonable size, by off-loading the GL headers to
their own package, using the headers from the OpenGL registry, for which
I already have a package ready:

    https://www.opengl.org/registry/
    http://patchwork.ozlabs.org/patch/396955/

I still have a few things to do on that package, though, but is working
pretty Ok for the x86 NVidia blob, so there's good hope it works for the
Tegra variant as well.

I won;t be able to touch that before the WE, though, and it;s low
priority because we're in feature-freeze until the end of November
anyway (so fixing stuff comes first).

I'll get you posted on the progress. ;-)

Regards,
Yann E. MORIN.


-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2014-11-19 21:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-05 15:52 [Buildroot] [PATCH 1/1] nvidia-tegra23: new package Nicolas Serafini
2014-11-18 20:22 ` Yann E. MORIN
2014-11-19  7:46   ` Nicolas Serafini
2014-11-19 21:42     ` Yann E. MORIN [this message]
2014-11-20 10:48       ` Nicolas Serafini
2014-11-19 22:58 ` Yann E. MORIN
2014-11-20 11:18   ` Nicolas Serafini
2014-11-20  0:06 ` Yann E. MORIN
2015-01-18 12:14 ` Yann E. MORIN
2015-01-19  7:51   ` Nicolas Serafini
2015-01-19 20:43     ` Yann E. MORIN
  -- strict thread matches above, loose matches on Subject: below --
2015-01-21 10:39 Ben Ben
2015-01-21 17:56 ` Yann E. MORIN

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=20141119214258.GB3779@free.fr \
    --to=yann.morin.1998@free.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox