An error occurred fetching the project authors.
- 19 Feb, 2003 1 commit
-
-
Christoph Hellwig authored
it's a noop in 2.5 now that the behvaiour of implicitly exporting all symbols is gone.
-
- 16 Feb, 2003 1 commit
-
-
David Woodhouse authored
In order to deal with the weird and wonderful ways of obtaining a uart clock which a lot of the high-speed hacks for 16550-based chips seem to have, we need to make uart_update_timeout() and uart_get_divisor() take the desired baud rate as their arguments, instead of termios or divisor as before. The main reason for the change to uart_get_divisor(), requiring a call to uart_get_baud_rate() before it, is so that the drivers actually _have_ the baud rate in order that they can pass it to uart_update_timeout().
-
- 08 Jan, 2003 1 commit
-
-
Russell King authored
-
- 06 Jan, 2003 1 commit
-
-
Russell King authored
set_termios matches the style used for the other methods. It should have been this from the start.
-
- 03 Jan, 2003 1 commit
-
-
Russell King authored
Several serial drivers want to obtain the numeric baud rate when configuring their serial ports. Currently, two methods are used to "work around" this inadequacy in the change_speed API: baud = tty_get_baud_rate(port->info->tty); baud = BAUD_BASE / (16 * quot); Passing the termios structure down means that we can use uart_get_baud_rate() instead. We can also ensure that the various termios flags for options we don't support are correctly set. Lastly, this also provides 8250.c with a clean method for supporting divisors that are greater than the baud_base.
-
- 02 Nov, 2002 3 commits
-
-
Russell King authored
The tty layer's tty_name requires formatting codes in driver->name for the devfs and non-devfs cases.
-
Russell King authored
-
Russell King authored
uart_event() only has one purpose, which is to wake up any pending writers via the line discipline. Rename it to reflect its real functionality, and drop EVT_WRITE_WAKEUP.
-
- 29 Jul, 2002 1 commit
-
-
Russell King authored
Al Viro pointed out there was a fair bit of redundancy here. We remove many include files from the serial layer, leaving those which are necessary for it to build. This has been posted to lkml, no one complained. This cset also combines a missing include of asm/io.h in 8250_pci.c (unfortunately I've lost the name of the reporter, sorry.)
-
- 27 Jul, 2002 2 commits
-
-
Russell King authored
After the last few days of debugging, we've ended up with the caller of the start_tx and stop_tx methods taking the per-port lock. This cset and the accompanying csets make the same change to some of the other methods for consistency reasons. Since these methods don't contain a lot of code, it is better that they have consistent locking rules. This cset fixes up the enable_ms method.
-
Russell King authored
After the last few days of debugging, we've ended up with the caller of the start_tx and stop_tx methods taking the per-port lock. This cset and the accompanying csets make the same change to some of the other methods for consistency reasons. Since these methods don't contain a lot of code, it is better that they have consistent locking rules. This cset fixes up the stop_rx method.
-
- 26 Jul, 2002 1 commit
-
-
Russell King authored
The old form of designated initializers are obsolete: we need to replace them with the ISO C forms before 2.6. Gcc has always supported both forms anyway. From Rusty's Trivial Patch - thanks.
-
- 23 Jul, 2002 2 commits
-
-
Russell King authored
-
Russell King authored
The original fix sent to Ingo for stop_tx didn't take account that the start_tx and stop_tx methods can be called from the device specific code under the port spinlock. Consequently, we move the spinlock to the callers of these methods. Documentation updated to reflect the change.
-
- 22 Jul, 2002 2 commits
-
-
Russell King authored
-
Russell King authored
-
- 21 Jul, 2002 1 commit
-
-
Russell King authored
The serial layer is restructured to allow less code duplication (and hence bug duplication) across various serial drivers. Since ARM adds six extra serial drivers, maintaining six copies of serial.c was not my idea of fun. Therefore, we've ended up with a core serial driver, which knows about the interactions with the tty layer, and low-level hardware drivers, which know all about the hardware. The interface between the two is described in "Documentation/serial/driver". This patch completely removes the old serial.c driver and its associated configuration options, as you requested at KS2002. We keep a certain amount of configuration compatibility with the per-architecture serial.h file for the moment; this *will* be killed in the next round of patches. The biggest user of this is x86, and since I don't have an x86 box to test this stuff on, I think the changes are best kept separate.
-