29 Apr, 2007
10 commits
-
the Sony Programmable I/O Control driver uses a semaphore as
mutex. use the mutex API instead of the (binary) semaphoreSigned-off-by: Matthias Kaehlcke
Acked-by: Mattia Dongili
Signed-off-by: Len Brown -
Avoid giving the user the possibility to shoot his own foot and let
the meye driver enable/disable the camera wisely (PCI_ID based).Signed-off-by: Mattia Dongili
Signed-off-by: Len Brown -
Change sonypi_camera_command() calls to sony_pic_camera_command() and use
the renamed macros.Signed-off-by: Mattia Dongili
Signed-off-by: Len Brown -
Copy and rename (for easier co-existence) the MEYE-wise exported interface.
Signed-off-by: Mattia Dongili
Signed-off-by: Len Brown -
Add the exported sony_pic_camera_command() function to make the MEYE
driver happy.Signed-off-by: Mattia Dongili
Signed-off-by: Len Brown -
Get the IO resources list in sony-laptop in the same order as listed
in sonypi and make sonypi check if one of those is already busy.
The sonypi check can be disabled by a module parameter in case the user
thinks we are plainly wrong (check_ioport=0).Signed-off-by: Mattia Dongili
Signed-off-by: Len Brown -
Try to migrate sonypi users to sony-laptop gracefully.
Signed-off-by: Mattia Dongili
Signed-off-by: Len Brown -
Some SZ Vaios have a gsm built-in modem. Allow powering on/off this device.
Thanks to Joshua Wise for the base code.Signed-off-by: Mattia Dongili
Signed-off-by: Len Brown -
Better avoid having ioport commands mixing and global variables reading/writing.
Signed-off-by: Mattia Dongili
Signed-off-by: Len Brown -
Use a parameter to enable/disable motion eye camera (for C1VE/C1VN models)
controls and avoid entering an infinite loop if the camera is not present
and the HW doesn't answer as we expect on io commands.Signed-off-by: Mattia Dongili
Signed-off-by: Len Brown
11 Apr, 2007
9 commits
-
Compatibility code to allow old sonypi bound userspace apps to still work.
Signed-off-by: Mattia Dongili
Signed-off-by: Len Brown -
Signed-off-by: Mattia Dongili
Signed-off-by: Len Brown -
Unify printks to resemble a unique driver.
Signed-off-by: Mattia Dongili
Signed-off-by: Len Brown -
Register additional platform attributes coming from the SPIC (sonypi) driver.
Signed-off-by: Mattia Dongili
Signed-off-by: Len Brown -
SNC and SPIC events are forwarded to the same input devices
and are thus handled together.Signed-off-by: Mattia Dongili
Signed-off-by: Len Brown -
Reimplement sonypi using ACPI only functions.
Signed-off-by: Mattia Dongili
Signed-off-by: Len Brown -
Signed-off-by: Mattia Dongili
Signed-off-by: Len Brown -
Both the SNC and SPIC device drivers will create attributes and thus
there's the need to have an internal usage count to avoid
re-registering or de-registering at the wrong time.Signed-off-by: Mattia Dongili
Signed-off-by: Len Brown -
Signed-off-by: Mattia Dongili
Signed-off-by: Len Brown
10 Apr, 2007
1 commit
-
* 'for-2.6.21' of master.kernel.org:/pub/scm/linux/kernel/git/davej/agpgart:
[AGPGART] intel_agp: PCI id update for Intel 965GM
09 Apr, 2007
6 commits
-
WARNING: arch/i386/kernel/built-in.o - Section mismatch: reference to .init.text:irqbalance_disable from .text between 'quirk_intel_irqbalance' (at offset 0x80a5) and 'i8237A_suspend'
Cc: Andi Kleen
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
WARNING: arch/x86_64/kernel/built-in.o - Section mismatch: reference to .init.text:nvidia_bugs from .data between 'early_qrk' (at offset 0x8428) and 'enable_cpu_hotplug'
WARNING: arch/x86_64/kernel/built-in.o - Section mismatch: reference to .init.text:via_bugs from .data between 'early_qrk' (at offset 0x8438) and 'enable_cpu_hotplug'
WARNING: arch/x86_64/kernel/built-in.o - Section mismatch: reference to .init.text:ati_bugs from .data between 'early_qrk' (at offset 0x8448) and 'enable_cpu_hotplug'The compiler is putting it into .data because the __initdata is in the wrong
place.Cc: Andi Kleen
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Convert omap_cf into a platform_driver ... this resolves oopsing during
suspend/resume.Evidently folk haven't tried suspend/resume on an OSK (the main platform
for this driver) since September or so, which is when platform_device
learned about suspend_late()/resume_early() and stopped being able to
suspend/resume without a platform_driver.Signed-off-by: David Brownell
Cc: Dominik Brodowski
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Since lazy MMU batching mode still allows interrupts to enter, it is
possible for interrupt handlers to try to use kmap_atomic, which fails when
lazy mode is active, since the PTE update to highmem will be delayed. The
best workaround is to issue an explicit flush in kmap_atomic_functions
case; this is the only way nested PTE updates can happen in the interrupt
handler.Thanks to Jeremy Fitzhardinge for noting the bug and suggestions on a fix.
This patch gets reverted again when we start 2.6.22 and the bug gets fixed
differently.Signed-off-by: Zachary Amsden
Cc: Andi Kleen
Cc: Jeremy Fitzhardinge
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
If rootmode isn't valid, we hit the BUG() in fuse_init_inode. Now
EINVAL is returned.Signed-off-by: Timo Savola
Signed-off-by: Miklos Szeredi
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Update PCI id info for Intel 965GM chipset.
Signed-off-by: Wang Zhenyu
Signed-off-by: Dave Jones
08 Apr, 2007
4 commits
-
Getting rid of the p->children printout in show_task() left behind an
unused variable.Signed-off-by: Linus Torvalds
-
the p->parent PID printout gives us all the information about the
task tree that we need - the eldest_child()/older_sibling()/
younger_sibling() printouts are mostly historic and i do not
remember ever having used those fields. (IMO in fact they confuse
the SysRq-T output.) So remove them.This code has sentimental value though, those fields and
printouts are one of the oldest ones still surviving from
Linux v0.95's kernel/sched.c:if (p->p_ysptr || p->p_osptr)
printk(" Younger sib=%d, older sib=%d\n\r",
p->p_ysptr ? p->p_ysptr->pid : -1,
p->p_osptr ? p->p_osptr->pid : -1);
else
printk("\n\r");written 15 years ago, in early 1992.
Signed-off-by: Ingo Molnar
Signed-off-by: Linus 'snif' Torvalds -
devres should be deallocated with devres_free() not kfree(). This bug
corrupts slab on IRQ request failure. Fix it.Signed-off-by: Tejun Heo
Cc: Andrew Morton
Cc: Greg KH
Signed-off-by: Linus Torvalds -
Soeren Sonnenburg reported that upon resume he is getting
this backtrace:[] smp_apic_timer_interrupt+0x57/0x90
[] retrigger_next_event+0x0/0xb0
[] apic_timer_interrupt+0x28/0x30
[] retrigger_next_event+0x0/0xb0
[] __kfifo_put+0x8/0x90
[] on_each_cpu+0x35/0x60
[] clock_was_set+0x18/0x20
[] timekeeping_resume+0x7c/0xa0
[] __sysdev_resume+0x11/0x80
[] sysdev_resume+0x47/0x80
[] device_power_up+0x5/0x10it turns out that on resume we mistakenly re-enable interrupts too
early. Do the timer retrigger only on the current CPU.Signed-off-by: Ingo Molnar
Acked-by: Thomas Gleixner
Acked-by: Soeren Sonnenburg
Signed-off-by: Linus Torvalds
07 Apr, 2007
3 commits
-
* master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6:
[TG3]: Fix crash during tg3_init_one().
[IPV6]: Revert recent change to rt6_check_dev().
[XFRM]: beet: fix IP option decapsulation
[XFRM]: beet: fix beet mode decapsulation
[XFRM]: beet: use IPOPT_NOP for option padding
[XFRM]: beet: fix IP option encapsulation -
The driver will crash when the chip has been initialized by EFI before
tg3_init_one(). In this case, the driver will call tg3_chip_reset()
before allocating consistent memory.The bug is fixed by checking for tp->hw_status before accessing it
during tg3_chip_reset().Signed-off-by: Michael Chan
Signed-off-by: David S. Miller -
This reverts a0d78ebf3a0e33a1aeacf2fc518ad9273d6a1c2f
It causes pings to link-local addresses to fail.
Signed-off-by: David S. Miller
06 Apr, 2007
5 commits
-
.. perfect? Ahh, sure.
Signed-off-by: Linus Torvalds
-
Beet mode looks for the beet pseudo header after the outer IP header,
which is wrong since that is followed by the ESP header. Additionally
it needs to adjust the packet length after removing the pseudo header
and point the data pointer to the real data location.Signed-off-by: Patrick McHardy
Signed-off-by: David S. Miller -
Beet mode decapsulation fails to properly set up the skb pointers, which
only works by accident in combination with CONFIG_NETFILTER, since in that
case the skb is fixed up in xfrm4_input before passing it to the netfilter
hooks.Signed-off-by: Patrick McHardy
Signed-off-by: David S. Miller -
draft-nikander-esp-beet-mode-07.txt states "The padding MUST be filled
with NOP options as defined in Internet Protocol [1] section 3.1
Internet header format.", so do that.Signed-off-by: Patrick McHardy
Signed-off-by: David S. Miller -
Beet mode calculates an incorrect value for the transport header location
when IP options are present, resulting in encapsulation errors.The correct location is 4 or 8 bytes before the end of the original IP
header, depending on whether the pseudo header is padded.Signed-off-by: Patrick McHardy
Signed-off-by: David S. Miller
05 Apr, 2007
2 commits
-
Up until this point we've accepted replay window settings greater than
32 but our bit mask can only accomodate 32 packets. Thus any packet
with a sequence number within the window but outside the bit mask would
be accepted.This patch causes those packets to be rejected instead.
Signed-off-by: Herbert Xu
Signed-off-by: David S. Miller -
Incoming trancated packets are counted as not only InTruncatedPkts but
also InHdrErrors. They should be counted as InTruncatedPkts only.Signed-off-by: Mitsuru Chinen
Acked-by: YOSHIFUJI Hideaki
Signed-off-by: David S. Miller