ppb diff for testing

2015-11-28 Thread Mark Kettenis
The diff below teaches ppb(4) how to configure PCI bridges that are left unconfigured by firmware. This happens for example on Apple hardware, where devices connected through Thunderbolt are left unconfigured. And since Thunderbolt is basically a bunch of PCI bridges (or more correctly PCIe

Re: Debugging cardbus issues

2015-11-28 Thread Tati Chevron
On Sat, Nov 28, 2015 at 07:18:25PM +0100, Mark Kettenis wrote: Date: Sat, 28 Nov 2015 17:12:03 + From: Tati Chevron cbb0 at pci1 dev 9 function 0 "ENE CB-1410 CardBus" rev 0x01: apic 1 int 22, CardBus support disabled cardslot0 at cbb0 slot 0 flags 0 pcmcia0 at

pledge spamd(8), better attempt

2015-11-28 Thread Ricardo Mestre
Hi, This time around I think this one looks better than my previous attempts, where I tried stupidly to grant almost every permission pledge allows. Hoist the sync_init() part to the top since it calls a setsockopt(2) forbidden by pledge(2). Then in the default mode (greylisting) spamd(8) needs

Debugging cardbus issues

2015-11-28 Thread Tati Chevron
I didn't get any response the first time I posted about this... Can somebody at least point me in the direction of something equivillent to pcidump/usbdevs, for cardbus devices, so I can try to identify this mystery ethernet controller? cbb0 at pci1 dev 9 function 0 "ENE CB-1410 CardBus" rev

Avoid -nan for ping std-dev

2015-11-28 Thread Nathanael Rensen
Sometimes floating point imprecision in the calculation of the standard deviation of round-trip latency by ping(8) / ping6(8) leads to attempting to evaluate the sqrt(3) of a negative value: $ ping -c 1 www.google.com PING www.google.com (150.101.170.166): 56 data bytes 64 bytes from

Re: Debugging cardbus issues

2015-11-28 Thread Mark Kettenis
> Date: Sat, 28 Nov 2015 17:12:03 + > From: Tati Chevron > > cbb0 at pci1 dev 9 function 0 "ENE CB-1410 CardBus" rev 0x01: apic 1 int 22, > CardBus support disabled > cardslot0 at cbb0 slot 0 flags 0 > pcmcia0 at cardslot0 > > The host interface attaches, but my

Re: Unlocking ix(4) a bit further

2015-11-28 Thread Hrvoje Popovski
On 16.10.2015. 20:30, Mark Kettenis wrote: >> Date: Fri, 16 Oct 2015 14:13:52 +0200 >> From: Martin Pieuchot >> >> On 08/10/15(Thu) 20:49, Mark Kettenis wrote: Date: Wed, 30 Sep 2015 14:30:11 +0200 (CEST) From: Mark Kettenis Since

Re: WAPBL: Adding the FFS capability to alloc files contiguously

2015-11-28 Thread Bob Beck
On Fri, Nov 27, 2015 at 02:50:57PM -0200, Walter Neto wrote: You have a number of places here where you introduce a line of 8 spaces after your #endif - please clean up the trailing spaces, they shouldn't be there. You also have uses of B_METAONLY that are not inside a #ifdef WAPBL in

Re: ppb diff for testing

2015-11-28 Thread Bryan Vyhmeister
On Sat, Nov 28, 2015 at 11:01:55PM -0700, Theo de Raadt wrote: > > On Sat, Nov 28, 2015 at 10:44:48PM -0700, Theo de Raadt wrote: > > > Mark has told me he thinks this chip model is likely to come up clean, > > > so let's see what he gets working! > > > > Thanks for the background on that! In

Re: ppb diff for testing

2015-11-28 Thread Theo de Raadt
> On Sat, Nov 28, 2015 at 10:44:48PM -0700, Theo de Raadt wrote: > > Mark has told me he thinks this chip model is likely to come up clean, > > so let's see what he gets working! > > Thanks for the background on that! In that case, the ppb.c diff seems to > work perfectly. If it's useful, I have

Re: ppb diff for testing

2015-11-28 Thread Bryan Vyhmeister
On Sat, Nov 28, 2015 at 10:44:48PM -0700, Theo de Raadt wrote: > Mark has told me he thinks this chip model is likely to come up clean, > so let's see what he gets working! Thanks for the background on that! In that case, the ppb.c diff seems to work perfectly. If it's useful, I have several

Re: ppb diff for testing

2015-11-28 Thread Theo de Raadt
> On Sat, Nov 28, 2015 at 02:02:57PM +0100, Mark Kettenis wrote: > > If you find any regressions, please send me: > > > > * dmesg (with and without this diff) > > * pcidump -vxx (with and without this diff) > > First off, it's great to have the Apple Thunderbolt to Ethernet adapter > working!