David Brownell [Mon, 7 Oct 2002 02:54:53 +0000 (19:54 -0700)]
[PATCH] pci/pool.c less spinlock abuse
That previous patch got rid of a boot time might_sleep() warning,
but I noticed two later on:
- kmalloc() needed SLAB_ATOMIC
- destroying the 'pools' driverfs attribute could sleep too
The clean/simple patch for the second one tweaked an API:
- pci_pool_create() can't be called in_interrupt() any more.
nobody used it there, and such support isn't needed; plus
that rule matches its sibling call, pci_pool_destroy().
- that made its SLAB_* flags parameter more useless, so it's
removed and the DMA-mapping.txt is updated. (this param
was more trouble than it was worth -- good that it's gone.)
Nobody (even DaveM) objected to those API changes, so I think
this should be merged.
Chuck Lever [Mon, 7 Oct 2002 02:35:13 +0000 (19:35 -0700)]
[PATCH] initial support for NFS direct I/O for 2.5
This adds initial support for NFS direct I/O in the 2.5 kernel. many
have asked for this support to be included in 2.5. this patch does not
provide working NFS direct I/O, but i'm sending what i have now so that
it can be included before October 20.
NFS direct I/O is enabled by its very own kernel config option. when
enabled, the NFS client won't build to prevent people from using this and
possibly corrupting their NFS files. later i will send a patch that
finishes the implementation.
Chuck Lever [Mon, 7 Oct 2002 02:35:08 +0000 (19:35 -0700)]
[PATCH] remove NFS client internal dependence on page->index
This makes the NFS client copy the page->index field into its read and
write request structures (struct nfs_page) when setting up I/O on a
page. this makes it possible for NFS direct I/O support to reuse
existing NFS client subroutines, and helps eventually allow NFS I/O to
and from anonymous pages. it is a prerequisite for NFS direct I/O
support.
Chuck Lever [Mon, 7 Oct 2002 02:35:02 +0000 (19:35 -0700)]
[PATCH] add struct file* to ->direct_IO addr space op
This makes file credentials available to the ->direct_IO address space
operation by replacing its struct inode* argument with a struct file*
argument. this patch is a prerequisite for NFS direct I/O support. it
breaks the raw device driver.
Marcel Holtmann [Sun, 6 Oct 2002 12:35:03 +0000 (05:35 -0700)]
[PATCH] Bluetooth kbuild fix and config cleanup
This removes the obsolete O_TARGET and cleans up the Config.* and *.c
files to have a unique CONFIG_BLUEZ prefix. Additional two missing help
entries are added.
This patch supports new driver nsp32 - NinjaSCSI-32Bi/UDE PCI/Cardbus
SCSI adapter for 2.5.40. This driver supports at least (we tested) 7
different PCI/Cardbus SCSI cards which use Workbit NinjaSCSI-32 SCSI
processor.
This is the driver part, next one is for things like Config.help,
Makefile, and so on.
Alan Cox [Sun, 6 Oct 2002 08:57:42 +0000 (01:57 -0700)]
[PATCH] add the mini 4x6 font from uclinux
This stands alone from UCLinux and is independent of whether it ever
merges with the mainstream. Its rather handy for getting an entire oops
onto a PDA screen
Alan Cox [Sun, 6 Oct 2002 08:57:20 +0000 (01:57 -0700)]
[PATCH] NCR5380 port to 2.5 first pass
There is still more work to do, the driver sucks in 2.4 and 2.5 but 2.5 has a
lot more of what is needed to make it work nicely. Basically NCR5380_main
probably has to become a thread in the next generation of the code.
After reverting my nice but totally broken idea about accelerating
the linking steps, make the three-stage .tmp_kallsyms.o generation
/ addition work again.
Yeah, that means that we now link vmlinux three times when
CONFIG_KALLSYMS is set, and that's annoying.
The kallsyms patches added __kallsyms as last section into vmlinux,
behind .bss.
This was done to save two additional kallsyms passes, since as the
added section was last, it did not change the symbols before it.
With the new infrastructure in the top-level Makefile, we do not need
to do full relinks for these passes, so they are cheaper. We now
use one additional link/kallsyms run to be able to place the __kallsyms
section before .bss. The other pass is saved by adding an empty but
allocated __kallsyms section in kernel/kallsyms.c, so the first kallsyms
pass already generates a section of the final size.
kbuild: Generalize adding of additional sections to vmlinux
kallsyms needs to actually have a final vmlinux to extract the symbols,
and then add this information as a new section to the final vmlinux.
Currently, we basically just do the vmlinux link twice, adding
.tmp_kallsyms.o the second time. However, it's actually possible to just
link together the temporary vmlinux generated the first time and the
new object file directly without going back to all the single parts
that the temporary vmlinux was linked from.
This mechanism should be useful for sparc as well, where the btfix
mechanism needs an already linked vmlinux, too.
IMPORTANT: This does only work as desired if the link script can be
used recursively, i.e.
Jaroslav Kysela [Sat, 5 Oct 2002 11:40:53 +0000 (13:40 +0200)]
ALSA update
- CS46xx driver - removed unused variable
- USB code
- pass struct usb_interface pointer to the usb-midi parser.
in usb-midi functions, this instance is used instead of parsing
the interface from dev and ifnum.
- allocate the descriptor buffer only for parsing the audio device.
- clean up, new probe/disconnect callbacks for 2.4 API.
- added the support for Yamaha and Midiman devices.