This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: WaveLAN PCMCIA network driver
- To: "'Todd Malsbary'" <toddm at iobjects dot com>,"'eCos Discussion'" <ecos-discuss at sourceware dot cygnus dot com>
- Subject: RE: [ECOS] WaveLAN PCMCIA network driver
- From: "Trenton D. Adams" <tadams at extremeeng dot com>
- Date: Tue, 9 Oct 2001 11:11:03 -0600
- Organization: Extreme Engineering
Actually, so do I! :) I was looking at two different source code files.
My old one was MANFID and the new one was using VERS_1 so I was getting
the version information not Manufacturer information. So, mine is as
you said 0x0156!
Do you have a working eCos driver for your WaveLAN cards? If so, would
you be interested in sending it over? The one I got from Andrea didn't
have the headers to go with it.
> -----Original Message-----
> From: Todd Malsbary [mailto:toddm@iobjects.com]
> Sent: Tuesday, October 09, 2001 10:53 AM
> To: Trenton D. Adams; eCos Discussion
> Subject: RE: [ECOS] WaveLAN PCMCIA network driver
>
>
> I've got an Orinoco WaveLAN card that reports 0x0156 as the
> manufacturer
> ID at offset 2 after cf_get_CIS(). That's worked for me on all the
> Orinoco cards that we have here.
>
> Todd
>
> > -----Original Message-----
> > From: Trenton D. Adams [mailto:tadams@extremeeng.com]
> > Sent: Tuesday, October 09, 2001 8:25 AM
> > To: eCos Discussion
> > Subject: [ECOS] WaveLAN PCMCIA network driver
> >
> >
> > I finally got the CL-PS6700 going. The documentation failed
> > to mention
> > one small thing that caused it not to work.
> >
> > Anyhow...
> >
> >
> > I'm looking at "dev/if_sc_lpe.c". I noticed that it checks for the
> > manufacturer ID of 0x0104 at offset 2 of the buffer after calling
> > cf_get_CIS (). Is this likely going to be at a different
> offset into
> > the MANFID for every single card? My wavelan card goes
> 0x15 0x50 0x05
> > starting at offset 0 into the MANFID. It then goes "Lucent
> > Technologies", "WaveLAN/IEEE" and finally "Version 01.01".
> >
> > I'm not sure what the 0x15 0x50 and 0x05 represent, but I haven't
> > received the documentation that Orinoco promised me yet.
> > Maybe I should
> > just check for the first two strings when writing my driver? That's
> > assuming of course all future WaveLAN cards will work in the
> > same way as
> > my version 1.1 card. Of course anyone that finds any different can
> > modify the driver to check for those cases. Right?
> >
> >
> >
> > Trenton D. Adams
> > Extreme Engineering
> > #17, 6025 - 12 St. SE
> > Calgary, Alberta, Canada
> > T2H 2K1
> >
> > Phone: 403 640 9494 ext-208
> > Fax: 403 640 9599
> >
> > http://www.extremeeng.com
> >
> >
>