Benson Leung wrote: > This is disappointing that Atmel decided to change the bootloader > address scheme for the 1664S family. Unfortunately, this ifdef won't > work for situations where there are more than one Atmel device of a > different kind on a system using this same driver. > > For the Chromebook Pixel, we use the same atmel_mxt_ts driver for a > 1664S device and a 224SL. > > The 1664S has the pair 0x26 and 0x4a, while the 224SL has 0x25 and > 0x4b.
If I put a bootloader address override in the platform data will that meet your requirements? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
