- 21 Oct, 2004 14 commits
-
-
David Woodhouse authored
- Reduce memory use by merging adjacent obsolete raw_node_refs - Error handling fixes - Respect kmalloc size limit in scan - NAND ECC updates Signed-Off-By:David Woodhouse <dwmw2@infradead.org>
-
Thomas Gleixner authored
- Use new RS library for ECC - Add support for new NAND flash chips - New board support: - iPAQ H1910 - Renesas AG-AND devel board - Simtec S3C210 - Support for shared controllers on multiple chips. Signed-Off-By:
Thomas Gleixner <tglx@linutronix.de> Signed-Off-By:
-
David Woodhouse authored
Signed-Off-By: -
Thomas Gleixner authored
Signed-Off-By:
-
David Woodhouse authored
Patch from Todd Poynor Signed-Off-By: -
David Woodhouse authored
Mostly from Eric Biederman for supporting BIOS flash. - Move support firmware hub style lock and unlock into fhw_lock.h (from cfi_cmdset_0002) - Move cfi_varsize_frob into cfi_util from cfi_cmdset_0001.c and cfi_cmdset_0002.c - reduce gen_probe probe failuers to a debug level message - Modify cfi_fixup to take a struct mtd_info instead of a struct map_info So that the fixup routines can modify the mtd functions. - Modify cfi_cmdset_0001() to allocate and initialize the mtd structure before calling cfi_fixup. - Modify cfi_cmdset_0002() to allocate and initialize the mtd structure before calling cfi_fixup. - Refactor the hard coded fixups in cfi_cmdset_0001 and cfi_cmdset_0002 so the improved cfi_fixup infrastructure. - Rewrote amd76xrom and ichxrom. They now report their starting physical address in their name. They now both handle multiple bankwidth configurations They both can create multipe mtd devices. They both now assume the rom windows are properly opened by the BIOS or whatever runs previous to them. Their code is now synchromized so it is almost identical, and could be a starting point for a x86_rom_probe. Signed-Off-By: -
David Woodhouse authored
- Technology Systems TS-5500 board - Simtec BAST - IBM 440GX Ocotea Signed-Off-By: -
Thomas Gleixner authored
This is sane, as the driver returns the real data and the return value is for information of NAND aware filesystems. Userspace access to raw NAND is usually restricted to debugging tools which are aware of the NAND specific problems. Signed-Off-By:
-
David Woodhouse authored
Patch from Ben Dooks <ben-mtd@fluff.org> Signed-Off-By: -
David Woodhouse authored
- Update mporter email address - Include file fixups - Tglx's __iomem fixes Signed-Off-By: -
David Woodhouse authored
- Change Pete Popov's email address - Tglx's __iomem fixes - Include file cleanups Signed-Off-By: -
David Woodhouse authored
... by making mtdpart_setup() non-static Patch from Juha Yrjölä committed by Jarkko Lavinen. Signed-Off-By: -
Thomas Gleixner authored
Signed-Off-By:
-
Thomas Gleixner authored
Signed-Off-By:
-
- 20 Oct, 2004 26 commits
-
-
Thomas Gleixner authored
The attached patch contains a shared Reed-Solomon Library analogous to the shared zlib. (N)AND FLASH is gaining popularity and there are a lot of ASIC/SoC/FPGA controllers around which implement hardware support for Reed-Solomon error correction. As usual they use different implementations (polynomials etc.). So it's obvious to use a shared library for the common tasks of error correction. A short scan through the kernel revealed that at least the ftape driver uses Reed-Solomon error correction. It could be easily converted to use the shared library code. The encoder/decoder code is lifted from the GPL'd userspace RS-library written by Phil Karn. I modified/wrapped it to provide the different functions which we need in the MTD/NAND code. The library is tested in extenso under various MTD/NAND configurations. The lib should be usable for other purposes right out of the box. Adjustment for currently not implemented functionality is an easy task. I'm willing to take the maintainership of the library. Signed-Off-By:
-
bk://kernel.bkbits.net/davem/sparc-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
bk://kernel.bkbits.net/davem/net-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Andrew Morton authored
Fix incorrect attempt to doubly-initialise the ethtool ops. Cc: <jgarzik@redhat.com> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Phil Oester authored
The scsihosts boot parameter was removed in 2.5.73, but references to it still exist in docs. Cleanup below. Signed-off-by:
-
Stephen C. Tweedie authored
The orphan list holds inodes that need to be truncated on recovery. In the O_DIRECT case, it's used if we extend the inode --- the truncate on recovery means we'll recover the newly-allocated disk blocks if we crash after the IO starts but before i_size is updated on disk. Now, the orphan list is *also* used to delete inodes that are unlinked but still-open. Those get truncated but also deleted on recovery. The orphan list is held both in memory and on disk. So the rules are that the inode can't be reclaimed while on the orphan list. There are only two cases --- either the inode is actively being written(O_DIRECT) or truncated (in which case the inode is by definition not going to be reused), or it's unlinked but still open (again, non-reclaimable). But in the case where you're truncating or write(O_DIRECT)ing a file that is *ALSO* unlinked, there's a problem --- the final unlink would put the inode on the orphan list, but the write/truncate would try to add/remove it. End result is that the inode disappears from the orphan list while it's still unlinked-but-in-use. That's just a leak-on-crash, it's not going to be detectable in normal use. But it's still a bug, and the way we fix it is for direct-IO and truncate not to do the ext3_orphan_del if the file is unlinked (ie. i_nlink==0). Signed-off-by:
-
William A. Adamson authored
Add the new lock manager callbacks to the documentation Signed-off-by:
Andy Adamson <andros@citi.umich.edu> Signed-off-by:
-
William A. Adamson authored
Export remove_lease(), an interface to time_out_leases() with an fl_break_time in the past. needed by nfsd Signed-off-by:
-
William A. Adamson authored
Export setlease(), a direct interface to __setlease() used by nfsd Signed-off-by:
-
William A. Adamson authored
Use the inode i_writecount to test for handing out a F_RDLCK lease. Signed-off-by:
-
William A. Adamson authored
nfsd will not have a file descriptor, nor an owner on the filp. nfsd also will not use signals. Seperate the lease processsing coe from fcntl_setlease() into a __setlease() call. Signed-off-by:
-
William A. Adamson authored
Move the f_delown processing from lease_modify() into a new default lock manager fl_release_private callback. Signed-off-by:
-
William A. Adamson authored
Separate the lease initialization code from lease_alloc(). set the default lock manager ops. Signed-off-by:
-
William A. Adamson authored
- Add a lock manager break callback to break_lease() for lock managers to initiate breaking a lease. - Move the break_lease() kill_fasync() call to a default lock manager fl_break callback Signed-off-by:
-
William A. Adamson authored
Add a lock manager release private callback to locks_free_lock() for lock manger lease clean-up. Signed-off-by:
-
William A. Adamson authored
The following patches provide an interface to the lease subsystem in the current VFS locking code. NFSv4 delegations and Samba op-locks share most architecture features. The version 4 NFS server delegation implementation should use leases to co-ordinate behavior between local, Samba, and NFS access. The main design points are - Seperate the fcntl interface from the file_lock FL_LEASE processing in fcntl_setlease, creating __setlease() called by fcntl_setlease() - Add new lock_manager callbacks to enable lease properties to be set, leases to be broken, and leases to be cleaned up: with default callbacks preserving the current fcntl_setlease properties. - Add a new interface, setlease() which also calls __setlease(), and remove_lease() for kernel lease managers (e.g. the v4 NFS server) This patch: Add a lock manager copy lock callback to locks_copy_lock() so that nfsd can set lease properties. Signed-off-by:
-
Jeff Mahoney authored
This patch uses the REISERFS_UNSUPPORTED_OPT flag to denote -o(no)acl, and -o(no)user_xattr as unsupported, but allowable, when support isn't built into the kernel. Signed-off-by:
Jeff Mahoney <jeffm@novell.com> Signed-off-by:
-
Jeff Mahoney authored
This patch adds a REISERFS_UNSUPPORTED_OPT flag to denote when a mount option is allowable, but is unsupported in the running configuration. This allows the potential for the set of mount options to be consistent, regardless of what features the kernel is compiled with. Rather than failing the mount, a warning is issued and the mount succeeds. Signed-off-by:
-
Kenneth W. Chen authored
Config option CONFIG_SCHEDSTATS is currently enabled via arch specific Kconfig.debug. Only x86 and ppc arches has code to turn it on. Why not put it in generic lib/Kconfig.debug so it is done once to enable everyone? Signed-off-by:
Ken Chen <kenneth.w.chen@intel.com> Signed-off-by:
-
Armin Schindler authored
The file Documentation/isdn/README.eicon is outdated and obsolete in kernel 2.6. This file includes description of the old Eicon ISDN driver in kernel 2.4, which was removed in 2.6. Signed-off-by:
-
Adrian Bunk authored
Signed-off-by:
Chris Wright <chrisw@osdl.org> Signed-off-by:
Adrian Bunk <bunk@stusta.de> Signed-off-by:
-
Adrian Bunk authored
kernel/built-in.o(.text+0x1d42b): In function `crash_create_proc_entry': : undefined reference to `proc_vmcore' Signed-off-by:
-
Keith Owens authored
Treat .pci_fixup entries the same as .init code/data. Signed-off-by:
Keith Owens <kaos@ocs.com.au> Signed-off-by:
-
Dean Gaudet authored
This patch adds efficeon as a cpu option, and makes a small update to the transmeta cpuid code. (i wasn't sure if the various doc files are UTF-8... if they are, then the e should be a U-275 ;) The compile options may not be ideal, but they're probably close. i used -march=pentium3, but -march=pentium4 would have been good enough too. The cpuid update teaches transmeta.c about the extended processor revision present in cpuid level 0x80860002... the external documentation does not indicate how to break apart this field, and instructs only that the 32-bit value should be printed in hex (alas). Signed-off-by:
dean gaudet <dean@arctic.org> Signed-off-by:
-
Maciej W. Rozycki authored
I've noticed that under specific circumstances the "console=" kernel parameter is ignored. This happens when EARLY_PRINTK is enabled and the serial console is the only available. In this case unregister_console() when called for the early console sets preferred_console back to -1 replacing the value that was recorded by console_setup() -- the order of calls is as follows: 1. register_console() -- for the early console, 2. console_setup() -- recording the console index for the real console, 3. unregister_console() -- for the early console, erasing the console index recorded above, 4. register_console() -- for the real console, picking up the first device available, instead of the selected one. I've observed this problem with a DECstation system using ttyS3 -- its default console device from the firmware's point of view. The solution is to restore the setting of "console=" upon unregister_console(). This made a snapshot of 2.4.26 work for me. I wasn't able to test the changes with 2.6 because DECstation drivers don't support it yet, but the code responsible for console selection appears functionally the same. So I've concluded it needs the same change. Here's a patch. Signed-off-by:
-
Matthieu Castet authored
Signed-off-by:
-
