28 Feb, 2008
12 commits
-
Switch the SSB PCI core driver to the new SPROM data structure now that
the old one has been removed.Signed-off-by: Aurelien Jarno
Acked-by: Michael Buesch
Signed-off-by: John W. Linville -
This may happen e.g. when the ssb is statically enables by the b44 driver,
and the b43 pci-ssb bridge is enbled by the b43/b43legacy drivers, or the
b43/b43legacy drivers are built statically.Signed-off-by: Alexey Zaytsev
Acked-by: Larry Finger
Signed-off-by: John W. Linville -
The bridge code was unnecessary enabled by the b44
driver, but it prevents the bcm43xx driver from
being loaded, as the bridge claims the same pci ids.Now we enable the birdge only if the b43{legacy}
drivers are selected.Signed-off-by: Alexey Zaytsev
Acked-by: Larry Finger
Signed-off-by: John W. Linville -
The libertas driver exports a number of symbols with no in-tree users;
remove these unused exports. lbs_reset_device() is completely unused, with
no callers at all, so remove the function completely.A couple of these unused exported symbols are static, which causes the
following build error on ia64 with gcc 4.2.3:drivers/net/wireless/libertas/main.c:1375: error: __ksymtab_lbs_remove_mesh causes a section type conflict
drivers/net/wireless/libertas/main.c:1354: error: __ksymtab_lbs_add_mesh causes a section type conflictSigned-off-by: Roland Dreier
Acked-by: Holger Schurig
Acked-by: Dan Williams
Signed-off-by: John W. Linville -
The "goto end;" part definitely must not be rate limited.
Signed-off-by: Johannes Berg
Signed-off-by: John W. Linville -
rt2x00lib_reset_link_tuner() can be called from within
the link tuner itself. This means that it should
_not_ call rt2x00lib_stop_link_tuner() since that will
cause the thread to hang.Reorder the things that should be done during a
link tuner reset and during a link tuner start.Also make antenna tuning the last step of the link
tuner since it could possibly reset some statistical
information which we need for average calculation.Signed-off-by: Ivo van Doorn
Signed-off-by: John W. Linville -
When rssi_a > rssi_b is true and the current antenna
was already antenna A, then rt2x00 incorrectly jumped
to antenna B.Also don't configure the antenna when there has been
no change in the antenna setup.Signed-off-by: Ivo van Doorn
Signed-off-by: John W. Linville -
This adds 2 new states which both are used to toggle
the RX. These new states are required for usage
inside the link tuner thread, because the normal
RX toggling will stop the link tuner thread.
While it is possible that the link tuner thread itself
is the caller of the RX toggle (when using software
antenna diversity).Signed-off-by: Ivo van Doorn
Signed-off-by: John W. Linville -
Fix 2 issues in antenna diversity selection.
1) the following statement will always return true.
if ((rssi_curr - rssi_old) > -5 || (rssi_curr - rssi_old) < 5)
It is cleaner to check if the absolute value is smaller then 5.2) Only enable software diversity when default antenna setup
indicates support for it. Don't select it when the hardware
does not indicate support for it...Signed-off-by: Ivo van Doorn
Signed-off-by: John W. Linville -
| CC drivers/net/ps3_gelic_wireless.o
| /home/bigeasy/git/linux-2.6/drivers/net/ps3_gelic_wireless.c: In function 'gelic_wl_setup_netdev_ops':
| /home/bigeasy/git/linux-2.6/drivers/net/ps3_gelic_wireless.c:2660: error: 'struct net_device' has no member named 'wireless_data'
| /home/bigeasy/git/linux-2.6/drivers/net/ps3_gelic_wireless.c:2661: error: 'struct net_device' has no member named 'wireless_handlers'
| make[3]: *** [drivers/net/ps3_gelic_wireless.o] Error 1
| make[2]: *** [drivers/net] Error 2
| make[1]: *** [drivers] Error 2
| make[1]: *** Waiting for unfinished jobs....
| make: *** [sub-make] Error 2Signed-off-by: Sebastian Siewior
Acked-by: Masakazu Mokuno
Signed-off-by: John W. Linville -
Link the net_device structure of the wireless part to the
corresponding device structure.Without this, the sysfs node for this net_device would not have
'device' link.Signed-off-by: Masakazu Mokuno
Acked-by: Dan Williams
Signed-off-by: John W. Linville -
It is obviously wrong to use an enum in a little endian struct,
and those other enums should be declared differently.Signed-off-by: Johannes Berg
Acked-by: Jussi Kivilinna
Signed-off-by: John W. Linville
27 Feb, 2008
6 commits
-
To make sure the procfs visibility occurs after the ->proc_fs ops are
setup, use proc_net_fops_create() and proc_net_remove().This also fixes an OOPS after module unload in that the name string
for remove was wrong, so it wouldn't actually be removed. That bug
was introduced by commit 61145aa1a12401ac71bcc450a58c773dd6e2bfb9
("[KEY]: Clean up proc files creation a bit.")Signed-off-by: David S. Miller
-
It is used in connector.c only, so make it static.
Signed-off-by: Li Zefan
Signed-off-by: David S. Miller -
This bug did bite at least one user, who did have to resort to rebooting
the system after an "ifconfig eth0 127.0.0.1" typo.Deleting the address and adding a new is a less intrusive workaround.
But I still beleive this is a bug that should be fixed. Some way or
another.Another possibility would be to remove the scope mangling based on
address. This will always be incomplete (are 127/8 the only address
space with host scope requirements?)We set the scope to RT_SCOPE_HOST if an IPv4 interface is configured
with a loopback address (127/8). The scope is never reset, and will
remain set to RT_SCOPE_HOST after changing the address. This patch
resets the scope if the address is changed again, to restore normal
functionality.Signed-off-by: Bjorn Mork
Signed-off-by: David S. Miller -
Add some more missing initializations of the new nl_info.nl_net field
in IPv6 stack. This field will be used when network namespaces are
fully supported.Signed-off-by: Benjamin Thery
Signed-off-by: David S. Miller -
Since the macvlan release I had at least 5 users asking how to configure
it since the old userspace tool doesn't work with the version in the
kernel. Add a pointer to the Kconfig help.Signed-off-by: Patrick McHardy
Signed-off-by: David S. Miller -
Delete a possibly armed timer before kfree'ing the connection object.
Solves: http://lkml.org/lkml/2008/2/15/514
Reported-by:Quel Qun
Signed-off-by: Thomas Gleixner
Signed-off-by: David S. Miller
25 Feb, 2008
10 commits
-
net/tipc/cluster.c:145:2: warning: Using plain integer as NULL pointer
net/tipc/link.c:3254:36: warning: Using plain integer as NULL pointer
net/tipc/ref.c:151:15: warning: Using plain integer as NULL pointer
net/tipc/zone.c:85:2: warning: Using plain integer as NULL pointerSigned-off-by: Harvey Harrison
Signed-off-by: David S. Miller -
Add the Intel ICH10 SMBus Controller DeviceID's and updates
Tolapai support.Signed-off-by: Jason Gaston
Signed-off-by: Jean Delvare -
Don't require platform code to be #ifdeffed according to whether
I2C is enabled or not ... if it's not enabled, let GCC compile out
all I2C device declarations. (Issue noted on an NSLU2 build that
didn't configure I2C.)Signed-off-by: David Brownell
Signed-off-by: Jean Delvare -
When probing i2c-pca-isa writes to legacy ioports, which crashes the kernel
if there is no device at that port.
This patch adds a check_legacy_ioport call, so probe fails gracefully
and thus prevents the oops.Signed-off-by: Christian Krafft
Signed-off-by: Jean Delvare -
Commit 8b798c4d16b762d15f4055597ff8d87f73b35552 broke
alchemy build, fix it. Pointed out by Adrian Bunk.Signed-off-by: Manuel Lauss
Signed-off-by: Jean Delvare -
The C99 specification states in section 6.11.5:
The placement of a storage-class specifier other than at the
beginning of the declaration specifiers in a declaration is an
obsolescent feature.Signed-off-by: Tobias Klauser
Signed-off-by: Jean Delvare -
While working on the PCA9564-platform driver, I sometimes had a glimpse at the
pxa-driver. I found some suspicious places, and this patch contains my
suggestions. Note: They are not tested, due to no hardware.[JD: Some more fixes.]
Signed-off-by: Wolfram Sang
Signed-off-by: Jean Delvare
Tested-by: Mike Rapoport
Tested-by: Eric Miao -
Each call to i2c_get_adapter() must be followed by a call to
i2c_put_adapter() to release the grabbed reference. Otherwise the
reference count grows forever and the adapter can never be
unregistered.Signed-off-by: Jean Delvare
Acked-by: Vladimir Ananiev
Acked-by: Tony Lindgren
24 Feb, 2008
12 commits
-
* 'upstream-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev:
libata-core: fix kernel-doc warning
sata_fsl: fix build with ATA_VERBOSE_DEBUG
[libata] ahci: AMD SB700/SB800 SATA support 64bit DMA
libata-pmp: clear hob for pmp register accesses
libata: automatically use DMADIR if drive/bridge requires it
power_state: get rid of write-only variable in SATA
pata_atiixp: Use 255 sector limit -
Fix libata-core kernel-doc warning:
Warning(linux-2.6.25-rc2-git6//drivers/ata/libata-core.c:168): No description found for parameter 'ap'Signed-off-by: Randy Dunlap
Signed-off-by: Jeff Garzik -
This patch fixes build and few warnings when ATA_VERBOSE_DEBUG
is defined:CC drivers/ata/sata_fsl.o
drivers/ata/sata_fsl.c: In function ‘sata_fsl_fill_sg’:
drivers/ata/sata_fsl.c:338: warning: format ‘%x’ expects type ‘unsigned int’, but argument 3 has type ‘void *’
drivers/ata/sata_fsl.c:338: warning: format ‘%x’ expects type ‘unsigned int’, but argument 4 has type ‘struct prde *’
drivers/ata/sata_fsl.c: In function ‘sata_fsl_qc_issue’:
drivers/ata/sata_fsl.c:459: error: ‘csr_base’ undeclared (first use in this function)
drivers/ata/sata_fsl.c:459: error: (Each undeclared identifier is reported only once
drivers/ata/sata_fsl.c:459: error: for each function it appears in.)
drivers/ata/sata_fsl.c: In function ‘sata_fsl_freeze’:
drivers/ata/sata_fsl.c:525: error: ‘csr_base’ undeclared (first use in this function)
make[2]: *** [drivers/ata/sata_fsl.o] Error 1Signed-off-by: Anton Vorontsov
Signed-off-by: Jeff Garzik -
SB700 SATA controller can support 64 bit DMA, the previous commit
badc2341579511a247f5993865aa68379e283c5c was added with
careless reference to SB600, which should be modified by this patch.Signed-off-by: Shane Huang
Signed-off-by: Jeff Garzik -
>> Mark Lord wrote:
>>> Tejun, I've added PMP to sata_mv, and am now trying to get it
>>> to work with a Marvell PM attached.
>>>
>>> And the behaviour I see is very bizarre.
>>>
>>> After hard+soft resets, the PM signature is found,
>>> and libata interrogates the PM registers.
>>>
>>> It successfully reads register 0, and then register 1.
>>> But all subsequent registers read out (incorrectly) as zeros.
...This behavior has been confirmed by Marvell with a SATA analyzer.
The Marvell port-multiplier apparently likes to see clean HOB
information when accessing PMP registers.Since sata_mv uses PIO shadow register access, this doesn't happen
automatically, as it might in a more purely FIS-based driver (eg. ahci).One way to fix this is to flag these commands with ATA_TFLAG_LBA48,
forcing libata to write out the HOB fields with known (zero) values.Signed-off-by: Saeed Bishara
Acked-by: Mark Lord
Signed-off-by: Jeff Garzik -
Back in 2.6.17-rc2, a libata module parameter was added for atapi_dmadir.
That's nice, but most SATA devices which need it will tell us about it
in their IDENTIFY PACKET response, as bit-15 of word-62 of the
returned data (as per ATA7, ATA8 specifications).So for those which specify it, we should automatically use the DMADIR bit.
Otherwise, disc writing will fail by default on many SATA-ATAPI drives.This patch adds ATA_DFLAG_DMADIR and make ata_dev_configure() set it
if atapi_dmadir is set or identify data indicates DMADIR is necessary.
atapi_xlat() is converted to check ATA_DFLAG_DMADIR before setting
DMADIR.Original patch is from Mark Lord.
Signed-off-by: Tejun Heo
Cc: Mark Lord
Signed-off-by: Jeff Garzik -
power_state is scheduled for removal, and libata uses it in write-only
mode. Remove it.Signed-off-by: Pavel Machek
Signed-off-by: Jeff Garzik -
AHCI needs sorting too but this deals with the old interface
Signed-off-by: Alan Cox
Signed-off-by: Jeff Garzik -
Signed-off-by: Auke Kok
Signed-off-by: Jeff Garzik -
Fix some spelling errors and inconsistencies in comment blocks.
Signed-off-by: Auke Kok
Signed-off-by: Jeff Garzik -
this patch avoids a denial of service from an evildoer sending a
continuous stream of flow control at our adapter that is plugged
into a non-flow control enabled switch.Signed-off-by: Jesse Brandeburg
Signed-off-by: Auke Kok
Signed-off-by: Jeff Garzik -
Signed-off-by: Jesse Brandeburg
Signed-off-by: Auke Kok
Signed-off-by: Jeff Garzik
