Re: uvideo patches: Overview [0/4]

On Thu, May 26, 2016 at 10:55:47PM +0200, Marcus Glocker wrote: > On Tue, May 17, 2016 at 05:15:51PM -0700, patrick keshishian wrote: > > > Greetings, > > > > I have been looking at uvideo trying to model a new driver I'm > > attempting to port over and found a few issues (or what I precive > >

utvfu driver port

Hi, Included is my initial effort to port the dual-licensed driver for Fushicai Audio-Video Grabber (vendor 0x1b71 product 0x3002). As I mentioned in previous email it is "mostly working". I have tested it on amd64 and macppc. The macppc audio issue mentioned got resolved thanks to a hint from

Re: uvideo patches: Overview [0/4]

On Tue, May 17, 2016 at 05:15:51PM -0700, patrick keshishian wrote: > Greetings, > > I have been looking at uvideo trying to model a new driver I'm > attempting to port over and found a few issues (or what I precive > as issues). > > Since the list likes separate diffs for easier discussion,

Re: use ${CC} -E rather than ${CPP}

On Thu, 26 May 2016 22:46:24 +0200, Martin Natano wrote: > Yes, the difference is due to cpp vs. cc -E. Try to diff against the > output generated with cpp. Then the files are the same. Strange, the only difference between the cpp vs. cc -E output is whitespace. Now I see that the end of lex.l

Re: use ${CC} -E rather than ${CPP}

On Thu, May 26, 2016 at 02:14:29PM -0600, Todd C. Miller wrote: > On Thu, 26 May 2016 22:07:14 +0200, Martin Natano wrote: > > > > diff -u -p -u -r1.11 Makefile > > > --- share/locale/ctype/Makefile 20 Mar 2016 15:45:40 - 1.11 > > > +++ share/locale/ctype/Makefile 23 Mar 2016

Re: use ${CC} -E rather than ${CPP}

On Thu, 26 May 2016 22:07:14 +0200, Martin Natano wrote: > > diff -u -p -u -r1.11 Makefile > > --- share/locale/ctype/Makefile 20 Mar 2016 15:45:40 - 1.11 > > +++ share/locale/ctype/Makefile 23 Mar 2016 20:16:56 - > > @@ -9,8 +9,7 @@ NOMAN= # defined > > all: UTF-8.out

Re: use ${CC} -E rather than ${CPP}

See one comment inline. On Thu, May 26, 2016 at 09:59:24AM -0600, Todd C. Miller wrote: > Since /usr/bin/cpp still specified -traditional, use ${CC} -E > instead. I've had this rotting in my tree for years now. > > - todd > > Index: lib/libcurses/Makefile >

ugen(4) Asynchronous USB Requests

Hi all, In order to make iPhone USB tethering work with OpenBSD, I ended up  going a bit down the proverbial rabbit's hole. After initially playing around with trying to build a userspace  'driver' using a tap interface, I found that ugen(4) was entirely  blocking. I had started hacking around

replace bpf open loops

I think it's time to get rid of all the bpf open() loops in base. dhclient and libpcap do a plain open("/dev/bpf0", ...) since a couple of weeks now and the upgrade issue (/dev/bpf vs. /dev/bpf0) has been fixed. I didn't hear any other complaints in the meantime. Ok? Too soon? natano Index:

use ${CC} -E rather than ${CPP}

Since /usr/bin/cpp still specified -traditional, use ${CC} -E instead. I've had this rotting in my tree for years now. - todd Index: lib/libcurses/Makefile === RCS file: /cvs/src/lib/libcurses/Makefile,v retrieving revision 1.67

Re: remove doforce from kern/vfs_subr.c

On Thu, 26 May 2016 17:43:06 +0200, Martin Natano wrote: > The doforce variable isn't modified anywhere. Also, the only filesystem > left using it is fuse. It has been removed from all other filesystems. OK millert@ - todd

remove doforce from kern/vfs_subr.c

The doforce variable isn't modified anywhere. Also, the only filesystem left using it is fuse. It has been removed from all other filesystems. Ok to remove? natano Index: kern/vfs_subr.c === RCS file:

iwm(4): The valid_{rx,tx}_ant values only be read from nvm for 8000 family

Hi, We only need to set the data->valid_tx_ant and data->valid_rx_ant values in iwm_parse_nvm_data() for the 8000 family chips. This matches what iwl_set_radio_cfg() in iwl-nvm-parse.c from Linux's iwlwifi does. Also the "if (!data->valid_tx_ant || !data->valid_rx_ant) {" check should be removed

Re: bridge, carp and HW-vlan

On Mon, May 23, 2016 at 03:23:52PM +0200, Martin Pieuchot wrote: > HW-vlan breaks our if_input() design because vlan packets are > decapsulated before calling if_input(). > > So it doesn't matter in which order you configured your pseudo-driver, > they all have to deal with this layer violation.

ftp5.usa.openbsd.org mirror up for the day, going down again overnight

I brought ftp5 back up this morning around 7:15am EDT and checked it was working, it will be going down again around 4pm EDT since RIT is doing the second half of their electrical substation work tonight from 5pm until 7am. I'll bring it back up tomorrow morning shortly after 7am. --Kurt

Re: SRV lookups in ypldap

On Mon, May 02, 2016 at 10:18:04AM +1000, Jonathan Matthew wrote: > ypldap currently can't do SRV lookups to locate the directory servers for > a domain, which makes it slightly harder than it should be to connect it to > an AD domain. The diff below lets you specify a directory service like

procmap: map vnodes to names again

This re-introduces the vnode-to-filename mapping code with adaptions to the new namecache layout. For example, running procmap -a 1 now prints the .text, .data, and .rodata segments of init(1) as below, if /sbin/init is in the name cache: 104ccb70-104ccb73dfff 248k 0 r-xp+ (rwx) 1/0/0