From: David Williams <franzferdinand2@blueyonder.co.uk>
To: linux-wireless@vger.kernel.org
Subject: WUSB54G v1 and latest wireless git tree
Date: Sat, 19 May 2007 10:33:35 +0100 [thread overview]
Message-ID: <464EC46F.3030904@blueyonder.co.uk> (raw)
hey guys this will be my first post. yesterday i got bored so i thought
i would look into the status of native support for my above mentioned
adaptor. i hit #prsim54 got talking to a couple of the guys there and
ended up getting the wireless-dev git tree and compiling it. i was
impressed the adaptor attempted to connect but quickly hung the system.
it did produce a bunch of errors in /var/log/messages but becasue i had
to hard reset the machine i lost them. i could easily reproduce it if
you would like.
i'm running suse 10.2 atm and all of the relevent networking stuff is as
of the most recent updates. i use wpa and a mac filter on my network and
the system is entirley 32bit. if you need any info, or even (lol), my
help let me know. i laugh coz i'm not exactly the most capable kernel
dev out there. in fact i would say - when it come to the kernel - i'm
nothing more than a very slightly experienced, intreged newbie
anyway if you need anything gimme a shout
reply other threads:[~2007-05-21 6:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=464EC46F.3030904@blueyonder.co.uk \
--to=franzferdinand2@blueyonder.co.uk \
--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).