I would like to kill matchlvl in order to move forward with cleaning
our usb stack. So I'd appreciate if people would test the following diff
and let me know if it breaks anything.
My devices don't seem to be affected by it.
Index: ugen.c
On Thu, Nov 14, 2013 at 05:49:44PM +0100, Dmitrij D. Czarkoff wrote:
Hello!
I'm strugling to find any documentation for RTL8188* wireless devices
(including those already supported in urtwn driver). I wrote to Realtek,
but no responce followed.
My problem is that I have a MiniPCI
On 14/11/13(Thu) 17:44, Brad Smith wrote:
On 14/11/13 3:29 PM, SASANO Takayoshi wrote:
Hello,
Here is Genesys Logic's GL620USB-A driver, new version.
I fixed crashing bug when peer is not connected, rewrite sc_dying to
usbd_is_dying() (advices from mpi@), and deleted useless codes.
This
Stefan Sperling said:
I don't think there are any docs. The Linux driver is the only
reference I could find.
The linux driver has pci/usb shims around a common core, much like
some other OpenBSD wireless drivers do (e.g. athn(4)).
I believe a good approach would be to write a working PCI
On Fri, Nov 15, 2013 at 04:55:23AM +0100, Dmitrij D. Czarkoff wrote:
Stefan Sperling said:
I don't think there are any docs. The Linux driver is the only
reference I could find.
The linux driver has pci/usb shims around a common core, much like
some other OpenBSD wireless drivers do
On Fri, Nov 15, 2013 at 04:55:23AM +0100, Dmitrij D. Czarkoff wrote:
That was my plan, though I hoped there is some documentation from
Realtek i could use to avoid looking at Linux driver - I'm afraid Linux
people would react badly if their driver is used even as plain
reference, without any
Tobias Ulmer said:
No, this is not how copyright works. What you want to learn from looking
at their code is not the part that is copyrighted, but the facts, like
which registers needs to be set to what value at which time and sequence.
Whoever wrote the driver copied those facts out of a
* Theo de Raadt dera...@cvs.openbsd.org [2013-11-15 01:38]:
My diff was on tech@ for one day during a hackathon before I commited it.
NOT hidden / circulated privately.
The reasons why I removed the check in the stack are:
- Scanning headers in the forwarding path is against the spirit of
On Thu, Nov 14, 2013 at 05:38:14PM -0700, Theo de Raadt wrote:
Beautiful.
I seems there was enough discussion. The Security argument is more
important than the others. The new diff has no performance impact
when pf is turned on.
So I need OKs.
bluhm
Index: net/pf.c
Is this done right?
Works here with pppoe(4) for both IPv4 and IPv6.
Index: if_sppp.h
===
RCS file: /cvs/src/sys/net/if_sppp.h,v
retrieving revision 1.19
diff -u -p -r1.19 if_sppp.h
--- if_sppp.h 14 Nov 2013 16:52:33 -
On 15 November 2013 15:08, Alexander Bluhm alexander.bl...@gmx.net wrote:
On Thu, Nov 14, 2013 at 05:38:14PM -0700, Theo de Raadt wrote:
Beautiful.
I seems there was enough discussion. The Security argument is more
important than the others. The new diff has no performance impact
when pf
On 15 November 2013 15:13, Stefan Sperling s...@openbsd.org wrote:
Is this done right?
Works here with pppoe(4) for both IPv4 and IPv6.
i think this diff might lack task_del's in the detach code.
have you tried destroying your pppoe interface?
On Fri, Nov 15, 2013 at 03:20:48PM +0100, Mike Belopuhov wrote:
On 15 November 2013 15:13, Stefan Sperling s...@openbsd.org wrote:
Is this done right?
Works here with pppoe(4) for both IPv4 and IPv6.
i think this diff might lack task_del's in the detach code.
Ooops, good catch.
have
On 15 November 2013 15:45, Stefan Sperling s...@openbsd.org wrote:
On Fri, Nov 15, 2013 at 03:20:48PM +0100, Mike Belopuhov wrote:
On 15 November 2013 15:13, Stefan Sperling s...@openbsd.org wrote:
Is this done right?
Works here with pppoe(4) for both IPv4 and IPv6.
i think this diff
Hello,
I committed ugl(4) driver to source tree.
The driver is derived from upl(4) driver, so licence is NetBSD.
Thanks.
--
SASANO Takayoshi u...@mx5.nisiq.net
At Fri, 15 Nov 2013 10:56:37 +0100,
Martin Pieuchot wrote:
On 14/11/13(Thu) 17:44, Brad Smith wrote:
On 14/11/13 3:29 PM, SASANO
Seems to work fine on my home network.
ok?
Index: if_wpi.c
===
RCS file: /cvs/src/sys/dev/pci/if_wpi.c,v
retrieving revision 1.113
diff -u -p -r1.113 if_wpi.c
--- if_wpi.c1 Oct 2013 20:06:02 - 1.113
+++ if_wpi.c15
This may slow down sustained reads from softraid1 volume which consists of
drives w/ enabled read-ahead caches.
Just a guess, no tests performed.
2013/11/8 Ted Unangst t...@tedunangst.com
This may be a bad idea. I can't really think of any pros or cons,
other than a general principle of when
17 matches
Mail list logo