linux-toradex.git/drivers/block/floppy.c, branch v2.6.30

floppy: provide a PNP device table in the module.

2009-04-03T02:04:49+00:00

The missing device table means that the floppy module is not auto-loaded,
even when the appropriate PNP device (0700) is found.

We don't actually use the table in the module, since the device doesn't
have a struct pnp_driver, but it's sufficient to cause an alias in the
module that udev/modprobe will use.

Signed-off-by: Scott James Remnant 
Signed-off-by: Tim Gardner 
Cc: Bjorn Helgaas 
Cc: Philippe De Muyter 
Acked-by: Kay Sievers 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

platform: make better use of to_platform_{device,driver}() macros

2009-03-24T23:38:24+00:00

This helps the code look more consistent and cleaner.

Signed-off-by: Eric Miao 
Cc: Kay Sievers 
Signed-off-by: Greg Kroah-Hartman

floppy: request and release only the ports we actually use

2009-02-18T23:37:55+00:00

The floppy driver requests an I/O port it doesn't need, and sometimes this
causes a conflict with a motherboard device reported by PNPBIOS.

This patch makes the floppy driver request and release only the ports it
actually uses.  It also factors out the request/release stuff and the
io-ports list so they're all in one place now.

The current floppy driver uses only these ports:

    0x3f2 (FD_DOR)
    0x3f4 (FD_STATUS)
    0x3f5 (FD_DATA)
    0x3f7 (FD_DCR/FD_DIR)

but it requests 0x3f2-0x3f5 and 0x3f7, which includes the unused port
0x3f3.

Some BIOSes report 0x3f3 as a motherboard resource.  The PNP system driver
reserves that, which causes a conflict when the floppy driver requests
0x3f2-0x3f5 later.

Philippe reported that this conflict broke the floppy driver between
2.6.11 and 2.6.22.  His PNPBIOS reports these devices:

    $ cat 00:07/id 00:07/resources	# motherboard device
    PNP0c02
    state = active
    io 0x80-0x80
    io 0x10-0x1f
    io 0x22-0x3f
    io 0x44-0x5f
    io 0x90-0x9f
    io 0xa2-0xbf
    io 0x3f0-0x3f1
    io 0x3f3-0x3f3

    $ cat 00:03/id 00:03/resources	# floppy device
    PNP0700
    state = active
    io 0x3f4-0x3f5
    io 0x3f2-0x3f2

Reference:
    http://lkml.org/lkml/2009/1/31/162

Signed-off-by: Bjorn Helgaas 
Signed-off-by: Philippe De Muyter 
Reported-by: Philippe De Muyter 
Tested-by: Philippe De Muyter 
Cc: Adam M Belay 
Cc: Robert Hancock 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

Create/use more directory structure in the Documentation/ tree.

2008-11-14T17:28:53+00:00

Create Documentation/blockdev/ sub-directory and populate it.
Populate the Documentation/serial/ sub-directory.
Move MSI-HOWTO.txt to Documentation/PCI/.
Move ioctl-number.txt to Documentation/ioctl/.
Update all relevant 00-INDEX files.
Update all relevant Kconfig files and source files.

Signed-off-by: Randy Dunlap

[PATCH] switch floppy

2008-10-21T11:47:49+00:00

Signed-off-by: Al Viro

[PATCH] beginning of methods conversion

2008-10-21T11:47:32+00:00

To keep the size of changesets sane we split the switch by drivers;
to keep the damn thing bisectable we do the following:
	1) rename the affected methods, add ones with correct
prototypes, make (few) callers handle both.  That's this changeset.
	2) for each driver convert to new methods.  *ALL* drivers
are converted in this series.
	3) kill the old (renamed) methods.

Note that it _is_ a flagday; all in-tree drivers are converted and by the
end of this series no trace of old methods remain.  The only reason why
we do that this way is to keep the damn thing bisectable and allow per-driver
debugging if anything goes wrong.

New methods:
	open(bdev, mode)
	release(disk, mode)
	ioctl(bdev, mode, cmd, arg)		/* Called without BKL */
	compat_ioctl(bdev, mode, cmd, arg)
	locked_ioctl(bdev, mode, cmd, arg)	/* Called with BKL, legacy */

Signed-off-by: Al Viro

[PATCH] eliminate use of ->f_flags in block methods

2008-10-21T11:47:08+00:00

store needed information in f_mode

Signed-off-by: Al Viro

[PATCH] introduce fmode_t, do annotations

2008-10-21T11:47:06+00:00

Signed-off-by: Al Viro

Merge commit 'origin'

2008-10-15T00:31:54+00:00

Manual fixup of conflicts on:

	arch/powerpc/include/asm/dcr-regs.h
	drivers/net/ibm_newemac/core.h

floppy: support arbitrary first-sector numbers

2008-10-09T06:56:19+00:00

The current floppy_struct allows floppies to number sectors starting
from 0 or 1.  This patch allows arbitrary first-sector numbers - for
example, 0xC1 for Amstrad CPC disks.

This extends the existing 1-bit field (FD_ZEROBASED, bit 2 of stretch)
to 8 bits (FD_SECTMASK, bits 2 to 9).

Currently 0x00 denotes a first sector number of 1, and 0x01 denotes a
first sector number of 0.  We extend this by interpreting FD_SECTMASK
as the first sector number with the LSB flipped.

Signed-off-by: Keith Wansbrough 
Cc: Alain Knaff 
Cc: Michael Kerrisk 
Cc: Karel Zak 
Signed-off-by: Andrew Morton 
Signed-off-by: Jens Axboe