summaryrefslogtreecommitdiff
path: root/external/gpl3/binutils/dist/makefile.vms
diff options
context:
space:
mode:
Diffstat (limited to 'external/gpl3/binutils/dist/makefile.vms')
0 files changed, 0 insertions, 0 deletions
ubject'>use in_control() for PRU_CONTROLpooka 2010-04-05Push the bpf_ops usage back into bpf.h. Push the common ifp->if_bpfjoerg check into the inline functions as well the fourth argument for bpf_attach. 2010-03-01Introduce RUMP_COMPONENT. It behaves mostly like a simplifiedpooka module which is linked into the kernel and cannot be unloaded. The main purpose is to get the proper constructors run and create any /dev nodes necessary for said component. Once more of the kernel (e.g. networking stack and device drivers) are converted to MODULE and devfs pops up from somewhere, rump components can be retired. 2010-01-26support bpfpooka 2009-12-12Use linker script to make __start/stop_link_set_modules be presentpooka in libs built with binutils >=2.19. This is a less error-prone method than the previous where components had to be tagged in the Makefile as modules (and if they weren't, things broke. and vice versa). 2009-10-20Only allocate a "struct iovec" array from the healp if a reasonably sizedtron stack array isn't large enough. 2009-10-18Avoid panic if a file system tries to write a chain of more than 32 mbuf-stron to a socket. This happens e.g. when copying large files to SMBFS. Code reviewed by Antti Kantee. 2009-10-17fix off-by-one in sanity check and bump lazy bum magic valuepooka 2009-10-16for udp sockets crank snd/rcvbufsize to 64kpooka 2009-09-13binutils 2.19 has changed the old behaviour of defining __start_SECTNAMEpooka for orphaned sections to using PROVIDE. What this means is that unless a rump component internally references that symbol, it will not be included in the component shared library, and hence cannot be referenced when the component is loaded. Add a workaround which works both with 2.16 and 2.19: force a reference to the __start symbol internally and hence retain it in the resulting library. 2009-09-02* implement pr_ctloutputpooka * check for errno before more costly checks 2009-05-28Use a bunch of weak symbols to determine which network componentspooka are present. This works in userspace as opposed relying in link sets, which fail miserably. Later, when the networking stack becomes modularized, we can move to a dynamic scheme like with file systems. Also, this change allows us to do proper autoconfig, namely attach the loopback interface iff it is present. 2009-03-18Ansify function definitions w/o arguments. Generated with sed.cegger 2009-01-30.. but we still need to check if nam is passed to PRU_SEND forpooka non-connected sockets. 2009-01-30Call soisconnected() in PRU_CONNECT for udp sockets too.pooka 2009-01-27* read TCP sockets in cluster-sized chunks instead of IP_MAXPACKET.pooka (it might be a better to chain a few clusters into the iov instead of just one since we are making the syscall anyway) * don't overwrite the useful error value 2009-01-27Hold softnet_lock only when we need it.pooka 2009-01-26* support PRU_SOCK/PEERADDRpooka * soisdisconnected() TCP sockets if read returns a non-transient error or 0 2009-01-26Convert compile-time SOCKIN_NOTHREADS into runtime rump_threads check.pooka 2008-12-18__KERNEL_RCSIDpooka 2008-11-26Add dummy pr_ctloutput. I'm sure I had one at some point, sincepooka it's required for rump_nfs to work, but I guess I lost it somewhere. (yes, it should actually be implemented also) 2008-11-25Make sockin radix-capable.pooka 2008-11-25Support PRU_BIND / PRU_LISTEN / PRU_ACCEPT in sockin.pooka 2008-10-26Remove trailing whitespace.minskim 2008-10-16appease 64bit gccpooka 2008-10-15Mostly support TCP, mostly meaning "client-side TCP", since listen,pooka accept etc. is not supported yet. Disconnect is not really supported either, but doesn't matter in most cases. 2008-10-02Add a very simplistic PF_INET/SOCK_DGRAM domain/proto implementation,pooka which delegates the work to host kernel sockets. This does not run the entire kernel TCP/IP stack in userspace and therefore does not require the ability to send or receive raw packets. This implies that root priviledges are not required. As already said above, only supports UDPv4 for now. Extending should be easy.