be90038a24
In order to sort out our struct termios and add proper speed control we need to separate the kernel and user termios structures. Glibc is fine but the other libraries rely on the kernel exported struct termios and we need to extend this without breaking the ABI/API To do so we add a struct ktermios which is the kernel view of a termios structure and overlaps the struct termios with extra fields on the end for now. (That limitation will go away in later patches). Some platforms (eg alpha) planned ahead and thus use the same struct for both, others did not. This just adds the structures but does not use them, it seems a sensible splitting point for bisect if there are compile failures (not that I expect them) Signed-off-by: Alan Cox <alan@redhat.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org> |
||
|---|---|---|
| .. | ||
| bcm43xx | ||
| hostap | ||
| prism54 | ||
| zd1211rw | ||
| Kconfig | ||
| Makefile | ||
| README | ||
| airo.c | ||
| airo.h | ||
| airo_cs.c | ||
| airport.c | ||
| arlan-main.c | ||
| arlan-proc.c | ||
| arlan.h | ||
| atmel.c | ||
| atmel.h | ||
| atmel_cs.c | ||
| atmel_pci.c | ||
| hermes.c | ||
| hermes.h | ||
| hermes_rid.h | ||
| i82586.h | ||
| i82593.h | ||
| ipw2100.c | ||
| ipw2100.h | ||
| ipw2200.c | ||
| ipw2200.h | ||
| netwave_cs.c | ||
| orinoco.c | ||
| orinoco.h | ||
| orinoco_cs.c | ||
| orinoco_nortel.c | ||
| orinoco_pci.c | ||
| orinoco_pci.h | ||
| orinoco_plx.c | ||
| orinoco_tmd.c | ||
| ray_cs.c | ||
| ray_cs.h | ||
| rayctl.h | ||
| spectrum_cs.c | ||
| strip.c | ||
| todo.txt | ||
| wavelan.c | ||
| wavelan.h | ||
| wavelan.p.h | ||
| wavelan_cs.c | ||
| wavelan_cs.h | ||
| wavelan_cs.p.h | ||
| wl3501.h | ||
| wl3501_cs.c | ||
| zd1201.c | ||
| zd1201.h | ||
README
README ------ This directory is mostly for Wireless LAN drivers, in their various incarnations (ISA, PCI, Pcmcia...). This separate directory is needed because a lot of driver work on different bus (typically PCI + Pcmcia) and share 95% of the code. This allow the code and the config options to be in one single place instead of scattered all over the driver tree, which is never 100% satisfactory. Note : if you want more info on the topic of Wireless LANs, you are kindly invited to have a look at the Wireless Howto : http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/ Some Wireless LAN drivers, like orinoco_cs, require the use of Wireless Tools to be configured : http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html Special notes for distribution maintainers : 1) wvlan_cs will be discontinued soon in favor of orinoco_cs 2) Please add Wireless Tools support in your scripts Have fun... Jean