<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>http://groups.google.com/group/fa.linux.kernel</id>
  <title type="text">fa.linux.kernel Google Group</title>
  <subtitle type="text">
  </subtitle>
  <link href="/group/fa.linux.kernel/feed/atom_v1_0_msgs.xml" rel="self" title="fa.linux.kernel feed"/>
  <updated>2009-11-24T02:01:17Z</updated>
  <generator uri="http://groups.google.com" version="1.99">Google Groups</generator>
  <entry>
  <author>
  <name>Robert Hancock</name>
  <email>hancock...@gmail.com</email>
  </author>
  <updated>2009-11-24T02:01:17Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/24a9e6d0ec64dd26/389867448293c9ce?show_docid=389867448293c9ce</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/24a9e6d0ec64dd26/389867448293c9ce?show_docid=389867448293c9ce"/>
  <title type="text">Re: Toshiba Satellite ACPI problems</title>
  <summary type="html" xml:space="preserve">
  Hmm, that looks really unhappy.. &lt;br&gt; Can you extract and post the DSDT in either raw or decompiled form, as &lt;br&gt; described here: &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://smackerelofopinion.blogspot.com/2009/10/dumping-acpi-tables-using-acpidump-and.html&quot;&gt;[link]&lt;/a&gt;
  </summary>
  </entry>
  <entry>
  <author>
  <name>Len Brown</name>
  <email>l...@kernel.org</email>
  </author>
  <updated>2009-11-24T01:57:15Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/8c5321d66ab7cfa0/64ca68d979e29fcf?show_docid=64ca68d979e29fcf</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/8c5321d66ab7cfa0/64ca68d979e29fcf?show_docid=64ca68d979e29fcf"/>
  <title type="text">Re: Vortex86SX: only works with irqpoll</title>
  <summary type="html" xml:space="preserve">
  Are there any BIOS SETUP options for enabling/disabling ACPI? &lt;br&gt; Does any other version of Linux, or any other OS find ACPI support? &lt;br&gt; does &amp;quot;acpidump&amp;quot; run as root output anything? &lt;br&gt; I couldn&#39;t follow your link to the BIOS manual, but if there &lt;br&gt; are some docs on this system that could tell us what the &lt;br&gt; hardware is and if it is supposed to suport ACPI or not,
  </summary>
  </entry>
  <entry>
  <author>
  <name>Kenji Kaneshige</name>
  <email>kaneshige.ke...@jp.fujitsu.com</email>
  </author>
  <updated>2009-11-24T01:51:56Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/58dc4d597c3f6144/af4dbf1c6abb993d?show_docid=af4dbf1c6abb993d</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/58dc4d597c3f6144/af4dbf1c6abb993d?show_docid=af4dbf1c6abb993d"/>
  <title type="text">Re: [PATCH 1/2] pci: release that leaf bridge&#39; resource that is not big -v11</title>
  <summary type="html" xml:space="preserve">
  Ok, I understood that if the BIOS assigns enough resources to the &lt;br&gt; bridge, it has no impact. &lt;br&gt; One question. I thought your patch shrinks the bridge resource to &lt;br&gt; allocate enough resource for sibling bridge. But it actually doesn&#39;t. &lt;br&gt; Right? &lt;br&gt; It would be appreciated if you update the patch description about
  </summary>
  </entry>
  <entry>
  <author>
  <name>Robin Holt</name>
  <email>h...@sgi.com</email>
  </author>
  <updated>2009-11-24T01:41:36Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/e5a8cec89867fe7f/44051e91474abc99?show_docid=44051e91474abc99</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/e5a8cec89867fe7f/44051e91474abc99?show_docid=44051e91474abc99"/>
  <title type="text">[patch 3/8] x86: UV - Introduce uv_gpa_is_mmr.</title>
  <summary type="html" xml:space="preserve">
  Provide a mechanism for determining if a global physical address is &lt;br&gt; pointing to a UV hub MMR. &lt;br&gt; To: Andrew Morton &amp;lt;a...@linux-foundation.org&amp;gt; &lt;br&gt; Signed-off-by: Robin Holt &amp;lt;h...@sgi.com&amp;gt; &lt;br&gt; Cc: Jack Steiner &amp;lt;stei...@sgi.com&amp;gt; &lt;br&gt; Cc: lkml &amp;lt;linux-ker...@vger.kernel.org&amp;gt; &lt;br&gt; Cc: linux...@vger.kernel.org &lt;br&gt; --- &lt;br&gt; arch/x86/include/asm/uv/uv_hub .h | 7 +++++++
  </summary>
  </entry>
  <entry>
  <author>
  <name>Robin Holt</name>
  <email>h...@sgi.com</email>
  </author>
  <updated>2009-11-24T01:41:32Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/e5a8cec89867fe7f/94dbd75addc7758f?show_docid=94dbd75addc7758f</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/e5a8cec89867fe7f/94dbd75addc7758f?show_docid=94dbd75addc7758f"/>
  <title type="text">[patch 6/8] x86: UV - XPC NULL deref when mesq becomes empty.</title>
  <summary type="html" xml:space="preserve">
  Under heavy load conditions, our set of xpc messages may become exhausted. &lt;br&gt; The code handles this correctly with the exception of the management &lt;br&gt; code which hits a NULL pointer dereference. &lt;br&gt; To: Andrew Morton &amp;lt;a...@linux-foundation.org&amp;gt; &lt;br&gt; Signed-off-by: Robin Holt &amp;lt;h...@sgi.com&amp;gt; &lt;br&gt; Cc: Jack Steiner &amp;lt;stei...@sgi.com&amp;gt;
  </summary>
  </entry>
  <entry>
  <author>
  <name>Robin Holt</name>
  <email>h...@sgi.com</email>
  </author>
  <updated>2009-11-24T01:41:11Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/e5a8cec89867fe7f/3153f683d3474e49?show_docid=3153f683d3474e49</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/e5a8cec89867fe7f/3153f683d3474e49?show_docid=3153f683d3474e49"/>
  <title type="text">[patch 8/8] [patch 8/8] X86: UV - XPC receive message reuse triggers invalid BUG_ON().</title>
  <summary type="html" xml:space="preserve">
  This was a difficult bug to trip. XPC was in the middle of sending an &lt;br&gt; acknowledgement for a received message. &lt;br&gt; In xpc_received_payload_uv(): &lt;br&gt; . &lt;br&gt; ret = xpc_send_gru_msg(ch-&amp;gt;sn.uv.cac hed_notify_gru_mq_desc, msg, &lt;br&gt; sizeof(struct xpc_notify_mq_msghdr_uv)); &lt;br&gt; if (ret != xpSuccess)
  </summary>
  </entry>
  <entry>
  <author>
  <name>Robin Holt</name>
  <email>h...@sgi.com</email>
  </author>
  <updated>2009-11-24T01:41:04Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/e5a8cec89867fe7f/7277da17e43382ac?show_docid=7277da17e43382ac</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/e5a8cec89867fe7f/7277da17e43382ac?show_docid=7277da17e43382ac"/>
  <title type="text">[patch 7/8] X86: UV - xpc_make_first_contact hang due to not accepting ACTIVE state.</title>
  <summary type="html" xml:space="preserve">
  Many times while the initial connection is being made, the &lt;br&gt; contacted partition will send back both the ACTIVATING and the ACTIVE &lt;br&gt; remote_act_state changes in very close succescion. The 1/4 second delay &lt;br&gt; in the make first contact loop is large enough to nearly always miss &lt;br&gt; the ACTIVATING state change. &lt;br&gt; Since either state indicates the remote partition has acknowledged our
  </summary>
  </entry>
  <entry>
  <author>
  <name>Robin Holt</name>
  <email>h...@sgi.com</email>
  </author>
  <updated>2009-11-24T01:40:55Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/e5a8cec89867fe7f/e3d1adc6935949ab?show_docid=e3d1adc6935949ab</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/e5a8cec89867fe7f/e3d1adc6935949ab?show_docid=e3d1adc6935949ab"/>
  <title type="text">[patch 2/8] x86: UV - XPC needs to provide an abstraction for uv_gpa.</title>
  <summary type="html" xml:space="preserve">
  Provide an SGI SN2/UV agnositic method for converting a global physical &lt;br&gt; address into a socket physical address. &lt;br&gt; To: Andrew Morton &amp;lt;a...@linux-foundation.org&amp;gt; &lt;br&gt; Signed-off-by: Robin Holt &amp;lt;h...@sgi.com&amp;gt; &lt;br&gt; Cc: Jack Steiner &amp;lt;stei...@sgi.com&amp;gt; &lt;br&gt; Cc: lkml &amp;lt;linux-ker...@vger.kernel.org&amp;gt; &lt;br&gt; Cc: linux...@vger.kernel.org
  </summary>
  </entry>
  <entry>
  <author>
  <name>Robin Holt</name>
  <email>h...@sgi.com</email>
  </author>
  <updated>2009-11-24T01:40:39Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/e5a8cec89867fe7f/2729386414671f56?show_docid=2729386414671f56</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/e5a8cec89867fe7f/2729386414671f56?show_docid=2729386414671f56"/>
  <title type="text">[patch 5/8] x86: UV - Update XPC to handle updated BIOS interface.</title>
  <summary type="html" xml:space="preserve">
  The UV BIOS has moved the location of some of their pointers to the &lt;br&gt; &amp;quot;partition reserved page&amp;quot; from memory into a uv hub MMR. The GRU does &lt;br&gt; not support bcopy operations from MMR space so we need to special case &lt;br&gt; the MMR addresses using VLOAD operations. &lt;br&gt; Additionally, the BIOS call for registering a message queue watchlist
  </summary>
  </entry>
  <entry>
  <author>
  <name>Robin Holt</name>
  <email>h...@sgi.com</email>
  </author>
  <updated>2009-11-24T01:40:24Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/e5a8cec89867fe7f/d24c3f4bb5ddf3ed?show_docid=d24c3f4bb5ddf3ed</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/e5a8cec89867fe7f/d24c3f4bb5ddf3ed?show_docid=d24c3f4bb5ddf3ed"/>
  <title type="text">[patch 4/8] X86: UV - Implement a gru_read_gpa kernel function.</title>
  <summary type="html" xml:space="preserve">
  The BIOS has decided to store a pointer to the partition reserved page &lt;br&gt; in a scratch MMR. The GRU is only able to read an MMR using a vload &lt;br&gt; instruction. The gru_read_gpa() function will implemented. &lt;br&gt; To: Andrew Morton &amp;lt;a...@linux-foundation.org&amp;gt; &lt;br&gt; Signed-off-by: Robin Holt &amp;lt;h...@sgi.com&amp;gt; &lt;br&gt; Signed-off-by: Jack Steiner &amp;lt;stei...@sgi.com&amp;gt;
  </summary>
  </entry>
  <entry>
  <author>
  <name>Robin Holt</name>
  <email>h...@sgi.com</email>
  </author>
  <updated>2009-11-24T01:40:03Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/e5a8cec89867fe7f/6d0ea0594bdeef68?show_docid=6d0ea0594bdeef68</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/e5a8cec89867fe7f/6d0ea0594bdeef68?show_docid=6d0ea0594bdeef68"/>
  <title type="text">[patch 0/8] x86: UV - XPC fixes with related support functionality V2.</title>
  <summary type="html" xml:space="preserve">
  The UV BIOS has been updated to implement some of our interface &lt;br&gt; functionality differently than originally expected. These patches update &lt;br&gt; the kernel to the bios implementation and include a few minor bug fixes &lt;br&gt; which prevent us from doing significant testing on real hardware. &lt;br&gt; Changes from V1: &lt;br&gt; - Actually include the patch introducing the gru_read_gpa. This
  </summary>
  </entry>
  <entry>
  <author>
  <name>Robin Holt</name>
  <email>h...@sgi.com</email>
  </author>
  <updated>2009-11-24T01:40:11Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/87723b2084902c16/9272788ae33b978e?show_docid=9272788ae33b978e</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/87723b2084902c16/9272788ae33b978e?show_docid=9272788ae33b978e"/>
  <title type="text">[patch 1/8] x86: UV - Introduce a means to translate from gpa -&gt; socket_paddr.</title>
  <summary type="html" xml:space="preserve">
  For SGI UV systems, translate from a global physical address back to &lt;br&gt; a socket physical address. This does nothing to ensure the socket &lt;br&gt; physical address is actually addressable by the kernel. That is the &lt;br&gt; responsibility of the user of the function. &lt;br&gt; To: Andrew Morton &amp;lt;a...@linux-foundation.org&amp;gt; &lt;br&gt; Signed-off-by: Robin Holt &amp;lt;h...@sgi.com&amp;gt;
  </summary>
  </entry>
  <entry>
  <author>
  <name>Ang Way Chuang</name>
  <email>wcan...@gmail.com</email>
  </author>
  <updated>2009-11-24T01:34:17Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/d066dfa26ffd7bce/485671f769eb499f?show_docid=485671f769eb499f</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/d066dfa26ffd7bce/485671f769eb499f?show_docid=485671f769eb499f"/>
  <title type="text">[PATCH] dvb-core: Fix ULE decapsulation bug when less than 4 bytes of ULE SNDU is packed into the remaining bytes of a MPEG2-TS frame</title>
  <summary type="html" xml:space="preserve">
  ULE (Unidirectional Lightweight Encapsulation RFC 4326) decapsulation &lt;br&gt; code has a bug that incorrectly treats ULE SNDU packed into the &lt;br&gt; remaining 2 or 3 bytes of a MPEG2-TS frame as having invalid pointer &lt;br&gt; field on the subsequent MPEG2-TS frame. &lt;br&gt; This patch was generated and tested against v2.6.32-rc8. Similar patch
  </summary>
  </entry>
  <entry>
  <author>
  <name>Robert Hancock</name>
  <email>hancock...@gmail.com</email>
  </author>
  <updated>2009-11-24T01:29:40Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/8c5321d66ab7cfa0/657c25a0d035ce96?show_docid=657c25a0d035ce96</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/8c5321d66ab7cfa0/657c25a0d035ce96?show_docid=657c25a0d035ce96"/>
  <title type="text">Re: Vortex86SX: only works with irqpoll</title>
  <summary type="html" xml:space="preserve">
  Looking at the BIOS manual on their web site: &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;ftp://downl...@ftp.dmp.com.tw/vortex86sx/Vortex86SX_BIOS_Manual.pdf&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; you can try toggling a few of the options: Try switching OnBoard IDE &lt;br&gt; Operate Mode between Legacy Mode and Native Mode. If the kernel and the &lt;br&gt; actual device disagree here, that could cause IRQ delivery problems. You
  </summary>
  </entry>
  <entry>
  <author>
  <name>Arnaldo Carvalho de Melo</name>
  <email>a...@infradead.org</email>
  </author>
  <updated>2009-11-24T01:20:54Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/ea7156b47c7ae5bb/147667ace02a9455?show_docid=147667ace02a9455</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/ea7156b47c7ae5bb/147667ace02a9455?show_docid=147667ace02a9455"/>
  <title type="text">Re: [PATCH 2/2] perf kmem: resolve symbols</title>
  <summary type="html" xml:space="preserve">
  Em Tue, Nov 24, 2009 at 08:50:57AM +0800, Li Zefan escreveu: &lt;br&gt; Ok, I&#39;ll have some sleep now, hack away! :-) &lt;br&gt; - Arnaldo
  </summary>
  </entry>
</feed>
