lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <AANLkTikiST6OxNj2TN951s5Mh45ypgVi0bo=g0Hhkmaq@mail.gmail.com>
Date:	Wed, 10 Nov 2010 10:46:06 -0800
From:	"Luis R. Rodriguez" <mcgrof@...il.com>
To:	Kevin Hayes <kevin@...eros.com>,
	Deepak Dhamdhere <Deepak.Dhamdhere@...eros.com>,
	Helen Chu <Helen.Chu@...eros.com>
Cc:	Marcel Holtmann <holtmann@...ux.intel.com>,
	Shanmugamkamatchi Balashanmugam 
	<Shanmugamkamatchi.Balashanmugam@...eros.com>,
	Luis Rodriguez <Luis.Rodriguez@...eros.com>,
	Johannes Berg <johannes@...solutions.net>,
	linux-bluetooth <linux-bluetooth@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	Sree Durbha <Sree.Durbha@...eros.com>
Subject: Re: RFC: btusb firmware load help

On Tue, Oct 12, 2010 at 6:38 AM, Kevin Hayes <kevin@...eros.com> wrote:
> Yes, it is a good idea to let the downloadable firmware set a new PID, along with the
>  blacklist on the 3002 PID for the first go round.  I emphasize, it is the downloaded
> firmware that will be required to do the PID swizzling, not the sflash firmware.  And I
> agree we should have a map of the PIDs in use and what they are used for, once
> we get through this immediate fixing phase.

FWIW, since we actually have customers already using this I took
Bala's original patch and put it into compat-wirelesss-2.6.36 and the
current bleeding edge compat-wireless so we can get customers at least
something working in the mean time. Of course this means we'll need to
support this patch should any issues come up ;).

The proper patch didn't make it to 2.6.37, hoping this will get
resolved for 2.6.38.

  Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ