On Tue, Sep 05, 2006 at 04:03:55PM -0400, [EMAIL PROTECTED] wrote:
Where is the best access point for this topic? Did anyone work on this
with MPC8xx? Thanks.
Probably [EMAIL PROTECTED] Is there anything about your wireless
needs that is specific to embedded work?
John
--
John W. Linville
/20060906/3a42d9f1/attachment.htm
Type: text/x-vcard
Size: 324 bytes
Desc: not available
Url :
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060906/2093dd55/attachment.vcf
FWIW, in my experience the hardware independent parts of the
networking stack are
very stable and the problem is almost always with the drivers, or with
the IP
configuration (e.g. two interfaces on the same subnet).
I have no doubt it is with the driver. I am somewhat fortunate in
On Tue, Sep 05, 2006 at 04:03:55PM -0400, wei.li4 at elf.mcgill.ca wrote:
Where is the best access point for this topic? Did anyone work on this
with MPC8xx? Thanks.
Probably netdev at vger.kernel.org. Is there anything about your wireless
needs that is specific to embedded work?
John
--
On Wed, Sep 06, 2006 at 09:30:00AM +0800, Chun Chung Lo wrote:
1. WLAN card driver: linux-wlan -- http://www.linux-wlan.org/
Is this project even still active? The last update to the page was
2.5 years ago (2/2004), and many of the links are broken...
Do the prism drivers in the upstream
I have no doubt it is with the driver. I am somewhat
fortunate in
this instance that I have a nearly identical setup - this
is an FPGA
based system
I can swap the FPGA firmware, get an almost identical
kernel with
a slightly different NIC, and everything works - same
On 9/6/06, Clint Thomas cthomas at soneticom.com wrote:
Hey,
I'm running the latest kernel pull from the mvista powerpc 2.4 dev source. I
built a root file system using Busybox 1.2.0 and the mkrootfs script by
Wolfgang Klingauf (removed all DOS carriage returns). When the system boots
up,
