Date: Wed, 21 Mar 2012 14:32:23 -0700 From: matt <sendtomatt@gmail.com> To: Bernhard Schmidt <bschmidt@techwires.net> Cc: Aleksandr Rybalko <ray@dlink.ua>, freebsd-wireless@freebsd.org Subject: Re: Please Test: Updated Ral Driver Patch for rt2860/rt3090 Message-ID: <4F6A48E7.1010006@gmail.com> In-Reply-To: <CAAgh0_apzg5tVsdPaE77Pg07OiG9GTO%2Bs2NamKF9SZKor2NQiA@mail.gmail.com> References: <CA%2BCYCL-d1hCzQK48EzPjgRu3UFO9EWMn-O%2B3V8%2B9cNrQE2s%2ByQ@mail.gmail.com> <4F5A8023.1090705@gmail.com> <CAJ-Vmonu4SUVOdfbTdAnmGfQ=T-PtcAbd-PCoQ0PV_ttwF5Scw@mail.gmail.com> <4F5AC7CF.3090409@gmail.com> <4F5C0C86.7040503@gmail.com> <4F5C24ED.3090601@gmail.com> <4F5CD920.2000905@gmail.com> <4F5D0876.5040409@gmail.com> <4F5D14E0.3050301@gmail.com> <CAJ-Vmo=jJmwY=bTVaKFYTd--1E9vzwgn54VMJyY82bc9pSWcBg@mail.gmail.com> <20120312001625.4d9b3b52.ray@ddteam.net> <4F5E7D17.7000102@gmail.com> <4F5E9814.7010803@gmail.com> <CAJ-VmomvqoV184PuBOpjuyQkGg7dTn8fv46uPXyGdf0o6L5PRg@mail.gmail.com> <4F5E9BA3.2000401@gmail.com> <20120313131415.36ecd761.ray@dlink.ua> <CAJ-VmokpT4RjqS_CwCm1Tpn5X6H1kutPy0pWTTLy16j%2BO_oJ3w@mail.gmail.com> <4F5FE891.7050306@gmail.com> <20120314200718.b6b51452.ray@ddteam.net> <4F651853.2050409@gmail.com> <CAJ-VmomiL%2B9r1T6pkcs88qgDdJaz1g0OWK6krCz%2BgK0bNHJKKw@mail.gmail.com> <CAAgh0_apzg5tVsdPaE77Pg07OiG9GTO%2Bs2NamKF9SZKor2NQiA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/21/12 00:54, Bernhard Schmidt wrote: > On Wed, Mar 21, 2012 at 06:04, Adrian Chadd <adrian@freebsd.org> wrote: >> Hi, >> >> How's the ralink driver tinkering going? >> >> How far out are we from committing something partially working to >> -HEAD? What are the showstoppers? > Lots of stuff, please let me go over at least the reg.h and var.h > first. I'm only half way through the reg file yet. > Agreed...google code version needs some looking at before anything is committed...There are/were some rough edges last chance I got...unitialized warning for "val" in io_eeeprom_read and of course a fine panic after attach. At least this time there was a debugger...I can't find my firewire bracket. I'll hopefully get some time to keep messing around with it this weekend and see if either Bernhard's work or careful line-by-line comparison with mine can make it happy again. There were quite a few changes to the eeprom side of things I saw (eeprom_ctl), which I think is bringing us closer to OpenBSD compatibility, ie. same eeprom defines? Or just newer code? Thanks, Matt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F6A48E7.1010006>