Not easily. As we discussed before, there is nowhere that really specifies this information. In some cases I've modified the device tree generator to understand what is backward compatible, as with ns16550, but for other cores it makes more sense to me to put this compatibility information with the driver if it has to be anywhere.
Steve > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Grant Likely > Sent: Monday, May 12, 2008 7:25 AM > To: Stephen Neuendorffer > Cc: linuxppc-dev@ozlabs.org > Subject: Re: [PATCH] Xilinx: framebuffer: add compatibility for ml507 dvi core. > > On Mon, May 5, 2008 at 11:59 AM, Stephen Neuendorffer > <[EMAIL PROTECTED]> wrote: > > Signed-off-by: Stephen Neuendorffer <[EMAIL PROTECTED]> > > --- > > drivers/video/xilinxfb.c | 1 + > > 1 files changed, 1 insertions(+), 0 deletions(-) > > > > diff --git a/drivers/video/xilinxfb.c b/drivers/video/xilinxfb.c > > index 848752e..a82c530 100644 > > --- a/drivers/video/xilinxfb.c > > +++ b/drivers/video/xilinxfb.c > > @@ -396,6 +396,7 @@ static int __devexit xilinxfb_of_remove(struct of_device *op) > > /* Match table for of_platform binding */ > > static struct of_device_id xilinxfb_of_match[] __devinitdata = { > > { .compatible = "xlnx,plb-tft-cntlr-ref-1.00.a", }, > > + { .compatible = "xlnx,plb-dvi-cntlr-ref-1.00.c", }, > > Can you get the dvi core to claim compatibility with the tft core > (assuming it is register level backwards compatible)? > > Cheers, > g. > > -- > Grant Likely, B.Sc., P.Eng. > Secret Lab Technologies Ltd. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
