summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Finish removal of matcdimp2005-01-101-540/+0
|
* Remove the clause 3, per berkeley and mail from rwatson representingimp2005-01-101-5/+1
| | | | that nai was OK with all third clause removals.
* NE200 -> NE200Timp2005-01-101-1/+1
|
* Tweaks to the name of this card, based on input from Sean Shapira.imp2005-01-101-1/+1
|
* Remove matcd. It isn't in the build, has issues and can be retired.imp2005-01-106-4133/+0
| | | | | Submitted by: trhodes (the real one) Approved by: core, mdodd, uhclem
* sort more things alphabeticallyimp2005-01-101-158/+158
|
* libarchive does much more than just tar ;-)kientzle2005-01-101-1/+1
|
* Sort entries.imp2005-01-101-9/+7
| | | | | Remove a couple of 'card' lines that were somehow missed when OLDCARD was desupported.
* Sort entires better.imp2005-01-101-4/+4
|
* Add support for:imp2005-01-101-0/+1
| | | | | | | | | | | fe1: <EAGLE Technology NE200 ETHERNET LAN MBH10302 04> As reported by Sean Shapira. This appears to be working. Eagle used Fujitsu's vendor number, with a product number of 4 (which is the same as the vendor number, which is a little suspect). Since there's no apparent conflict, go ahead and use it. Submitted by: Sean Shapira
* Add Eagle NE200 Ethernet LAN MBH10302 card. This appears to be a feimp2005-01-101-0/+1
| | | | | | card, and works with that driver. However, Eagle is using Fujitsu's vendor number and a product code of 4, which seems a little odd. Still, there's no conflicts...
* Free the shared devq last since CAM expects it to be there ifdwhite2005-01-102-5/+11
| | | | | | | xpt_alloc_device() gets called, which can happen during detach in certain situations. Fixes module unload. MFC after: 3 days
* Wording nit.trhodes2005-01-101-1/+1
|
* fix a "little-endian-big-endian confusion that luckily:julian2005-01-091-2/+2
| | | | | | | | | | | 1/ doesn't matter on most of our architectures 2/ will never happen unless we start queueing multiple trasactions to a single endpoint at one time (which we do not allow yet). If anyone has a big_endian machine with EHCI they might check this if they are having problems with EHCI but it's unlikely even there.. Submitted by: Hans Petter Selasky <hselasky@c2i.net> MFC after: 3 days
* Cosmetic typo in check_pidfile()keramida2005-01-091-1/+1
| | | | | PR: bin/75946 Submitted by: zero@gddn.org (Finn)
* Only update the boot sector when there is a valid drive number provided.peadar2005-01-091-14/+15
| | | | | | | | | (After squeezing a few more bytes out of boot0) Discussed With: jhb, julian PR: 66248 Submitted By: Hans Petter Selasky MFC After: 1 week
* Fix typos and add .Pp after the end of a display to separate thekeramida2005-01-091-2/+3
| | | | displayed text from the paragraph right after it.
* In my last commit, I'd assumed that LINE30 was always defined. Itimp2005-01-094-0/+58
| | | | | | | | turns out that LINE30_ROW was always defined, not LINE30. I confused this for LINE30 and did the unifdef -DLINE30 using that mistaken belief. This corrects that problem. Submitted by: nyan-san
* Remove the meteor helper files, imp removed the driver and manual pagetrhodes2005-01-096-637/+0
| | | | over a year ago.
* correct direction for bus_dma sync of rx buffersam2005-01-092-2/+2
| | | | Submitted by: Tai-hwa Liang
* Scheduled mdoc(7) sweep.ru2005-01-095-10/+14
|
* Don't panic when we're asked to allocate a resource type that we knowmarcel2005-01-091-3/+2
| | | | | | won't exist for EBus. Just fail the allocation by returning NULL. Now drivers that are MI can try resources that the driver knows may be used by the device.
* Use uint32_t instead of u_long when appropriate.cognet2005-01-091-64/+64
| | | | | | That's enough to make my bt848 work on amd64. MFC after: 1 week
* Increase default synchronization speed.pjd2005-01-092-2/+2
| | | | MFC after: 3 days
* Revert previous revision. Including bsd.compat.mk is necessaryru2005-01-091-0/+1
| | | | | both from sys.mk (to handle old knobs set in /etc/make.conf), and from here (to handle old knobs set in individual makefiles).
* o Make telnet[d] -S (IP TOS) flag really work. We do not havemaxim2005-01-093-10/+32
| | | | | | | | | /etc/iptos implementation so only numeric values supported. o telnetd.8: steal the -S flag description from telnet.1, bump the date of the document. MFC after: 6 weeks
* Fix build on all (hopefully) 64 bit architectures.trhodes2005-01-091-1/+1
| | | | | Noticed by: tinderbox Tested on: panther
* Mark the IPX netisr as MPSAFE so that inbound IPX traffic is processedrwatson2005-01-091-1/+1
| | | | | | | without Giant, and can be directly dispatched in the ithread when net.isr.enable is turned on. MFC after: 4 weeks
* Recent changes have locked down most of the highly dynamic datarwatson2005-01-092-4/+0
| | | | | | | | | | | | | | structures in IPX/SPX -- primarily, sequence numbering, PCB lists, and PCBs for IPX raw sockets, IPX datagram sockets, and IPX/SPX. As such, remove remove NET_NEEDS_GIANT() for IPX, and remove the assertion of Giant in the ipxintr() IPX input path. Note that IPX/SPX is not fully MPSAFE, and that there are some problems with IPX/SPX locking that will require some further work. However, it is now safe enough to run in general without the Giant lock. MFC after: 4 weeks
* Use the IPX PCB list mutex and IPX PCB mutexes to lock down the SPXrwatson2005-01-092-39/+110
| | | | | | | | | | | | | | | | | | | | | | | | portion of IPX/SPX: - Protect IPX PCB lists with the IPX PCB list mutex, in particular when calling PCB and PCB list manipulation routines in ipx_pcb.c. - Protect both IPX PCB state and SPX PCB state using the IPX PCB mutex. - Generally annotate locking, as well as adding liberal use of lock assertions to document locking requirements. - Where possible, use unlocked reads when reading integer or smaller sized socket options on SPX sockets. - De-spl throughout. Notes: - spx_input() expects both the list mutex and PCB mutex to be held on entry, but will release both on return. Because sonewconn() is called from spx_input(), it may actually drop one PCB lock and acquire another during generation of a new connection, meaning the caller is not in a position to unlock the PCB mutex. MFC after: 3 weeks
* Clean up return handling for a number of SPX-related routines thatrwatson2005-01-091-22/+29
| | | | | | | | | | | | | | | | were derived from more complex TCP versions of the same: - spx_close(), spx_disconnect(), spx_drop(), and spx_usrclosed() all always free's the spxpcb invalidating the argument, so a return value is not required to indicate if it has. - Annotate that the cb arguments to each of these functions is invalidated via a comment. - When tearing down a pcb due to sonewconn() having failed, mark the cb as NULL; later, when deciding whether to store trace information due to SO_DEBUG, check that cb is not NULL before dereferencing or a NULL pointer dereference may occur. MFC after: 3 weeks
* Protect ipx_pexseq with the IPX PCB list mutex.rwatson2005-01-092-3/+12
| | | | | | | | When processing socket options against IPX PCBs, generally protect PCB fields using the IPX PCB mutex. Where possible, use unlocked reads on integer values to avoid locking overhead. MFC after: 3 weeks
* Acquire or assert the IPX PCB list lock or IPX PCB lock during variousrwatson2005-01-091-33/+72
| | | | | | | | | | protocol methods relating to IPX. Conditionally acquire the PCB list lock in the send operation only if the socket requires binding in order to use the requested address. Remove spl's generally no longer required during these accesses. MFC after: 3 weeks
* Assert or acquire the IPX PCB list lock or IPX PCB locks throughoutrwatson2005-01-091-1/+21
| | | | | | | | | the IPX-related PCB routines. In general, the list lock is required to iterate the PCB list, either for read or write; the PCB lock is required to access or modify a PCB. To change the binding of a PCB, both locks must be held. MFC after: 3 weeks
* Hold the IPX PCB mutex around calls to ipx_input() in the IPX inputrwatson2005-01-091-1/+8
| | | | | | path. MFC after: 3 weeks
* Hold the global IPX PCB list mutex in the IPX input path when walkingrwatson2005-01-091-0/+7
| | | | | | the IPX PCB list. MFC after: 3 weeks
* Introduce a global mutex, ipxpcb_list_mtx, to protect the globalrwatson2005-01-093-1/+24
| | | | | | | | | | | | IPX PCB lists. Add macros to initialize, destroy, lock, unlock, and assert the mutex. Initialize the mutex when IPX is started. Add per-IPX PCB mutexes, ipxp_mtx in struct ipxpcb, to protect per-PCB IPX/SPX state. Add macros to initialize, destroy, lock, unlock, and assert the mutex. Initialize the mutex when a new PCB is allocated; destroy it when the PCB is free'd. MFC after: 2 weeks
* In ipx_setsockaddr(), use M_WAITOK instead of M_NOWAIT so that therwatson2005-01-091-2/+2
| | | | | | | call always succeeds, avoiding causing the caller to return success even though the returned *sockaddr is NULL. MFC after: 2 weeks
* Eliminate jump to 'bad' label in order to clean up the ipx_input()rwatson2005-01-091-13/+14
| | | | | | return/unwind path for locking work. MFC after: 2 weeks
* Implement rpmatch(), a semi-standard interface (as found on AIX, Tru64,tjr2005-01-094-2/+122
| | | | | | GNU) for determining whether a string is an affirmative or negative response to a question according to the current locale. This is done by matching the response against nl_langinfo(3) items YESEXPR and NOEXPR.
* Move the acquisition and release of the page queues lock outside of a loopalc2005-01-081-2/+3
| | | | in vm_object_split() to avoid repeated acquisition and release.
* Use static const char and bump WARNS.trhodes2005-01-082-2/+2
|
* Remove support for FreeBSD < 4.recent from this driver.imp2005-01-087-35/+1
|
* Remove unused variable.trhodes2005-01-081-1/+0
|
* Remove vnode.h and adjust includes to compensate for pollution.imp2005-01-085-6/+13
|
* LINE30 is always defined now, so unifdef -DLINE30 for clarity.imp2005-01-082-42/+0
|
* Merge module.h into 30line.h and remove it. It lacked aimp2005-01-083-69/+10
| | | | | | | | | copyright/license header and was only used by 30line.h. It appears that the copyright/license in 30line.h covers the old contents module.h anyway, so this simplifies things a little while cleaning up one obscure potential license confusion... Revired by: nyan-san
* Recognize and parse symlinks in ISO9660 CDROM images with Rockridge extensions.kientzle2005-01-081-17/+75
|
* Documentation improvements. In particular,kientzle2005-01-085-52/+145
| | | | | | | expand and clarify the description of the client callback functions and how they should handle errors. Thanks to: Antony Dovgal
* Correctly document the order of argumentskientzle2005-01-082-2/+2
| | | | | | to archive_read_open and archive_write_open. Thanks to: Antony Dovgal
OpenPOWER on IntegriCloud