From: Martin List-Petersen <martin@list-petersen.dk>
To: linux-kernel@vger.kernel.org
Cc: "David S. Miller" <davem@redhat.com>,
Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>,
bas.mevissen@hetnet.nl
Subject: RE: Broadcom BCM4306/BCM2050 support
Date: Tue, 29 Apr 2003 14:58:40 +0200 [thread overview]
Message-ID: <1051621120.3eae7700b1586@roadrunner.hulpsystems.net> (raw)
In-Reply-To: <472501c30e4a$c596d0b0$d16897c2@hetnet.nl>
Citat bas.mevissen@hetnet.nl:
> > /me wants binary only driver for these cards to build opensource driver
> > with ability to set "interesting" frequency range.
>
> > Carl-Daniel
>
> But I don't want to read in the papers that Linux was used as an illegal
> hacker tool to snoop into mil stuff...
Ehh .. no .. probably wouldn't be nice, but you cat do stuff like that on any
OS, so that doesn't really matter.
For my case, i would be glad if I just could do 802.11b on these cards right
now. 802.11g and 802.11a would be nice though.
However, if it is like that (the chip supports all frequencies), that would
mean, that a TrueMobile 1300 and TrueMobile 1400 practically is the same card.
(TM1300: 802.11b/g, TM1400: 802.11a/b/g)
Another thing about the TM1400 is, that it has 2 MAC adresses, but that's
probably due to, that 802.11a operates on another frequency than 802.11b/g (one
MAC is assigned to 802.11a, the other one to 802.11g).
Regards,
Martin List-Petersen
martin at list-petersen dot dk
--
The probability of someone watching you is proportional to the
stupidity of your action.
next prev parent reply other threads:[~2003-04-29 12:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 12:28 Broadcom BCM4306/BCM2050 support bas.mevissen
2003-04-29 12:58 ` Martin List-Petersen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-01 13:35 Martin List-Petersen
2003-05-01 13:22 bas.mevissen
2003-04-29 16:58 harry
2003-04-29 21:19 ` Oliver Neukum
2003-04-29 15:22 Nicholas Berry
2003-04-29 12:51 bas.mevissen
2003-04-29 14:40 ` Stuffed Crust
2003-05-01 11:01 ` David S. Miller
2003-04-29 6:16 Martin List-Petersen
2003-04-29 11:06 ` David S. Miller
2003-04-29 11:38 ` Carl-Daniel Hailfinger
2003-04-29 12:12 ` Martin List-Petersen
2003-04-29 12:27 ` Grzegorz Jaskiewicz
2003-04-29 13:26 ` Richard B. Johnson
2003-04-29 13:18 ` Alan Cox
2003-04-29 14:45 ` Stuffed Crust
2003-04-29 13:48 ` Carl-Daniel Hailfinger
2003-04-29 13:28 ` Alan Cox
2003-04-28 15:53 bas.mevissen
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=1051621120.3eae7700b1586@roadrunner.hulpsystems.net \
--to=martin@list-petersen.dk \
--cc=bas.mevissen@hetnet.nl \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=davem@redhat.com \
--cc=linux-kernel@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).