Post a Comment
They should have a team writing patches for QEMU and Bochs in order to make them emulate their hardware, if it's not already the case.
Otherwise, I don't see people coding drivers for $800 hardware that probably has about the same performance as a Radeon 9600, twice its power consumption, and less than a thousandth of its user base. Nice project, though.
Otherwise, I don't see people coding drivers for $800 hardware that probably has about the same performance as a Radeon 9600, twice its power consumption, and less than a thousandth of its user base. Nice project, though.
It's not too powerful, indeed, but it was never even meant to be. The whole point of OGD1 is that you can customize ANY part of it as you see fit with detailed instructions as to how to do it and all, and as such it's an absolutely fantastic piece of hardware for anyone who is genuinely interested in hardware development as opposed to software development, and it could f.ex. be hugely useful to engineering students et al.
I personally wouldn't know what to do with OGD1, but hey, I don't belong in the target audience anyway. And from what I've seen at offer elsewhere it seems very competitive compared to other similar products, both performance- and pricewise, not to mention it being completely open and as such allowing for larger amount of cooperation and experimentation between the developers.
I agree, emulator support would be nice. I also think Radeon 9600 performance is a pipe dream.
However, it still has a lot of value for people, like me. It was really frustrating writing embedded software that controlled everything at a low level, but I couldn't touch the code that ran on the FPGA out of verilog ignorance. I did identify a couple of bugs in the FPGA implementation, but we had to contract out that work to the author of the original code and convince him that the bug was real.
Thanks indeed for the article.
However, I (maybe like some other people who'll read it) have no idea what "FPGA" stands for. Ditto for "ODG1", although I can easily guess the "G" is for graphic(s). But guessing isn't knowing and educating is what OSnews is about. For me.
Edited 2010-06-24 10:57 UTC
FPGA = field programmable gate array. A special kind of chip that can be programmed. However, unlike a CPU, you don't program a sequence of instructions, but rather a set of parallel interconnected data processing units that compute boolean logic functions. The programming model is very much like designing a custom chip, so programming these things is very much considered "hardware design" - and in fact, an FPGA configuration (i.e. the "software for it) can be turned into a real chip with a fair amount of work.
Sorry, wrong again, you were on the right track the first time. ;-)
Here's my understanding of their situation: The Open Graphics project wants to build a graphics card, but the fabrication is insanely expensive. They built a flexible board that, from the spec's, can do graphics. (See also, "late binding" in the context of computer programming languages.)
The financial reasoning is that they can sell these boards to any tinkerer, student, or even a professional hardware engineer. Not to ignore video performance that's now merely acceptable, it's so much more than a video card that they will cover their costs when (I hope) people soak them up as fast as they're made. We need more stuff like this for hobbyists to disrupt the market.
In other news Intel is about ready to do away with the PCI spec. I hope we can see PCI express versions of this card soon.
http://hardware.slashdot.org/story/10/06/23/1751244/Intel-Says-Fare...
Instead of this, why didn't they design a real GPU in an open source fashion?
This thing will never reach the hands of anyone who isn't an hardware designer, and won't definitively be of any help to open up the hardware market. A real GPU instead could be manufactured by any silicon fab with its own customizations.
Back at school we were busy designing our own electronics circuits, drawing the schematics with OrCAD, and print to real PCBs. But we couldn't go beyond very simple digital appliances, because of lack of time and knowledge - both limits which can be overcome with the power of open source.
I would love to go to a website, download the schematics of, say, a USB sound card, customize it, have the PCB printed by a local company for a few bucks, and solder the parts on it.
Extend this to microchips and your open hardware is served - I can't see a local company manufacture a single microchip for me for a few bucks in the foreseeable future, but at least they could offer a large choice of them.
The main purpose behind OGD1 is to provide a platform for developing a "real GPU."
Now, a "real GPU" contains dozens to hundreds of small parallel stream processor cores. GPUs actually have more transistors than CPUs to fit on all this hardware.
Also, we are developing a "real GPU", and we have a spec for it. If you're interested, join the mailing list and help us out.
Lastly, to fabricate a run of "real GPUs" would cost millions of dollars. That's just manufacturing. Forget design, which you can't pull out of your arse either, and for that, we need manpower.
As far as I understand OGD1 will never be for end-users. I wonder about donations.
No, OGD1 itself is not intended for most end users. Hobbyists who want to do FPGA development would find it useful for lots of things, and THEY are "end users" in that domain. But most people are not chip designers. OGD1's purpose is to provide chip designers with a platform they can use to develop (prototype) products that can be turned into end-user products.
Servers have no need of graphics, and joe public asks if it can run Crysis.
The problem is getting specs opened up, not rolling your own sub-par hardware for $$$$'s. All that time and money would have been better spent getting vendors to open up specs for hardware, or committing to release driver source under an *open* license so all OS's can benefit.
Now i could be wrong, since they've produced some other useful hardware bits, but I can't help but feel theres more useful LGPL designs at http://opencores.org/.
Hardware vendors typically only open up specs when they're pressured to, sometimes by market demand, and sometimes by the strong arm of people like Theo de Raadt who somehow manages to be able to influence stock prices. Personally, I have no interest in fighting with these companies. They have their business, and we FOSS enthusiasts are like a bunch of annoying flies interfering with their primary purpose, which is to make profit and lock in customers so they can make more profit.
What I really want to do is develop hardware that is friendly to free software from the outset. This way, there is no fight. Just science and engineering.
I have nothing against capitalism and business. I think good money could be made from open hardware, if we could only get enough starting capital to get the ball rolling. But I'm more motivated by solving problems than just making money for its own sake. I'm more interested in community than my own profit margin. And if I did find myself able to make an income from this, I would be happiest if a lot of other enthusiasts were making an income from it right along with me.




