From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] AVX512 NUCs for FATE and development
Date: Fri, 9 Dec 2022 18:07:43 +0100
Message-ID: <20221209170743.GG3806951@pb2> (raw)
In-Reply-To: <CAK+ULv4-7AvSJ48B4XRWMe3JL7zPpaLr9ftz5jpYNXAJzByf_Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 938 bytes --]
On Thu, Dec 08, 2022 at 09:40:12PM +0000, Kieran Kunhya wrote:
> I intend to buy this RAM:
> https://www.amazon.co.uk/Crucial-CT2K16G4SFRA32A-PC4-25600-SODIMM-260-Pin/dp/B08C4X9VR5
>
> 2x £529 for NUCs
> 2x £102.48 for RAM
> 2x £69 for M.2 NVMe SSD
>
> £1400 total.
iam in favor of this too
I would also recommand to use (SPI or FFIS) FFmpeg funds as these seem to
increase each year and i presume people who donate want their donation to
be used.
also note that SPI will own the hardware legally for us IIRC if SPI/FFmpeg
funds are used.
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
If you drop bombs on a foreign country and kill a hundred thousand
innocent people, expect your government to call the consequence
"unprovoked inhuman terrorist attacks" and use it to justify dropping
more bombs and killing more people. The technology changed, the idea is old.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-12-09 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 18:08 Kieran Kunhya
2022-12-08 21:20 ` Ronald S. Bultje
2022-12-08 21:29 ` Jean-Baptiste Kempf
2022-12-08 21:40 ` Kieran Kunhya
2022-12-09 17:07 ` Michael Niedermayer [this message]
2022-12-10 18:10 ` Carl Eugen Hoyos
2022-12-17 19:57 ` Kieran Kunhya
2022-12-17 20:46 ` Michael Niedermayer
2022-12-18 10:41 ` Stefano Sabatini
2023-01-03 11:23 ` Kieran Kunhya
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=20221209170743.GG3806951@pb2 \
--to=michael@niedermayer.cc \
--cc=ffmpeg-devel@ffmpeg.org \
/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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git