From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [REFUND-REQUEST] BananaPi BPI-F3 SpacemiT K1 RISC-V Devboard
Date: Thu, 01 Aug 2024 21:22:13 +0300
Message-ID: <22395185.EfDdHjke4D@basile.remlab.net> (raw)
In-Reply-To: <20240801170013.GY4991@pb2>
Le torstaina 1. elokuuta 2024, 20.00.13 EEST Michael Niedermayer a écrit :
> On Thu, Aug 01, 2024 at 05:14:52PM +0200, Niklas Haas wrote:
> > Hi all,
> >
> > I would like to request reimbursement on the named RISC-V development
> > board. It will be used to develop and test H.264 RVV routines, and
> > probably more in the future (e.g. swscale).
> >
> > The total cost including tax and shipping to Germany is 153.41 EUR.
>
> that LGTM
>
> on a related topic, what to look for when choosing a RISC-V board ?
I hate to sound like a smartass but it really depends on your purpose.
For FFmpeg development, you need support for Bit-manip (B) and Vector (V).
There are currently two eligible chipsets:
- Canaan K230: single (vector-capable) core, 128-bit vectors,
- SpacemiT K1 (or M1): octa-core, 256-bit vectors.
The later is available in several form factors: BananaPi-F3, Milk-V Jupiter,
DC-ROMA laptop II, etc. Beware that cheaper variants come with only 4 GiB RAM,
which is little for 8 cores.
N.B.: The market situation is fluid, so Osborne effect rules.
--
Rémi Denis-Courmont
http://www.remlab.net/
_______________________________________________
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:[~2024-08-01 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 15:14 Niklas Haas
2024-08-01 17:00 ` Michael Niedermayer
2024-08-01 18:22 ` Rémi Denis-Courmont [this message]
2024-08-04 18:30 ` Stefano Sabatini
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=22395185.EfDdHjke4D@basile.remlab.net \
--to=remi@remlab.net \
--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