linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ian <ischram@telenet.be>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Marvell pci wifi chips
Date: Thu, 09 Aug 2007 11:27:13 +0200	[thread overview]
Message-ID: <46BADDF1.9080604@telenet.be> (raw)
In-Reply-To: <a728f9f90708082243u2e66e84cjeed8856722c4bea5@mail.gmail.com>

it appears to be using files from the madwifi project.

ian

Alex Deucher wrote:
> On 8/8/07, Alex Deucher <alexdeucher@gmail.com> wrote:
>> On 8/7/07, John W. Linville <linville@tuxdriver.com> wrote:
>>> On Tue, Aug 07, 2007 at 12:21:02PM -0400, Alex Deucher wrote:
>>>> Is anyone working on a driver for the marvell pci libertas chips
>>>> (8335, 8300, 8310, etc.) or know of someone who is?  I've got several
>>>> of these cards not doing anything at the moment if someone is
>>>> interested in one.  It seems there are several drivers floating
>>>> around:
>>>>
>>>> - mrv8k driver (http://www.saillard.org/linux/mrv8k/)
>>>> - openbsd malo driver (http://www.openbsd.org/cgi-bin/man.cgi?query=malo)
>>>> - marvell GPL driver (http://johannes.sipsolutions.net/files/marvell.tar.bz2)
>>>>
>>>> Reading through the linux-wireless archive, several people seemed to
>>>> indicate there was work going on, but I have not been able to find any
>>>> information on that other than Holger's CF libertas integration.  I
>>>> and others have asked before, but there seems to be some confusion as
>>>> to the whole libertas line and their relative compatibility.  Just
>>>> curious.
>>> I think I saw discussion lately to the effect that the PCI devices are
>>> not currently supported, and that they likely could be supported by
>>> simply implementing a PCI front-end to the core of the libertas code.
>>> I think Holger is the person most likely to know for sure.
>>>
>>> I've got cards like that too -- would love for you to get them
>>> working... :-)
>> Has anyone tested the marvell driver
>> (http://johannes.sipsolutions.net/files/marvell.tar.bz2)?  Does it
>> work?
> 
> I attempted to build the driver on 2.6.22, but I got the following
> errors.  Unfortunately, I'm not too familiar with the net80211 stuff.
> Anyone got any ideas?
> 
>   CC [M]  drivers/net/wireless/marvell_softap/driver/mwl_debug.o
> In file included from drivers/net/wireless/marvell_softap/driver/mwl_main.h:42,
>                  from drivers/net/wireless/marvell_softap/driver/mwl_debug.h:42,
>                  from drivers/net/wireless/marvell_softap/driver/mwl_debug.c:26:
> drivers/net/wireless/marvell_softap/driver/mwl_descriptors.h:72:
> warning: 'packed' attribute ignored
> drivers/net/wireless/marvell_softap/driver/mwl_descriptors.h:90:
> warning: 'packed' attribute ignored
> In file included from drivers/net/wireless/marvell_softap/driver/mwl_main.h:43,
>                  from drivers/net/wireless/marvell_softap/driver/mwl_debug.h:42,
>                  from drivers/net/wireless/marvell_softap/driver/mwl_debug.c:26:
> drivers/net/wireless/marvell_softap/driver/mwl_wlanext.h:37:26: error:
> if_ethersubr.h: No such file or directory
> drivers/net/wireless/marvell_softap/driver/mwl_wlanext.h:38:22: error:
> if_media.h: No such file or directory
> drivers/net/wireless/marvell_softap/driver/mwl_wlanext.h:39:20: error:
> if_llc.h: No such file or directory
> drivers/net/wireless/marvell_softap/driver/mwl_wlanext.h:40:27: error:
> ieee80211_var.h: No such file or directory
> In file included from drivers/net/wireless/marvell_softap/driver/mwl_debug.h:42,
>                  from drivers/net/wireless/marvell_softap/driver/mwl_debug.c:26:
> drivers/net/wireless/marvell_softap/driver/mwl_main.h:44:29: error:
> ieee80211_proto.h: No such file or directory
> In file included from drivers/net/wireless/marvell_softap/driver/mwl_debug.h:42,
>                  from drivers/net/wireless/marvell_softap/driver/mwl_debug.c:26:
> drivers/net/wireless/marvell_softap/driver/mwl_main.h:125: error:
> field 'beaconOffsets' has incomplete type
> drivers/net/wireless/marvell_softap/driver/mwl_main.h:129: error:
> field 'node' has incomplete type
> drivers/net/wireless/marvell_softap/driver/mwl_main.h:200: warning:
> 'enum ieee80211_state' declared inside parameter list
> drivers/net/wireless/marvell_softap/driver/mwl_main.h:200: warning:
> its scope is only this definition or declaration, which is probably
> not what you want
> drivers/net/wireless/marvell_softap/driver/mwl_main.h:200: warning:
> 'struct ieee80211com' declared inside parameter list
> drivers/net/wireless/marvell_softap/driver/mwl_main.h:201: warning:
> 'struct ieee80211com' declared inside parameter list
> drivers/net/wireless/marvell_softap/driver/mwl_main.h:204: warning:
> 'struct ieee80211com' declared inside parameter list
> drivers/net/wireless/marvell_softap/driver/mwl_main.h:208: warning:
> 'struct ieee80211com' declared inside parameter list
> drivers/net/wireless/marvell_softap/driver/mwl_main.h:231: error:
> field 'curr80211com' has incomplete type
> drivers/net/wireless/marvell_softap/driver/mwl_main.h:232: error:
> field 'initialOpmode' has incomplete type
> drivers/net/wireless/marvell_softap/driver/mwl_main.h:233: error:
> field 'currChannel' has incomplete type
> make[4]: *** [drivers/net/wireless/marvell_softap/driver/mwl_debug.o] Error 1
> make[3]: *** [drivers/net/wireless/marvell_softap] Error 2
> make[2]: *** [drivers/net/wireless] Error 2
> make[1]: *** [drivers/net] Error 2
> make: *** [drivers] Error 2
> 
> 
> Thanks,
> 
> Alex
> -
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 

  reply	other threads:[~2007-08-09 11:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-07 16:21 Marvell pci wifi chips Alex Deucher
2007-08-07 17:34 ` John W. Linville
2007-08-08  4:29   ` Alex Deucher
2007-08-08  6:48     ` Holger Schurig
2007-08-08  9:36       ` Johannes Berg
2007-08-09  5:43     ` Alex Deucher
2007-08-09  9:27       ` ian [this message]
2007-08-08 11:19   ` Dan Williams
2007-08-08  6:48 ` Holger Schurig

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=46BADDF1.9080604@telenet.be \
    --to=ischram@telenet.be \
    --cc=alexdeucher@gmail.com \
    --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).