<?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-08T18:23:32Z</updated>
  <generator uri="http://groups.google.com" version="1.99">Google Groups</generator>
  <entry>
  <author>
  <name>Matteo Croce</name>
  <email>technobo...@gmail.com</email>
  </author>
  <updated>2009-11-08T18:23:32Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/4e5e83af4c2358ba/2bfd690111b54a38?show_docid=2bfd690111b54a38</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/4e5e83af4c2358ba/2bfd690111b54a38?show_docid=2bfd690111b54a38"/>
  <title type="text">Re: i686 quirk for AMD Geode</title>
  <summary type="html" xml:space="preserve">
  Right, but what if is_geode_lx() is called befor the x86.id change takes effect? &lt;br&gt; Maybe something like this? &lt;br&gt; --- a/arch/x86/include/asm/geode.h 2009-11-08 19:13:43.531117343 +0100 &lt;br&gt; +++ b/arch/x86/include/asm/geode.h 2009-11-08 19:19:42.130618023 +0100 &lt;br&gt; @@ -177,7 +177,7 @@ &lt;br&gt; static inline int is_geode_lx(void)
  </summary>
  </entry>
  <entry>
  <author>
  <name>Bartlomiej Zolnierkiewicz</name>
  <email>bzoln...@gmail.com</email>
  </author>
  <updated>2009-11-08T18:15:01Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/7cd216588da7b111/7f1ab7210f59ca42?show_docid=7f1ab7210f59ca42</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/7cd216588da7b111/7f1ab7210f59ca42?show_docid=7f1ab7210f59ca42"/>
  <title type="text">Re: [git patches] rt2800 drivers updates</title>
  <summary type="html" xml:space="preserve">
  The current branch is now rt2800-v3.1, changes: &lt;br&gt; - fixed build problem reported by Hauke Mehrtens &lt;br&gt; - added &amp;quot;rt2x00: Remove deprecated ieee80211_rx_status-&amp;gt;qual usage&amp;quot; patch &lt;br&gt; from Ivo and &amp;quot;rt2x00: Update copyright statements.&amp;quot; from you &lt;br&gt; It may take some time to get it to kernel.org mirrors though..
  </summary>
  </entry>
  <entry>
  <author>
  <name>Matteo Croce</name>
  <email>technobo...@gmail.com</email>
  </author>
  <updated>2009-11-08T18:13:36Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/4e5e83af4c2358ba/461e35d6e3b2cb5e?show_docid=461e35d6e3b2cb5e</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/4e5e83af4c2358ba/461e35d6e3b2cb5e?show_docid=461e35d6e3b2cb5e"/>
  <title type="text">Re: i686 quirk for AMD Geode</title>
  <summary type="html" xml:space="preserve">
  This is on my TODO list, but better to discuss it in the GCC mailing list, &lt;br&gt; the kernel should use -march=geode and GCC should generate the best code &lt;br&gt; for the AMD Geode, actually the i686 one
  </summary>
  </entry>
  <entry>
  <author>
  <name>Pavel Machek</name>
  <email>pa...@ucw.cz</email>
  </author>
  <updated>2009-11-08T18:10:41Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/4e5e83af4c2358ba/7d1fed2d3ebbc0f0?show_docid=7d1fed2d3ebbc0f0</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/4e5e83af4c2358ba/7d1fed2d3ebbc0f0?show_docid=7d1fed2d3ebbc0f0"/>
  <title type="text">Re: i686 quirk for AMD Geode</title>
  <summary type="html" xml:space="preserve">
  Good. So there&#39;s really no point in breaking kernel. &lt;br&gt; ..fix gcc to genereta code at least as good as for i686 and you are &lt;br&gt; done...? &lt;br&gt; Pavel
  </summary>
  </entry>
  <entry>
  <author>
  <name>Matteo Croce</name>
  <email>technobo...@gmail.com</email>
  </author>
  <updated>2009-11-08T18:05:07Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/4e5e83af4c2358ba/7c2f44e7859f3cd9?show_docid=7c2f44e7859f3cd9</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/4e5e83af4c2358ba/7c2f44e7859f3cd9?show_docid=7c2f44e7859f3cd9"/>
  <title type="text">Re: i686 quirk for AMD Geode</title>
  <summary type="html" xml:space="preserve">
  True, but also remove the duplicate function is_geode in the NAND driver &lt;br&gt; and use the identical one defined in geode.h: &lt;br&gt; --- a/drivers/mtd/nand/cs553x_nand .c	2009-11-08 18:58:14.835043214 +0100 &lt;br&gt; +++ b/drivers/mtd/nand/cs553x_nand .c	2009-11-08 19:00:07.914117831 +0100 &lt;br&gt; @@ -30,6 +30,7 @@ &lt;br&gt; #include &amp;lt;asm/msr.h&amp;gt;
  </summary>
  </entry>
  <entry>
  <author>
  <name>Ingo Molnar</name>
  <email>mi...@elte.hu</email>
  </author>
  <updated>2009-11-08T18:04:07Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/701f64fc3b46c6cb/3f1e715e99fcdae0?show_docid=3f1e715e99fcdae0</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/701f64fc3b46c6cb/3f1e715e99fcdae0?show_docid=3f1e715e99fcdae0"/>
  <title type="text">Re: [PATCH -tip] x86,apic: Use PAGE_SIZE instead of numbers</title>
  <summary type="html" xml:space="preserve">
  Not in the next 10-20 years or so. (and any prediction beyond that is &lt;br&gt; pointless i suspect) &lt;br&gt; Ingo
  </summary>
  </entry>
  <entry>
  <author>
  <name>Ali Gholami Rudi</name>
  <email>a...@rudi.ir</email>
  </author>
  <updated>2009-11-08T17:56:03Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/f6b6814c88ec30a6/c261e353aeb7fde1?show_docid=c261e353aeb7fde1</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/f6b6814c88ec30a6/c261e353aeb7fde1?show_docid=c261e353aeb7fde1"/>
  <title type="text">Re: [PATCH] trivial: fix checking socket() in net tstamp example</title>
  <summary type="html" xml:space="preserve">
  Hi Patrick, &lt;br&gt; By the way, I tried igb hardware timestamp but HWTSTAMP_FILTER_ALL works &lt;br&gt; almost like HWTSTAMP_FILTER_PTP_*. Isn&#39;t it supposed to timestamp all &lt;br&gt; of the incoming packets? Maybe there is something wrong with my test &lt;br&gt; setup? &lt;br&gt; Thanks, &lt;br&gt; Ali
  </summary>
  </entry>
  <entry>
  <author>
  <name>Julia Lawall</name>
  <email>ju...@diku.dk</email>
  </author>
  <updated>2009-11-08T17:49:19Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/7733932ed6044e3e/2c49ae12ca52f4f7?show_docid=2c49ae12ca52f4f7</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/7733932ed6044e3e/2c49ae12ca52f4f7?show_docid=2c49ae12ca52f4f7"/>
  <title type="text">[PATCH] drivers/media/video: correct initialization of audio_mode</title>
  <summary type="html" xml:space="preserve">
  This initialization of the value of audio_mode is the one used if nothing &lt;br&gt; matches in the subsequent switch. The variable audio_mode is subsequently &lt;br&gt; assigned to constants such as TUNER_AUDIO_MONO and TUNER_AUDIO_STEREO. &lt;br&gt; TUNER_AUDIO_STEREO has the same value as V4L2_TUNER_MODE_STEREO, so it &lt;br&gt; would seem better to use that value here.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Matteo Croce</name>
  <email>technobo...@gmail.com</email>
  </author>
  <updated>2009-11-08T17:47:19Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/4e5e83af4c2358ba/9ee1dc983f102cba?show_docid=9ee1dc983f102cba</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/4e5e83af4c2358ba/9ee1dc983f102cba?show_docid=9ee1dc983f102cba"/>
  <title type="text">Re: i686 quirk for AMD Geode</title>
  <summary type="html" xml:space="preserve">
  Gcc 4.4 already knows about it, just sucks at optimizing: &lt;br&gt; gcc -c -O3 -march=geode ./dry.c -o dry1.o &lt;br&gt; gcc -DPASS2 -O3 -march=geode ./dry.c dry1.o -o dry2 &lt;br&gt; Dhrystone Benchmark, Version C, Version 2.2 &lt;br&gt; Program compiled without &#39;register&#39; attribute &lt;br&gt; Using times(), HZ=100 &lt;br&gt; Trying 5000000 runs through Dhrystone:
  </summary>
  </entry>
  <entry>
  <author>
  <name>Randy Dunlap</name>
  <email>randy.dun...@oracle.com</email>
  </author>
  <updated>2009-11-08T17:43:59Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/8954377f589a9a7a/e1d2bb99cb062c35?show_docid=e1d2bb99cb062c35</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/8954377f589a9a7a/e1d2bb99cb062c35?show_docid=e1d2bb99cb062c35"/>
  <title type="text">Re: mmotm 2009-11-01-10-01 uploaded</title>
  <summary type="html" xml:space="preserve">
  OK. yes, weird. &lt;br&gt; thanks. &lt;br&gt; --- &lt;br&gt; ~Randy
  </summary>
  </entry>
  <entry>
  <author>
  <name>Pavel Machek</name>
  <email>pa...@ucw.cz</email>
  </author>
  <updated>2009-11-08T17:37:28Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/4e5e83af4c2358ba/9d03768364272868?show_docid=9d03768364272868</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/4e5e83af4c2358ba/9d03768364272868?show_docid=9d03768364272868"/>
  <title type="text">Re: i686 quirk for AMD Geode</title>
  <summary type="html" xml:space="preserve">
  .. &lt;br&gt; Teach gcc that geodelx exists? No need to break kernel for that... and &lt;br&gt; you probably can gain even bigger gains. &lt;br&gt; Pavel
  </summary>
  </entry>
  <entry>
  <author>
  <name>Cyrill Gorcunov</name>
  <email>gorcu...@gmail.com</email>
  </author>
  <updated>2009-11-08T17:37:02Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/701f64fc3b46c6cb/858eafbf2be1f8c9?show_docid=858eafbf2be1f8c9</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/701f64fc3b46c6cb/858eafbf2be1f8c9?show_docid=858eafbf2be1f8c9"/>
  <title type="text">Re: [PATCH -tip] x86,apic: Use PAGE_SIZE instead of numbers</title>
  <summary type="html" xml:space="preserve">
  [Maciej W. Rozycki - Sun, Nov 08, 2009 at 05:28:05PM +0000] &lt;br&gt; Yeah, as far as I know. I didn&#39;t find any sign if we going to &lt;br&gt; change PAGE_SHIFT. &lt;br&gt; -- Cyrill
  </summary>
  </entry>
  <entry>
  <author>
  <name>Pavel Machek</name>
  <email>pa...@ucw.cz</email>
  </author>
  <updated>2009-11-08T17:35:54Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/4e5e83af4c2358ba/d7994a58bf0734b8?show_docid=d7994a58bf0734b8</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/4e5e83af4c2358ba/d7994a58bf0734b8?show_docid=d7994a58bf0734b8"/>
  <title type="text">Re: i686 quirk for AMD Geode</title>
  <summary type="html" xml:space="preserve">
  Hi! &lt;br&gt; It is not. &lt;br&gt; NOP should be fast, so this is bad idea. &lt;br&gt; Pavel
  </summary>
  </entry>
  <entry>
  <author>
  <name>K.Prasad</name>
  <email>pra...@linux.vnet.ibm.com</email>
  </author>
  <updated>2009-11-08T17:32:30Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/33a4df59346c06e1/a22101746399c0cb?show_docid=a22101746399c0cb</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/33a4df59346c06e1/a22101746399c0cb?show_docid=a22101746399c0cb"/>
  <title type="text">Re: [PATCH 4/6] hw-breakpoints: Rewrite the hw-breakpoints layer on top of perf events</title>
  <summary type="html" xml:space="preserve">
  When we originally had this discussion on LKML, one of the use-cases &lt;br&gt; cited was &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://lkml.org/lkml/2009/7/29/243&quot;&gt;[link]&lt;/a&gt;. I can&#39;t see why such &lt;br&gt; need should be restricted to a given CPU only, rather than a subset of &lt;br&gt; CPUs (say &#39;x&#39; is a variable normally read/written-to in the interrupt &lt;br&gt; path, and if the said interrupt is has a cpu affinity to a subset of
  </summary>
  </entry>
  <entry>
  <author>
  <name>K.Prasad</name>
  <email>pra...@linux.vnet.ibm.com</email>
  </author>
  <updated>2009-11-08T17:31:35Z</updated>
  <id>http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/a823a632dc012a95/51557d6456c4475e?show_docid=51557d6456c4475e</id>
  <link href="http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/a823a632dc012a95/51557d6456c4475e?show_docid=51557d6456c4475e"/>
  <title type="text">Re: [PATCH 5/7] hw-breakpoints: Rewrite the hw-breakpoints layer on top of perf events</title>
  <summary type="html" xml:space="preserve">
  So, will the breakpoint values be stored in per-cpu variables and be &lt;br&gt; restored when a cpu (from the list of for_each_possible_cpu) eventually &lt;br&gt; turns online due to cpu-hotplug or resume from hibernate (as originally &lt;br&gt; done by load_debug_registers())? &lt;br&gt; A few more observations.... &lt;br&gt; int reserve_bp_slot(struct perf_event *bp)
  </summary>
  </entry>
</feed>
