

They’re getting better, but per the last Gamers Nexus video I watched, they are still falling behind nVidia/AMD’s, performance-wise. They’re good price wise.
All posts/comments by me are licensed by CC BY-NC-SA 4.0.
They’re getting better, but per the last Gamers Nexus video I watched, they are still falling behind nVidia/AMD’s, performance-wise. They’re good price wise.
Maybe, you never know. That would be even harder for them to do though, since that is a utility app for working with files, and files are shared between devices.
It’s too bad that there’s still a proprietary binary layer that this driver will talk to. (I’m assuming right/wrong that it’s not open source, since it’s binary.)
I must’ve missed that from in the post. Do you have more information on that?
The article mentions the following …
the NOVA driver is intentionally limited to the RTX 20 “Turing” GPUs and newer where there is the NVIDIA GPU System Processor (GSP) with the firmware support to leverage for an easier driver-writing experience.
Also in the same article, there’s a link to another article that mentions it a little bit more …
“… serving as a hard- and firmware abstraction layer for GSP-based NVIDIA GPUs.”
I’ve also read something about it from other places, other articles as well …
The GSP is binary-only firmware loaded at run-time. The open-source kernel driver explicitly depends upon the GSP-supported graphics processors.
Basically, some/allot of the Nvidia “magic” is in their hardware/firmware, and that they are not open source.
Feel free to double check me on this though, that’s just my interpretation based on quickly reading some articles over the last six months or so.
The cost of moving everything over to AMD is high so it just takes time to get rid of old hardware as a best case scenario.
Totally understand. I hang on to my current GPU for as long as I can before switching to a new one (fiveish years), especially these days.
Having said that, if your goal is to move to Linux for gaming, best to go with a whole AMD setup if possible. Also a distro that updates often but is not bleeding edge. (For me, Fedora/KDE.)
Somewhere, somebody’s having a meltdown because Rust is spreading more and more in the kernel.
Probably more than just one somebody, based on the drama in these last few week’s. 😜
Good to see that NVIDIA is writing opensource drivers (or starting to). I guess it’s too much to ask to support old graphics cards, with NVIDIA mostly caring about money and a linux driver being an incentive to choose NVIDIA over AMD for some.
It’s too bad that there’s still a proprietary binary layer that this driver will talk to. (I’m assuming right/wrong that it’s not open source, since it’s binary.)
Best to support AMD if you game on Linux. Really wish Intel would step up their GPU game.
This was from their wiki …
The RetroDECK Team considers RetroDECK an in-between solution of EmuDeck and Batocera that fills a gap no one else is filling.
Could someone elaborate on this for me please? What the different is between the three products, and what is there to go “in-between” of/on?
Yeah you got to wonder why they’re bothering to remove it if the functionality is still there from another one of their apps.
From the article …
You can still use Files by Google to share Android applications in a similar manner. Under Categories, go to “Apps” and then the overflow menu for what you want to “Share.”
Was quick browsing for openwrt and found the banana pi r3.
One thing that surprised me when I was looking to upgrade my old router ith OpenWRT is if a firmware for your router supports ALL of the features/hardware of that router. In my case, Wifi support was not supported, so I had to disregard using OpenWRT as a choice.
So be sure to look carefully at the firmware that you find. I personally had just thought that if a firmware exists for your hardware that all of the major (but maybe not minor) features would be supported, and that is not always the case.
This was a good read, thank you for doing this!
As far as the shutdown of the Epic game Dauntless, was any reason given for the shutdown?
I mean, its just a ctrl+c and a ctrl+v. 🙂
It looks like the Eternity client doesn’t support subscript?
Don’t know what to say, my account is on Lemmy.World, and that’s their instructions on how to format one’s comments. /shrug
In the past (tenish months ago) I heard this same issue, and I tried removing the subscripting, which made the footer text the same size of the rest of the text, and then I was getting people complaining about my footer text being too large for a footer. My hope was that ten months later, all clients would support subscript fonts/text.
Honestly, at this point I’d suggest you talk to the devs of your client, to support subscript font/text.
Nah, I think it’s neat as well. Lemmy would be more boring if no user had idiosyncrasies.
Kind of a sad state of affairs for us all, that wanting to license your own content would be considered an idiosyncrasy, but I get what you were trying to say. 🙂
Hell, I’ve even tagged you with “CC BY-NC-SA 4.0” in my Lemmy client -
Well I’m not the first to use it, I learned to use it here from someone else, but open source licensing notoriety is something I can live with. 😜
which means I will confront you if you ever stop doing it.
Honestly it would be me just leaving Lemmy (again) if the harassment gets to be too much (Edit: Example: https://lemmy.world/comment/15320340).
But I’d rather be here than Reddit, even with the lesser moderation that happens here.
I do appreciate your support, thank you. 👍
Why all the tilde symbols? That’s what makes it quite distracting and hard to read for me tbh.
I’m using the Lemmy.World formatting (https://join-lemmy.org/docs/users/02-media.html). I’m subscripting the text/link to make it smaller/footer.
It sounds like your client is not supporting that. You should speak with the devs of your client about that. Here’s the actual formatting string being used by me…
[~This~ ~comment~ ~is~ ~licensed~ ~under~ ~CC~ ~BY-NC-SA~ ~4.0~](https://creativecommons.org/licenses/by-nc-sa/4.0/legalcode.en)
Well, scrapers probably would ignore it.
Maybe, I wouldn’t doubt it, if true. We live in the age of “ask for forgiveness and not permission”. But the law is the law, and forgiveness may cost them some $$$ down the road. At the very least it leaves them exposed vis-a-vis ‘Safe Harbor’ laws-wise, when some other powerful entity wants to go to war with them.
In either case, I’m not going to give up my rights just because currently laws are not enforced. Like most things with humans, things move back-and-forth throughout time, and what may be overlooked today may be scrutinized thoroughly tomorrow.
(And for the record, you’re the bazillionish person to tell me that. The repetition is real.)
TOS can’t change Law, can’t strip away rights that you have.
Law always trumps TOS.
In fact, if a company tries to via their TOS they are opening themselves up for big risks/lawsuits, as they are trying to gain ownership of your content, voiding their Safe Harbor law protections.
They can’t have it both ways, thats not how the Law works. Either they have the protection, or they own the content.
Also as someone else suggested, look into automation lol
I comment on both my phone and PC. As a sofware developer, its not a big deal for me to copy/paste, I do it all the time (even read the O’Reilly book on the subject 😜 ).
I can’t find the link to show you, but I had thought I read before where some of the Nvidia ‘Secret Sauce’ code that would normally be in the driver software was in the firmware, and that the firmware was not open sourced.
So it would mean extra effort for the open source driver coders to try to get the same kind of performance. Basically Nvidia not open sourcing their proprietary code that gives them the/partial advantage in speed.
I think I remember reading about it in a web article, but like as I mentioned, I can’t remember which, or else I’d link it for you.
More than willing to admit I’m wrong about that interpretation too, but I remember it’s sticking out in my mind at the time of reading, as a “Sneaky Nvidia!” type of thought.
This comment is licensed under CC BY-NC-SA 4.0