Since the critics focus on missing reclocking, does that mean every thing else is done and nouveau would be perfect once the firmware magically appears? I doubt it and believe there is enough other stuff that people have to work on.
Announcement
Collapse
No announcement yet.
Nouveau Persevered In 2017 For Open-Source NVIDIA But 2018 Could Be Much Better
Collapse
X
-
Cards before the pascal series of nvidia cards needed no firmware whatsoever unless you wanted GPU video decoding and encoding. After pascal you need signed firmware for anything to load or execute on the GPU. This is similar to AMD requiring a signed firmware VBIOS to be loaded by the linux kernel to be put onto the GPU. But AMD gives out that signed firmware and since nvidia never needed such firmware till pascal cards it is only now a problem. Old cards that run nouveau are entirely FOSS with no blobs except the read only firmware on the hardware itself. But that doesn't affect the linux kernel implementation.
- Likes 1
Comment
-
Originally posted by bemerk View PostSince the critics focus on missing reclocking, does that mean every thing else is done and nouveau would be perfect once the firmware magically appears? I doubt it and believe there is enough other stuff that people have to work on.
Hardware acceleration for media is again bound by firmwares, so what else can they do?
- Likes 2
Comment
-
Originally posted by notanoob View PostThis is similar to AMD requiring a signed firmware VBIOS to be loaded by the linux kernel to be put onto the GPU.
* The VBIOS code is actually written in a CPU-independent bytecode. The only x86-specific code in VBIOS is the bytecode interpreter and the INT15 handlers.Test signature
- Likes 5
Comment
-
Originally posted by bridgman View Post* The VBIOS code is actually written in a CPU-independent bytecode. The only x86-specific code in VBIOS is the bytecode interpreter and the INT15 handlers.
Is it possible to add arch-specific bytecode interpreters and "INT15 handlers" (whatever these handlers are) with VBIOS mods?
Comment
-
The biggest issue with Nouveau is how distro maintainers are ignoring it. Even a latest live image of cutting-edge rolling release distros won't boot on Pascal because of Nouveau: unsupported chipset, and it's not Nouveau's fault, but of those who include outdated shit in distributions.
Comment
-
Originally posted by bridgman View Post
Quick note - for unfortunate historical reasons VBIOS and microcode are both referred to as "firmware", but it's not the VBIOS that gets loaded into the GPU, it's separate microcode images.
- Likes 2
Comment
-
Originally posted by shmerl View PostIs there a reason for AMD not to open source microcode and VBIOS (besides HDCP DRM related stuff?). I.e. can AMD for instance release DRM-free version of both that's FOSS?
- Likes 1
Comment
-
Originally posted by starshipeleven View PostWait, so what are the supported architectures apart from x86? (I assume this was for supporting more than just x86) Is it possible to add arch-specific bytecode interpreters and "INT15 handlers" (whatever these handlers are) with VBIOS mods?
Originally posted by ua=42Legally, they can't release it as it would allow circumventing the DRM. It would violate the agreements they signed to be able to implement the various DRM systems in the first place.
Comment
Comment