On Wed, Aug 15, 2007 at 11:00:47PM +0200, Ulrich Kunitz wrote:
> Forest Bond wrote:
> > >> I hope this is enough info to get this working in mainline.
> > 
> > > Not really, we need to find another way to identify the chip.
> > 
> > It wouldn't be something you could find in /proc/bus/usb/devices, would it?
> I don't think so, I'm thinking more specific entries in the
> EEPROM. We would need a debug version that dumps the EEPROM before
> we load the firmware. We will have to find data at some offset,
> which reliably would tell us, whether we deal with a ZD1211B
> instead of a ZD1211. Just classical reverse engineering. If I have
> such code ready I would send it to you and I would need your dump. I
> happened to own the old PN18 and so we could compare the EEPROM
> contents and do something with this. But don't expect any working
> code before the weekend.

Ok.  I'm not in a huge rush, although it would be nice to see this work out
positively.  I'm available to help out however I can.

> > Ah, so you can't use a EAFP/trial-and-error approach (and LBYL is not an
> > option due to the chip not making any mechanism available by which it can be
> > identified)?
> I don't want to try it, we had several problems with reloading
> issues.

Got it.

Forest Bond

Attachment: signature.asc
Description: Digital signature

This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

Reply via email to