<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/include/asm-arm, branch v2.6.16.1</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/include/asm-arm?h=v2.6.16.1</id>
<link rel='self' href='https://git.amat.us/linux/atom/include/asm-arm?h=v2.6.16.1'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2006-03-15T23:17:26Z</updated>
<entry>
<title>[ARM] 3364/1: [cleanup] warning fix - definitions for enable_hlt and disable_hlt</title>
<updated>2006-03-15T23:17:26Z</updated>
<author>
<name>Ben Dooks</name>
<email>ben-linux@fluff.org</email>
</author>
<published>2006-03-15T23:17:26Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=dabaeff06cca86048cfa3f74ce59688bc3addba9'/>
<id>urn:sha1:dabaeff06cca86048cfa3f74ce59688bc3addba9</id>
<content type='text'>
Patch from Ben Dooks

The enable_hlt and disable_hlt should be declared in
include/asm/setup.h. This fixes sparse errors from
arch/arm/kernel/process.c

Signed-off-by: Ben Dooks &lt;ben-linux@fluff.org&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>[ARM] iwmmxt thread state alignment</title>
<updated>2006-03-12T22:36:06Z</updated>
<author>
<name>Russell King</name>
<email>rmk@dyn-67.arm.linux.org.uk</email>
</author>
<published>2006-03-12T22:36:06Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=cdaabbd74b15296acf09215355a7f3b07b92b83e'/>
<id>urn:sha1:cdaabbd74b15296acf09215355a7f3b07b92b83e</id>
<content type='text'>
This patch removes the reliance of iwmmxt on hand coded alignments.
Since thread_info is always 8K aligned, specifying that fpstate is
8-byte aligned achieves the same effect without needing to resort
to hand coded alignments.

Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>[ARM] 3352/1: DSB required for the completion of a TLB maintenance operation</title>
<updated>2006-03-07T14:42:27Z</updated>
<author>
<name>Catalin Marinas</name>
<email>catalin.marinas@arm.com</email>
</author>
<published>2006-03-07T14:42:27Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6a0e243069b09a323255f6e847c87d531961cd96'/>
<id>urn:sha1:6a0e243069b09a323255f6e847c87d531961cd96</id>
<content type='text'>
Patch from Catalin Marinas

Chapter B2.7.3 in the latest ARM ARM (with v6 information) states that
the completion of a TLB maintenance operation is only guaranteed by
the execution of a DSB (Data Syncronization Barrier, formerly Data
Write Barrier or Drain Write Buffer).

Note that a DSB is only needed in the flush_tlb_kernel_* functions
since the completion is guaranteed by a mode change (i.e. switching
back to user mode) for the flush_tlb_user_* functions.

Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>[ARM] 3325/2: GPIO function to control multi-drive (open collector) capability</title>
<updated>2006-02-22T21:23:35Z</updated>
<author>
<name>Andrew Victor</name>
<email>andrew@sanpeople.com</email>
</author>
<published>2006-02-22T21:23:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=df666b9c510fd27fd3b1afd9ddfa1eaa62ce12b3'/>
<id>urn:sha1:df666b9c510fd27fd3b1afd9ddfa1eaa62ce12b3</id>
<content type='text'>
Patch from Andrew Victor

This patch adds the at91_set_multi_drive() function to enable/disable
the multi-drive (open collector) pin capability on the AT91RM9200
processor.

This is necessary to fix the UDC (USB Gadget) driver for the AT91RM9200
board as it will not allow the board reset line to be pulled low if the
pullup is not driven as an open collector output as the boards are wired
to the USB connector on both the DK/EK.

This version of the patch updates it to 2.6.16-rc4.
Orignal patch by Jeff Warren.

Signed-off-by: Andrew Victor &lt;andrew@sanpeople.com&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>[ARM] 3343/1: NAS100d: Fix incorrect I2C pin assignment</title>
<updated>2006-02-22T21:12:06Z</updated>
<author>
<name>Alessandro Zummo</name>
<email>azummo-armlinux@towertech.it</email>
</author>
<published>2006-02-22T21:12:06Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=af898b8f602441a3bebe918a3b26adc92b30762e'/>
<id>urn:sha1:af898b8f602441a3bebe918a3b26adc92b30762e</id>
<content type='text'>
Patch from Alessandro Zummo

The I2C pin assignment for the Iomega NAS100d board was incorrect.  This
patch fixes it.  The correct assignment has now been tested using the
new RTC class and a new driver for the RTC on the NAS100d.

Signed-off-by: Rod Whitby &lt;rod@whitby.id.au&gt;
Signed-off-by: Alessandro Zummo &lt;a.zummo@towertech.it&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>Merge master.kernel.org:/home/rmk/linux-2.6-arm</title>
<updated>2006-02-17T16:13:11Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@g5.osdl.org</email>
</author>
<published>2006-02-17T16:13:11Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a5222049f3e26c21ecd65bfcc9b666d4c813933b'/>
<id>urn:sha1:a5222049f3e26c21ecd65bfcc9b666d4c813933b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[ARM] 3339/1: ARM EABI: make unmuxed syscalls visible</title>
<updated>2006-02-16T22:36:15Z</updated>
<author>
<name>Nicolas Pitre</name>
<email>nico@cam.org</email>
</author>
<published>2006-02-16T22:36:15Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d9db950cfa3d674ee834d980c329efdf8e4a0568'/>
<id>urn:sha1:d9db950cfa3d674ee834d980c329efdf8e4a0568</id>
<content type='text'>
Patch from Nicolas Pitre

With EABI the multiplex sys_ipc and sys_socketcall syscalls are
unavailable and their support code even removed from the compiled
kernel, and the new unmuxed syscalls must be used instead.

Make those syscall numbers visible.

Signed-off-by: Nicolas Pitre &lt;nico@cam.org&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>[ARM] Fix SMP initialisation oops</title>
<updated>2006-02-16T11:08:09Z</updated>
<author>
<name>Russell King</name>
<email>rmk@dyn-67.arm.linux.org.uk</email>
</author>
<published>2006-02-16T11:08:09Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7bbb79403163e047c6e333ff169db34e3c969e65'/>
<id>urn:sha1:7bbb79403163e047c6e333ff169db34e3c969e65</id>
<content type='text'>
A change to the SMP initialisation caused the following oops:

 CPU1: Booted secondary processor
 CPU1: D VIPT write-back cache
 CPU1: I cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets
 CPU1: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets
 &lt;7&gt;Calibrating delay loop... 83.14 BogoMIPS (lpj=415744)
 &lt;1&gt;Unable to handle kernel NULL pointer dereference at virtual address 0000001c
 ...
 PC is at enqueue_task+0x1c/0x64
 LR is at activate_task+0xcc/0xe4

SMP initialisation now requires cpu_possible_map to be initialised in
setup_arch().  Move this from smp_prepare_cpus() to smp_init_cpus()
and call it from our setup_arch() if CONFIG_SMP is enabled.

Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>[PATCH] add asm-generic/mman.h</title>
<updated>2006-02-15T23:32:22Z</updated>
<author>
<name>Michael S. Tsirkin</name>
<email>mst@mellanox.co.il</email>
</author>
<published>2006-02-15T23:17:39Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5f6164f3092832e0d9b12eed52e09a76bf39c64a'/>
<id>urn:sha1:5f6164f3092832e0d9b12eed52e09a76bf39c64a</id>
<content type='text'>
Make new MADV_REMOVE, MADV_DONTFORK, MADV_DOFORK consistent across all
arches.  The idea is to make it possible to use them portably even before
distros include them in libc headers.

Move common flags to asm-generic/mman.h

Signed-off-by: Michael S. Tsirkin &lt;mst@mellanox.co.il&gt;
Cc: Roland Dreier &lt;rolandd@cisco.com&gt;
Cc: Badari Pulavarty &lt;pbadari@us.ibm.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] madvise MADV_DONTFORK/MADV_DOFORK</title>
<updated>2006-02-15T00:09:34Z</updated>
<author>
<name>Michael S. Tsirkin</name>
<email>mst@mellanox.co.il</email>
</author>
<published>2006-02-14T21:53:08Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=f822566165dd46ff5de9bf895cfa6c51f53bb0c4'/>
<id>urn:sha1:f822566165dd46ff5de9bf895cfa6c51f53bb0c4</id>
<content type='text'>
Currently, copy-on-write may change the physical address of a page even if the
user requested that the page is pinned in memory (either by mlock or by
get_user_pages).  This happens if the process forks meanwhile, and the parent
writes to that page.  As a result, the page is orphaned: in case of
get_user_pages, the application will never see any data hardware DMA's into
this page after the COW.  In case of mlock'd memory, the parent is not getting
the realtime/security benefits of mlock.

In particular, this affects the Infiniband modules which do DMA from and into
user pages all the time.

This patch adds madvise options to control whether memory range is inherited
across fork.  Useful e.g.  for when hardware is doing DMA from/into these
pages.  Could also be useful to an application wanting to speed up its forks
by cutting large areas out of consideration.

Signed-off-by: Michael S. Tsirkin &lt;mst@mellanox.co.il&gt;
Acked-by: Hugh Dickins &lt;hugh@veritas.com&gt;
Cc: Michael Kerrisk &lt;mtk-manpages@gmx.net&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
</feed>
