summaryrefslogtreecommitdiffstats
path: root/drivers/usb/serial
diff options
context:
space:
mode:
authorPetko Manolov <petkan@nucleusys.com>2006-09-27 14:25:37 -0700
committerGreg Kroah-Hartman <gregkh@suse.de>2006-09-28 15:36:42 -0700
commit37cf3477d2140f496e0713738fabdb5bc6fd60f3 (patch)
tree162f7a38f3279f03924d80272d9dd723c60c654b /drivers/usb/serial
parent7923811a46f7e29ae8052edf2461e6c6b8ec2415 (diff)
downloadlinux-37cf3477d2140f496e0713738fabdb5bc6fd60f3.tar.gz
linux-37cf3477d2140f496e0713738fabdb5bc6fd60f3.tar.bz2
linux-37cf3477d2140f496e0713738fabdb5bc6fd60f3.zip
USB: Pegasus driver failing for ADMtek 8515 network device
Address http://bugzilla.kernel.org/show_bug.cgi?id=7126 Attempting to read the ethernet ID directly from the eeprom somehow confuses ADM8515. Subsequent read requests to either the eeprom or the MII fail as well. Didn't dig much deeper, though. For example ADM8513 does not experience this problem. I used the fact that at power up the device is reading its ID automatically (not true for older Pegasus based devices) and put it in the Ethernet ID registers. So now the driver uses get_registers() instead of read_eprom_word() if the device is Pegasus_II based one. Tested it with all (Pegasus and Pegasus_II) gadgets i have and everything seems ok. Cc: <jogeedaklown@yahoo.com> Cc: David Brownell <david-b@pacbell.net> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/usb/serial')
0 files changed, 0 insertions, 0 deletions