In an ideal world, this is exactly what you'd do. There are three reasons why I don't think there's much point in this case:- Gpl-violations.org hasn't been active since 2008.- The founder of Gpl-Violations.org, Harald Welte, now actually works for VIA as their OSS liaison. We traded a few emails last week and he explained to me that Wondermedia has not violated GPL, because they provided source code with all of the binaries that they sent to their clients with the WM8505 SDK. He also said that the clients were informed that the SDK contained GPL licensed source code, and that consequently they would be obliged to release source. So the legal onus seems to lie squarely with Eken & other such companies.- To legally go after Eken means going after a small company based entirely out of a factory in Shenzhen, China, and I have no idea how you would go about doing this - I think gpl-violations.org has traditionally targeted larger companies with international presences.exilaus;15908 said:
scooter66;16956]That said:This is the angle I went for. Harald sympathised personally but told me Wondermedia aren't interested. Everyone feel free to email them yourselves though ([email protected])' date=' also Wondermedia ([email protected]) and Eken ([url']www.ekengroup.com/en/about/contact.asp[/url]).You're probably right' date=' which is why in my original post I said someone could go to the effort of building a kernel from scratch. 'bushing' started on it a while back: [url']http://github.com/bushing/android_wm8505[/url]There's a few things, though:- The datasheet posted on this site is extremely vague about lots of things, my guess is "the SDK is the documentation" for a lot of it.- There's a lot of little things that you'd need to implement to get to the current kernel's status. It'd be a great learning experience, but a lot of work I think (LCD, power management, graphics acceleration are all custom and AFAIK there are no kernel sources for even similar components.)- I'm pretty unmotivated to spend lots of my own time improving the product of a company who blatantly violate GPL and shamelessly rip off open source developers.- Even with a GPL source release of the kernel that Eken currently use, there is a fair bit of extra development work to support Android 2.2. The existing kernel doesn't do double-buffering in the kernel driver, the userspace side of Android (which is not GPL) has been patched to do it, and that layer has changed a lot between 1.6 and 2.x. So that would need to be reimplemented in the kernel framebuffer driver. This is the kind of job that I would be keen to help with, if a working kernel already existed.scooter66;16956]Why all the secrecy? This is a LOW-END part said:The only thing I can think is that at the moment Wondermedia charge for access to their SDK. So it's at least indirectly in their interest to keep it in closed hands, otherwise people could build devices with the WM8505 without licensing the SDK. Even if they are handing out source as Harald says, they benefit in that way if their clients don't pass it on.That said, I find it hard to believe that the margins on the SDK are so high, and the margins on the chips themselves are so low, that a strategy like that makes good business sense.[quote name='scooter66;16960]Can someone also explain why the PDFs that are circulating documenting the WM8505 aren't enough? I can't imagine the design is so dissimilar to what's been released before that other kernel drivers can't be used as a base.