<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Microsoft&#8217;s Dirty ACPI Secrets: It&#8217;s Back! (Updated)</title>
	<atom:link href="http://techrights.org/2008/07/25/foxconn-bios-acpi/feed/" rel="self" type="application/rss+xml" />
	<link>http://techrights.org/2008/07/25/foxconn-bios-acpi/</link>
	<description>Free Software Sentry – watching and reporting maneuvers of those threatened by software freedom</description>
	<lastBuildDate>Tue, 07 Feb 2012 14:00:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Roy Schestowitz</title>
		<link>http://techrights.org/2008/07/25/foxconn-bios-acpi/comment-page-2/#comment-16989</link>
		<dc:creator>Roy Schestowitz</dc:creator>
		<pubDate>Sun, 27 Jul 2008 20:40:26 +0000</pubDate>
		<guid isPermaLink="false">http://boycottnovell.com/2008/07/25/foxconn-bios-acpi/#comment-16989</guid>
		<description>Ditto. Thanks, David, for putting a rational and positive spin on it. You should see what Carla at Linux Today wrote about this incident.</description>
		<content:encoded><![CDATA[<p>Ditto. Thanks, David, for putting a rational and positive spin on it. You should see what Carla at Linux Today wrote about this incident.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roy Bixler</title>
		<link>http://techrights.org/2008/07/25/foxconn-bios-acpi/comment-page-2/#comment-16986</link>
		<dc:creator>Roy Bixler</dc:creator>
		<pubDate>Sun, 27 Jul 2008 17:23:52 +0000</pubDate>
		<guid isPermaLink="false">http://boycottnovell.com/2008/07/25/foxconn-bios-acpi/#comment-16986</guid>
		<description>@David Gerard:

Thanks for the technical explanation.  It seems to confirm what I&#039;ve already heard about ACPI, which is that it&#039;s complex.  The answer in a nutshell thusfar seems to be &quot;it&#039;s either a Linux bug or a BIOS bug.&quot;  Either way, I hope it&#039;s sorted.  Further down in the comments, Ryan (the original person who reported the problem) indicates that Foxconn managers are now willing to work with the Linux ACPI developers.  Apparently, they&#039;re not oblivious to the argument that they could sell more boards if they achieve better compatibility.</description>
		<content:encoded><![CDATA[<p>@David Gerard:</p>
<p>Thanks for the technical explanation.  It seems to confirm what I&#8217;ve already heard about ACPI, which is that it&#8217;s complex.  The answer in a nutshell thusfar seems to be &#8220;it&#8217;s either a Linux bug or a BIOS bug.&#8221;  Either way, I hope it&#8217;s sorted.  Further down in the comments, Ryan (the original person who reported the problem) indicates that Foxconn managers are now willing to work with the Linux ACPI developers.  Apparently, they&#8217;re not oblivious to the argument that they could sell more boards if they achieve better compatibility.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Gerard</title>
		<link>http://techrights.org/2008/07/25/foxconn-bios-acpi/comment-page-2/#comment-16985</link>
		<dc:creator>David Gerard</dc:creator>
		<pubDate>Sun, 27 Jul 2008 17:10:46 +0000</pubDate>
		<guid isPermaLink="false">http://boycottnovell.com/2008/07/25/foxconn-bios-acpi/#comment-16985</guid>
		<description>From the Linux side, Matthew is the most prominent person doing so. From the hardware side, the trick is how to make hardware people &lt;i&gt;want&lt;/i&gt; to actively support Linux working (which is why Matthew got so annoyed at the conspiracy theorising in the Foxconn case, when he sees only the usual blithering stupidity and incompetence. Dell pushing its suppliers for bits that&#039;ll work well in Ubuntu is basically what we need. The suppliers need to &lt;i&gt;want&lt;/i&gt; to support Linux.</description>
		<content:encoded><![CDATA[<p>From the Linux side, Matthew is the most prominent person doing so. From the hardware side, the trick is how to make hardware people <i>want</i> to actively support Linux working (which is why Matthew got so annoyed at the conspiracy theorising in the Foxconn case, when he sees only the usual blithering stupidity and incompetence. Dell pushing its suppliers for bits that&#8217;ll work well in Ubuntu is basically what we need. The suppliers need to <i>want</i> to support Linux.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roy Schestowitz</title>
		<link>http://techrights.org/2008/07/25/foxconn-bios-acpi/comment-page-2/#comment-16984</link>
		<dc:creator>Roy Schestowitz</dc:creator>
		<pubDate>Sun, 27 Jul 2008 16:49:30 +0000</pubDate>
		<guid isPermaLink="false">http://boycottnovell.com/2008/07/25/foxconn-bios-acpi/#comment-16984</guid>
		<description>What bothers me a lot is that I regularly find people who ditch Linux for something like Vista just because of ACPI. Here is a brand-new example I found just an hour ago:

http://llynix.com/articles/linux/i-bid-adieu-ubuntu/

&quot;&lt;em&gt;Yesterday I threw in the towel. I’ve been having problems with ACPI on my new Ubuntu partition. I’ve got other small problems but the ACPI ones are really the deal breaker. A laptop that can’t hibernate isn’t much of a laptop. [...] Perhaps the LiveCD of the new version will fair better, for now though I’m taking a break and going back to the slower, more sluggish but more compatible Vista system.&lt;/em&gt;&quot;

Whether there was technical sabotage or not, someone ought to start taking Linux support seriously. That memo from  Gates ain&#039;t helping. Foxconn&#039;s attitude (watch the conversations with them), is  not helping, either.</description>
		<content:encoded><![CDATA[<p>What bothers me a lot is that I regularly find people who ditch Linux for something like Vista just because of ACPI. Here is a brand-new example I found just an hour ago:</p>
<p><a href="http://llynix.com/articles/linux/i-bid-adieu-ubuntu/" rel="nofollow">http://llynix.com/articles/linux/i-bid-adieu-ubuntu/</a></p>
<p>&#8220;<em>Yesterday I threw in the towel. I’ve been having problems with ACPI on my new Ubuntu partition. I’ve got other small problems but the ACPI ones are really the deal breaker. A laptop that can’t hibernate isn’t much of a laptop. [...] Perhaps the LiveCD of the new version will fair better, for now though I’m taking a break and going back to the slower, more sluggish but more compatible Vista system.</em>&#8221;</p>
<p>Whether there was technical sabotage or not, someone ought to start taking Linux support seriously. That memo from  Gates ain&#8217;t helping. Foxconn&#8217;s attitude (watch the conversations with them), is  not helping, either.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Gerard</title>
		<link>http://techrights.org/2008/07/25/foxconn-bios-acpi/comment-page-1/#comment-16983</link>
		<dc:creator>David Gerard</dc:creator>
		<pubDate>Sun, 27 Jul 2008 16:43:18 +0000</pubDate>
		<guid isPermaLink="false">http://boycottnovell.com/2008/07/25/foxconn-bios-acpi/#comment-16983</guid>
		<description>Matthew Garrett explains it as: everyone copy&#039;n&#039;pastes their ACPI code, and so the Linux code there is probably leftover fragments of junk code that are never executed anyway; the manufacturer bodged something together, checked it didn&#039;t actually catch fire running Vista and shipped. (i.e. such stupidity is the norm.)  Here&#039;s his &lt;a href=&quot;http://mjg59.livejournal.com/94998.html&quot; rel=&quot;nofollow&quot;&gt;full technical writeup&lt;/a&gt; as an expert on ACPI code archaeology.</description>
		<content:encoded><![CDATA[<p>Matthew Garrett explains it as: everyone copy&#8217;n'pastes their ACPI code, and so the Linux code there is probably leftover fragments of junk code that are never executed anyway; the manufacturer bodged something together, checked it didn&#8217;t actually catch fire running Vista and shipped. (i.e. such stupidity is the norm.)  Here&#8217;s his <a href="http://mjg59.livejournal.com/94998.html" rel="nofollow">full technical writeup</a> as an expert on ACPI code archaeology.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roy Bixler</title>
		<link>http://techrights.org/2008/07/25/foxconn-bios-acpi/comment-page-1/#comment-16982</link>
		<dc:creator>Roy Bixler</dc:creator>
		<pubDate>Sun, 27 Jul 2008 16:36:29 +0000</pubDate>
		<guid isPermaLink="false">http://boycottnovell.com/2008/07/25/foxconn-bios-acpi/#comment-16982</guid>
		<description>No doubt that this is really confusing, so it&#039;s an issue ripe for different interpretations.  The exhibit from the Comes Iowa anti-trust case just adds fuel to the fire.  On the other hand, it does sound reasonable that the vendor just never bothered testing their board with Linux because they have no intention of supporting that.

My questions would be the following.  Why test for an operating system in the code if there is no intention to support it?  Why exactly would a hardware vendor explicitly want to exclude an operating system if supporting it would mean more sales for them?</description>
		<content:encoded><![CDATA[<p>No doubt that this is really confusing, so it&#8217;s an issue ripe for different interpretations.  The exhibit from the Comes Iowa anti-trust case just adds fuel to the fire.  On the other hand, it does sound reasonable that the vendor just never bothered testing their board with Linux because they have no intention of supporting that.</p>
<p>My questions would be the following.  Why test for an operating system in the code if there is no intention to support it?  Why exactly would a hardware vendor explicitly want to exclude an operating system if supporting it would mean more sales for them?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alon David</title>
		<link>http://techrights.org/2008/07/25/foxconn-bios-acpi/comment-page-1/#comment-16838</link>
		<dc:creator>Alon David</dc:creator>
		<pubDate>Sat, 26 Jul 2008 21:51:44 +0000</pubDate>
		<guid isPermaLink="false">http://boycottnovell.com/2008/07/25/foxconn-bios-acpi/#comment-16838</guid>
		<description>Hi,

I have a lenovo 3000 N100 laptop, and after coming back from sleep mode the fans on the motherboard don&#039;t work anymore, i think this is an ACPI issue (i&#039;ve tested this on multiple kernels) but I have no idea on how to investigate it and fix it, can anybody help ?

Thanks.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I have a lenovo 3000 N100 laptop, and after coming back from sleep mode the fans on the motherboard don&#8217;t work anymore, i think this is an ACPI issue (i&#8217;ve tested this on multiple kernels) but I have no idea on how to investigate it and fix it, can anybody help ?</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Gerard</title>
		<link>http://techrights.org/2008/07/25/foxconn-bios-acpi/comment-page-1/#comment-16831</link>
		<dc:creator>David Gerard</dc:creator>
		<pubDate>Sat, 26 Jul 2008 20:57:39 +0000</pubDate>
		<guid isPermaLink="false">http://boycottnovell.com/2008/07/25/foxconn-bios-acpi/#comment-16831</guid>
		<description>Matthew Garrett &lt;a href=&quot;http://mjg59.livejournal.com/94905.html&quot; rel=&quot;nofollow&quot;&gt;attributes&lt;/a&gt; it to stupidity rather than malice, and says such stupidity is the norm. (He does a ton of work on ACPI in the Linux kernel.)</description>
		<content:encoded><![CDATA[<p>Matthew Garrett <a href="http://mjg59.livejournal.com/94905.html" rel="nofollow">attributes</a> it to stupidity rather than malice, and says such stupidity is the norm. (He does a ton of work on ACPI in the Linux kernel.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yuhong Bao</title>
		<link>http://techrights.org/2008/07/25/foxconn-bios-acpi/comment-page-1/#comment-16730</link>
		<dc:creator>Yuhong Bao</dc:creator>
		<pubDate>Sat, 26 Jul 2008 06:07:51 +0000</pubDate>
		<guid isPermaLink="false">http://boycottnovell.com/2008/07/25/foxconn-bios-acpi/#comment-16730</guid>
		<description>The difference is this time they are actually doing it, where last time it was just a suggestion.</description>
		<content:encoded><![CDATA[<p>The difference is this time they are actually doing it, where last time it was just a suggestion.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

