<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://kerneltrap.org"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>KernelTrap - chipset</title>
 <link>http://kerneltrap.org/taxonomy/term/336/0</link>
 <description></description>
 <language>en-local</language>
<item>
 <title>Manageability Engine Interface</title>
 <link>http://kerneltrap.org/Linux/Manageability_Engine_Interface</link>
 <description>&lt;div class=&quot;taxonomy-images&quot;&gt;&lt;a href=&quot;/news/linux&quot; class=&quot;taxonomy-image-links&quot;&gt;&lt;img src=&quot;http://kerneltrap.org/files/category_pictures/K-Linux.gif&quot; alt=&quot;Linux news&quot; title=&quot;Linux news&quot;  width=&quot;75&quot; height=&quot;75&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;!-- google_ad_section_start --&gt;&lt;p&gt;&quot;&lt;i&gt;The Manageability Engine Interface (aka HECI) allows applications to communicate with the Intel(R) Manageability Engine (ME) firmware.  It is meant to be used by user-space manageability applications to access ME features such as Intel(R) Active Management Technology, Intel(R) Quiet System Technology and ASF,&lt;/i&gt;&quot; Anas Nashif began, describing a new driver for accessing services found in most recent Intel desktop chipsets.  Andrew Morton offered an initial review of the patch and asked for additional information, &quot;&lt;i&gt;why do we want to include this code in Linux?  What value has it to our users, etc?  Basically: tell us more stuff.&lt;/i&gt;&quot;. Anas added:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;&quot;The core hardware architecture of Intel Active Management Technology (Intel AMT) is resident in firmware. The micro-controller within the chipset&#039;s graphics and memory controller (MCH) hub houses the Management Engine (ME) firmware, which implements various services on behalf of management applications. Additionally, flash memory houses system BIOS, code used by the management engine, and a third-party data store (3PDS) that enables applications to store information as needed in non-volatile memory.&quot;&lt;/p&gt;&lt;/blockquote&gt;
&lt;!-- google_ad_section_end --&gt;&lt;p&gt;&lt;a href=&quot;http://kerneltrap.org/Linux/Manageability_Engine_Interface&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://kerneltrap.org/Linux/Manageability_Engine_Interface#comments</comments>
 <category domain="http://kerneltrap.org/taxonomy/term/1109">Anas Nashif</category>
 <category domain="http://kerneltrap.org/Andrew_Morton">Andrew Morton</category>
 <category domain="http://kerneltrap.org/taxonomy/term/336">chipset</category>
 <category domain="http://kerneltrap.org/taxonomy/term/263">firmware</category>
 <category domain="http://kerneltrap.org/Intel">Intel</category>
 <category domain="http://kerneltrap.org/Linux">Linux</category>
 <category domain="http://kerneltrap.org/news/linux">Linux news</category>
 <pubDate>Thu, 25 Oct 2007 01:28:27 +0000</pubDate>
 <dc:creator>Jeremy</dc:creator>
 <guid isPermaLink="false">14672 at http://kerneltrap.org</guid>
</item>
<item>
 <title>Linux:  965GM Express Chipset Drivers</title>
 <link>http://kerneltrap.org/node/8185</link>
 <description>&lt;div class=&quot;taxonomy-images&quot;&gt;&lt;a href=&quot;/news/linux&quot; class=&quot;taxonomy-image-links&quot;&gt;&lt;img src=&quot;http://kerneltrap.org/files/category_pictures/K-Linux.gif&quot; alt=&quot;Linux news&quot; title=&quot;Linux news&quot;  width=&quot;75&quot; height=&quot;75&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;!-- google_ad_section_start --&gt;&lt;p&gt;Keith Packard announced the &lt;a href=&quot;http://intellinuxgraphics.org&quot;&gt;availability of drivers&lt;/a&gt; for Intel&#039;s &lt;a href=&quot;http://www.intel.com/products/chipsets/945gm/index.htm&quot;&gt;965GM Express Chipset&lt;/a&gt;.  Jeff Garzik responded, &quot;&lt;i&gt;great news.  Here&#039;s hoping that Intel produces a standalone video card eventually, to further take away market share from closed source competitors.&lt;/i&gt;&quot;  In Keith&#039;s announcement he explained:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;&quot;The Intel® 965GM Express Chipset represents the first mobile product that implements fourth generation Intel graphics architecture. Designed to support advanced rendering features in modern graphics APIs, this chipset includes support for programmable vertex, geometry, and fragment shaders.&lt;/p&gt;
&lt;p&gt;&quot;Extending Intel&#039;s commitment to work with the X.org and Mesa communities to continuously improve and enhance the drivers, support for this new chipset is provided through the X.org 2.0 Intel driver and the Mesa 6.5.3 releases. These drivers represent significant work by both Intel and the broader open source community.&quot;&lt;/p&gt;&lt;/blockquote&gt;
&lt;!-- google_ad_section_end --&gt;&lt;p&gt;&lt;a href=&quot;http://kerneltrap.org/node/8185&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://kerneltrap.org/node/8185#comments</comments>
 <category domain="http://kerneltrap.org/taxonomy/term/334">965GM</category>
 <category domain="http://kerneltrap.org/taxonomy/term/336">chipset</category>
 <category domain="http://kerneltrap.org/driver">driver</category>
 <category domain="http://kerneltrap.org/Intel">Intel</category>
 <category domain="http://kerneltrap.org/Jeff_Garzik">Jeff Garzik</category>
 <category domain="http://kerneltrap.org/taxonomy/term/332">Keith Packard</category>
 <category domain="http://kerneltrap.org/taxonomy/term/335">video card</category>
 <category domain="http://kerneltrap.org/news/linux">Linux news</category>
 <pubDate>Thu, 10 May 2007 22:54:46 +0000</pubDate>
 <dc:creator>Jeremy</dc:creator>
 <guid isPermaLink="false">8185 at http://kerneltrap.org</guid>
</item>
<item>
 <title>OpenBSD:  Intel Refuses To Open Wireless Chipsets</title>
 <link>http://kerneltrap.org/node/4202</link>
 <description>&lt;div class=&quot;taxonomy-images&quot;&gt;&lt;a href=&quot;/news/openbsd&quot; class=&quot;taxonomy-image-links&quot;&gt;&lt;img src=&quot;http://kerneltrap.org/files/category_pictures/K-OpenBSD_0.gif&quot; alt=&quot;OpenBSD news&quot; title=&quot;Articles about OpenBSD.&quot;  width=&quot;75&quot; height=&quot;75&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;!-- google_ad_section_start --&gt;&lt;p&gt;&lt;a href=&quot;http://openbsd.org/&quot; target=&quot;new&quot;&gt;OpenBSD&lt;/a&gt; creator Theo de Raadt [&lt;a href=&quot;http://kerneltrap.org/node/view/6&quot;&gt;interview&lt;/a&gt;] announced that Intel has refused his request to permit that the firmware for their wireless chipsets be made freely distributable.  He explains, &quot;&lt;i&gt;I had asked for free terms under which we (and Linux, anyone) can redistribute the firmwares for their wireless chipsets.  Without these firmware files included in OpenBSD, users must go do some click-through license at some web site to get at the files.  Without those files, these devices are just bits of metal, plastic, and sand.&lt;/i&gt;&quot;  Intel is one of several companies being approached by OpenBSD in a coordinated effort to try and free up the availability of firmware for wireless chipsets [&lt;a href=&quot;http://kerneltrap.org/node/view/4118&quot;&gt;story&lt;/a&gt;].  Several vendors including Symbol, Zydas, and Atmel have responded favorably, licensing their firmwares so that they can be distributed freely with OpenBSD.&lt;/p&gt;
&lt;p&gt;As to the reason Intel refused to update their licensing, Theo explained that they referenced obligations to outside parties.  Further clarification as to exactly what that means was not provided by the company.  Theo went on to note that though this concludes his dealings with Intel, users are still encouraged to contact them and express their concern for this policy, &quot;&lt;i&gt;maybe they will listen to enough customers, or they will learn to not make this mistake again with future chipsets.  I for one have already decided that I will never recommend an Intel product to anyone ever if there is choice.  (There is almost always choice).&lt;/i&gt;&quot;&lt;/p&gt;
&lt;!-- google_ad_section_end --&gt;&lt;p&gt;&lt;a href=&