- 15 Jun, 2005 1 commit
-
-
Ladislav Michl authored
Small voiceblue update Signed-off-by:
Ladislav Michl <MICHL@2n.cz> Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
- 13 Jun, 2005 4 commits
-
-
Tony Lindgren authored
Looks like 16xx OHCI still needs USB_HOST_HHC_UHOST_EN although some documentation claims that it does not. Commented out reset of MOD_CONF_CTRL_0 until a proper fix is done.
-
Tony Lindgren authored
It's CLOCK_IN_OMAP730, not CLOCK_IN_OMAP_730
-
Martin Fouts authored
Attached is a patch that will prevent a kernel OOPS if Omap NAND support is enabled on the 730. Signed-off-by:
Martin Fouts <Martin.Fouts@palmsource.com> Signed-off-by:
-
Tony Lindgren authored
Serial wake depends on mux
-
- 10 Jun, 2005 2 commits
-
-
Tony Lindgren authored
Added omap_searly_clk_reset() that gets called before clocks are initialized. Another round of bootloader clock resets is still done after module inits are done.
-
Tony Lindgren authored
By muxing serial RX lines into GPIO interrupts it's possible to wake-up from deep sleep from serial port. This is protected by Kconfig option CONFIG_OMAP_SERIAL_WAKE until we have dev specific wake-up events that can be configured via sysfs.
-
- 09 Jun, 2005 5 commits
-
-
Tony Lindgren authored
CONFIG_OMAP_RESET_CLOCKS would not reset UART2 clock on boards with just one serial port.
-
Tony Lindgren authored
Check for SRAM null pointer
-
David Brownell authored
Minor fixes -- doc, and "rmmod" if anyone used this as a module! Signed-off-by:
David Brownell <david-b@pacbell.net> Signed-off-by:
-
David Brownell authored
Make the default OSK config more current: - Ran through "make oldconfig" - Turn off unused clocks - Use 32 KHz timer and NO_IDLE_HZ - Use normal writeback cache (not writethrough) - Reenable NOR flash - Enable CF stack, and (modular) IDE + VFAT stack over it - Serio? none of that on this board, disable it! - Enable NFS root by default. I left Audio, DSP and USB host support disabled for now, though arguably they should all be turned on too. Ditto other stuff. CF is turned on since it seems too easy for folk to miss something important there (can you say non-intuitive?), and NFSroot since it's likewise easy to miss (and simpler to set up than an initrd). Signed-off-by:
-
David Brownell authored
Hmm, someone cleaned up the LED stuff so it misbehaves on OSK. More than just H2 and Perseus have LEDs ... if there are boards that do NOT support both LEDs, those should get manual overrides. Signed-off-by:
-
- 06 Jun, 2005 5 commits
-
-
Tony Lindgren authored
-
Tony Lindgren authored
-
David Brownell authored
Get rid of a build warning, and move a funtion into the init section. Signed-off-by:
David Brownell <dbrownell@users.sourceforge.net> Signed-off-by:
-
Tony Lindgren authored
-
Linus Torvalds authored
Getting ready for the real release..
-
- 05 Jun, 2005 6 commits
-
-
Yoichi Yuasa authored
- Changed the return value of unknown type to NULL. - Deleted the NULL check of dev_id in siu_interrupt(). - Deleted the NULL check of port->membase in siu_shutdown(). - Added the NULL check of port->membase to siu_startup(). - Removed early_uart_ops. Now using vr41xx_siu standerd one. - Changed KSEG1ADDR() in siu_console_setup() to ioremap(). - When uart_add_one_port() failed, changed to set NULL to port->dev. Signed-off-by:
Yoichi Yuasa <yuasa@hh.iij4u.or.jp> Cc: Russell King <rmk@arm.linux.org.uk> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Gerald Schaefer authored
The system might hang when using appldata_mem with high I/O traffic and a large number of devices. The spinlocks bdev_lock and swaplock are acquired via calls to si_meminfo() and si_swapinfo() from a tasklet, i.e. interrupt context, which can lead to a deadlock. Replace tasklet with work queue. Signed-off-by:
Martin Schwidefsky <schwidefsky@de.ibm.com> Signed-off-by:
-
Martin Schwidefsky authored
The condition for no context in do_exception checks for hard and soft interrupts by using in_interrupt() but not for preemption. This is bad for the users of __copy_from/to_user_inatomic because the fault handler might call schedule although the preemption count is != 0. Use in_atomic() instead in_interrupt(). Signed-off-by:
-
Bodo Stroesser authored
To make UML build and run on s390, I needed to do these two little changes: 1) UML includes some of the subarch's (s390) headers. I had to change one of them with the following one-liner, to make this compile. AFAICS, this change doesn't break compilation of s390 itself. 2) UML needs to intercept syscalls via ptrace to invalidate the syscall, read syscall's parameters and write the result with the result of UML's syscall processing. Also, UML needs to make sure, that the host does no syscall restart processing. On i386 for example, this can be done by writing -1 to orig_eax on the 2nd syscall interception (orig_eax is the syscall number, which after the interception is used as a "interrupt was a syscall" flag only. Unfortunately, s390 holds syscall number and syscall result in gpr2 and its "interrupt was a syscall" flag (trap) is unreachable via ptrace. So I changed the host to set trap to -1, if the syscall number is changed to an invalid value on the first syscall interception. Signed-off-by:
-
Martin Schwidefsky authored
The special cases of peek and poke on acrs[15] and the fpc register are not handled correctly. A poke on acrs[15] will clobber the 4 bytes after the access registers in the thread_info structure. That happens to be the kernel stack pointer. A poke on the fpc with an invalid value is not caught by the validity check. On the next context switch the broken fpc value will cause a program check in the kernel. Improving the checks in peek and poke fixes this. Signed-off-by:
-
Qu Fuping authored
When fsync() runs wait_on_page_writeback_range() it only inspects pages which are actually under I/O (PAGECACHE_TAG_WRITEBACK). If a page completed I/O prior to wait_on_page_writeback_range() looking at it, it is supposed to have recorded its I/O error state in the address_space. But mpage_mpage_end_io_write() forgot to set the address_space error flag in this case. Signed-off-by:
Qu Fuping <fs@ercist.iscas.ac.cn> Signed-off-by:
-
- 04 Jun, 2005 2 commits
-
-
- 03 Jun, 2005 15 commits
-
-
Nathan Lynch authored
A typo in prom_find_machine_type from Ben's recent patch "ppc64: Fix result code handling in prom_init" prevents pSeries LPAR systems from booting. Tested on a pSeries 570 and OpenPower 720 (both Power5 LPAR). Signed-off-by:
Nathan Lynch <ntl@pobox.com> Signed-off-by:
-
-
Greg Ungerer authored
Re-work the m68knommu specific idle code according to suggestions from Nick Piggin <nickpiggin@yahoo.com.au>. A couple of rules that we need to follow: 1. Preempt should now disabled over idle routines. Should only be enabled to call schedule() then disabled again. 3. When cpu_idle finds (need_resched() == 'true'), it should call schedule(). It should not call schedule() otherwise. Also fix interrupt locking around the need_resched() and cpu stop state so that there is no race condition. Signed-off-by:
Greg Ungerer <gerg@snapgear.com> Signed-off-by:
-
David Brownell authored
This "obvious" one-liner is needed to recognize Zaurus SL 6000; it just checks two GUIDs not just one. OSDL bugids #4512 and #4545 seem to be duplicates of this report. From: Gerald Skerbitz <gsker@tcfreenet.org> Signed-off-by:
-
Nathan Lynch authored
With CONFIG_DEBUG_SLAB=y I see slab corruption messages during boot on pSeries machines with IPR adapters with any 2.6.12-rc kernel. The change which seems to have introduced the problem is "SCSI: revamp target scanning routines" and may be found at: http://marc.theaimsgroup.com/?l=bk-commits-head&m=111093946426333&w=2 In order to revert that in a 2.6.12-rc1 tree, I had to revert "target code updates to support scanned targets" first: http://marc.theaimsgroup.com/?l=bk-commits-head&m=111094132524649&w=2 With both patches reverted, the corruption messages go away. ipr: IBM Power RAID SCSI Device Driver version: 2.0.13 (February 21, 2005) ipr 0001:d0:01.0: Found IOA with IRQ: 167 ipr 0001:d0:01.0: Starting IOA initialization sequence. ipr 0001:d0:01.0: Adapter firmware version: 020A005C ipr 0001:d0:01.0: IOA initialized. scsi0 : IBM 570B Storage Adapter Vendor: IBM Model: VSBPD4E1 U4SCSI Rev: 4770 Type: Enclosure ANSI SCSI revision: 02 Vendor: IBM H0 Model: HUS103036FL3800 Rev: RPQF Type: Direct-Access ANSI SCSI revision: 04 Vendor: IBM H0 Model: HUS103036FL3800 Rev: RPQF Type: Direct-Access ANSI SCSI revision: 04 Vendor: IBM H0 Model: HUS103036FL3800 Rev: RPQF Type: Direct-Access ANSI SCSI revision: 04 Vendor: IBM H0 Model: HUS103036FL3800 Rev: RPQF Type: Direct-Access ANSI SCSI revision: 04 Vendor: IBM Model: VSBPD4E1 U4SCSI Rev: 4770 Type: Enclosure ANSI SCSI revision: 02 Slab corruption: start=c0000001e8de5268, len=512 Redzone: 0x5a2cf071/0x5a2cf071. Last user: [<c00000000029c3a0>](.scsi_target_dev_release+0x28/0x50) 080: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6a Prev obj: start=c0000001e8de5050, len=512 Redzone: 0x5a2cf071/0x5a2cf071. Last user: [<0000000000000000>](0x0) 000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b Next obj: start=c0000001e8de5480, len=512 Redzone: 0x170fc2a5/0x170fc2a5. Last user: [<c000000000228d7c>](.as_init_queue+0x5c/0x228) 000: c0 00 00 01 e8 83 26 08 00 00 00 00 00 00 00 00 010: 00 00 00 00 00 00 00 00 c0 00 00 01 e8 de 54 98 Slab corruption: start=c0000001e8de5268, len=512 Redzone: 0x5a2cf071/0x5a2cf071. Last user: [<c00000000029c3a0>](.scsi_target_dev_release+0x28/0x50) 080: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6a Prev obj: start=c0000001e8de5050, len=512 Redzone: 0x5a2cf071/0x5a2cf071. Last user: [<0000000000000000>](0x0) 000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b Next obj: start=c0000001e8de5480, len=512 Redzone: 0x170fc2a5/0x170fc2a5. Last user: [<c000000000228d7c>](.as_init_queue+0x5c/0x228) 000: c0 00 00 01 e8 83 26 08 00 00 00 00 00 00 00 00 010: 00 00 00 00 00 00 00 00 c0 00 00 01 e8 de 54 98 ... I did some digging and the problem seems to be a refcounting issue in __scsi_add_device. The target gets freed in scsi_target_reap, and then __scsi_add_device tries to do another device_put on it. Signed-off-by:
James Bottomley <James.Bottomley@SteelEye.com>
-
Andrew Vasquez authored
Correct incorrect locking order in qla2xxx_eh_abort() handler which would case a hang during certain code-paths. With extra pieces to fix the irq state in the locks. Signed-off-by:
Andrew Vasquez <andrew.vasquez@qlogic.com> Signed-off-by:
-
Craig Shelley authored
Added support to get/set flow control line levels using TIOCMGET and TIOCMSET. Added support for RTSCTS hardware flow control. cp2101_get_config and cp2101_set_config modified to support long request strings, required for configuring flow control. Signed-off-by: Craig Shelley craig@microtron.org.uk Signed-off-by:Greg Kroah-Hartman <gregkh@suse.de>
-
Roman Kagan authored
On Wed, May 04, 2005 at 01:37:30PM -0700, David Brownell wrote: > On Wednesday 04 May 2005 12:19 pm, Roman Kagan wrote: > > struct urb { > > /* private, usb core and host controller only fields in the urb */ > > ... > > struct list_head urb_list; /* list pointer to all active urbs */ > > ... > > }; > > > > Is it safe to use it for driver's purposes when the driver owns the urb, > > that is, starting from the completion routine until the urb is submitted > > with usb_submit_urb()? > > Right now, it should be. Great! FWIW I've briefly tested a modified version of usbatm using the list head in struct urb instead of creating a wrapper struct, and I haven't seen any failures yet. So I tend to believe that your "should be" actually means "is" :) > > If it is, can it be guaranteed in future, e.g. > > by moving the list head into the public section of struct urb? > > In fact I'm not sure why it ever got called "private" to usbcore/hcds. > I thought the idea was that it should be like urb->status, reserved for > whoever controls the URB. OK then how about the following (essentially documentation) patch? Signed-off-by:Roman Kagan <rkagan@mail.ru> Acked-by:
-
Phil Dibowitz authored
The original entry of this patch was submitted by Filippo Bardelli <filibard@libero.it>, with cleanups and patch-ification by me. This corrects the subclass that the device reports. Signed-off-by:
Phil Dibowitz <phil@ipom.com> Signed-off-by:
-
Paulo Marques authored
This patch makes the code to provide modalias in sysfs for usb devices 56 bytes smaller in i386, while making it clear that the first part of the modalias string is the same no matter what the device class is. Signed-Off-By:
Paulo Marques <pmarques@grupopie.com> Signed-off-by:
-
Matthias Urlichs authored
This patch adds a new driver for "Option" cards. This is a GSM data card, controlled by three "serial ports" which are connected via an OHCI adapter, all located on an oversized PC-Card. It's sold by several GSM service providers. Traditionally, this card has been accessed via the standard serial driver and appropriate vendor= and product= options. However, testing has revealed several problems with this approach, including hung data transfers and lost data blocks when receiving. Therefore, I've written a separate driver. Signed-off-by:
Matthias Urlichs <smurf@smurf.noris.de> Signed-off-by:
-
Greg Kroah-Hartman authored
They aren't really HID devices. Damm microsoft HID driver, that thing has caused more companies to have to do this kind of hack... Signed-off-by: -
Lonnie Mendez authored
This patch adds the DeLorme Earthmate lt-20 productid to the hid blacklist table. This patch ensures the lt-20 can be claimed by the appropriate driver (cypress_m8). Adds the product id 0x200, of the DeLorme Earthmate lt-20, to the hid blacklist table. Signed-off-by:
Lonnie Mendez <lmendez19@austin.rr.com> Signed-off-by:
-
Ping Cheng authored
- add Intuos3 and Cintiq 21UX Signed-off-by:
Ping Cheng <pingc@wacom.com> Signed-off-by:
-
Adrian Bunk authored
This patch removes the outdated ChangeLog file for this driver. Signed-off-by:
Adrian Bunk <bunk@stusta.de> Signed-off-by:
-
