<?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: Windows as a poorly debugged set of device drivers?</title>
	<atom:link href="http://ianmurdock.com/cloud/windows-as-a-poorly-debugged-set-of-device-drivers/feed/" rel="self" type="application/rss+xml" />
	<link>http://ianmurdock.com/cloud/windows-as-a-poorly-debugged-set-of-device-drivers/</link>
	<description>on emerging platforms and the power of aggregation and integration</description>
	<lastBuildDate>Fri, 23 Oct 2009 23:28:31 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Ian Murdock</title>
		<link>http://ianmurdock.com/cloud/windows-as-a-poorly-debugged-set-of-device-drivers/comment-page-1/#comment-767</link>
		<dc:creator>Ian Murdock</dc:creator>
		<pubDate>Fri, 04 Aug 2006 18:15:14 +0000</pubDate>
		<guid isPermaLink="false">http://ianmurdock.com/?p=350#comment-767</guid>
		<description>It does have a little bit to do with the kernel though. Right now, it&#039;s very hard to write and distribute a third party driver because the kernel ABI is a moving target. (Yes, the ABI is important---compiling drivers is not a viable option for the vast majority of people out there.) The current solution, &quot;get it added to the upstream kernel&quot;, is an odd and inconsistent one. Why? One of the fundamental strengths of open source development is its distributed nature; yet in the case of Linux drivers, we&#039;re told the only viable solution is to centralize everything. I understand that&#039;s so the kernel developers can change the API at will. But at some point, the quality of third party software/drivers/etc. needed to build a strong ecosystem needs to come before making the lives of the developers easier. -ian</description>
		<content:encoded><![CDATA[<p>It does have a little bit to do with the kernel though. Right now, it&#8217;s very hard to write and distribute a third party driver because the kernel ABI is a moving target. (Yes, the ABI is important&#8212;compiling drivers is not a viable option for the vast majority of people out there.) The current solution, &#8220;get it added to the upstream kernel&#8221;, is an odd and inconsistent one. Why? One of the fundamental strengths of open source development is its distributed nature; yet in the case of Linux drivers, we&#8217;re told the only viable solution is to centralize everything. I understand that&#8217;s so the kernel developers can change the API at will. But at some point, the quality of third party software/drivers/etc. needed to build a strong ecosystem needs to come before making the lives of the developers easier. -ian</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Somebody passing by</title>
		<link>http://ianmurdock.com/cloud/windows-as-a-poorly-debugged-set-of-device-drivers/comment-page-1/#comment-766</link>
		<dc:creator>Somebody passing by</dc:creator>
		<pubDate>Fri, 04 Aug 2006 16:52:13 +0000</pubDate>
		<guid isPermaLink="false">http://ianmurdock.com/?p=350#comment-766</guid>
		<description>All in all this has to do with 3rd party drivers and software, you can&#039;t only rely on smart people working in the kernel guessing what to do with devices they didn&#039;t design. Linux keeps getting better and better, but it has to keep pace with vendors. Some people are lucky and have everything working (like me) and some other aren&#039;t. It can only be changed in the mid-term by making it easy for vendors to deploy their software (I&#039;m thinking of the LSB and Portland) and off course encouraging them to go open source, but also being practical and flexible about propietary software for Linux.</description>
		<content:encoded><![CDATA[<p>All in all this has to do with 3rd party drivers and software, you can&#8217;t only rely on smart people working in the kernel guessing what to do with devices they didn&#8217;t design. Linux keeps getting better and better, but it has to keep pace with vendors. Some people are lucky and have everything working (like me) and some other aren&#8217;t. It can only be changed in the mid-term by making it easy for vendors to deploy their software (I&#8217;m thinking of the LSB and Portland) and off course encouraging them to go open source, but also being practical and flexible about propietary software for Linux.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wolfgang.lonien.de &#187; Blog Archive &#187; Agent provocateur, or: nice try</title>
		<link>http://ianmurdock.com/cloud/windows-as-a-poorly-debugged-set-of-device-drivers/comment-page-1/#comment-765</link>
		<dc:creator>wolfgang.lonien.de &#187; Blog Archive &#187; Agent provocateur, or: nice try</dc:creator>
		<pubDate>Fri, 04 Aug 2006 10:31:19 +0000</pubDate>
		<guid isPermaLink="false">http://ianmurdock.com/?p=350#comment-765</guid>
		<description>[...] Hehe - just stumbled over this. [...]</description>
		<content:encoded><![CDATA[<p>[...] Hehe &#8211; just stumbled over this. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Murdock</title>
		<link>http://ianmurdock.com/cloud/windows-as-a-poorly-debugged-set-of-device-drivers/comment-page-1/#comment-764</link>
		<dc:creator>Ian Murdock</dc:creator>
		<pubDate>Thu, 03 Aug 2006 19:19:08 +0000</pubDate>
		<guid isPermaLink="false">http://ianmurdock.com/?p=350#comment-764</guid>
		<description>I don&#039;t propose this as a general strategy for Linux by any means! Maybe a practical solution for a frustrated individual like myself. But mostly just food for thought.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t propose this as a general strategy for Linux by any means! Maybe a practical solution for a frustrated individual like myself. But mostly just food for thought.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Murdock</title>
		<link>http://ianmurdock.com/cloud/windows-as-a-poorly-debugged-set-of-device-drivers/comment-page-1/#comment-763</link>
		<dc:creator>Ian Murdock</dc:creator>
		<pubDate>Thu, 03 Aug 2006 19:16:50 +0000</pubDate>
		<guid isPermaLink="false">http://ianmurdock.com/?p=350#comment-763</guid>
		<description>The same thing I do now: Curse.</description>
		<content:encoded><![CDATA[<p>The same thing I do now: Curse.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexandre Oliva</title>
		<link>http://ianmurdock.com/cloud/windows-as-a-poorly-debugged-set-of-device-drivers/comment-page-1/#comment-762</link>
		<dc:creator>Alexandre Oliva</dc:creator>
		<pubDate>Thu, 03 Aug 2006 18:06:15 +0000</pubDate>
		<guid isPermaLink="false">http://ianmurdock.com/?p=350#comment-762</guid>
		<description>And what do you do when you hit a bug in the driver?  Heck, I have even a USB mouse that will instantly crash Windows on boot up if it&#039;s plugged in on my wife&#039;s notebook!  Good thing we don&#039;t ever use Windows :-)</description>
		<content:encoded><![CDATA[<p>And what do you do when you hit a bug in the driver?  Heck, I have even a USB mouse that will instantly crash Windows on boot up if it&#8217;s plugged in on my wife&#8217;s notebook!  Good thing we don&#8217;t ever use Windows :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruno</title>
		<link>http://ianmurdock.com/cloud/windows-as-a-poorly-debugged-set-of-device-drivers/comment-page-1/#comment-761</link>
		<dc:creator>Bruno</dc:creator>
		<pubDate>Thu, 03 Aug 2006 17:20:19 +0000</pubDate>
		<guid isPermaLink="false">http://ianmurdock.com/?p=350#comment-761</guid>
		<description>3D acceleration on vmware doesn&#039;t work either :P</description>
		<content:encoded><![CDATA[<p>3D acceleration on vmware doesn&#8217;t work either :P</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Linux Daily Log &#187; XGL, repositório autenticado, problemas com drivers e falta de tempo.</title>
		<link>http://ianmurdock.com/cloud/windows-as-a-poorly-debugged-set-of-device-drivers/comment-page-1/#comment-760</link>
		<dc:creator>Linux Daily Log &#187; XGL, repositório autenticado, problemas com drivers e falta de tempo.</dc:creator>
		<pubDate>Thu, 03 Aug 2006 00:48:54 +0000</pubDate>
		<guid isPermaLink="false">http://ianmurdock.com/?p=350#comment-760</guid>
		<description>[...] Já no desktop, tentei utilizar o XGL/Compiz, a partir de alguns tutoriais que encontrei por aí, o que resultou em uma estação de trabalho entrando apenas no console, depois de tentar carregar o X. Antes disso, passei quatro meses tentando descobrir porque minha placa Radeon 9550 não habilitava a aceleração 3D. Depois de muita procura, testes e compilações de kernels com parâmetros obscuros, descobri, numa discussão da lista de desenvolvedores do módulo AGPGART, que o problema era a BIOS - a placa K8N, da ASUS, tem um problema sério com a BIOS, em versões posteriores à 1006, que impedem que o módulo funcione corretamente. Esta última situação, e mais algumas coisas espalhadas, me fez refletir um bocado sobre o uso de Linux no desktop. Não estava muito decidido a escrever sobre isso até ler um post, no blog do Ian Murdock, sobre o mesmo tipo de problema, do qual traduzo um trecho a seguir: Claro, há outro lado da moeda nisso: se um sistema operacional é apenas um conjunto de drivers de dispositivos, você não gostaria de ter o conjunto mais amplo? Tão longe quanto o desktop Linux chegou nos últimos anos, ainda fica muito atrás do Windows em termos de plug-and-play. Por exemplo, durante minha recente viagem a Moscou, meus colegas usuários do Windows conectaram-se em redes wireless impunemente, no hotel e até mesmo sentado em táxis no infame tráfego de Moscou. Enquanto eles estavam clicando em agradáveis balões dizendo &#8220;rede wireless detectada&#8221;, eu estava aprendendo mais do que desejaria saber sobre o iwconfig, xingando enquanto isso. E não foi apenas o wifi. Meu laptop só entrava em suspensão com sucesso cerca de metade do tempo. Por qualquer razão, a aceleração 3D do meu laptop não funcionava com as mais recentes decorações. E por aí vai&#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] Já no desktop, tentei utilizar o XGL/Compiz, a partir de alguns tutoriais que encontrei por aí, o que resultou em uma estação de trabalho entrando apenas no console, depois de tentar carregar o X. Antes disso, passei quatro meses tentando descobrir porque minha placa Radeon 9550 não habilitava a aceleração 3D. Depois de muita procura, testes e compilações de kernels com parâmetros obscuros, descobri, numa discussão da lista de desenvolvedores do módulo AGPGART, que o problema era a BIOS &#8211; a placa K8N, da ASUS, tem um problema sério com a BIOS, em versões posteriores à 1006, que impedem que o módulo funcione corretamente. Esta última situação, e mais algumas coisas espalhadas, me fez refletir um bocado sobre o uso de Linux no desktop. Não estava muito decidido a escrever sobre isso até ler um post, no blog do Ian Murdock, sobre o mesmo tipo de problema, do qual traduzo um trecho a seguir: Claro, há outro lado da moeda nisso: se um sistema operacional é apenas um conjunto de drivers de dispositivos, você não gostaria de ter o conjunto mais amplo? Tão longe quanto o desktop Linux chegou nos últimos anos, ainda fica muito atrás do Windows em termos de plug-and-play. Por exemplo, durante minha recente viagem a Moscou, meus colegas usuários do Windows conectaram-se em redes wireless impunemente, no hotel e até mesmo sentado em táxis no infame tráfego de Moscou. Enquanto eles estavam clicando em agradáveis balões dizendo &#8220;rede wireless detectada&#8221;, eu estava aprendendo mais do que desejaria saber sobre o iwconfig, xingando enquanto isso. E não foi apenas o wifi. Meu laptop só entrava em suspensão com sucesso cerca de metade do tempo. Por qualquer razão, a aceleração 3D do meu laptop não funcionava com as mais recentes decorações. E por aí vai&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Brandizzi</title>
		<link>http://ianmurdock.com/cloud/windows-as-a-poorly-debugged-set-of-device-drivers/comment-page-1/#comment-759</link>
		<dc:creator>Adam Brandizzi</dc:creator>
		<pubDate>Thu, 03 Aug 2006 00:14:40 +0000</pubDate>
		<guid isPermaLink="false">http://ianmurdock.com/?p=350#comment-759</guid>
		<description>It&#039;s really pratical and useful, but it smells like the OS/2 error: adopting compatibility with Windows drivers, why would hardware vendors produce Linux drivers? Didn&#039;t you see here a serious risk?</description>
		<content:encoded><![CDATA[<p>It&#8217;s really pratical and useful, but it smells like the OS/2 error: adopting compatibility with Windows drivers, why would hardware vendors produce Linux drivers? Didn&#8217;t you see here a serious risk?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: none</title>
		<link>http://ianmurdock.com/cloud/windows-as-a-poorly-debugged-set-of-device-drivers/comment-page-1/#comment-758</link>
		<dc:creator>none</dc:creator>
		<pubDate>Wed, 02 Aug 2006 16:32:17 +0000</pubDate>
		<guid isPermaLink="false">http://ianmurdock.com/?p=350#comment-758</guid>
		<description>Do you really think doing this encourages driver development?

And what happens when you start getting mysterious problems with windows drivers? Is it even possible to track down the problems &amp; fix them? No. You just have to shrug and reinstall windows.

Best of both worlds, eh?</description>
		<content:encoded><![CDATA[<p>Do you really think doing this encourages driver development?</p>
<p>And what happens when you start getting mysterious problems with windows drivers? Is it even possible to track down the problems &amp; fix them? No. You just have to shrug and reinstall windows.</p>
<p>Best of both worlds, eh?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

