Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 10 Dec 2017 12:52:31 +0800
From:      blubee blubeeme <gurenchan@gmail.com>
To:        Baho Utot <baho-utot@columbus.rr.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: CUDA under FreeBSD
Message-ID:  <CALM2mEm8RdC8D_ghctZDdfY4=hz+OwPEVH+e+STstna_ENfs-w@mail.gmail.com>
In-Reply-To: <e2ff2591-3011-0f28-41b6-47168bbd4414@columbus.rr.com>
References:  <34331.107.77.207.211.1512384505.squirrel@cosmo.uchicago.edu> <0545699d-9df7-ced2-4990-27e3ecb8e531@ShaneWare.Biz> <a7yr-z4gf-wny@FreeBSD.org> <e2ff2591-3011-0f28-41b6-47168bbd4414@columbus.rr.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Sun, Dec 10, 2017 at 11:13 AM, Baho Utot <baho-utot@columbus.rr.com>
wrote:

> On 12/9/2017 9:45 PM, Jan Beich wrote:
>
>> Shane Ambler <FreeBSD@ShaneWare.Biz> writes:
>>
>> On 04/12/2017 21:19, galtsev@kicp.uchicago.edu wrote:
>>>
>>> On Mon, December 4, 2017 4:24 am, Carmel NY wrote:
>>>>
>>>>> Out of morbid curiosity, I was wondering if anyone could tell me
>>>>> the real reason that Nvidia does not support CUDA under
>>>>>
>>>> Arrogance would be my guess.
>>>>
>>> The morbid part is that they give us the linux libcuda, so we should be
>>> able to run linux binaries that use cuda, just not native apps.
>>>
>> Modern CUDA toolkit is 64bit but runtime only works on 32bit (bug 206711).
>> Building as -m32 is probably still possible but may not fit all workloads
>> nor run as fast.
>>
>> FreeBSD? Also, what are the realistic expectations for it getting
>>>>> supported shortly?
>>>>>
>>>> Zero is my estimate. The way to let one's steam about them is just
>>>> not to buy ther hardware. Their attitude to open sourse and
>>>> unwillingness to disclose details of their hardware was always much
>>>> worse than that of their competitors (ATI/AMD, matrox...).
>>>>
>>>> This is just my opinion based on my subjective observations.
>>>>
>>> I'm sure on an episode of bsdnow, they mentioned asking an nvidia dev
>>> at one of the conferences and they said there shouldn't be any technical
>>> reason, it just isn't enabled in the build and they would look into it.
>>> Still hasn't helped any.
>>>
>> Just like Vulkan, just like KMS, just like encoding/capture acceleration.
>> NVIDIA always conveniently forgets about FreeBSD. However, the ailment
>> isn't really specific to NVIDIA but affects most binary blob vendors.
>> For one, Widevine CDM is maintained by Google but EME itself was pushed
>> to W3C by Netflix, a FreeBSD vendor which conveniently forgot a browser
>> can run on FreeBSD.
>>
>>
> What is FreeBSD market share?
> Could be the market share of FreeBSD is so small it is not worth their
> time?
> Maybe the FreeBSD developers are too abrasive?
> Or maybe some other reason?
> Linux is everywhere so maybe that is why Linux gets all the glory?
>
>
>
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe
> @freebsd.org"
>

NVIDIA doesn't forget about FreeBSD, there are devs over there that uses
it. The issue is FreeBSD didn't have enough devs willing or able to do the
work necessary to get the graphics ported in a way that would bring
interest to this platform.

The linuxkpi stuff is cute but it's not a real long term solution. The
whole DRM/KMS needs to be ported to FreeBSD and have a few major titles
over here; Steam for example, that would get people's attention.

It's something that will get done but it needs some time.

@Baho
Maybe if you spent more time providing solutions and doing productive work
you wouldn't have to be feeling like nobody wants you around.

How does your answer help anyone overcoming the obstacle of getting CUDA on
FreeBSD?



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?CALM2mEm8RdC8D_ghctZDdfY4=hz+OwPEVH+e+STstna_ENfs-w>