David Hollis wrote:
I'm the current maintainer of the ASIX code in usbnet. I've spent some
time working with ASIX on a driver for the AX88178 device, but it hasn't
gotten to a stable point worth merging at this time. Let's work
together to get this code fixed up so that we can have a stable driver
that doesn't re-invent the wheel.
One of the things I am currently trying to implement is use of the new
PHY abstraction code (in -mm, not mainline at this point) since
according to ASIX, there are many different potential PHY controllers
that might be used with the 178 chip. All of the traffic handling bits
operate the same as the AX88772 chip so it's really just a matter of
handling initialization of the device and handling the PHY.
Sounds good. I'll send you what I have once I've made a pass over it
to clean it up.
My initialization and PHY handling is limited to supporting the one
device I had to test with:
airlink-101 AGIGUSB: http://www.airlink101.com/products/agigausb.html
--Jamie
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
