I've you're seriously going to hack together a driver for this, I can send you one of my cards...

I'd consider taking a crack at writing a driver for one. It looks like all the audio is handled through a headphone jack on the card itself (likely to simplify the interface and use the headphone cord as an antenna), so the "driver" for the card is purely for tuning and volume.

I am also attempting writing a driver for it. I have bought one card from local dealer, the price seems to be acceptable so I just bought it. Don't know the difference between mine ProLink FM201 and the Ambicom one, they look identical, so may use the same chip or pcb. It will make us a little happier. In fact, a little surfing, I got a better price from buy.com: $31.25http://www.buy.com/retail/product.asp?sku=...hdwt=22114&sp=1 Mine from local dealer was even lower than this price, which made me happy.

What astonished myself is the driver part, mine comes with a floppy disk, thanks to my desktop, it can still handle it. Search from web returns the identical driver. I'm now turning to Ambicom's driver for more information.

I would like to discuss with you guys on the right approach for hacking a working driver for CF devices with only CE driver. Both CE driver and Linux driver may rely on the underline PCMCIA controller, which encapulates some PCMCIA support, so we may only need to hack the layer above this. The CE driver itself exports several routines, which seems to be the INIT/READ/WRITE/SEEK driver part, we can rely on these routines for more information. On linux part, it seems that we may program in the V4L way. More work needs to be done for me.

Oops, It seems that my hardware is different from the Ambicom's one, in spite of they do come from the same designer: ProLink, but it seems that mine is FM201, while the Ambicom's is FM203. Any WinXP usage report? Can you guys use Ambicom's card function correctly? Even after hack the inf part, which made the driver work with my FM201, it seems that it doesn't function correctly. It seems that I need to buy a new one in US.

I just donated an initial installment of $25 to your account to get started. I rely on you to match the donation, coordinate the effort and keep us informed.

The other $25 I will donate as soon as I test the driver+GUI on the hardware in my sig.

QUOTE(kahm @ Jun 4 2005, 11:54 PM)

I'd consider taking a crack at writing a driver for one. It looks like all the audio is handled through a headphone jack on the card itself (likely to simplify the interface and use the headphone cord as an antenna), so the "driver" for the card is purely for tuning and volume.

What does the card get recognized as when it's inserted?

Well, I am happy things might be easier than expected.I do hope, however, that any option to use the speaker of the 5600 will be pursued -- I am ready to be tester for this along with anything else.

I would expect the GUI to have (some of) these controls: * a Power-On/Off button* a Mute button* Automatic/Manual Tuning start-button* a Volume button* a couple of Presets buttons and an option to store presets* an option to set the frequency (range) for the US/Europe/JapanA sliding ruler to visualize the tuning and allow for manual adjustment might be nice, but in no way mandatory. A digital-clock-type frequency counter might be enough.

Oops, It seems that my hardware is different from the Ambicom's one, in spite of they do come from the same designer: ProLink, but it seems that mine is FM201, while the Ambicom's is FM203. Any WinXP usage report? Can you guys use Ambicom's card function correctly? Even after hack the inf part, which made the driver work with my FM201, it seems that it doesn't function correctly. It seems that I need to buy a new one in US.

I don't know about the differences with the Prolink Card, and I do not have XP.However under Win2K with the drivers on the enclosed CD the card works well (only the sensitivity is a bit low and the GUI is quite ugly.)

I bought mine new and unopened on EBay for about $25. Unfortunately, currently there are no offerings. I'd suggest you ask offroadgeek to send you one of his as he kindly offered.

Oops, It seems that my hardware is different from the Ambicom's one, in spite of they do come from the same designer: ProLink, but it seems that mine is FM201, while the Ambicom's is FM203. Any WinXP usage report? Can you guys use Ambicom's card function correctly? Even after hack the inf part, which made the driver work with my FM201, it seems that it doesn't function correctly. It seems that I need to buy a new one in US.

I don't know about the differences with the Prolink Card, and I do not have XP.However under Win2K with the drivers on the enclosed CD the card works well (only the sensitivity is a bit low and the GUI is quite ugly.)

I bought mine new and unopened on EBay for about $25. Unfortunately, currently there are no offerings. I'd suggest you ask offroadgeek to send you one of his as he kindly offered.

1.Referenced the Radio TrackII driver in Linux driver for some information on FM card working model2.Read documents on V4L for FM card control3.Reference wireless pcmcia driver for PCMCIA service control and programming 4.Dig the internet for available information on the card5.Disassemble the PPC and XP version drivers for more information

A little finding: PPC's PCMCIA interface seems to be similiar to Linux's. Card configuration may be available in PCMCIA Card Information Structure part. I will try to find out whether it is feasible or not.

Today, verified the chip used in the CompactFlash card, which was refused by AmbiCom's technical support to provide. The CF card itself is easy to unpack, I will attach the photo taken when it was naked.

The chip used is Philips TEA5767, seems to be widely used. I will also attach the datasheet for it.

CE's driver part seems to be endless, I was so hard at reading the code, but it seems without datasheet, it's too difficult to do reverse-engineering.

A little search with Linux showed that the chip with I2C was contributed by developers and provided as patch to 2.6.12, so life seems to be a little better.