Re: [MeeGo-dev] Broadcom WL on MeeGo Netbook 1.1.90.0.20110125

2011-02-08 Thread Auke Kok

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 Venar...@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


Re: [MeeGo-dev] Broadcom WL on MeeGo Netbook 1.1.90.0.20110125

2011-02-08 Thread Glen Gray

On 8 Feb 2011, at 19:34, Auke Kok wrote:

 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 Venar...@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.
 
So where does that leave the lockdep rcu debugs setting in the kernel. Is that 
going to remain enabled for the release and thus blocking the Broadcom STA 
driver from loading ?

 of course, nothing stops anyone from doing a backport and adding the open 
 source driver in the community OBS

Nope, nothing stopping anyone from doing that and that's great for developers. 
But that's not going to satisfy the many regular users out there the the 
Netbook UX was designed for. Those on netbooks that have a Broadcom wifi chip, 
such as the Dell Mini 9 which I won or the Lenovo ideapad that was given out at 
the Meegoconf in dublin. At least they can at present, with the 1.1 release, 
get a Broadcom driver built and running on their netbooks, even if it's a 
convoluted process for them. I'd hate to see us loose that of force a situation 
where we're forcing a Broadcom driver to claim its GPL when it's not. 

Kind Regards,
--
Glen Gray
sla...@slaine.org




___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev


Re: [MeeGo-dev] Broadcom WL on MeeGo Netbook 1.1.90.0.20110125

2011-02-02 Thread Glen Gray
I have an update to that source rpm pending for the 1.2 release, I just haven't 
gotten the chance to upload it yet. I'll try and make time over lunch today.

Of follow Shane's suggestions. 

On 1 Feb 2011, at 22:32, Rudolf Streif wrote:

 I understand your concerns about Broadcom's open-source policy. However, 
 since I was successfully able to build the very same driver on the MeeGo 1.1 
 release form October but not with the one from 1/25 the not so far fetched 
 conclusion is that something changed in MeeGo. Which I now know it did.
 
 Ok, this may not be the right list but one is probably more likely to get an 
 answer about init_MUTEX on a developer list than on an end-user list.
 
 On Tue, Feb 1, 2011 at 12:58 PM, Arjan van de Ven ar...@linux.intel.com 
 wrote:
 On 2/1/2011 12:57 PM, Rudolf Streif wrote:
 Thank you. Yes, I did download the latest source from 
 http://www.broadcom.com/support/802.11/linux_sta.php. The version number is 
 5.100.82.38 which is the version of the spec file. It's the one I am having 
 issues with.
 
 not to be an ass about it, but I would suspect that Broadcom is in a much 
 better position to support their binary driver
 than the MeeGo development list Have you tried asking Broadcom for 
 support instead ?
 
 (never mind that this is a development list not an end user help list)
 
 
 
 
 
 
 ___
 MeeGo-dev mailing list
 MeeGo-dev@meego.com
 http://lists.meego.com/listinfo/meego-dev

--
Glen Gray
sla...@slaine.org




___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev


Re: [MeeGo-dev] Broadcom WL on MeeGo Netbook 1.1.90.0.20110125

2011-02-02 Thread Glen Gray

On 1 Feb 2011, at 06:39, Shane Bryan wrote:

 On Mon, Jan 31, 2011 at 05:37:51PM -0800, Rudolf Streif wrote:
 I am trying t build the pita Broadcom WL driver module on a MeeGo Netbook
 for which I built the image using meego-netbook-ia32-1.1.90.0.20110125.3.ks.
 When compiling the wl_linux.c it throws implicit declaration of function
 'init_MUTEX'. I installed the kernel headers and supposedly that macro is
 declared in semaphore.h. I built that driver on previous MeeGo Netbook
 releases but it won't compile on this one. I am not a kernel hacker, so if
 this is obvious, please forgive me.
 
 init_MUTEX was dropped in 2.6.37 kernel
 
 Grab the src.rpm from slain.org[1] and extract the Mutex and semaphore
 patches from that (or, just use his rpm).
 
 Shane...
 [1] http://slaine.org/_slaine/Meego_1.1_Wifi.html

Actually, now I remember why I didn't post the update for this last week. 

The kernel as it ships with the 1.1.90 builds is blocking the Broadcom driver 
from loading indirectly.

In order to remove the init_MUTEX code from the driver you have to include the 
semaphore headers and use sema_init func in init_MUTEX's place. However, the 
kernel has lockdep rcu debugging enabled which is strictly GPL and by including 
the semaphore.h, including the inline code. When you try and load the Wl 
module, which doesn't specify a license type or if it does should be 
'Mixed/Proprietary', it 'taints' the kernel which then unloads the module. 

I'm not sure if this is a recent addition to the kernels in the 1.1.90 builds 
as I think just patching the init_MUTEX function out of the driver worked ok on 
the 1.1.80 builds.

A work around is to have the wl module report it's license as GPL, but I'm not 
prepared to ship a source rpm that makes those modifications as that's just not 
right.

So, either the MeeGo trunk kernels turn off lockdep rcu debugs or we all spend 
time making the opensource BCM driver work on 2.6.37

Given the proliferation of BCM chipsets out there, this is something that 
should be addressed prior to the 1.2 release.
--
Glen Gray
sla...@slaine.org




___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev


Re: [MeeGo-dev] Broadcom WL on MeeGo Netbook 1.1.90.0.20110125

2011-02-02 Thread Arjan van de Ven

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.

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev


Re: [MeeGo-dev] Broadcom WL on MeeGo Netbook 1.1.90.0.20110125

2011-02-02 Thread Glen Gray

On 2 Feb 2011, at 14:46, Arjan van de Ven 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.
 

It definitely is the path forward, absolutely. Whether it's the path for 1.2 
I'm not so sure. 
--
Glen Gray
sla...@slaine.org




___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev


Re: [MeeGo-dev] Broadcom WL on MeeGo Netbook 1.1.90.0.20110125

2011-02-02 Thread Robinson Tryon
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?

Curious,
--R
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev


Re: [MeeGo-dev] Broadcom WL on MeeGo Netbook 1.1.90.0.20110125

2011-02-01 Thread Sergio Schvezov
On Mon, 2011-01-31 at 22:39 -0800, Shane Bryan wrote:

 On Mon, Jan 31, 2011 at 05:37:51PM -0800, Rudolf Streif wrote:
  I am trying t build the pita Broadcom WL driver module on a MeeGo Netbook
  for which I built the image using meego-netbook-ia32-1.1.90.0.20110125.3.ks.
  When compiling the wl_linux.c it throws implicit declaration of function
  'init_MUTEX'. I installed the kernel headers and supposedly that macro is
  declared in semaphore.h. I built that driver on previous MeeGo Netbook
  releases but it won't compile on this one. I am not a kernel hacker, so if
  this is obvious, please forgive me.
 
 init_MUTEX was dropped in 2.6.37 kernel
 
 Grab the src.rpm from slain.org[1] and extract the Mutex and semaphore
 patches from that (or, just use his rpm).
 


You might need to update to the latest broadcom source as the one linked
there is not avail anymore. Just search broadcom for that driver name as
specified in the spec file


 Shane...
 [1] http://slaine.org/_slaine/Meego_1.1_Wifi.html


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev


Re: [MeeGo-dev] Broadcom WL on MeeGo Netbook 1.1.90.0.20110125

2011-02-01 Thread Rudolf Streif
Thank you. Yes, I did download the latest source from
http://www.broadcom.com/support/802.11/linux_sta.php. The version number is
5.100.82.38 which is the version of the spec file. It's the one I am having
issues with.

Rudi

On Tue, Feb 1, 2011 at 12:27 PM, Sergio Schvezov sergius...@ieee.orgwrote:

  On Mon, 2011-01-31 at 22:39 -0800, Shane Bryan wrote:

 On Mon, Jan 31, 2011 at 05:37:51PM -0800, Rudolf Streif wrote:
  I am trying t build the pita Broadcom WL driver module on a MeeGo Netbook
  for which I built the image using meego-netbook-ia32-1.1.90.0.20110125.3.ks.
  When compiling the wl_linux.c it throws implicit declaration of function
  'init_MUTEX'. I installed the kernel headers and supposedly that macro is
  declared in semaphore.h. I built that driver on previous MeeGo Netbook
  releases but it won't compile on this one. I am not a kernel hacker, so if
  this is obvious, please forgive me.

 init_MUTEX was dropped in 2.6.37 kernel

 Grab the src.rpm from slain.org[1] and extract the Mutex and semaphore
 patches from that (or, just use his rpm).



 You might need to update to the latest broadcom source as the one linked
 there is not avail anymore. Just search broadcom for that driver name as
 specified in the spec file


  Shane...
 [1] http://slaine.org/_slaine/Meego_1.1_Wifi.html



 ___
 MeeGo-dev mailing list
 MeeGo-dev@meego.com
 http://lists.meego.com/listinfo/meego-dev


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev


Re: [MeeGo-dev] Broadcom WL on MeeGo Netbook 1.1.90.0.20110125

2011-02-01 Thread Arjan van de Ven

On 2/1/2011 12:57 PM, Rudolf Streif wrote:
Thank you. Yes, I did download the latest source from 
http://www.broadcom.com/support/802.11/linux_sta.php. The version 
number is 5.100.82.38 which is the version of the spec file. It's the 
one I am having issues with.


not to be an ass about it, but I would suspect that Broadcom is in a 
much better position to support their binary driver
than the MeeGo development list Have you tried asking Broadcom for 
support instead ?


(never mind that this is a development list not an end user help list)

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev


Re: [MeeGo-dev] Broadcom WL on MeeGo Netbook 1.1.90.0.20110125

2011-02-01 Thread Rudolf Streif
I understand your concerns about Broadcom's open-source policy. However,
since I was successfully able to build the very same driver on the MeeGo 1.1
release form October but not with the one from 1/25 the not so far fetched
conclusion is that something changed in MeeGo. Which I now know it did.

Ok, this may not be the right list but one is probably more likely to get an
answer about init_MUTEX on a developer list than on an end-user list.

On Tue, Feb 1, 2011 at 12:58 PM, Arjan van de Ven ar...@linux.intel.comwrote:

 On 2/1/2011 12:57 PM, Rudolf Streif wrote:

 Thank you. Yes, I did download the latest source from
 http://www.broadcom.com/support/802.11/linux_sta.php. The version number
 is 5.100.82.38 which is the version of the spec file. It's the one I am
 having issues with.


 not to be an ass about it, but I would suspect that Broadcom is in a much
 better position to support their binary driver
 than the MeeGo development list Have you tried asking Broadcom for
 support instead ?

 (never mind that this is a development list not an end user help list)


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev