Re: Fix to diskless(8) manpage: add amd64 and i386 to the list of clients that needs rpc.bootparamd(8)

2013-07-25 Thread Rafael Neves
On 7/14/13, Rafael Neves wrote: > On 7/14/13, Theo de Raadt wrote: >>> > Date: Sun, 14 Jul 2013 18:51:13 +0200 >>> > From: Sebastian Benoit >>> > >>> > Mark Kettenis(mark.kette...@xs4all.nl) on 2013.07.14 17:06:24 +0200: ... >>> Index: diskless.8 >>> =

Re: working ral(4) driver with Ralink 35xx chipset.

2013-07-25 Thread Nathan Goings
On 7/25/2013 3:31 AM, Mark Kettenis wrote: New diff. Please give this one a shot. Thanks! I'll get to it as soon as possible! (~3 hours) I need to figure out how to apply a diff first... Couple notes on my testing. - Having severe latency or packetloss issues with some games on a Windows

Re: working ral(4) driver with Ralink 35xx chipset.

2013-07-25 Thread Mark Kettenis
> Date: Thu, 25 Jul 2013 11:10:21 +0200 (CEST) > From: Mark Kettenis > > > Date: Thu, 25 Jul 2013 10:33:12 +0200 (CEST) > > From: Mark Kettenis > > > > Looked at your diff, and then noticed that run(4) already had support > > for the RT3572 MAC/BBP. It has a few more RT3572-specific bits that

Re: working ral(4) driver with Ralink 35xx chipset.

2013-07-25 Thread Mark Kettenis
> Date: Thu, 25 Jul 2013 10:33:12 +0200 (CEST) > From: Mark Kettenis > > Looked at your diff, and then noticed that run(4) already had support > for the RT3572 MAC/BBP. It has a few more RT3572-specific bits that > match what the Linux driver does. So I ported them over to ral(4). > Could you g

Re: working ral(4) driver with Ralink 35xx chipset.

2013-07-25 Thread Mark Kettenis
Looked at your diff, and then noticed that run(4) already had support for the RT3572 MAC/BBP. It has a few more RT3572-specific bits that match what the Linux driver does. So I ported them over to ral(4). Could you give the attached diff a go? Index: rt2860.c ===

Re: working ral(4) driver with Ralink 35xx chipset.

2013-07-25 Thread Martin Pieuchot
On 25/07/13(Thu) 01:15, Nathan Goings wrote: > On 7/24/2013 6:11 PM, Artturi Alm wrote: > >Hi, > > > >No //-comments, { on the same line as if/else, and else after }, but > >since both have only one statement, no braces needed. > >Same goes for the for-loops, I suggest reading style(9). > > > > > >

Re: working ral(4) driver with Ralink 35xx chipset.

2013-07-25 Thread Nathan Goings
On 7/24/2013 6:11 PM, Artturi Alm wrote: Hi, No //-comments, { on the same line as if/else, and else after }, but since both have only one statement, no braces needed. Same goes for the for-loops, I suggest reading style(9). - Artturi Whoops, completely forgot. This should be correct: --- /