On 02/08/11 04:49, Glen Gray wrote:
On 3 Feb 2011, at 18:45, Auke Kok wrote:
On 02/02/11 12:21, Robinson Tryon wrote:
On Wed, Feb 2, 2011 at 9:46 AM, Arjan van de Ven<ar...@linux.intel.com> wrote:
On 2/2/2011 6:43 AM, Glen Gray wrote:
or we all spend time making the opensource BCM driver work on 2.6.37
this sounds like a really good idea regardless of anything else.
I remember hearing that Broadcom had become a member of the Linux
Foundation, and that they'd released some set of drivers under FOSS
licenses. Given that Broadcom is a member of LF, and MeeGo is a
project of the LF, is there any ongoing support by Broadcom to help
get their hardware working with open drivers under the Linux kernel,
and with the MeeGo stack in particular?
We're hopeful that the upstream driver will mature fast with the help of
broadcom engineers, and I can see from the commit logs in the kernel that there
is work ongoing by them. The upstream-first scheme will work well for us here -
Broadcom gets to focus development on the mainstream kernel driver, and we'll
be able to get the code from there.
That's great, but where does it leave is for the upcoming 1.2 release ?
probably out of luck, since we won't change the kernel for the 1.2
release - something that was decided a long time ago.
of course, nothing stops anyone from doing a backport and adding the
open source driver in the community OBS>
Auke
_______________________________________________
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
