Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: Use assigned USB VID/PID instead of FTDI #14

Open
broth-itk opened this issue Dec 18, 2020 · 1 comment
Open

Proposal: Use assigned USB VID/PID instead of FTDI #14

broth-itk opened this issue Dec 18, 2020 · 1 comment

Comments

@broth-itk
Copy link

broth-itk commented Dec 18, 2020

See

https://github.com/torvalds/linux/blob/master/drivers/i2c/busses/i2c-tiny-usb.c

Quote:

/*
 * Initially the usb i2c interface uses a vid/pid pair donated by
 * Future Technology Devices International Ltd., later a pair was
 * bought from EZPrototypes
 */
static const struct usb_device_id i2c_tiny_usb_table[] = {
	{ USB_DEVICE(0x0403, 0xc631) },   /* FTDI */
	{ USB_DEVICE(0x1c40, 0x0534) },   /* EZPrototypes */
	{ }                               /* Terminating entry */
};

So:

	.idVendor = 0x1c40,
	.idProduct = 0x0534,

I tested the new IDs and they work fine.

@broth-itk broth-itk changed the title Use assigned USB VID/PID instead of FTDI Proposal: Use assigned USB VID/PID instead of FTDI Dec 18, 2020
@tormodvolden
Copy link

Just for info, here is why it was changed: https://www.mail-archive.com/[email protected]/msg00680.html

However, Till has still not changed the vid/pid in his own i2c-tiny-usb project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants