Add ATI Radeon HD 7850 and 7850 HD Audio to pcidevs

2013-01-13 Thread Thomas Pfaff
Add ATI Radeon HD 7850 and 7850 HD Audio to pcidevs. Verified with the Windows driver information (I was unable to find these ids anywhere else). Index: pcidevs === RCS file: /cvs/src/sys/dev/pci/pcidevs,v retrieving revision 1.1664

Re: PATCH: Print threads in top(1) output

2013-01-13 Thread Philip Guenther
On Mon, 7 Jan 2013, Vadim Zhukov wrote: Small nit that allows (immediately) differentiate processes and threads output of top(1). Adds another dependency on machine.h, though. :( Tested on both smart and dumb terminals. Any comments/okays? Adding an extern declaration to a .c file? Blech.

Re: PATCH: Print threads in top(1) output

2013-01-13 Thread Vadim Zhukov
13.01.2013 14:55 пользователь Philip Guenther guent...@gmail.com написал: On Mon, 7 Jan 2013, Vadim Zhukov wrote: Small nit that allows (immediately) differentiate processes and threads output of top(1). Adds another dependency on machine.h, though. :( Tested on both

Re: Add ATI Radeon HD 7850 and 7850 HD Audio to pcidevs

2013-01-13 Thread Alexey E. Suslikov
Thomas Pfaff tpfaff at tp76.info writes: product ATI RADEON_HD6400_HDA0xaa98 Radeon HD 6400 Audio +product ATI RADEON_HD7850_HDA0xaab0 Radeon HD 7850 HD Audio I think 7850 audio entry shouldn't say HD twice (see 6400).

Re: Add ATI Radeon HD 7850 and 7850 HD Audio to pcidevs

2013-01-13 Thread Thomas Pfaff
On Sun, 13 Jan 2013 12:18:50 + (UTC) Alexey E. Suslikov alexey.susli...@gmail.com wrote: Thomas Pfaff tpfaff at tp76.info writes: product ATI RADEON_HD6400_HDA 0xaa98 Radeon HD 6400 Audio +product ATI RADEON_HD7850_HDA 0xaab0 Radeon HD 7850 HD Audio I think 7850 audio

Re: [miniroot/install.sub] skip x* sets if do not expect to run X.

2013-01-13 Thread Gleydson Soares
please, disregard this diff. it is definitely wrong. -- gsoares

pf tcp window check

2013-01-13 Thread Alexander Bluhm
Hi I think pf sequence number tracking is too strict by one octet. The bug is triggered by a TCP packet with the FIN bit set and containing data that fits exactly into the announced window. This packet announces a window of 1024 octets as scaling factor is 3: 00:58:30.250388 10.188.50.50.45397

Re: hardware VLAN tagging for vr(4)

2013-01-13 Thread Darren Tucker
Resurrecting this, I've now fixed the problem I introduced when I merged in your changes and have tested it. The performance on my ALIX routing from a VLAN to another non-VLAN interface, iperf TCP went up a little (the CPU is saturated at this point): baseline: RX 80.0 Mbits/sec TX 65.2