- 06 Jul, 2004 15 commits
-
-
Wen-chien Jesse Sung authored
hm, I had a brainfart here. The recent "fix" to snd_ctl_read() actually unfixed it. Revert that, and fix the real bug. Cc: Jaroslav Kysela <perex@suse.cz> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Jerzy Szczepkowski authored
There was a memory leak in epoll. The reference count (d_count) of the struct dentry of a new epoll-fd was set to TWO. (new_inode() assigned ONE, than ep_getfd() incremented it by dget()). There was only ONE reference to this dentry, so struct dentry and struct inode were never freed. Signed-off-by:
Davide Libenzi <davidel@xmailserver.org> Signed-off-by:
-
Rusty Russell authored
From: Alexey Dobriyan <adobriyan@mail.ru> drivers/char/upd4990a.c was removed from 2.6. Signed-off-by:
-
Gerd Knorr authored
From: Michael Geng <linux@MichaelGeng.de> The patch updates docs, comments + strings to also mention the SAA5281 chip (which is compatible to the SAA5246A) as supported. Signed-off-by:
Michael Geng <linux@MichaelGeng.de> Signed-off-by:
Gerd Knorr <kraxel@bytesex.org> Signed-off-by:
-
Mika Kukkonen authored
CHECK fs/smbfs/smbiod.c fs/smbfs/smbiod.c:68:25: warning: non-ANSI parameter list CHECK drivers/isdn/tpam/tpam_crcpc.c drivers/isdn/tpam/tpam_crcpc.c:57:15: warning: non-ANSI parameter list CHECK drivers/scsi/aic7xxx/aic79xx_reg_print.c drivers/scsi/aic7xxx/aic79xx_osm.h:791:19: warning: non-ANSI parameter list Signed-off-by:
-
Andi Kleen authored
Move the memory policy freeing to later in exit to make sure the last memory allocations don't use an uninitialized policy. Signed-off-by:
-
Antonino Daplas authored
This patch sets the correct capabilities flag for vesafb and vga16fb to provide fbcon with the correct hints as to the best scrolling mode. Signed-off-by:
Antonino Daplas <adaplas@pol.net> Signed-off-by:
-
Antonino Daplas authored
Added a new scrolling mode (SCROLL_PAN_REDRAW) to fbcon that should greatly benefit unaccelerated drivers such as VESA fbdev. An increase of 3-10 times in scrolling speed can be expected. Currently, fbcon has 4 different scrolling methods (1-4). Potentially, we can have 6. This patch implements SCROLL_PAN_REDRAW (5). SCROLL_WRAP_REDRAW (6) is still unimplemented. Scroll Mode Operation YPan YWrap +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1. SCROLL_ACCEL copyarea No No 2. SCROLL_REDRAW imageblit No No 3. SCROLL_PAN copyarea Yes No 4. SCROLL_WRAP copyarea No Yes 5. SCROLL_PAN_REDRAW imageblit Yes No 6. SCROLL_WRAP_REDRAW imageblit No Yes +++++++++++++++++++++++++++++++++++++++++++++++++++++ Note 1: I've changed the nomenclature to increase clarity: SCROLL_ACCEL = SCROLL_MOVE SCROLL_REDRAW = SCROLL_REDRAW SCROLL_PAN = SCROLL_PAN_MOVE SCROLL_WRAP = SCROLL_WRAP_MOVE To demonstrate the effect of each of the scrolling methods on an unaccelerated PCI/AGP-based driver (vesafb), I used a simple benchmark (time cat linux/MAINTAINERS - a 50K text file). The framebuffer is set at: 1024x768-8bpp, 8x16 font, yres_virtual = 2*yres 1. SCROLL_MOVE: real 5m50.277s user 0m0.001s sys 5m50.227s Almost 6 minutes for a 50K text file. Using soft copyarea on a PCI-based card is just too slow (because copyarea has to read from the framebuffer memory). 2. SCROLL_PAN_MOVE scrollmode: SCROLL_PAN real 0m8.592s user 0m0.000s sys 0m8.586s Using ypan with copyarea dramatically improves the scrolling. However, the scrolling action is jerky (fast during the panning stages, slows down during the copyarea stages). 3. SCROLL_REDRAW (this is the default scrolling mode) real 0m3.189s user 0m0.000s sys 0m3.170s Simply eliminating the copyarea, even without ypanning, makes it faster than SCROLL_PAN_MOvE. Plus, the scrolling action is smoother. So, if we combine YPanning with imageblit (PAN_REDRAW), we get this: 4. SCROLL_PAN_REDRAW real 0m0.520s user 0m0.000s sys 0m0.518s That's almost 6x faster than SCROLL_REDRAW. Increasing the amount of video RAM still increases the speed, but not very dramatically. Higher than 16 MB, the increase is negligible. Using an accelerated driver, we see almost the same effect but not as dramatically: 1. SCROLL_MOVE - accel real 0m3.112s user 0m0.000s sys 0m3.112s 2. SCROLL_REDRAW - accel real 0m2.604s user 0m0.000s sys 0m2.603s Redraw is still faster than move, but not much. 3. SCROLL_PAN_MOVE - accel real 0m0.203s user 0m0.000s sys 0m0.202s 4. SCROLL_PAN_REDRAW - accel real 0m0.326s user 0m0.002s sys 0m0.323s This is one exception. If panning is enabled, move is actually faster than redraw. As to why, I don't know. So based on the above, fbcon will choose the scrolling method based on the following preference: Ypan/Ywrap > accel imageblit > accel copyarea > soft imageblit > (soft copyarea) Note 2: Exception: accel copyarea > accel imageblit if Pan/Wrap is enabled. Note 3: soft copyarea will be avoided by fbcon as much as possible unless there is a specific override, ie., FBINFO_READS_FAST flag is set. If this flag is set, fbcon will prefer copyarea over imageblit, accel or soft. As a final note, in order for fbcon to use the best scrolling method, the low-level drivers must provide the correct hinting by setting the FBINFO_HWACCEL_* flags. To vesafb users: boot vesafb like this for fastest scrolling action: video=vesafb:ypan,vram:16 Signed-off-by:
-
Antonino Daplas authored
1. From Petr Vandrovec <vandrove@vc.cvut.cz>. Begin quote yesterday I finally found why 2.6.x has problems with taking over vgacon. Problem is that take_over_console does: if (IS_VISIBLE) save_screen(i); ... visual_init(i, 0); ... so code nicely saves screen contents, and calls visual_init, which calls fbcon's init, which in turn can issue vc_resize. And this vc_resize will trigger read from vc->vc_origin. But vc_origin still points to videomemory, not to the buffer where save_screen() copied its data. End quote So updating vc->vc_origin to point to screenbuf after the previous console deinitializes allows fbcon to correctly update the screen from the screen buffer. This change makes the clearing of vram (using fillrect) unnecessary. 2. If FBINFO_MISC_MODESWITCH flag is set in info, do the set_par() in fbcon_switch() instead of piggy-backing the set_par() on fbcon_resize(). This preserves the current var, skipping the unnecessary fb_find_mode() step. Signed-off-by: -
Antonino Daplas authored
Ugly workaround. When switching from KD_GRAPHICS to KD_TEXT, the event is captured at fbcon_blank() allowing fbcon to reinitialize the hardware. However, some hardware requires the reinitialization to be done immediately, others require it to be done later. Others may need it to be done immediately and later, this is the worst case. Signed-off-by:
-
Martin Schwidefsky authored
From: Ursula Braun-Krahl <braunu@de.ibm.com> From: Heiko Carstens <heiko.carstens@de.ibm.com> From: Gerald Schaefer <geraldsc@de.ibm.com> From: Martin Schwidefsky <schwidefsky@de.ibm.com> Add s390 architecture support for cpu hotplug. Signed-off-by:
Martin Schwidefsky <schwidefsky@de.ibm.com> Signed-off-by:
-
Martin Schwidefsky authored
This patch introduces a notifier chain for cpu idle. There are two events CPU_IDLE and CPU_NOT_IDLE that are called just before the cpu goes to sleep and right after the cpu woke up again. The notifier is used to simplify the no-hz-timer-in-idle feature and the virtual cpu timers. In addition the virtual cpu timer functions have been moved to arch/s390/kernel/vtime.c, which gives a nice separation between the timer functions related to real time and the timer functions related to virtual cpu time. Signed-off-by:
-
Martin Schwidefsky authored
From: Peter Tiedemann <ptiedem@de.ibm.com> ctc driver changes: - Make use of the debug feature to ease debugging. - ctctty: use dev_alloc_name to allocate a network device name. - ctctty: avoid deadlock of ctc_tty_close vs ctc_tty_flush_buffer. Signed-off-by:
-
Martin Schwidefsky authored
From: Arnd Bergmann <arndb@de.ibm.com> Common i/o layer changes: - Reorder checking and setting of the ccw device id. Signed-off-by:
-
Martin Schwidefsky authored
From: Horst Hummel <horst.hummel@de.ibm.com> dasd device driver changes: - Set and check the retry counter in start_IO for all requests. Signed-off-by:
-
- 05 Jul, 2004 20 commits
-
-
Herbert Xu authored
This way we will not forget to update XFRM_MSG_MAX in the future. Signed-off-by:
Herbert Xu <herbert@gondor.apana.org.au> Signed-off-by:
David S. Miller <davem@redhat.com>
-
Hideaki Yoshifuji authored
Save space for 'dst underflow' message. Signed-off-by:
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org> Signed-off-by:
-
Hideaki Yoshifuji authored
D: [TCP] Diet using unknown
-
Hideaki Yoshifuji authored
Because RTF_LOCAL is for local unicast address, it was wrong to set RTF_LOCAL to ndisc dst. This patch also adds some comment on other fields. Signed-off-by:
-
Petr Vandrovec authored
-
http://linux-mh.bkbits.net/bluetooth-2.6David S. Miller authored
into nuts.davemloft.net:/disk1/BK/net-2.6
-
Hideaki Yoshifuji authored
IPv6 was not configured appropriately without lo. Noticed by / tested by Russell King <rmk+lkml@arm.linux.org.uk>. Signed-off-by:
-
Herbert Xu authored
This is another step towards the union of the tunnel mode encapsulation between transforms. As there are significant differences between the tunnel encapsulation of IPv4 and IPv6, I'll be dealing with IPv4 only for now. This particular patch rearranges the code in ah_output to isolate the tunnel mode encapsulation. Signed-off-by:
-
Andrew Morton authored
Fix deadlock identified by the Stanford locking checker. Signed-off-by:
-
Andrew Morton authored
Fix deadlock identified by the Stanford locking checker. Signed-off-by:
-
Andrew Morton authored
Fix deadlock identified by the Stanford locking checker. Signed-off-by:
-
Andrew Morton authored
Fix deadlock in rose_del_loopback_node(). Found by the Stanford locking checker. Signed-off-by:
-
Herbert Xu authored
-
Stephen Hemminger authored
It is useful for testing to allow larger MTU value to be set on the dummy network device. The current code limits it to valid Ether mtu's. Signed-off-by:
Stephen Hemminger <shemminger@osdl.org> Signed-off-by:
-
Herbert Xu authored
This patch makes netlink_connect() return the value of err instead of 0. It doesn't actually make any difference since the current implementation of netlink_autobind() never fails. But since we went to all this trouble to check the return status of autobind, might as well return the correct value :) Signed-off-by:
-
Herbert Xu authored
-
Jaap Keuter authored
While getting hands-on with netkit (www.netkit.org), a networking simulation environment based on UML, it struck me that ifconfig wasn't capable of calculating the proper broadcast address for a subnetted interface. Some browsing through newsgroups and on the Debian package site (nettools), showed that this leads to misconfigured interfaces and a couple of bugreports on ifconfig. Digging a bit deeper revealed that it actually is an issue with SIOIFNETMASK. Once you bring up an interface with SIOIFADDR, a classfull netmask and broadcast address is set (if applicable for the type of interface), in order to get a properly configured interface. But if you subnet the network using SIOIFNETMASK no proper broadcast address is set. So you always have to calculate it yourself, obviously leading to configuration errors. This patch takes care of this. First of all it doesn't change existing functionality, eg. a command like 'ifconfig eth0 192.168.1.1 netmask 255.255.255.240 broadcast 192.168.1.0' still works. But if you omit the broadcast address, a proper 'all ones' broadcast address for the subnet is set. 'ifconfig eth0 192.168.1.1 netmask 255.255.255.240' gives you 'eth0 inet addr:192.168.1.1 Bcast:192.168.1.15 Mask:255.255.255.240' and this should solve some real life problems. Signed-off-by:
Jaap Keuter <jaap.keuter@xs4all.nl> Signed-off-by:
-
David S. Miller authored
-
Jamal Hadi Salim authored
-
-
- 06 Jul, 2004 3 commits
-
-
Dave Airlie authored
-
Dave Airlie authored
-
Dave Airlie authored
-
- 05 Jul, 2004 2 commits
-
-
Andrew Morton authored
drivers/video/kyro/fbdev.c: In function `kyrofb_probe': drivers/video/kyro/fbdev.c:736: warning: passing arg 1 of `memset' makes pointer from integer without a cast Signed-off-by:
-
Adrian Bunk authored
allowdma0 is gone in 2.6, the patch below removes the mentionings of this option in the documentation. Signed-off-by:
-
