On Wed, Jan 09, 2013 at 04:12:23PM +0000, Richard N wrote:
> Mark Kettenis <mark.kettenis <at> xs4all.nl> writes:
> 
> > 
> > > Date: Tue, 13 Nov 2012 21:02:24 -0500
> > > From: James Turner <james <at> calminferno.net>
> > > 
> > > I was actually able to add support myself with the following diff.
> > 
> > Great!
> > 
> > Committed an improved diff that also adds the "other" 6030 variant.
> > 
> > > Index: if_iwn.c
> > > ===================================================================
> > > RCS file: /cvs/src/sys/dev/pci/if_iwn.c,v
> > > retrieving revision 1.115
> > > diff -u -p if_iwn.c
> > > --- if_iwn.c      11 Nov 2012 20:45:31 -0000      1.115
> > > +++ if_iwn.c      14 Nov 2012 02:00:52 -0000
> > > @@ -639,7 +639,8 @@ iwn5000_attach(struct iwn_softc *sc, pci_product_id_t 
> > >           break;
> > >   case IWN_HW_REV_TYPE_6005:
> > >           sc->limits = &iwn6000_sensitivity_limits;
> > > -         if (pid == PCI_PRODUCT_INTEL_WL_6235_1) {
> > > +         if (pid == PCI_PRODUCT_INTEL_WL_6235_1 ||
> > > +             pid == PCI_PRODUCT_INTEL_WL_6030_2) {
> > >                   sc->fwname = "iwn-6030";
> > >  
> > >                   /* XXX: The 6235 generates a fatal firmware error when
> > 
> > 
> 
> ------------------------------------------------------
> 
> Thankyou for all the above info
> I am interested in purchasing a Laptop which will unfortunately have the 
> "Intel
> Centrino Advanced-N 6235 + Bluetooth Combo Module"
> 
>  I assume, in an earlier post, that someone "disabled" bluetooth (in their
> BIOS), and then the "iwn0 firmware/driver" had worked flawlessly. ?
> 
>  I'm sorry for interrupting here, but I just wanted to confirm, that in 
> OpenBSD
> 5.2 Official (Stable) Release , that this in fact is still the case. ?
>  Either way, I do NOT plan on using Bluetooth on my laptop.
> 
>  Thanks for all your efforts as well.
> 
> Rick.
> 

Rick,

I did not have to disable BT in my bios, the driver it self
disables/skips over it I believe.

This commit was made to cvs after 5.2 was released so you will need to
run a snapshot or follow -current instead.

-- 
James Turner

Reply via email to