kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: shrey.linux@gmail.com (Shreyansh Jain)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Problem compiling BCM Wireless driver on 2.6.37 (lib80211 symbol issue)
Date: Sun, 20 Mar 2011 23:42:36 +0530	[thread overview]
Message-ID: <AANLkTinqQj6tmYK9ZxAH3kecMKscCTRgPL4WTaR_yJ04@mail.gmail.com> (raw)
In-Reply-To: <20110320155809.GA15283@kroah.com>

Hi Greg

On Sun, Mar 20, 2011 at 9:28 PM, Greg KH <greg@kroah.com> wrote:
> On Sun, Mar 20, 2011 at 09:04:21PM +0530, Shreyansh Jain wrote:
>> Dear List,
>>
>> I recently compiled and booted up the 2.6.37 kernel on my Ubuntu
>> (10.04), from 2.6.36.1. I have been trying to compile the Broadcom
>> Wireless driver on 2.6.37, after making some changes in the source
>> code. Just to add, this driver has been working fine on 2.6.36.1 which
>> my machine ran earlier.
>
> <snip>
>
> Why not ask the authors of that code? ?As it is closed source, they are
> the only ones that can legally help you out.

Well, I have not considered asking the authors because I have the
code, I can successfully compile it and then, unable to link to the
kernel because of a missing function which is present in another
module and exported in the kernel.

Yes, this driver might not be GPL'd, but I certainly have its code. As
for help on compilation, if a source code is not getting compiled and
giving a common error like symbol not found (and that symbol being
present in another GPL'd module), any issue of the code not GPL
shouldn't prevent the code from being compiled-linked-loaded.
Probably, Its just that I am missing some basic point (of a random
kernel module compilation-loading) which I am not able to figure out.

And yes, thanks for your suggestion - I will search for an appropriate
list (specific for this driver) and post there as well.

>
> Or you could try the 2.6.38 kernel which has support for this hardware
> already in it...

Certainly that is an option - its just that I haven't yet compiled the
2.6.38 kernel. In case nothing works out on this issue, I would take
this path. But, not before understanding why this is not working.

>
> best of luck,

Thanks!

>
> greg k-h
>

Shreyansh

  reply	other threads:[~2011-03-20 18:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-20 15:34 Problem compiling BCM Wireless driver on 2.6.37 (lib80211 symbol issue) Shreyansh Jain
2011-03-20 15:58 ` Greg KH
2011-03-20 18:12   ` Shreyansh Jain [this message]
2011-03-20 18:50     ` Greg KH
2011-03-21  8:04       ` Shreyansh Jain

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTinqQj6tmYK9ZxAH3kecMKscCTRgPL4WTaR_yJ04@mail.gmail.com \
    --to=shrey.linux@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).