On Mon, 2009-01-19 at 21:24 -0600, Brandon Gooch wrote:
> On Mon, Jan 19, 2009 at 8:48 PM, Da Rock
> wrote:
> > On Mon, 2009-01-19 at 20:38 -0500, Damian Gerow wrote:
> >> Sam Leffler wrote:
> >> : OTOH iwn is now out of date and someone needs to update it. There's
> >> : newer firmware that is
On Mon, Jan 19, 2009 at 8:48 PM, Da Rock wrote:
> On Mon, 2009-01-19 at 20:38 -0500, Damian Gerow wrote:
>> Sam Leffler wrote:
>> : OTOH iwn is now out of date and someone needs to update it. There's
>> : newer firmware that is supposed to fix many of the bugs I hit when I
>> : worked on the driv
On Mon, 2009-01-19 at 20:38 -0500, Damian Gerow wrote:
> Sam Leffler wrote:
> : OTOH iwn is now out of date and someone needs to update it. There's
> : newer firmware that is supposed to fix many of the bugs I hit when I
> : worked on the driver (and Intel refused to acknowledge) and obsd has
>
On Mon, Jan 19, 2009 at 7:38 PM, Damian Gerow wrote:
> Sam Leffler wrote:
> : OTOH iwn is now out of date and someone needs to update it. There's
> : newer firmware that is supposed to fix many of the bugs I hit when I
> : worked on the driver (and Intel refused to acknowledge) and obsd has
> : a
Sam Leffler wrote:
: OTOH iwn is now out of date and someone needs to update it. There's
: newer firmware that is supposed to fix many of the bugs I hit when I
: worked on the driver (and Intel refused to acknowledge) and obsd has
: added support for newer parts that people want. It'd be great
Jan Henrik Sylvester wrote:
Torfinn Ingolfsen wrote:
On Sun, 18 Jan 2009 14:17:39 -0600
Brandon Gooch wrote:
I have a working driver for the Intel 4965, aka iwn(4), loaded on my
Lenovo X300 running FreeBSD 7.1-RELEASE (amd64).
FWIW, I am using the latest perforce version of the iwn driver a
