From: Bill Davidsen <davidsen@tmr.com>
To: marado@isp.novis.pt
Cc: Linux-kernel@vger.kernel.org, fawadlateef@gmail.com,
s0348365@sms.ed.ac.uk, hostmaster@ed-soft.at,
jerome.lacoste@gmail.com, carlsj@yahoo.com
Subject: Re: New Linux Development Model
Date: Sat, 12 Nov 2005 08:45:34 -0500 [thread overview]
Message-ID: <4375F1FE.9060509@tmr.com> (raw)
In-Reply-To: <1131567020.8930.74.camel@noori.ip.pt>
Marcos Marado wrote:
>On Wed, 2005-11-09 at 14:05 -0500, Bill Davidsen wrote:
>
>
>
>>With the current firmware and driver a "scan" shows 14 connectible
>>points outside an apartment building (only one secured in any way ;-)
>>whic is just what Windows shows. With the stock kernel zero are found.
>>That's not stable that's moribund.
>>
>>
>
>Sorry to disagree, but I use the stock kernel version of ipw2100 almost
>daily, with no problems.
>
>
>
Well if ipw2100 works on one machine for one person, obviously ipw2200
must be correct as well. I never said they didn't work anywhere, and I
have no old 2100 hardware.
But the new {firm,soft}ware works and gives the same results as XP,
while the default says there are no usable signals in range. And like it
or not, it has to work at least as well as Windows on the same machine
to be considered functional. Many devices work better.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2005-11-12 13:36 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 1:47 New Linux Development Model Ian Kumlien
2005-11-09 11:08 ` Marcos Marado
2005-11-09 11:30 ` Ian Kumlien
2005-11-09 12:03 ` Wed, 9 Nov 2005 13:03:07 +0100
2005-11-09 15:49 ` Ian Kumlien
2005-11-09 15:58 ` Al Viro
2005-11-09 16:32 ` Ian Kumlien
2005-11-09 12:37 ` Marcos Marado
2005-11-09 16:01 ` Ian Kumlien
2005-11-10 0:55 ` Alistair John Strachan
2005-11-10 15:10 ` Mark Lord
2005-11-10 19:29 ` Alistair John Strachan
2005-11-10 19:47 ` Ian Kumlien
2005-11-09 19:05 ` Bill Davidsen
2005-11-09 20:10 ` Marcos Marado
2005-11-10 0:57 ` Alistair John Strachan
2005-11-10 20:08 ` Bill Davidsen
2005-11-10 20:21 ` Alistair John Strachan
2005-11-12 13:45 ` Bill Davidsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-05 9:42 hostmaster
2005-11-05 10:29 ` Francois Romieu
2005-11-05 11:29 ` Jean Delvare
2005-11-05 13:19 ` Edgar Hucek
2005-11-05 13:44 ` Adrian Bunk
2005-11-05 13:47 ` Alistair John Strachan
2005-11-05 22:23 ` Mark Lord
2005-11-06 0:28 ` Alistair John Strachan
2005-11-05 14:34 ` Jesper Juhl
2005-11-05 14:48 ` Oliver Neukum
2005-11-05 14:56 ` Fawad Lateef
2005-11-05 15:28 ` Adrian Bunk
2005-11-06 10:52 ` jerome lacoste
2005-11-06 11:55 ` Edgar Hucek
2005-11-06 12:39 ` Adrian Bunk
2005-11-06 12:57 ` Bernd Petrovitsch
2005-11-06 17:38 ` Jean Delvare
[not found] ` <436DEEFC.4020301@ed-soft.at>
2005-11-06 13:43 ` jerome lacoste
2005-11-09 0:11 ` caszonyi
2005-11-09 0:23 ` Con Kolivas
2005-11-09 7:00 ` Diego Calleja
2005-11-09 12:30 ` jerome lacoste
2005-11-09 14:03 ` caszonyi
2005-11-09 15:45 ` Marcos Marado
2005-11-06 16:50 ` John Carlson
2005-11-06 18:17 ` Bernd Petrovitsch
2005-11-09 0:16 ` caszonyi
2005-11-06 15:22 ` Jim Nance
2005-11-06 16:55 ` John Carlson
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=4375F1FE.9060509@tmr.com \
--to=davidsen@tmr.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=carlsj@yahoo.com \
--cc=fawadlateef@gmail.com \
--cc=hostmaster@ed-soft.at \
--cc=jerome.lacoste@gmail.com \
--cc=marado@isp.novis.pt \
--cc=s0348365@sms.ed.ac.uk \
/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