That's partially correct; and completely irrelevant to the discussion at hand. The chipset distinction is not 1st/second generation; but based on the intended use. The first generation atoms intended by intel for desktop/laptop computers (N2xx/N3xx) supported a standard chipset (i945) with an intel GPU. The ones intended for small embedded systems (Z5xx) used Polubso with a 3rd party GPU. The same distinction is present with the 2nd generation. Those intended for desktop/laptops have an intel GPU (NM10), while those intended for embedded systems (smartphone/tablets) are using a GPU from Imagination Technologies that doesn't have an intel written driver. The scope of the problems caused by this one is probably a bit more limited though; because the langwell chipset lacks PCI support (power consumption) it can't run windows. This means it's unlikely to end up in many mass market netbooks. Pure linux netbooks are still possible but unless it gets much better battery life (which Intel's unwillingless to comment on non-idle power consumption makes me doubt) the mass market sales needed to finance the design costs aren't likely to be there.
Originally Posted by Jimbo
I'm new on these forums, and at this website. I followed a news link from ArsTechnica's home page. I am also a Macintosh user, not a Linux user. I do, however, have a MS in Computer Science from some years ago.
I simply cannot understand the first paragraph of the article, although I'd like to. Would it be possible to have it edited by someone whose first language is English, who can construct sentences at least at the 8th-grade level, and who hasn't been awake for 28 hours straight?
The first sentence, if I can call it that, is particularly bad. If it was intended to give an outsider a background introduction, it fails miserably. I'm very disappointed.
Sorry to have to say this in my first post. Hope to be more positive in future posts.
Originally Posted by DavidH
Heh... It *was* atrocious...Michael, you might want to fix that first part.
I didn't read the article because I'm kind-of following the saga a little more directly for business reasons.
Basically speaking, Intel, until it released the Poulsbo chipset used for Atom based mobile devices, had been providing adequate, though not stellar 2D and 3D support for Linux.
With the GMA500, used in the Poulsbo chipset, they licensed and rebranded a low-power core from a third party, Imagination Technologies, developer of the PowerVR GPU line. Because of this, Intel couldn't provide an open source driver for this IGP like the previous mobile and desktop chipsets. Worse, they had difficulties producing a serviceable driver until recently for that chipset- on either Linux OR Windows.
Sadly, even with the properly functioning driver, they can't provide access to the driver to use on a Poulsbo or similar platform without an NDA signed by the recipient of the driver. In a nutshell, they produced this lovely Linux based distribution for handhelds and they can't deliver the same with full support for their hardware because of this small bit of what could probably be called short-sightedness.
By the way, welcome to the forums and to the site. :-D
Where are the open 2d components downloadable from?
Originally Posted by AdamW
Android and Maemo phones have binary/closed drivers. Binary/closed drivers are a part of life right now in embedded devices. Also, MeeGo is a reference distro not an actual product. It's up to the OEM to take MeeGo, productize it and put it on hardware. When they do, they'll likely include any closed drivers they need to make their hardware work.
Originally Posted by movieman
When you take meego and install it on your hardware, you are responsible for that hardware and supporting it.
Exactly. Some people said how bad Intel was with their chips policy. It turns out they failed to segment the chips market as people supposed. i.e. some HW vendors seem to have been able to make Netbooks with Atom Zxx + US15W whereas this wasn't intended use... thus, it's the responsibility of the OEM to provide the drivers and sign the necessary contracts with Intel. Intel doesn't HAVE to provide the embedded drivers to the whole public. However, they do so because they try to play nice anyway. Have you ever seen video drivers updates publicly available for your phone or other ARM-based devices, in particular those based on PowerVR chips? Or even sources to those drivers? Why don't people understand "embedded"?
Originally Posted by tripzero
In particular, can someone provide links to drivers at the chip's vendor website for the following netbooks?
- Qualcomm: Compaq Airlife 100 for Snapdragon drivers, including the OpenMAX IL components for video decoding acceleration?
- NVIDIA: Toshiba AC-100 for Tegra 2 drivers, including the OpenMAX IL components for video decoding acceleration?
Better, would you have sources to any of those?
You're kind of missing the point.
Fact is that nobody *has* to provide *any* drivers to *anyone* for *anything*.
** but if your customers REQUIRE it, then you end up not selling your stuff due to being impossible to use. This is why drivers get made and distributed. Just because they don't *HAVE* to doesn't mean that it isn't in their BEST INTERESTS to do so.
Now the good news about the world as it is changing today is that we are starting to see some embedded devices where there is a very real need for the hardware vendors to not just provide drivers, but to provide OPEN drivers. One of these platforms is meego, another much bigger platform, which is starting to become really well known is ANDROID. These platforms are really changing the embedded market from what was originally the "somevendor's_proprietary_junk_firmware" market into a "this_is_a_general_purpose_computer and i_should_be_able_to_do_what_i_want_with_it" market. The fact that hardware vendors are putting things like poulsbo and maybe soon moorestown into some fairly general purpose netbooks and tablets is the other side of this coin -- so not only are the software platforms pushing embedded into the non-embedded market, the hardware itself is now strong enough that what would otherwise be considered embedded hardware actually *can be* used quite successfully in devices that previously wouldn't be considered for embedded.
In other words.... the word "embedded" is really losing its meaning. If I own something, I really should be able to do anything I want with it, and if the hardware vendor doesn't support me in that, then I might just go to a different vendor.
AMD if you're reading this, NOW is the time to get into the ultra mobile market. With open specs and drivers, you'll make a KILLING.
Meego on O2 Jogger (GMA500) EMGD Driver
I've been paying with the new EMGD driver on my Joggler there may be some hope for all the GMA500 users !
Instructions and prebuit .img on
Originally Posted by vgrade