This patch: Big endian support for megaraid_sas driver is not complete. In few areas, we need to do changes like this patch does not have changes for Thunderbolt/invader/Fury controllers(file: megaraid_sas_fusion.c), and needs few changes in file: megaraid_sas_fp.c(while host reads some member of raidmap, it needs endianness change there also).. LSI has megaraid_sas driver with big endian support for driver version "06.506.00.00". But to add big endian support for latest upstream megaraid_sas driver (06.600.18.00), we need to make some more changes. We will get back with big endian support patch on top of latest upstream megaraid_sas driver. Sumit >-----Original Message----- >From: Martin K. Petersen [mailto:martin.petersen@xxxxxxxxxx] >Sent: Friday, August 16, 2013 6:42 AM >To: Ben Collins >Cc: Martin K. Petersen; DL-MegaRAID Linux; linux-scsi; >aradford@xxxxxxxxx >Subject: Re: State of big-endian for MegaRAID SAS driver > >>>>>> "Ben" == Ben Collins <ben.c@xxxxxxxxxxxx> writes: > >Ben, > >Ben> Considering your patch has had two success stories (I suspect yours >Ben> was on SPARC, so that would even make two different platforms) and >Ben> low likelihood of regression on little endian, I think it's pretty >Ben> safe. > >I ordered a MegaRAID card today so I can test on x86 just to be sure. > > >Ben> The only thing I think that could make it better is to annotate the >Ben> structures in megaraid_sas.h as __le32 where applicable. > >I have an older patch that does just that. And another one that gets rid >of the 32-bit DMA limitations on large systems. But I didn't want to >clutter the initial submission. > >-- >Martin K. Petersen Oracle Linux Engineering -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
