Updated ./distrib/sets/lists/base/mi to include new firmware files... 6300.tgz now reflects this.
On 4/9/10, B Harder <[email protected]> wrote: > Attachment was too big for mailing list... I will host at > http://methodlogic.net/flat/file/6300.tgz temporarily. > > -bch > > On 4/9/10, B Harder <[email protected]> wrote: >> Well, I've got working wireless now... I haven't benchmarked or tested >> for full feature compliance, but it is useable. Attached are diffs, >> new files, and references to Intel firmware. I don't think I like the >> PCI device name, but it apes what OpenBSD is using at the moment, so >> the driver didn't require other modifications for the case of PCI >> device name. This driver is based on the files that Sverre did supply >> to me; Thanks Sverre. The unified diffs are based off -current as of >> few minutes ago. >> >> Thanks Sverre and Brett for your help and interest. >> >> *Intel firmware pulled from http://intellinuxwireless.org/?n=downloads >> *attached .tgz expands to "6300" dir; Contents are to be applied from >> /usr/src >> >> -bch >> >> On 4/8/10, Brett Lymn <[email protected]> wrote: >>> On Wed, Apr 07, 2010 at 04:00:36PM -0700, B Harder wrote: >>>> >>>> Hi Sverre -- I am interested... I've actually already got the 6000-4 >>>> firmware, got the pcidevs setup, and worked w/ the existing driver >>>> code to get the device attached... at this point, it's failing w/ >>>> eeprom errors (two of them, don't recall what there are, at the >>>> moment). If you've got something in some state of "working", you're >>>> further ahead than I am, though, and I'd love to see that code. >>>> >>> >>> As you have discovered, it is highly unlikely that you can just add >>> the device to pci devs and use the current iwn driver to make it >>> work. I would expect that the interface to the firmware on the card >>> is slightly different, requiring different command structures. This >>> can happen even between versions of firmware on the same hardware. I >>> am not sure how different our iwn driver is from the OpenBSD one these >>> days, perhaps patching in the card specific code from their driver >>> would be possible. >>> >>> -- >>> Brett Lymn >>> "Warning: >>> The information contained in this email and any attached files is >>> confidential to BAE Systems Australia. If you are not the intended >>> recipient, any use, disclosure or copying of this email or any >>> attachments is expressly prohibited. If you have received this email >>> in error, please notify us immediately. VIRUS: Every care has been >>> taken to ensure this email and its attachments are virus free, >>> however, any loss or damage incurred in using this email is not the >>> sender's responsibility. It is your responsibility to ensure virus >>> checks are completed before installing any data sent in this email to >>> your computer." >>> >>> >>> >> >> >> -- >> Brad Harder >> Method Logic Digital Consulting >> http://www.methodlogic.net >> http://twitter.com/bcharder >> > > > -- > Brad Harder > Method Logic Digital Consulting > http://www.methodlogic.net > http://twitter.com/bcharder > -- Brad Harder Method Logic Digital Consulting http://www.methodlogic.net http://twitter.com/bcharder
