Page 1 of 4 123 ... LastLast
Results 1 to 10 of 39

Thread: We Have Poulsbo Hardware, But No Driver

  1. #1
    Join Date
    Jan 2007
    Posts
    14,654

    Default We Have Poulsbo Hardware, But No Driver

    Phoronix: We Have Poulsbo Hardware, But No Driver

    For the past year we have been documenting the Intel Poulsbo Linux driver and how it is a bloody mess on the basis of it being a binary-only driver (in comparison to their fully open-source stack for their other IGPs) that is not well maintained, is not easy to procure outside of Ubuntu, and is ridden by other problems. Intel though is not solely at fault because the GMA 500 "Poulsbo" chipset is actually a product of PowerVR. A month ago we learned that a new Poulsbo Linux driver is under development and that it would use Gallium3D and be a big improvement over the current Poulsbo driver stack, albeit it would remain closed-source. A month has passed since sharing the news and this morning we finally got our hands on new Intel Poulsbo hardware...

    http://www.phoronix.com/vr.php?view=Nzc2MA

  2. #2
    Join Date
    Oct 2007
    Posts
    27

    Default

    I've used the existing IEGD releases on similar hardware. My main gripes are that Linux support seems to be an afterthought and everything is handjammed in. You are supposed to create a configuration with some windows tool and then export it to a tar file that you copy to your linux target. Then you run it as root and it does a bunch of random makefile and shell script stuff, asking you questions along the way.

    Looking at the xorg config format, it seems like they are trying to make it look like a registry.

    For myself, I made a clean makefile for the userspace bits that installs them to proper places with install and accepts DESTDIR. The kernel module is a bit more difficult to deal with as they have attempted to support multiple kernel versions in a particularly bizarre way. They copied the headers from a whole bunch of kernels and keep them in various directories. I ripped all those and made it include headers from the actual kernel and added a simple Kbuild and Makefile instead of their Frankenstein setup. Using real kernel headers makes it much easier to build on 2.6.32.

  3. #3
    Join Date
    Aug 2007
    Posts
    6,615

    Default

    Didn't you try

    https://wiki.ubuntu.com/HardwareSupp...oCardsPoulsbo/

    As your favorite distro is U

    Also you could send me something to test *g*

  4. #4

    Default

    Quote Originally Posted by Kano View Post
    Didn't you try

    https://wiki.ubuntu.com/HardwareSupp...oCardsPoulsbo/

    As your favorite distro is U

    Also you could send me something to test *g*
    Right, the cruddy current driver is available, but that's it. Not the new Gallium3D driver to benchmark and compare to.

  5. #5
    Join Date
    Mar 2009
    Location
    Portland
    Posts
    32

    Default Moblin is not the upstream/source for the PowerVR driver

    I do not understand where the author of the article gets the idea that Moblin would be the upstream/origin/place of publishing of such a driver, if it existed.

    It just does not make sense to have a Linux distribution being this source....

  6. #6
    Join Date
    Sep 2007
    Location
    Edmonton, Alberta, Canada
    Posts
    117

    Default

    I'm also still really awaiting news on this to debrickify my Panasonic CF-U1! I need to give F12 a try to see if the VESA driver is now smart enough to mode set my nonstandard screen resolution.

  7. #7
    Join Date
    Oct 2007
    Posts
    27

    Default

    Quote Originally Posted by Kano View Post
    Didn't you try

    https://wiki.ubuntu.com/HardwareSupp...oCardsPoulsbo/

    As your favorite distro is U

    Also you could send me something to test *g*
    I'm pretty sure the IEGD 10.2 is newer. However, I'm not sure what the differences are between the iged xorg driver for poulsbo and the psb xorg driver for poulsbo. Are they two different drivers, or do the ubuntu packages just rename the xorg driver?

    http://edc.intel.com/Software/Downloads/IEGD/

    Also, the target system is an embedded system that is from scratch (distroless) and the filesystem image for it is constructed on a development machine. That's why the IEGD scripts that attempt to find out the version of things on the host box and then install to the host box annoy me so.

  8. #8
    Join Date
    Oct 2007
    Posts
    27

    Default

    Quote Originally Posted by arjan_intel View Post
    I do not understand where the author of the article gets the idea that Moblin would be the upstream/origin/place of publishing of such a driver, if it existed.

    It just does not make sense to have a Linux distribution being this source....
    I think this comes from the driver that came with canonical netbooks and could not be obtained independently, or at least, thats the way I understand it. Just like ATI sometimes releases a driver through Ubuntu before the driver is available on their site.

    There is a great deal of confusion surrounding this driver, who makes what version, who distributes what version, etc. Including the strangeness of Intel requiring an account to download a driver (free account).

  9. #9
    Join Date
    Aug 2007
    Posts
    6,615

    Default

    @Michael

    3d is not really usefull on this device anyway. Better test if vaapi works.

    http://kanotix.com/files/fix/mplayer-vaapi-latest-1.txt

  10. #10

    Default

    Quote Originally Posted by arjan_intel View Post
    I do not understand where the author of the article gets the idea that Moblin would be the upstream/origin/place of publishing of such a driver, if it existed.

    It just does not make sense to have a Linux distribution being this source....
    An Intel engineering partner told me that it was supposed to premiere with Moblin 2.1... Care to elaborate then where/when this new driver should be?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •