- 11 Sep, 2003 29 commits
-
-
Chas Williams authored
-
Chas Williams authored
- introduction of the struct array 'atm_proc_ents': - removal of code duplication in atm_proc_cleanup(); - removal of code duplication in atm_proc_init(); - removal of the macros CREATE_SEQ_ENTRY() and CREATE_ENTRY(); - /proc/net/atm/vcc returns to /proc/net/atm/vc; - credits at the top of the file; - replaced proc_dev_atm_operations by proc_atm_dev_ops; - atm_proc_dev_register: removal of tasteless "fail0/fail1" labels.
-
Chas Williams authored
seq_file support for /proc/net/atm/lec: - lec_info(): seq_printf/seq_putc replaces sprintf; - traversal of the lec structure needs to walk: -> the lec interfaces -> the tables of arp tables(lec_arp_tables); -> the arp tables themselves -> the misc tables (lec_arp_empty_ones/lec_no_forward/mcast_fwds) Sum up of the call tree: atm_lec_seq_start()/atm_lec_seq_next() -> atm_lec_get_idx() -> atm_lec_itf_walk() (responsible for dev_lec/dev_put handling) -> atm_lec_priv_walk() (responsible for lec_priv locking) -> atm_lec_arp_walk() -> atm_lec_tbl_walk() -> atm_lec_misc_walk() -> atm_lec_tbl_walk() Each of the dedicated functions follows the same convention: return NULL as long as the seq_file cursor hasn't been digested (i.e. until < 0). Locking is only done when an entry (i.e. a lec_arp_table) is referenced. atm_lec_seq_stop()/atm_lec_itf_walk()/atm_lec_priv_walk() are responsible for getting this point right. - module refcounting is done in atm_lec_seq_open()/atm_lec_seq_release(); - atm_lec_info() is removed. Chas's suggestions applied since last version: - atm_seq_lec_fops renamed to lec_seq_fops; - change in state handling: it wasn't correctly set to its reset value after a complete interface walk; - lec_arp_get_status_string() bugfix.
-
Chas Williams authored
seq_file support for /proc/net/atm/arp: - svc_addr/atmarp_info(): seq_printf/seq_putc replace sprintf and friends; - arp_getidx/arp_vcc_walk() take care of the usual seq_file cursor positionning: they both return NULL until the cursor has reached its position. struct atm_arp_state is updated accordingly; - arp_seq_{stop/start} are responsible for clip_tbl_hook (un)locking; - module refcounting is done in arp_seq_open()/arp_seq_release(); - atm_lec_info() is removed. Chas's suggestions applied since last version: - atm_arp_xxx renamed to arp_xxx; - atm_seq_arp_fops renamed to arp_seq_fops. Chas didn't ask for it but I renamed arp_vc_walk to arp_vcc_walk.
-
Chas Williams authored
seq_file support for /proc/net/atm/vc: Same comments as for pvc and svc. Extra Chas's suggestion applied since last version: - atm_vc_xxx renamed to vcc_xxx.
-
Chas Williams authored
seq_file support for /proc/net/atm/svc: Exactly same comments as pvc. Just s/p/s/
-
Chas Williams authored
seq_file support for /proc/net/atm/pvc: - pvc_info(): seq_printf/seq_putc replaces sprintf; - atm_pvc_info() removal; - the vc helpers (vcc__seq_xxx) do the remaining work. Chas's suggestions applied since last version: - atm_pvc_xxx renamed to pvc_xxx - atm_seq_pvc_fops renamed to pvc_seq_fops
-
Chas Williams authored
Helpers for seq_file conversion of proc/atm/{pvc/svc/vc}: - struct vcc_state keeps 1) the struct sock from which the current struct atm_vcc is deduced 2) the family to which must belong the vcc (PF_ATM{SVC/PVC/any}) 3) the availability of clip module - vcc_seq{start/stop} are responsible for vcc_sklist locking - __vcc_seq_open and vcc_seq_release take care of get/put for the clip module. Chas's suggestions applied since last version: - atm_vc_xxx renamed to vcc_xxx - atm_vc_common_seq_open renamed __vcc_seq_open (future name clashes avoidance)
-
Chas Williams authored
seq_file conversion for proc/atm/devices: - code inspired from seq_file use in net/core/dev.c; - atm_dev_lock taken/released in atm_dev_seq_{start/stop}; - add a helper CREATE_SEQ_ENTRY() similar to CREATE_ENTRY() (both are removed once conversion is done). - atm_dev_seq_{start/stop/next} done in net/atm/resource.[ch] to ease future handling of atm_devs and locking structure (per Chas suggestion)
-
Stephen Hemminger authored
-
Hideaki Yoshifuji authored
-
Hideaki Yoshifuji authored
-
Hideaki Yoshifuji authored
-
Andrew Morton authored
-
Herbert Xu authored
-
Dennis Jørgensen authored
-
Felipe Damasio authored
-
Stephen Hemminger authored
-
Stephen Hemminger authored
-
Hirofumi Ogawa authored
-
Chas Williams authored
-
Chas Williams authored
-
Harald Welte authored
-
Erlend Aasland authored
-
Hideaki Yoshifuji authored
-
Hideaki Yoshifuji authored
-
Hideaki Yoshifuji authored
-
Nick Piggin authored
Thish fixes Suparna's fsx and aio-stress and Dave Olien's concurrent mke2fs problems. It moves the hash adding into as_add_request. This fixes a small bug where a request could be added to the merge hash after being put on the dispatch list. It also moves responsibility for handling rbtree aliases (requests with the same start sector) out of as_add_arq_rb and into its caller. This cleans up a layering problem which was causing the state machine to go silly. Now instead of forcing the alias out onto the dispatch list, we chain the new request behind it, and they get sorted out at dispatch time.
-
Alexander Viro authored
The PS/2 ESDI driver has some problems: a couple of typos on the modular side and misuse of module_init():
-
- 10 Sep, 2003 2 commits
-
-
Andries E. Brouwer authored
A colleague reported that the keyboard of his brandnew laptop is dead under 2.6 while 2.4 works. Now I once wrote In order to avoid interference between scancode sequences or mouse packets and the reponses given to commands, the keyboard or mouse should always be disabled before giving a command that requires a response, and probably enabled afterwards. Some keyboards or mice do the disable automatically in this situation, but still require an explicit enable afterwards. (http://www.win.tue.nl/~aeb/linux/kbd/scancodes-9.html) This is what happens on this laptop. The routine atkbd_probe() probes for a keyboard, and after detecting it, enables it. But immediately afterwards the routine atkbd_set_3() reads the current scancode set and sets the desired set, and as a side effect of these commands, the keyboard gets disabled again. Thus, the keyboard enable must be moved after all command sending has been done. Now that I patch this area anyway: we are almost always in scancode set 2 but send the ATKBD_CMD_SETALL_MB command that only works in scancode set 3. At best this is useless. At worst it confuses the keyboard. So, I put this command in a separate routine and call that only when we really are in scancode set 3.
-
bk://bk.arm.linux.org.uk/linux-2.6-rmkLinus Torvalds authored
into home.osdl.org:/home/torvalds/v2.5/linux
-
- 11 Sep, 2003 1 commit
-
-
Russell King authored
Combine the two initialisation functions, allow SA1111 to be built as a module, and remove a redundant SA1111 function prototype.
-
- 10 Sep, 2003 8 commits
-
-
Holger Freyther authored
Patch from Holger Freyther Make it work ;)
-
Holger Freyther authored
Patch from Holger Freyther This fixes initialization of PCMCIA for the SIMpad unsigned long now user for the flag
-
Holger Freyther authored
Patch from Holger Freyther This the the resubmit of the flash partition changes for SIMpad. Two versions one for cramfs one for all jffs2 and also the SIM has two banks instead of one even if they're next to each other...
-
bk://bk.arm.linux.org.uk/linux-2.6-pcmciaLinus Torvalds authored
into home.osdl.org:/home/torvalds/v2.5/linux
-
Russell King authored
into flint.arm.linux.org.uk:/usr/src/bk/linux-2.6-pcmcia
-
Armin Schindler authored
devfs_handle is not used any more.
-
Joe Perches authored
My fault. Fix for broken aarp.c which got an extra closing parenthesis.
-
Matthew Wilcox authored
<linux/interrupt.h> uses barrier() but does not include <linux/kernel.h>.
-