88W8305 CF
Marek Vašut
marek.vasut at gmail.com
Thu Feb 22 14:07:36 EST 2007
Dne čtvrtek 22 únor 2007 19:43 jste napsal(a):
> On Thu, 2007-02-22 at 19:06 +0100, Marek Vašut wrote:
> > Hi,
> > Im watching the situation about 8385CF for some time now and I noticed
> > recent Holger´s progress. Well, I also have similar device and Id like to
> > see it working. Actually, it´s a WiFi chip in PDA. SyChip WLAN6061EB
> > which is in fact 88W8305 connected over CF interface. My task, which I
> > assigned to me myself ;) is to make it working in linux. I started
> > investigating this a few months ago when I became bored by porting linux
> > to omap based stuff (palmtt/palmz71) and moved to pxa (palm lifedrive).
> > You can check this thread
> >
> > http://hackndev.com/node/423?from=110&comments_per_page=10
> >
> > I wrote all I know now there. I probably forgot to say I have Palm
> > LifeDrive and Im cooperating on porting linux to it ... hmm ... the
> > project leader broke his device and moved to palmt650 some time ago and
> > Im alone there now :S
> >
> > You can also see this
> > http://www.handhelds.org/moin/moin.cgi/AcerN50Hardware
> > and notice also Marvell 8305 ... I dont have that handheld, but I think
> > it´d help them too ;)
> >
> > So ... what I wanted to ask is whether I can cooperate with you too -
> > porting stuff from 8385CF to 8305CF. Id like also to ask where can I buy
> > some of those 8388 dongles so I wont break your code. Im looking forward
> > for your reply.
>
> That really depends on how similar the 8305 is to the 8388/8385. For
> example, the 8338 is quite different than the 8388 (which OLPC uses).
> If the firmware and hardware interface is quite similar, then maybe it
> should all go in the same driver. But if they are different in
> significant ways, then it should be a separate driver. The only reason
> why the 8388 and 8385 should be the same driver is that the firmware API
> for the two is almost identical, just the bus type is different.
>
> Dan
Hi,
8305=8385 without 80211g support (and maybe something security related like
wpa). There is also 8381 (in PalmTX) which is also b-only but has wpa2 etc. I
´d like to add support for that as soon as I have palmtx available too...
Some press-crap for sychip wlan6061 (88w8305) is here
http://www.sychip.com/PUB/WLAN6061EB.pdf
and for wlan6064 (8381) here
http://www.sychip.com/PUB/WLAN6064EB.pdf
Both of those cards (chips) are for CF and I think the interface is similar,
at least I´d like to give it a try ...
Also see this:
8385 based CF card - manfid: 0x02df, 0x8103
8305 based CF card - manfid: 0x02db, 0x8103
and dump_cis of 8305:
Socket 0:
no CIS present
Socket 1:
dev_info
NULL 0ns, 512b
attr_dev_info
SRAM 450ns, 512b
vers_1 1.0, "SyChip", "Cheetah WLAN Module", "WLAN6061", "01"
manfid 0x02db, 0x8103
funcid network_adapter
lan_technology wireless
lan_speed 1 mb/sec
lan_speed 2 mb/sec
lan_speed 5 mb/sec
lan_speed 11 mb/sec
lan_media 2.4_GHz
lan_node_id 00 02 2d 42 e8 cc
lan_connector Closed connector standard
config base 0x0200 mask 0x0063 last_index 0x01
cftable_entry 0x01 [default]
Vcc Vmin 3V Vmax 3500mV Iavg 300mA Ipeak 300mA
Idown 10mA
io 0x0400-0x0447 [lines=7] [8bit] [16bit] [range]
irq mask 0xffff [level] [pulse]
btw. I know usb8338 is different a lot, I red that too ;)
More information about the libertas-dev
mailing list