linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: George Chriss <GChriss@openvideo.pro>
Cc: linux-wireless@vger.kernel.org, libertas-dev@lists.infradead.org
Subject: Re: libertas on ETRAX FS / Elphel 353?
Date: Fri, 17 Jun 2011 10:46:19 -0400	[thread overview]
Message-ID: <4DFB68BB.5070902@gnu.org> (raw)
In-Reply-To: <40525.74.64.51.206.1308265716.squirrel@openvideo.pro>

On 06/16/2011 07:08 PM, George Chriss wrote:

> Is libertas support for this embedded system feasible?  I attempted to
> build compat-wireless against the Elphel kernel sources and successfully
> generated a long list of errors with 'make --keep-going' after commenting
> out unnecessary parts of the Makefile.  The build log may be found at [4].

If it's a one-off effort for one driver, I think it should be possible. 
  MadWifi (current snapshots) supports kernels from 2.4.22 to 3.0, and 
the compatibility layer is not very thick.

Many errors in that log come from the compatibility code you are not 
going to need, such as MSI support.

INIT_WORK changes are tricky, but it should be easier to backport the 
code than it was to forward port it.  MadWifi could be used as a reference.

You probably don't want mesh support.  Try disabling as all the code 
that can be disabled.

I don't know how intrusive USB changes have been.  Basically, until you 
try, there is no way to tell how hard it might be.

compat-wireless didn't go to older kernels because it needs to be 
constantly maintained and because it supports multiple drivers.

-- 
Regards,
Pavel Roskin

      reply	other threads:[~2011-06-17 14:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16 23:08 libertas on ETRAX FS / Elphel 353? George Chriss
2011-06-17 14:46 ` Pavel Roskin [this message]

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=4DFB68BB.5070902@gnu.org \
    --to=proski@gnu.org \
    --cc=GChriss@openvideo.pro \
    --cc=libertas-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.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).