Message ID | 5458E605.6070801@gmail.com |
---|---|
State | Accepted, archived |
Delegated to: | David Miller |
Headers | show |
On 11/04/2014 03:43 PM, Chen Gang wrote: > Microblaze is a fpga soft core, it can be customized easily, which may > cause many various hardware version strings. > > So the original fix patch based on hard-coded compatible version strings > is not a good idea (although it is correct for current issue). For it, > there will be a new solving way soon (which based on the device tree). > > The original issue is related with qemu, so can only change the hardware > version string in qemu for it, then keep the original driver no touch ( > qemu is for virtualization which has much easier life than real world). > > > Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com> > --- > drivers/net/ethernet/xilinx/xilinx_emaclite.c | 1 - > 1 file changed, 1 deletion(-) Acked-by: Michal Simek <michal.simek@xilinx.com> Thanks, Michal -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Michal Simek <michal.simek@xilinx.com> Date: Wed, 5 Nov 2014 08:19:41 +0100 > On 11/04/2014 03:43 PM, Chen Gang wrote: >> Microblaze is a fpga soft core, it can be customized easily, which may >> cause many various hardware version strings. >> >> So the original fix patch based on hard-coded compatible version strings >> is not a good idea (although it is correct for current issue). For it, >> there will be a new solving way soon (which based on the device tree). >> >> The original issue is related with qemu, so can only change the hardware >> version string in qemu for it, then keep the original driver no touch ( >> qemu is for virtualization which has much easier life than real world). >> >> >> Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com> >> --- >> drivers/net/ethernet/xilinx/xilinx_emaclite.c | 1 - >> 1 file changed, 1 deletion(-) > > Acked-by: Michal Simek <michal.simek@xilinx.com> Applied, thanks. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/drivers/net/ethernet/xilinx/xilinx_emaclite.c b/drivers/net/ethernet/xilinx/xilinx_emaclite.c index 298fad3..28dbbdc 100644 --- a/drivers/net/ethernet/xilinx/xilinx_emaclite.c +++ b/drivers/net/ethernet/xilinx/xilinx_emaclite.c @@ -1236,7 +1236,6 @@ static struct of_device_id xemaclite_of_match[] = { { .compatible = "xlnx,opb-ethernetlite-1.01.b", }, { .compatible = "xlnx,xps-ethernetlite-1.00.a", }, { .compatible = "xlnx,xps-ethernetlite-2.00.a", }, - { .compatible = "xlnx,xps-ethernetlite-2.00.b", }, { .compatible = "xlnx,xps-ethernetlite-2.01.a", }, { .compatible = "xlnx,xps-ethernetlite-3.00.a", }, { /* end of list */ },
Microblaze is a fpga soft core, it can be customized easily, which may cause many various hardware version strings. So the original fix patch based on hard-coded compatible version strings is not a good idea (although it is correct for current issue). For it, there will be a new solving way soon (which based on the device tree). The original issue is related with qemu, so can only change the hardware version string in qemu for it, then keep the original driver no touch ( qemu is for virtualization which has much easier life than real world). Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com> --- drivers/net/ethernet/xilinx/xilinx_emaclite.c | 1 - 1 file changed, 1 deletion(-) -- davem@davemloft.net 1.9.3 -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html