Slashdot Mirror
Group Outlines Specs For Linux-based Set-top boxes
Shadowhawk writes "According to
Silicon Strategies, a group called "TV Linux Alliance" is creating a spec for digital set-top boxes using Linux. The specifications, dubbed version 0.8, defines the functions for RF tuners and other components in Linux-based set-top boxes. It also outlines the application programming interfaces (APIs) for those devices, according to officials from the alliance."
...Do these standards help linux spread out and mature or simply go against everything that linux has done right?
Personally i think if its done right its a good thing.
unzip; strip; touch; finger; mount; fsck; more; yes; unmount; sleep
I'm I the only one who found no real information here?
It'd be nice to actually see what standards were set, or at least have a link to them.
It's like CNN having a news update about a presidental speech and saying "well the president outlined his goals for the economy and foreign policy, he is supported by these congressmen"
Then failing to say what the policy is.
Talk about a fluff piece.
Chicago2600.net more than a lifestyle, its a survival trait.
From article: "The TV Linux Alliance consists of ACTV, ATI, Broadcom, Concurrent Computer, Conexant, Convergence Integrated Media, iSurfTV, Liberate, Lineo, MontaVista, Motorola, Pace Micro, ReplayTV, STMicroelectronics, Sun Microsystems, TiVo, Trintech, and Worldgate." Odd. Somehow they left out WebTV
The article doesn't contain any meat. What standards? I want to know how I can make use of these standards, are they being made available or are they sort of passed around to others in the industry only?
HOUSTON, Tex.--The TV Linux Alliance here today announced the availability of its initial specifications for use in developing digital set-top boxes, based on the Linux operating system.
The specifications, dubbed version 0.6, defines the functions for RF tuners and other components in Linux-based set-top boxes. It also outlines the application programming interfaces (APIs) for those devices, according to officials from the alliance. The TV Linux Alliance is a consortium that hopes to define a proprietary Linux environment for digital set-top boxes.
The specification also simplifies the implementation of middleware and device drivers for the Linux operating environment. It also paves the way for support of industry-standard content specifications, such as DVB-MHP, Palladium, and CableLabs OCAP, said Dennis Thompson, chairman for the Austin-based alliance.
"This specification is a long awaited solution that will accelerate the availability of new content and services, though it may include some porting and integration challenges," he said in a statement.
The TV Linux Alliance consists of ACTV, Apple, ATI, Broadcom, Concurrent Computer, Conexant, Convergence Integrated Media, iSurfTV, Liberate, Lineo, MontaVista, Motorola, Pace Micro, ReplayTV, STMicroelectronics, Sun Microsystems, TiVo, Trintech, WebTV, and Worldgate.
> The specifications, dubbed version 0.8
How long did it take them to come up with that? I think I'll name my next kid that...
tvlinuxalliance.org
To even see the specs you have to print out a license agreement, sign it, fax it to them, and more... So much for an open standard.
Like I said, real informative.
$2000 for a set of standards that no one knows what they are at the moment?
Chicago2600.net more than a lifestyle, its a survival trait.
I remember Linus getting the Linux trademark back a couple of years ago. Don't know if the mark is specifically for "software" or "product" or might include "services", but it seems to me that anyone calling themselves "TV Linux Alliance" and being less than forthcoming with their standard, much less their code, may be up for a challenge.
This sig intentionally left justified.
Linux already has a standard for TV tuners, video cards and both analog and digital TV systems. The palladium thing does demonstrate the need for more GPL software authors to include language like this
(from bits of the kernel...)
* For the avoidance of doubt the "preferred form" of this code is one which
* is in an open non patent encumbered format. Where cryptographic key signing
* forms part of the process of creating an executable the information
* including keys needed to generate an equivalently functional executable
* are deemed to be part of the source code.
*
and I'd urge the FSF to adopt such language in the GPL next generation too
the Specifications are available here: http://tvlinuxalliance.org/specifications/index.ph p
"...industry-standard content specifications, such as ...Palladium..."
This cannot be good. Should Linux-based set-top boxes be used to limit the freedom of the users. I can see the irony, but I do *not* find it funny!
What bs, open source for the wealthy, wait a sec, I guess that means its not open source at all....hmmmm
Chicago2600.net more than a lifestyle, its a survival trait.
I wonder how many other industries could follow this trend? Note that MS has its hand into other pies like HAVI (Home Audio Video Interoperability), Media center, recent announcements with Panasonic for CDs etc...
"Do something man. Right now."
This sounds like a big business thing. What will undoubtedly happen if this alliance makes significant market pentration is that some dude in Washington will lean on them in some way:
Force Palladium-like stuff on them (or)
Force viewing stats (or)
Force no ad-skipping (or)
or whatever.
Hackers, on the other hand, start a sourceforge project, another sees what's available, enhances it for their needs, puts it back in the pot, and so on. That will never be controlled in the way this alliance can be.
I expect that some of the alliance "components" will end up having some restrictions in them, so even they will not be available for open-source hackers.
The only way will be to write your own, from the ground up (at best keep a "standard" interface). Sorry.
Note to ACs: I won't mod you up, even if you are being funny or insightful. So take a chance! It's not real life!
This is better:
The Dreambox 7000S, Dream Multimedia:
- 250 MHz IBM PowerPC Processor (350 Mips)
- Linux open source (most parts under the terms of GPL, accordingly
expandable)- Supports Linux Standard API (Direct-FB, Linux-FB, LIRC)
- 1 x DVB Common-Interface Slot
- 2 x Smartcard-Reader
- Integrated Compact Flash Interface Slot
- MPEG2 Hardware decoding (fully DVB compliant)
- Support for MPEG4 decoding
- Common available NIMs (DVB-S, DVB-T, DVB-C)
- 100 MBit full duplex Ethernet Interface
- USB Port Keyboard, Pointing Devices, WebCams and other devices
- V.24/RS232 Interface
- Big-size LCD-Display
- Up to 64 MByte of RAM
- integrated IDE UDMA66 Master/Slave Interface
- Support for internal HDD in any capacity
To counter WinXP Media Center edition of Windows XP, we need something similar running Linux, but this "Linux Standard" costs $2000 just to READ, and you don't even know what it contains beforehand.
Is there a competing standard available or being worked on, that's FREE to read?
Jesus, Standards were meant to be free.
can closed specs produce open software? the specs will cost $2000 to license.
fear is the mind killer
Okay, this alleged Alliance is all well and good (or, more probably, unwell and double ungood), but a bunch of TiVo modders could probably grab some codecs and software off of Freshmeat and do a better job than these big, ungainly businesses. Besides, who really cares what their "standards" are when it will be hacked to pieces within weeks of the boxen actually being released to the public. Encryption keys, ha!! Just grab the old beltsander. Proprietary codecs... didn't the whole DVD industry try that one already??? Didn't hackers already get around that like a mofo? Aaaahhh, these guys are such jerks, I'm just going to go to bed and dream about monkeys smoking hookahs or something more reasonable.
Voodoo Girl is the bomb!
Now, I guess it's fine to put these restrictions on a specification of a GPL-d system, but once they start releasing products, they'll have to release source code - so i'm a bit confused as to what the license implies. They're protecting the standard, but are going to release the source of implementations? Why?
This site has the terrific and very active VDR project. It has full DVB support, full PVR support, and plugins for DVD playback, DivX, MPEG-4, MP3, LCD displays and more... If you want GPL Digital TV this is the place to go. Sign up to the mailing lists and contribute to this fantastic example of open source working well.
- Paul
I see little point in adding additional terms to the GPL when current terms are being ignored.
Dell/Red hat was notified in JULY 2002 that the Dell PowerEdge Web Server version 3.0 Powered by Red hat Linux was violating the GPL by not provide the source code or a written notice of the source code. Red hat's Mark Webbink responded that under contract between Dell and Red hat, the Red hat v7.2 packages (on CD 2 of 3 and CD 3 of 3 of the PowerEdge Web Server) where distributed by Dell, not Red hat and Red hat would make sure the GPL was honored. Dell responded that the next release of the PowerEdge Web Server would honor the GPL including the non-RH packages covered by the GPL on CD 1 of 3.
Well, the next release is out under the name of Dell PowerEdge Server version 3.1 Powered By Red Hat Linux and guess what:
It does not include the source code for the non-RH portions on CD 1 of 3
It does not include a written offer for the source code for the non-RH portions on CD 1 of 3
It does not include the source code for the RH 7.2 packages on CD 2 and CD 3
It does not include a written offer for the source code for the RH 7.2 packages on CD 2 and CD 3
Mark Webbink refuses to respond to e-mails requesting details on what Red hat considers to be a written offer for the source code that was included with Dell PowerEdge Web Server version 3.1 Powered By Red Hat Linux.
Dell technical support when asked for the after-market part # for the source code explains that Dell does not intend the PowerEdge Web Server software to be "open source" and does not intend to provide *ANY* source code related to the product. In addition, he explained that any customer modifications that Dell intends to be provided is already in the web configuration screens and modifying the source code would only "break it."
Despite this excuse for continuing the violate the GPL, Red hat/Dell is now (October 29) giving a talk at Georgetown U. to explain why software distributed under the license they are both violating will result in better security.
So which is it that Red hat/Dell believes? That modifying the source code only breaks it or improves security?
And Red hat's Alan Cox would like additional terms added to the next GPL so that the Red hat/Dell alliance can ignore those terms as well! That is really cute. Why don't you talk to Mark Webbink about honoring the FSF request to snail mail every reciever of the PowerEdge Web Server version 3.x a written offer for the source code before declairing what more the FSF should do. Maybe if the FSF wasn't busy policing GPL violators like the Red hat/Dell alliance then they would have time to work on GPL-NG instead.
In short, adding your above language to the GPL is NOT going to ever make RH's Mark Webbink responsive to the requirements of the GPL.
Why doesn't somebody put together a set top box with a 40 gig harddrive, plus a couple more IDE slots, a couple of PCI slots, capture card, TV out, a network card, USB, firewire and a remote, and sell the damn thing as a kit... then let the standards make themselves... Personally, even if the thing cost 500 bucks, I'd buy one just to make my own Tivo and I'd plug a CDRW into the thing so I could archive the content as well. And before you respond with some rehtorical whitty comment about how nobody would buy it, that's the problem! See, years ago, you actually had to build your television (now that's what I call dedication!!!) I think people have lost a bit of the lust to tinker!
Yes Francis, the world has gone crazy.
According to Silicon Strategies, a group called "TV Linux Alliance" is creating a spec for digital set-top boxes using Linux.
The way to develop a product is to work out what you want to do, then look for a technology that can do it. Choosing the technology first then designing the product to fit the technology is backwards. Is the objective here to sell an STB, or is it to further the Linux cause? Because a for-profit company should prioritize the former over the latter.
If you've got the guts to continue this other than as an "anonymous coward" then I would be interested in evidence that something like that is going on so I can go kick people and find out what is happening.
It may also depend on the code involved. If its about 'web server software' and that software is dell written and created it may be Dell proprietary. If it is Apache mods then it is under a very weak BSD license and they can take their version proprietary.
You might also want to ask Matt Domsch at Dell