Slashdot Mirror
Tilera Releases 64-Way Chip Dev Tools
eldavojohn writes to tell us that Tilera has released a Linux-based development kit for their 64-core system on a chip. "The Tile64 is based on a proprietary VLIW (very long instruction word) architecture, on which a MIPS-like RISC architecture is implemented in microcode. A hypervisor enables each core to run its own instance of Linux, or alternatively the whole chip can run Tilera's 64-way SMP (symmetrical multiprocessing) Linux implementation. An 'iMesh' switching interconnect, developed by Tilera's founder, MIT professor and serial entrepreneur Dr. Anant Agarwal, is said to eliminate the centralized bus intersection that limited scalability in previous multicore designs."
I used the 64 way chip to get first post!
Do it yourself, because no one else will do it yourself. [beta blockade 10-17 Feb]
Because if you can't, I'm honestly not interested.
WTF is this? Smells like a Microsoft marketing asshat. Mod this shit down.
Thats GREAT! I used to wonder why the bus used to be late always for my cereal breakfast.
EOF
I might be a little inaccurate about this, but AFAIK nobody forces you to GPL license your kernel patches, but you are forced to tell people that you used a GPL'd kernel in the first place and tell them where they can get it for free.
Serves you right if you are trying to make a buck off other people's hard work. Running software (including kernel drivers) on Linux DOES NOT require you to release your source code. Where's the source code for Googleearth, or VMWare, or NXClient/Server or the nVidia proprietary drivers? Where's the source code for your router? Exactly.
I don't know who you have for a lawyer, but I can't see how your case is real. Nobody else is seeming to be having this problem.
Do it yourself, because no one else will do it yourself. [beta blockade 10-17 Feb]
I'm not sure about this particular chip but doesn't VLIW normally mean no microcode? Microcode is the set of RISC commands that make up a CISC command. VLIW is just a RISC machine in which the compiler does all the optimization (branch prediction, hazard detection, etc). Normally VLIW machines fetch multiple instructions at once and issue them without fear of any hazards because the compiler takes care of it. Very neat idea, but not CISC
An investment firm that obviously has no intelligence? OMFG this is a dream come true!
Gimme a dollar!
Fascism trolls keeping me up every night. When I starts a preachin', he HITS ME WITH HIS REICH!
Imagine a beow... oh, never mind....
Clearly some kind of troll.
Note the use of the words:
Recently, ext2, defrag, and.. token ring??
Was that even still around when a student named Linus messaged some newsgroups describing his latest little hobby?
Can you be Even More Awesome?!
OK troll. First, you only have to give the source you wrote to people you distribute binaries to. No one else. Of course, they can give them to anyone they want to. Second, you don't have to give the source out to anyone at all IF you don't distribute binaries. So if it's just for in house use, you are free and clear, you don't have to give back to the people you took from. You are lucky you posted as an AC. Who the hell would hire you if you take code without knowing even the basics of the license you got that code under ? Then you hire a lawyer who gets the basics wrong too ? Hey buddy, it would have been cheaper just to read the GPL yourself. Oh, that's the General Public License. Not "Protective". Get the basics right, then complain.
I thought the chip has been out for a few months; I feel bad for anyone who has been trying to use the processor with no development tools.
Also, it looks like the tools have been released to Tilera's customers, not to the public. A shame, since I'm sure a lot of Slashdotters would like to at least gawk at the docs for this chip.
Would you like a little FUD with your whine?
In the odd, small, tiny chance that you're not some idiot with an agenda (the wwworld is fast filling up with posts like this), then your lawyers are the ones with an agenda and/or incompetence.
According to your incorrect interpretation, a vast majority of internaly held code that has been written the world over is illegal. Lets take one simple example, Google. Do you honestly think that all of Googles code is released into the open?
This post is mostly pointless. I seriously doubt you'll ever be back to this thread, AC. However, various web archives will be around for a long time, and for each example of FUD that's shoveled down the collective pipe needs a rational "WTF" post after it to point out just what it is.
Enjoy your Windows 2000 solution.
Robert Anton Wilson
I hate press releases like this. "$435 in 10,000 quantities". How much for just one of the damn things with the software I need to fool around with it? Is that too much to ask? It would be cool to have one of these, but I'm sure it won't be worth the effort or the expense (I figure a single unit will be at least double the quantity price).
-- Will program for bandwidth
I went on to read their in-depth article (linked to the main article) at http://linuxdevices.com/news/NS8981295285.html and I found this:
"Another touted benefit is the ability to consolidate control- and data-plane functions on a single device, with "solid-wall" processor boundaries reinforcing security and licensing containment barrier. In this regard, the Tile64 chip resembles another heavily multicore MIPS64 chip, Cavium's 16-way Octeon."
Does anyone know what the heck a "licensing containment barrier" is? It definitely sounds like a performance hit if it's turned on. And if it's forced to have it on then this design just lost a lot of its sex-appeal.
You can't send a takedown notice to an already printed newspaper.
Now that is an outright lie. Do you realize how many commercial programs were compiled with gcc? The only time you must release your source is if you were linking GPL'd libraries...and at that, the legal issues are still unresolved.
Do it yourself, because no one else will do it yourself. [beta blockade 10-17 Feb]
Not necessarily. Only if you distribute ALL your binaries with source do you not have to provide source for ANYONE on demand. If you allow written requests for source, you must allow the source to be obtained by ANYONE.
http://www.gnu.org/licenses/gpl-faq.html#WhatDoesWrittenOfferValid
Come on guys, this isn't a troll. This is just hilarious.
A quick giggle for "or the Gnu Protective License" barfed up the following:
http://www.news.com/5208-1030_3-0.html?forumID=1&threadID=2246&messageID=11919&start=-1
http://linux.slashdot.org/comments.pl?sid=389856&cid=21705136
http://yro.slashdot.org/comments.pl?sid=67877&no_d2=1&cid=6220788
http://slashdot.org/comments.pl?sid=159323&cid=13343214
http://www.kuro5hin.org/comments/2003/2/13/8422/16656/11#11
I think the biggest thing keeping this troll from being truly informative is the lack of understanding of the licence, and the deliberate mis-statement of its effects. Its fictitious and incorrect pronouncements virtually guarentee that nobody with even rudimentary analytical skills will believe it. After my experience with these beliefs, I won't be recommending them any of my associates. I may reconsider if it switches to something a little more believable, like the HIV-protective benefits of nailing your head to the floor. Until then its attempts to deliberately distort the facts about what you can and cannot do with in-house software that's not for external distribution shall continue to attract such a flurry of indignant responses that it's easy to believe that Mother Henrietta Hickey's day job is posting anti-GPL FUD.
Thank you for your time.
Read all the sibling posts above this one. What a fucking brilliant troll & what a bunch of fucking idiots.
I don't have a hard time believing that this person consults for large companies, because I have met a number of totally clueless people who made big bucks consulting for large companies. That part is quite believable. But really...
(1) If I were a client, and your company put linux to use for me without researching the licensing well in advance, then your firm lost me money. I don't even need any hard numbers to know that. If you tried to charge me a dime I would mark the contract "loser" and start a lawsuit over payment for services not rendered.
(2) If your lawyers really thought that code compiled with gcc had to be made public, then your lawyers are also from another world. Even if they did not know computers very much, they should understand the basic concept that something made with a tool -- a lathe for example -- does not belong to the tool manufacturer. The same is true of software: someone cannot hand you a tool for "free", then insist that they have legal control over a product you build with that tool. The very idea is ludicrous. If anyone even tried to do that, nobody would use the tool! The majority of linux users are NOT idiots. However, the legal team you describe seems to be a whole pack of them.
(3) Just about anything you wanted to do would be at least POSSIBLE to do without modifying the kernel, though it might not be as easy or perform quite as well. Provision for installable file systems and drivers is built in.
(4) Fuck it. I am tired of explaining why just about everything you say simply ain't so. You are either a troll or one of those annoying people who are well-paid for being clueless. Either way, I would appreciate it very much if you would go away.
Can anyone please translate this to Layman? I mean I do know bits and pieces about computing but this is really unintelligible for anyone but maybe hardware engineers.
epic troll is epic
Wish 1.
It's less than $4000.
Wish 2. It runs games well.
Wish 3. It could plug into my AGP slot 3
The press release, oh pardon me, the article linked to in the posting above lists pricing in units of 10,000. I want one or two TILexpress-64 boards please, not 10,000 units. Until the software is built 10,000 units would just sit in my garage doing nothing.
Also, I guess they had to put out a press release to respond to the massive threat that NVidia's new Tesla board represents. At least this is going to be good for competition.
GP post is a verbatim copy of http://linux.slashdot.org/comments.pl?sid=389856&cid=21705136
I like the idea, I like the idea a lot, but the fact that they opted for a simple but slow topology doesn't fill me with hope. Especially as they suggest running SMP over it. Processors close to the centre of the "mesh" will be resource-starved. There needs to be strong affinity of a given thread to a given core, where the weighting is by the operations expected and where that weighting can (and will) shift as code blocks change or new threads start. In other words, you want something that is semi-static, semi-dynamic according to need. Only the OS is capable of obtaining that kind of information, so it is the OS that needs to do the dividing, NOT the architecture underneath OR a system administrator.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
The lathe does not copy itself into what it works on.
There was a case of a pattern-lathe and it was a condition of sale of the patterns that you don't duplicate the patterns!
So while your point is good, the lathe analogy doesn't make it for you.
CIISC and RISC describe the architecture. Either can be implemented directly, using horizontal or vertical microcode, or via a translator. RISC is similar to vertical microcode, where each micro-instruction controls part of the core, and VLIW is similar to horizontal microcode, where each micro-instruction controls a number of components at once. Whether you call them "microcode" or "RISC/VLIW" is almost more a matter of marketing at this level, like when Intel started talking about the 486 having a "RISC core". Just don't try and blend them or you're setting yourself up for an EPIC fail.
The way they're describing it, the RISC instruction set is implemented using horizontal microcode that they're calling "VLIW" because it's sexier right now.
Not mine, but for some peoples routers it's here: ;D
http://openwrt.org/
http://www.youtube.com/view_play_list?p=9F74AFA03AA06A11 , just in case someone hasn't dug on these yet (my personal fave).
No. All processors have microcode, including the most infamous VLIW chip the Itanic. You're confusing yourself.
Actually, that may well be coming in the next version of the GPL. For now, it's a separate license, but I suspect future versions of the GPL will be such that if you write any application based on GPL'd code which provides a service to anyone but yourself, you must provide the users of your service with the source code for that service. This particularly hits Google, with its web services, but I suspect it will be expanded to include any service (e.g., a mail server).
Perhaps more interesting will be when the FSF guys start to address the "content loophole." I.e., if you create content with GPL'd software (or with software derived from GPL'd code), you must provide the source code for the software when you distribute the created content. If I put on my "freedom" hat, that seems like a perfectly rational thing. (If, for example, I wrote a GPL'd 3-D modeling program and some game company modifies it and uses it to help create their next blockbuster, I'd at least like to get the source code for their improvements, even if I don't get a cut of the revenue from the game.) If I put on any other hat (or no hat at all), it seems bonkers, though.
Anyone else notice, Copypasta brand Trolling bait seems to catch a lot of fish lately?
Given that I was ripping out token ring from banks as recently as 2005... yeah. Big organizations like that don't move quickly, and TR was the default (and at one point only) option available for connecting AS/400 and Mainframe systems to a LAN. It was only in the mid 90's that it started to all switch to Ethernet, to the sound of much wailing and gnashing of teeth from the Mainframe and 400 guys and gals.
Also bear in mind, many mainframes and 400's installed at the end of this TR era may actually still be in use today in many locations... some of them so loaded up with cards that they are incapable of accepting an Ethernet interface. In our client/server-centric world we sometimes forget that there are systems out there with a much longer shelf-life than the 3-5 year x86 system running Windows or Linux.
How did this work with client machines that only had Ethernet? Quite well. TCP/IP is a very versatile protocol, quite happy to go across a set of routers from one architecture to another. As a result, even up until 2005 I touched on Token Ring systems in datacenters that used routers and gateways to get to their Ethernet-connected clients.
Okay, so I know that VLIW stands for some very long word, but couldn't you have told us what it's an acronym for anyway?
sounds impressive =) "Tilera claims that the Tile64 outperforms Intel's dual-core Xeon processor by a factor of 10, while offering 30 times better performance per Watt." and "The Tile64 is available now, in three variants differentiated by I/O mix and clock. Pricing starts at $435 in 10,000 quantities".
where can i buy this?
College-Pages.com - Online Colleges, Degrees, and Programs
Lbh fubhyq or ganaxsgy V gvga'g ebg13 gur jubyr cbfg gb erqhpqr gur evfx bs hajnagrq nggragvba - that would have been really annoying to casual readers, if it made it past the lameness filter.