This will eliminate that judder effect that makes motion appear to stop and start 24 times each second. Now the motion will be smoother. I just wonder if it is smooth enough. I think the projectors... and TVs... need to support any arbitrary frame rate up to at least 120 fps. Then let the shooting camera decide what works best for what they are shooting. Disk drives are not as expensive as a mile of 35mm film.
You do have backups of all the data, including from workstations, at a backup site well away from the fire zone, right? If not, grab the disks first and do nothing else until those are out of danger. Then deal with what will get you back on online and in operation somewhere, first. Don't bother what what insurance can replace.
Actually, there are kernel developers willing to sign an NDA for the specs... provided they can release the SOURCE CODE they produce. That a compromise that NVIDIA seems unwilling to work with.
I get pretty graphics and nice clean crisp text from nouveau. Can't say that about the nvidia driver. Sure, it can twist and rotate the graphics 100 times a second. But who cares when it comes out like crap after the eye candy show is done and I need to get back to work?
... there is the Nouveau free driver, it works very well for 2D stuff, but does not work for 3D stuff.
Then there is the NVIDIA blob driver, it works very well for 3D stuff, but works like crap for 2D stuff (and crashes).
So it depends on your requirements, and how wedded you are to the "Free" concept. Having said that, if there was a free driver that does 3D on Nvidia cards, I'd take it.
I'm not so wedded to 3D stuff as I am 2D stuff. You can figure out which driver is working for me on the NVIDIA based machines. If ATI ever gets REAL about playing well with Linux, it will get the "always buy that" recommendation. For now it's half-assed support with big problems vs. half-assed support with different big problems.
But... they don't. The majority of my system crashes are due to NVIDIA drivers being poorly programmed. Nouveau has never caused any such problems since 2.6.38.
A reference driver is fine. Open source it. Then the Linux source tree can include it. Then when the hardware maker adds new hardware or firmware features, submit patches. If they make a whole new architecture that is not compatible, submit a whole new driver... as source code. Then it's in the Linux tree and it can be maintained by kernel developers when the kernel changes that requires something to change in the driver (for example a change in number of parameters needed for some kernel function call to support some new feature).
NVIDIA should make the hardware and firmware that runs it. The main CPU should be the realm of the OS. These two should talk to each other. NVIDIA is not cooperating with that.
And of course whoever comes 2nd has to make drivers for whatever was 1st. But once each recognizes the importance of the other, the roles can settle out to where they should be.
There should never be intellectual property in an INTERFACE. I don't GAF what is going on inside the video card to accomplish what is asked of it by software. Put the IP in the hardware/firmware, open the interface, and lets move forward. Simple as that. A blob for the firmware image itself is fine if they don't want to store it in flash on the card. Get some memory, load the blob from disk, transfer the blob to the card, free the memory, and move on.
Then how come when I am running their driver and some issue requires me to Ctrl+Alt+F1 to get a console to fix X or something that is bogging down X, I get a total crap video mode with glyphs I cannot read, and bit splatter in the video buffer than X cannot clear up when I Ctrl+Alt+F7 to get back to X? FYI, this never happens with nouveau... so it is clear the NVIDIA hardware CAN do text mode well. The NVIDIA programmers need to fix even the text mode or at least arrange for driver splitting where they hand off to nouveau in text mode.
Oh, and did I mention, they need to keep up with the kernel versions? Yeah, yeah, I know, the pace of change is fast. If they were to just open source the driver AND continue working on changes, sharing with the community, then the community can share back (and then we can openly see who is able to do better support).
Hardware to software interfaces are just that... interfaces. Hardware, meet software. Software, meet hardware. Now if hardware wants to make the rules for the language to be spoken, then fine... let the software know what that language is.
At least I don't have "fracas du jour" with the nouveau driver.
Web browsing experiences are slowing down from advertising. But it's not an issue around the images that advertising loads. Instead, it is a combination of the extra time needed to load Javascript from advertisers (whether it is to spy on you or just to rotate ads around), and programming defects in that Javascript (doesn't play well with others). Browsers have to stop and wait for scripts to finish loading before allowing everything to run or even be rendered. You can have a page freeze in a blank state when some advertiser's Javascript request isn't connecting or loading.
The solution SHOULD be that browsers DISALLOW loading Javascript (or any script as the case may be) from more than one different hostname per page (e.g. the page's own hostname not being counted against the limit of one). This would remain flexible enough to reference scripts from a different server, or even an advertising provider, without allowing it to get excessive. Browsers should also limit the time needed to load other scripts, though this may be complicated for scripts calling functions in other scripts. Perhaps the rule should be that even within a page, scripts are not allowed to call scripts loaded from a different hostname, except the scripts from the page's hostname itself can call scripts in one.
I've also noted quite many web sites that just get totally stuck and refuse to even render anything at all when they can't finish a connection for some script URL. Site scripting programmers need to get a better handle on error conditions. The advertising companies seem to be using too many unqualified programmers.
Slashdot Mirror
This will eliminate that judder effect that makes motion appear to stop and start 24 times each second. Now the motion will be smoother. I just wonder if it is smooth enough. I think the projectors ... and TVs ... need to support any arbitrary frame rate up to at least 120 fps. Then let the shooting camera decide what works best for what they are shooting. Disk drives are not as expensive as a mile of 35mm film.
How about just every other frame, then?
... if it were fast enough, had enough RAM (4G) and storage (32G), and had a fully open architecture ... and priced $1 each.
You do have backups of all the data, including from workstations, at a backup site well away from the fire zone, right? If not, grab the disks first and do nothing else until those are out of danger. Then deal with what will get you back on online and in operation somewhere, first. Don't bother what what insurance can replace.
Actually, there are kernel developers willing to sign an NDA for the specs ... provided they can release the SOURCE CODE they produce. That a compromise that NVIDIA seems unwilling to work with.
I get pretty graphics and nice clean crisp text from nouveau. Can't say that about the nvidia driver. Sure, it can twist and rotate the graphics 100 times a second. But who cares when it comes out like crap after the eye candy show is done and I need to get back to work?
... there is the Nouveau free driver, it works very well for 2D stuff, but does not work for 3D stuff.
Then there is the NVIDIA blob driver, it works very well for 3D stuff, but works like crap for 2D stuff (and crashes).
So it depends on your requirements, and how wedded you are to the "Free" concept. Having said that, if there was a free driver that does 3D on Nvidia cards, I'd take it.
I'm not so wedded to 3D stuff as I am 2D stuff. You can figure out which driver is working for me on the NVIDIA based machines. If ATI ever gets REAL about playing well with Linux, it will get the "always buy that" recommendation. For now it's half-assed support with big problems vs. half-assed support with different big problems.
But ... they don't. The majority of my system crashes are due to NVIDIA drivers being poorly programmed. Nouveau has never caused any such problems since 2.6.38.
A reference driver is fine. Open source it. Then the Linux source tree can include it. Then when the hardware maker adds new hardware or firmware features, submit patches. If they make a whole new architecture that is not compatible, submit a whole new driver ... as source code. Then it's in the Linux tree and it can be maintained by kernel developers when the kernel changes that requires something to change in the driver (for example a change in number of parameters needed for some kernel function call to support some new feature).
Drivers are not an OS.
NVIDIA should make the hardware and firmware that runs it. The main CPU should be the realm of the OS. These two should talk to each other. NVIDIA is not cooperating with that.
And of course whoever comes 2nd has to make drivers for whatever was 1st. But once each recognizes the importance of the other, the roles can settle out to where they should be.
Theo was a very honest guy when I talked to him. He put me in my place. I look forward to that from Linus.
There should never be intellectual property in an INTERFACE. I don't GAF what is going on inside the video card to accomplish what is asked of it by software. Put the IP in the hardware/firmware, open the interface, and lets move forward. Simple as that. A blob for the firmware image itself is fine if they don't want to store it in flash on the card. Get some memory, load the blob from disk, transfer the blob to the card, free the memory, and move on.
Projectile chairs are a pretty clear message.
Then how come when I am running their driver and some issue requires me to Ctrl+Alt+F1 to get a console to fix X or something that is bogging down X, I get a total crap video mode with glyphs I cannot read, and bit splatter in the video buffer than X cannot clear up when I Ctrl+Alt+F7 to get back to X? FYI, this never happens with nouveau ... so it is clear the NVIDIA hardware CAN do text mode well. The NVIDIA programmers need to fix even the text mode or at least arrange for driver splitting where they hand off to nouveau in text mode.
Oh, and did I mention, they need to keep up with the kernel versions? Yeah, yeah, I know, the pace of change is fast. If they were to just open source the driver AND continue working on changes, sharing with the community, then the community can share back (and then we can openly see who is able to do better support).
Hardware to software interfaces are just that ... interfaces. Hardware, meet software. Software, meet hardware. Now if hardware wants to make the rules for the language to be spoken, then fine ... let the software know what that language is.
At least I don't have "fracas du jour" with the nouveau driver.
It isn't NVIDIA's job to make drivers for someone else's OS.
Web browsing experiences are slowing down from advertising. But it's not an issue around the images that advertising loads. Instead, it is a combination of the extra time needed to load Javascript from advertisers (whether it is to spy on you or just to rotate ads around), and programming defects in that Javascript (doesn't play well with others). Browsers have to stop and wait for scripts to finish loading before allowing everything to run or even be rendered. You can have a page freeze in a blank state when some advertiser's Javascript request isn't connecting or loading.
The solution SHOULD be that browsers DISALLOW loading Javascript (or any script as the case may be) from more than one different hostname per page (e.g. the page's own hostname not being counted against the limit of one). This would remain flexible enough to reference scripts from a different server, or even an advertising provider, without allowing it to get excessive. Browsers should also limit the time needed to load other scripts, though this may be complicated for scripts calling functions in other scripts. Perhaps the rule should be that even within a page, scripts are not allowed to call scripts loaded from a different hostname, except the scripts from the page's hostname itself can call scripts in one.
I've also noted quite many web sites that just get totally stuck and refuse to even render anything at all when they can't finish a connection for some script URL. Site scripting programmers need to get a better handle on error conditions. The advertising companies seem to be using too many unqualified programmers.
And stupid CEOs are wooing stupid VCs.
Someone in a CEO roles should not need this feedback. If they can't see what they are doing wrong, they need to start over.
DISAGREE! If you need to be told what's wrong, you were already a loser before.
You have it wrong. Agent Smith created this bug.
... except if they are a government contractor.
What are they afraid of? They are the government. Oh wait ...
Random bits are best. Be sure to choose a good balance so they have to record LOTS of different URLs and e-mail addresses.