Re: iwn driver on 7.1 [no vaps in RELENG_7]
Jan Henrik Sylvester wrote: Torfinn Ingolfsen wrote: On Sun, 18 Jan 2009 14:17:39 -0600 Brandon Gooch jamesbrandongooch at gmail.com 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 as documented here[1] on a ThinkPad T61 running FreeBSD 7.1-stable / i386 - no modifications necessary. It works great. I just use the p4fetch.rb script to get the driver. HTH References: 1) http://clearchain.com/wiki/iwn Since from that address, you are using the latest version of the benjsc perforce branch, you are probably using the same as I, since I took the initial version from the sam_vap branch (before vap got introduced). I do not know how far it is, but there is vap_releng7 in the sam perforce and projects/vap7 in svn on which Sam Leffler is actively working: http://lists.freebsd.org/pipermail/svn-src-projects/2009-January/thread.html I would like to have if_iwn working on a otherwise unmodified 7.1-RELEASE-pX and help to test it, but maybe waiting on sam to bring vap to 7 would be a better way to go. vaps will never be committed to RELENG_7 due to API/ABI constraints. However that svn branch is operational and being maintained as it's used by multiple people. I considered bringing back iwn (it's just copying the bits); will add it to my TODO list. 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 if someone wanted to take over this driver. Sam ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: iwn driver on 7.1 [no vaps in RELENG_7]
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 if : someone wanted to take over this driver. I've been working on this driver for the past few weeks (Christmas provided a healthy distraction), but it's a steep learning curve for a novice C coder. If anyone wants to work on this, let me know, as I have a small portion of the work already done. - Damian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: iwn driver on 7.1 [no vaps in RELENG_7]
On Mon, Jan 19, 2009 at 7:38 PM, Damian Gerow dge...@afflictions.org 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 : added support for newer parts that people want. It'd be great if : someone wanted to take over this driver. I've been working on this driver for the past few weeks (Christmas provided a healthy distraction), but it's a steep learning curve for a novice C coder. If anyone wants to work on this, let me know, as I have a small portion of the work already done. - Damian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org I'd like to work on this as well. I just pulled down the iwn code from OpenBSD current a little while ago and started hacking on it. I haven't made a lot of progress, so I'll gladly work with you on it. I'm a decent C programmer, but my lack of knowledge of kernel internals, functions, and data structures is my stumbling block. That's one of the main reasons I'm all about getting this driver working -- it gives me yet another chance to get into the kernel source and learn something new. Where do we begin? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: iwn driver on 7.1 [no vaps in RELENG_7]
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 : added support for newer parts that people want. It'd be great if : someone wanted to take over this driver. I've been working on this driver for the past few weeks (Christmas provided a healthy distraction), but it's a steep learning curve for a novice C coder. If anyone wants to work on this, let me know, as I have a small portion of the work already done. - Damian I'm willing to work on it (doing so now), but from what you have said here it sounds like you're in the same boat as myself as I'm very new to this too :) What about collaboration between us with a Freebsd core team mentor? Is this possible? Code, test, then send the new code through the core team member for approval as well as hints to get the job done? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: iwn driver on 7.1 [no vaps in RELENG_7]
On Mon, Jan 19, 2009 at 8:48 PM, Da Rock rock_on_the_...@comcen.com.au 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 driver (and Intel refused to acknowledge) and obsd has : added support for newer parts that people want. It'd be great if : someone wanted to take over this driver. I've been working on this driver for the past few weeks (Christmas provided a healthy distraction), but it's a steep learning curve for a novice C coder. If anyone wants to work on this, let me know, as I have a small portion of the work already done. - Damian I'm willing to work on it (doing so now), but from what you have said here it sounds like you're in the same boat as myself as I'm very new to this too :) What about collaboration between us with a Freebsd core team mentor? Is this possible? Code, test, then send the new code through the core team member for approval as well as hints to get the job done? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org I don't know how mentoring works in the FreeBSD world or if a canonical process of mentoring even exists, but I would definitely be willing to participate. I know it would be a heck of a lot better than hacking around on this stuff by myself. -Brandon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: iwn driver on 7.1 [no vaps in RELENG_7]
On Mon, 2009-01-19 at 21:24 -0600, Brandon Gooch wrote: On Mon, Jan 19, 2009 at 8:48 PM, Da Rock rock_on_the_...@comcen.com.au 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 driver (and Intel refused to acknowledge) and obsd has : added support for newer parts that people want. It'd be great if : someone wanted to take over this driver. I've been working on this driver for the past few weeks (Christmas provided a healthy distraction), but it's a steep learning curve for a novice C coder. If anyone wants to work on this, let me know, as I have a small portion of the work already done. - Damian I'm willing to work on it (doing so now), but from what you have said here it sounds like you're in the same boat as myself as I'm very new to this too :) What about collaboration between us with a Freebsd core team mentor? Is this possible? Code, test, then send the new code through the core team member for approval as well as hints to get the job done? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org I don't know how mentoring works in the FreeBSD world or if a canonical process of mentoring even exists, but I would definitely be willing to participate. I know it would be a heck of a lot better than hacking around on this stuff by myself. -Brandon Ok then, as you said- where do we start? From what I can see in the running of the card currently is its having trouble scanning- but they maybe a ruse, I'm trying to find a way to definitively determine what is going on here. Also, once the card has started scanning it locks up and appears to 'reset' or something, so that when I run wpa_supplicant the next time round it works again- but still won't scan. I'll just run through what I did yesterday again and post the results, but I believe those results from yesterday are already there on the -questions@ list if you wish to jump the gun. I'm currently looking along the lines of what people are running atm- it just clicked with me that my card is 4965AGN, but most reference this card as BGN, so I'm wondering if thats making a difference. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
