A big problem in 1994 was the poor quality of DRAM used in graphics cards and/or tight DRAM timmings (many SVGA cards had overclocked DRAM, specially the ones running in VESA Local Bus 32-bit bus for i80486 CPUs).
Same here: total boycott to anything related to Sony until they remove the Other OS option and recognice they were wrong when fucking paying customers (!) (DRM rootkit anyone?). My boycott includes Games, DVD, BluRay, non watching Columbia pictures movies on cinema, bitching about Sony Corporation stocks, etc.
I also discourage family and friends for doing the same. Screwed once, my fault, twice is being idiot.
Parent comment was mine, I forgot to log in. I'm glad to see you here (I posted as 'aragon' in the PS2 Linux forums). I keep the PS2 Linux kit, but I'm no longer using it (2002-2007), and the PS3 with the last update before the one that banned Linux, as I like exotic CPU architectures (although I'm a long term x86 Linux user, since 1994).
For economics to be a science there also must be a way to test hypotheses. To date I haven't seen anything like this. So at best economics is wishful thinking, IMO.
Economics is full of ad hoc models, many of them in clear contradiction. I agree also with your signature: yes, debt is slavery (I can not yet believe people accepting 30-40 years mortgages, being some kind of neo-feudalism).
I wanted to say "vertex shader" and not "pixel shader". As you point, the PS3 has both vertex and pixel shaders, while the PICA200 seems to have just vertex shader support.
Note that the article summary is wrong: there is no pixel shader support in the PICA200 device (and neither is in OpenGLES 1.1), although the chip supports several marketspeak 'extensions' that somewhat allows you to hack a few selected shader-like features into the rendering pipeline.
That is also the case for the Playstation 3, and you can not deny it has pixel shader support.
I saw it in late nineties (circa 1998), American Megatrends (AMI) BIOS for Socket 7 Pentium-compatible processors. It was text mode, but used VGA character programming for simulating a graphic cursor with "arrow" shape typical from other GUI (it was noticed it was text mode and not full-fledge graphic mode because of 8th and 9th row in character bounding box were duplicated, if I recall correctly).
Trying it is not enough. It's 2010, and AMD bought ATI almost 4 years ago (1), so there are no excuses. I would be glad of buying AMD+ATI integrated graphics instead of Intel, but it is a no-no until drivers for Linux reach its Windows counterparts performance-wise, and of course, I will not buy anything from AMD+ATI until then, not before. I buy products based on facts, not promises (I already made a mistake 3 years ago buying a AMD/ATI integrated graphics, still today without proper driver for Linux WTF!!!).
If Google, because etics, is willing to lose such market as China, could get a huge credibility and respect increase (kudos, Google). Unfortunately, I'm skeptical about it.
This solution is simple transcoding, using a lot of CPU. They are probably picking the framebuffer from the display driver, providing it to a userland application that does the encoding and sending.
I expected a true lossless wifi link to the DVI/HDMI connector, this is a vendor-specific dirty hack.
Yes, 3.5" widescreen is small. However, you can change the font size both in the xterm, web browser, and many other apps just using the "zoom" button, and most applications use fonts larger than typical paperpack book. My eyesight is far from perfect (I'm in my mid-thirties, with myopia and some astigmatism in both eyes), not only I have no problem with, but I'm much happier with the new rather than the previous 3-and-something-inches mobile.
I replaced my netbook with a Nokia N900, because of:
- Built-in physical keyboard, and external full-size standard bluetooth keyboard.
- It is the first { Linux + X11 + phone } that works nicely (OpenMoko was a poor attempt), and it's Debian based! (Maemo).
- As music player: impressive.
- As video player: impressive for h264 (hardware accelerated), not bad for mpeg4-baseline.
- As photocamera: quite good (5MP + two-LED flash, quite sharp for a mobile camera, and much better than my previous standalone 3MP Canon Powershot 4 year old camera).
- As agenda: very good.
- For notes: I love the default notes application provided by Nokia. You can use Conboy too, which is also OK.
- Multitasking: very good, the best I've seen in smartphones, because of using Linux plus plenty RAM (256MB + 768MB for swap) is years-light ahead from Symbian, iPhone, and Windows Mobile devices.
- User interface: uses desktop composition, but with the vertical sync disabled (it is possible to enable it, but I will not enable it until some other does it and confirm that it is safe). That makes it less smooth than the one from the iPhone or from Android devices.
- Geekness: Linux, X11, 256MB RAM + 768MB of swap, 2-way in-order supescalar ARM CPU (ARM Cortex A8 @600MHz, 1200MIPS, 2.4-4.8GFLOPs (4.8 GFLOPs when using the VMLA -FMAC, floating point multiply and accumulate-)), ssh, sshd, xterm, dosbox, game console emulation, perl, python, clisp, ml, airodump/aircrack, etc. With the exception of the C++ compiler, which haven't manage to install into the device yet (I'm using a cross compiler in my main PC, provided with the SDK), because I'm afread of broken the shared library links (I'll do it when I'm sure I'll don't break anything), the device runs most Linux applications!
- Presentations/slideshows/portable video player/etc: TV-out (composite NTSC/PAL plus stereo sound, via 3 RCA connectors).
- Storage: 32GB built-in (write speed is about 10 MB/s), expandable up to to 48GB with an additional 16GB micro-SDHC card.
It's a port, I tried it this morning: runs in full resolution (800x480), accelerated 3D, and it is very smooth. The N900 is tiny monster: Linux, X11, composite desktop, 256MB RAM + 768MB swap, 2-way-in-order superscalar ARM ARM Cortex A8 CPU @600MHz, 1200MIPS, 2.4-4.8GFLOPs (4.8 GFLOPs when using VMLA opcode -similar to the FMAC, floating point multiply and accumulate-), hardware accelerated OpenGL ES 2.0, etc.
As contrast, using Dosbox on the N900 is slow, barey enough for simulating an 8MHz 80286.
Slashdot Mirror
A big problem in 1994 was the poor quality of DRAM used in graphics cards and/or tight DRAM timmings (many SVGA cards had overclocked DRAM, specially the ones running in VESA Local Bus 32-bit bus for i80486 CPUs).
Same here: total boycott to anything related to Sony until they remove the Other OS option and recognice they were wrong when fucking paying customers (!) (DRM rootkit anyone?). My boycott includes Games, DVD, BluRay, non watching Columbia pictures movies on cinema, bitching about Sony Corporation stocks, etc.
I also discourage family and friends for doing the same. Screwed once, my fault, twice is being idiot.
I don't doubt about organic storage capabilities, I was asking about random access time, capisci?
Parent comment was mine, I forgot to log in. I'm glad to see you here (I posted as 'aragon' in the PS2 Linux forums). I keep the PS2 Linux kit, but I'm no longer using it (2002-2007), and the PS3 with the last update before the one that banned Linux, as I like exotic CPU architectures (although I'm a long term x86 Linux user, since 1994).
Ok, and what about random access time?
Forgive my question: It's Sony, the PS3 Linux killer company, removing features and fucking paying customers.
Past benefits doesn't guarantee future income. In my opinion it makes no sense unless for "dumb devices".
For economics to be a science there also must be a way to test hypotheses. To date I haven't seen anything like this. So at best economics is wishful thinking, IMO.
Economics is full of ad hoc models, many of them in clear contradiction. I agree also with your signature: yes, debt is slavery (I can not yet believe people accepting 30-40 years mortgages, being some kind of neo-feudalism).
I wanted to say "vertex shader" and not "pixel shader". As you point, the PS3 has both vertex and pixel shaders, while the PICA200 seems to have just vertex shader support.
Note that the article summary is wrong: there is no pixel shader support in the PICA200 device (and neither is in OpenGLES 1.1), although the chip supports several marketspeak 'extensions' that somewhat allows you to hack a few selected shader-like features into the rendering pipeline.
That is also the case for the Playstation 3, and you can not deny it has pixel shader support.
I saw it in late nineties (circa 1998), American Megatrends (AMI) BIOS for Socket 7 Pentium-compatible processors. It was text mode, but used VGA character programming for simulating a graphic cursor with "arrow" shape typical from other GUI (it was noticed it was text mode and not full-fledge graphic mode because of 8th and 9th row in character bounding box were duplicated, if I recall correctly).
At least they're trying?
Trying it is not enough. It's 2010, and AMD bought ATI almost 4 years ago (1), so there are no excuses. I would be glad of buying AMD+ATI integrated graphics instead of Intel, but it is a no-no until drivers for Linux reach its Windows counterparts performance-wise, and of course, I will not buy anything from AMD+ATI until then, not before. I buy products based on facts, not promises (I already made a mistake 3 years ago buying a AMD/ATI integrated graphics, still today without proper driver for Linux WTF!!!).
... told you
Probably it is not ASCII nor EBCDIC (both dating from 1963). After searching a bit, it seems that uses its own character encoding: GOST 10859-64.
claimed that cracking wireless networks was "just in theory" and that 64 bit WEP was in "as secure as a wired network".
Really?
If Google, because etics, is willing to lose such market as China, could get a huge credibility and respect increase (kudos, Google). Unfortunately, I'm skeptical about it.
This solution is simple transcoding, using a lot of CPU. They are probably picking the framebuffer from the display driver, providing it to a userland application that does the encoding and sending.
I expected a true lossless wifi link to the DVI/HDMI connector, this is a vendor-specific dirty hack.
Already done, see the Sega Dreamcast discs: GD-ROM.
It has started with the Nokia N900, targets almost everything (the only "mistake" is using a TV-out instead of a HDMI output).
... I don't care about Gods, but this is a weird thing, trepassing the censorship line (in my opinion).
So: Fuck that Irish law and fuck that Irish fucking God (I apologize for the inconvenience, I'm just Breaking the Law ).
Yes, 3.5" widescreen is small. However, you can change the font size both in the xterm, web browser, and many other apps just using the "zoom" button, and most applications use fonts larger than typical paperpack book. My eyesight is far from perfect (I'm in my mid-thirties, with myopia and some astigmatism in both eyes), not only I have no problem with, but I'm much happier with the new rather than the previous 3-and-something-inches mobile.
I replaced my netbook with a Nokia N900, because of:
- Built-in physical keyboard, and external full-size standard bluetooth keyboard.
- It is the first { Linux + X11 + phone } that works nicely (OpenMoko was a poor attempt), and it's Debian based! (Maemo).
- As music player: impressive.
- As video player: impressive for h264 (hardware accelerated), not bad for mpeg4-baseline.
- As photocamera: quite good (5MP + two-LED flash, quite sharp for a mobile camera, and much better than my previous standalone 3MP Canon Powershot 4 year old camera).
- As agenda: very good.
- For notes: I love the default notes application provided by Nokia. You can use Conboy too, which is also OK.
- Multitasking: very good, the best I've seen in smartphones, because of using Linux plus plenty RAM (256MB + 768MB for swap) is years-light ahead from Symbian, iPhone, and Windows Mobile devices.
- User interface: uses desktop composition, but with the vertical sync disabled (it is possible to enable it, but I will not enable it until some other does it and confirm that it is safe). That makes it less smooth than the one from the iPhone or from Android devices.
- Geekness: Linux, X11, 256MB RAM + 768MB of swap, 2-way in-order supescalar ARM CPU (ARM Cortex A8 @600MHz, 1200MIPS, 2.4-4.8GFLOPs (4.8 GFLOPs when using the VMLA -FMAC, floating point multiply and accumulate-)), ssh, sshd, xterm, dosbox, game console emulation, perl, python, clisp, ml, airodump/aircrack, etc. With the exception of the C++ compiler, which haven't manage to install into the device yet (I'm using a cross compiler in my main PC, provided with the SDK), because I'm afread of broken the shared library links (I'll do it when I'm sure I'll don't break anything), the device runs most Linux applications!
- Presentations/slideshows/portable video player/etc: TV-out (composite NTSC/PAL plus stereo sound, via 3 RCA connectors).
- Storage: 32GB built-in (write speed is about 10 MB/s), expandable up to to 48GB with an additional 16GB micro-SDHC card.
The Nokia N900 is the first { Linux + X11 + phone } that works nicely (OpenMoko was a poor attempt), and it's Debian based! (Maemo).
It's a port, I tried it this morning: runs in full resolution (800x480), accelerated 3D, and it is very smooth. The N900 is tiny monster: Linux, X11, composite desktop, 256MB RAM + 768MB swap, 2-way-in-order superscalar ARM ARM Cortex A8 CPU @600MHz, 1200MIPS, 2.4-4.8GFLOPs (4.8 GFLOPs when using VMLA opcode -similar to the FMAC, floating point multiply and accumulate-), hardware accelerated OpenGL ES 2.0, etc.
As contrast, using Dosbox on the N900 is slow, barey enough for simulating an 8MHz 80286.
*Checks calendar* Yup, it's 2009. VOIP still not possible on my smartphone...
Check the Nokia N900... and yes, it runs Linux.