02 Aug, 2005
16 commits
-
Improve the likelihood that someone submitting a patch will notify the
MAN-PAGES maintainer.This is a follow-up to comments on the July 29 lkml email thread: "Broke nice
range for RLIMIT NICE"Signed-off-by: Paul Jackson
Cc: "Michael Kerrisk"
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Michael maintains the kernel manpages. He wants us to tell him when we
change or augment the userspace API. Add his contact details to
MAINTAINERS.Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Peter Missel:
- Add support for the SVideo input on the GDI Black Gold.Mauro Carvalho Chehab:
- Linux/version.h removed. Replaced by linux/utsname.hMichael Krufky:
- Added analog support for DViCO FusionHDTV5 Gold.CC: Peter Missel
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Michael Krufky
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
- Fixed some bttv card numbers.
- BTTV and SAA7134 version numbers incremented to reflect changes.
- pci_dma_supported() is called after pci_set_dma_mask() which
already did check that for us. This patch removes the unneeded call to
pci_dma_supported() at bttv-driver.c- Ensure a sufficient I2C bus idle time between 2 messages for
saa7134-i2c.c- It is important to write at first to MO_GP3_IO for cx88-tvaudio.c
- Use try_to_freeze() instead of refrigerator at msp3400.c
- Recognizing the MFPE05-2 Tuner at tveeprom.c
- Add new parameter to help identify radio chipsets at tuner module:
show_i2c=1 will show 16 reading bytes from detected tuners.- BTTV does generate some Unimplemented IOCTL log at tuner module:
0x40046d11(dir=1,tp=0x6d,nr=17,sz=4) means that it is sending
MSP3400 calls to non-msp3400 tuners. Warning eliminated.
VIDIOSAUDIO is also called, so debug messages updated. It is still
requiring IOCTL implementation.- Added two more tuners.
- Add support for the SVideo input on the GDI Black Gold.
Signed-off-by: Peter Missel
Signed-off-by: Graham Bevan
Signed-off-by: Torsten Seeboth
Signed-off-by: Hartmut Hackmann
Signed-off-by: Tobias Klauser
Signed-off-by: Michael Krufky
Signed-off-by: Mauro Carvalho Chehab
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
We know that the randomisation slows down some workloads on Transmeta CPUs
by quite large amounts. We think it's because the CPU needs to recode the
same x86 instructions when they pop up at a different virtual address after
a fork+exec.So disable randomization by default on those CPUs.
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Make it compile with CONFIG_PM=n
Cc: "Rafael J. Wysocki"
Cc: Jeff Garzik
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Seems that both Greg and I submitted the same patch and it just kept on
applying...Cc: Greg KH
Cc: Kumar Gala
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
If there are devices that use interrupts over a suspend event, ACPI must
restore the PCI interrupt links on resume. Anything else breaks any
device that hasn't been converted to the new (dubious) PM rules.Drivers that need the irq free/re-aquire sequence can be done one by one
independently of this one. -
There's no real guarantee that handle_mm_fault() will always be able to
break a COW situation - if an update from another thread ends up
modifying the page table some way, handle_mm_fault() may end up
requiring us to re-try the operation.That's normally fine, but get_user_pages() ended up re-trying it as a
read, and thus a write access could in theory end up losing the dirty
bit or be done on a page that had not been properly COW'ed.This makes get_user_pages() always retry write accesses as write
accesses by making "follow_page()" require that a writable follow has
the dirty bit set. That simplifies the code and solves the race: if the
COW break fails for some reason, we'll just loop around and try again.Signed-off-by: Linus Torvalds
-
Reported by: Jochen Hein (Bugzilla Bug 4312)
When there is disk I/O happening, the framebuffer has a little snow on
the screen. Once I/O has finished, no garbage remains on screen.This bug was explained by: Knut Petersen
Most important is CRTC register 2f, signal quality is also improved for
higher vclk values by changing set_vclk() according to the X drivers and
cyblafb.cThe fix is to set the performance register (0x2f) with a more stable
value.Signed-off-by: Antonino Daplas
Signed-off-by: Linus Torvalds -
Reported by: Jochen Hein (Bugzilla Bug 4386)
booting leaves the end of long lines in the last line on screen when
scrolling. When X is running, scrolling puts garbage on the screen
(looks like X data) Console switch fixes the screen. Behaviour seems to
be identical with noaccel and without on the video=tridentfb parameter
in lilo.conf.This bug was explained by: Knut_Petersen
Acceleration is broken for all BLADE 3D chips for all versions of kernel
2.6 except for 32bit modes. Most important reason is that the u32 col
parameter of the graphics engine needs the color value replicated to all
u8 of the u32 (8bit modes) and to both u16 of the u32.Fix color value passed to graphics engine, verified by the reporter.
Signed-off-by: Antonino Daplas
Signed-off-by: Linus Torvalds -
This removes sys_set_zone_reclaim() for now. While i'm sure Martin is
trying to solve a real problem, we must not hard-code an incomplete and
insufficient approach into a syscall, because syscalls are pretty much
for eternity. I am quite strongly convinced that this syscall must not
hit v2.6.13 in its current form.Firstly, the syscall lacks basic syscall design: e.g. it allows the
global setting of VM policy for unprivileged users. (!) [ Imagine an
Oracle installation and a SAP installation on the same NUMA box fighting
over the 'optimal' setting for this flag. What will they do? Will they
try to set the flag to their own preferred value every second or so? ]Secondly, it was added based on a single datapoint from Martin:
http://marc.theaimsgroup.com/?l=linux-mm&m=111763597218177&w=2
where Martin characterizes the numbers the following way:
' Run-to-run variability for "make -j" is huge, so these numbers aren't
terribly useful except to see that with reclaim the benchmark still
finishes in a reasonable amount of time. 'in other words: the fundamental problem has likely not been solved, only
a tendential move into the right direction has been observed, and a
handful of numbers were picked out of a set of hugely variable results,
without showing the variability data. How much variance is there
run-to-run?I'd really suggest to first walk the walk and see what's needed to get
stable & predictable kernel compilation numbers on that NUMA box, before
adding random syscalls to tune a particular aspect of the VM ... which
approach might not even matter once the whole picture has been analyzed
and understood!The third, most important point is that the syscall exposes VM tuning
internals in a completely unstructured way. What sense does it make to
have a _GLOBAL_ per-node setting for 'should we go to another node for
reclaim'? If then it might make sense to do this per-app, via numalib or
so.The change is minimalistic in that it doesnt remove the syscall and the
underlying infrastructure changes, only the user-visible changes. We
could perhaps add a CAP_SYS_ADMIN-only sysctl for this hack, a'ka
/proc/sys/vm/swappiness, but even that looks quite counterproductive
when the generic approach is that we are trying to reduce the number of
external factors in the VM balance picture.Signed-off-by: Ingo Molnar
Signed-off-by: Linus Torvalds -
The ordering of setting and clearing device_add_pending went wrong on some
occasions, causing multifunction cards only to be handled correctly on the
first insertion, not on subsequent ones.Signed-off-by: Dominik Brodowski
Signed-off-by: Linus Torvalds -
Avoid registering PCMCIA CF cards before other IDE stuff. This means the risk
of /dev/hd* being re-ordered is lessened. The _sane_ thing to assert any
ordering is to use udev, nameif and so on, of course.Signed-off-by: Dominik Brodowski
Signed-off-by: Linus Torvalds -
When you rm a watch, an IN_IGNORED event is sent down the event queue
with the watch descriptor that you just rm'd.If you then add a watch you could get the ignored watch's wd and if you
haven't read the entire event queue, user space will think that it's
newly created watch was just ignored.To avoid this problem we just use idr_get_new_above instead of
idr_get_new.Signed-off-by: John McCutchan
Signed-off-by: Robert Love
Signed-off-by: Linus Torvalds -
When a file is moved over an existing file that you are watching,
inotify won't send you a DELETE_SELF event and it won't unref the inode
until the inotify instance is closed by the application.Signed-off-by: John McCutchan
Signed-off-by: Robert Love
Signed-off-by: Linus Torvalds
01 Aug, 2005
3 commits
-
This patch displays the name of the fbdev driver in sysfs.
Down the road this will replace the current proc handle we have.Signed-off-by: James Simmons
Signed-off-by: Linus Torvalds
31 Jul, 2005
21 commits
-
Drivers really only work well in SMP if they actually can be selected.
This is a leftover from the time when the 6pack drive only used to be
a bitrotten variant of the slip driver.Signed-off-by: Ralf Baechle DL5RB
Kconfig | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Signed-off-by: Jeff Garzik -
--ReaqsoxgOBHFXBhH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inlineHi Jeff,
Here's a little patch fixing a typo in smc91x.h.
Regards,
Tony
--ReaqsoxgOBHFXBhH
Content-Type: text/x-chdr; charset=us-ascii
Content-Disposition: inline; filename="patch-fix-typo-smc91x.h"
Signed-off-by: Jeff Garzik -
Yukon-Lite chipset needs workaround for revision 7 (or later).
Without this patch, chip gets stuck in low power mode and never
boots. Newer SysKonnect vendor code already had same patch.Related bug in skge is http://bugs.gentoo.org/87822
Chris, please add for 2.6.12.2
Signed-off-by: Stephen Hemminger
Signed-off-by: Jeff Garzik -
Contains general updates (additional configuration info, hopefully
better examples, updated some out of date info, and a bonus pass
through ispell to banish the "paramters.") and info specific to
gratuitous ARP and xmit policy functionality already in 2.6.13-rc2.Signed-off-by: Jay Vosburgh
Signed-off-by: Jeff Garzik -
SCSI=m must disallow static drivers.
The problem is that all the SATA drivers depend on SCSI_SATA.
With SCSI=m and SCSI_SATA=y this allows the static enabling of the SATA
drivers with unwanted effects, e.g.:
- SCSI=m, SCSI_SATA=y, SCSI_ATA_ADMA=y
-> SCSI_ATA_ADMA is built statically but scsi/built-in.o is not linked
into the kernel
- SCSI=m, SCSI_SATA=y, SCSI_ATA_ADMA=y, SCSI_SATA_AHCI=m
-> SCSI_ATA_ADMA and libata are built statically but
scsi/built-in.o is not linked into the kernel,
SCSI_SATA_AHCI is built modular (unresolved symbols due to missing
libata)Signed-off-by: Adrian Bunk
Cc: Jeff Garzik
Signed-off-by: Andrew Morton
Signed-off-by: Jeff Garzik -
Increase driver version to 0.8
Signed-off-by: Stephen Hemminger
Signed-off-by: Jeff Garzik -
Cleanup code that is used to toggle LED's. Since we
get called from ethtool, can use that thread rather than
setting up a timer.Signed-off-by: Stephen Hemminger
Signed-off-by: Jeff Garzik -
During autonegotiation set PHY interrupt mask to ignore
bogus speed change interrupts.Signed-off-by: Stephen Hemminger
Signed-off-by: Jeff Garzik -
The code to clear fifo errors was incorrect and sending garbage
to the external phy. Removed the no longer used inline's funcs.Signed-off-by: Stephen Hemminger
Signed-off-by: Jeff Garzik -
Minor whitespace cleanups.
Signed-off-by: Stephen Hemminger
Signed-off-by: Jeff Garzik -
The check for Yukon lite changes was restricting itself to
rev A3. It turns out that these changes are also true on A4
and later.Signed-off-by: Stephen Hemminger
Signed-off-by: Jeff Garzik -
Cleanup the phy_lock deadlock because of relocking in the nway_reset path.
Reported by Francois Romieu.Also, don't need to do irqsave/restore for blink,
just excluding bh is good enough.Signed-off-by: Stephen Hemminger
Signed-off-by: Jeff Garzik -
Here is a fix for a typo, thanks Eliot Dresselhaus.
Since transmitter not active when device is down, it wasn't really noticed.Signed-off-by: Stephen Hemminger
Signed-off-by: Jeff Garzik -
The SK-9E boards use the Marvell Yukon2 chipset which
is not supported by the skge driver. Thanks to Ralph Roesler
for noticing.Signed-off-by: Stephen Hemminger
Signed-off-by: Jeff Garzik -
Using Genesis board, I get harmless error reports. Rather than console
error, turn it into a error counter.Signed-off-by: Stephen Hemminger
Signed-off-by: Jeff Garzik -
The bug is evident when it is seen once. dst gc timer was backed off,
when gc queue is not empty. But this means that timer quickly backs off,
if at least one destination remains in use. Normally, the bug is invisible,
because adding new dst entry to queue cancels the backoff. But it shots
deadly with destination cache overflow when new destinations are not released
for long time f.e. after an interface goes down.The fix is to cancel backoff when something was released.
Signed-off-by: Denis Lunev
Signed-off-by: Alexey Kuznetsov
Signed-off-by: David S. Miller -
Tunnel modules used to obtain module refcount each time when
some tunnel was created, which meaned that tunnel could be unloaded
only after all the tunnels are deleted.Since killing old MOD_*_USE_COUNT macros this protection has gone.
It is possible to return it back as module_get/put, but it looks
more natural and practically useful to force destruction of all
the child tunnels on module unload.Signed-off-by: Alexey Kuznetsov
Signed-off-by: David S. Miller -
masq_index is used for cleanup in case the interface address changes
(such as a dialup ppp link with dynamic addreses). Without this patch,
slave connections are not evicted in such a case, since they don't inherit
masq_index.Signed-off-by: Harald Welte
Signed-off-by: David S. Miller -
Just simple spelling mistake fixes.
Signed-Off-By: Baruch Even
Signed-off-by: David S. Miller -
ACPI is wrong. Devices should not release their IRQ's on suspend and
re-aquire them on resume. ACPI should just re-init the IRQ controller
instead of breaking most drivers very subtly.Breakage reported by Hugh Dickins
Undo: d8c4b4195c7d664baf296818bf756775149232d3
Signed-off-by: Linus Torvalds
-
An early version of the sk98lin patch was merged via Len's tree. But there
were subsequent updates as a result of review from Jeff. THis fixes things
up.Signed-off-by: Rafael J. Wysocki
Cc: Jeff Garzik
Cc: "Brown, Len"
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
