Re: CPU revision IDs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Friday 13 June 2014 09:05:14 jonsmirl@xxxxxxxxx wrote:
> I was adding the CPU revision ID to the top level compatible string,
> nothing specific to the device.  By knowing the CPU revision I know
> which errata to apply.
> 
> If you patch the device strings, then you have to maintain knowledge
> of which devices are broken in two places -- the device driver and the
> machine file where you are patching the strings.

IMHO, the driver only has to know what device versions exist, it
shouldn't need to know which soc has which version of the device.

Can you describe which kind of quirk you are looking at in the driver,
and how common it is?

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]
  Powered by Linux