>
> https://bugzilla.redhat.com/show_bug.cgi?id=288421
>
> When running Fedora on a Dell 2950 w/ integrated LSI Perc5i
(megaraid), the
> system will not boot after upgrading to 2.6.22. The boot message
indicates the
> system is somehow seeing through RAID, cannot access logical volume.
This
> ca
>
> Hello Sreenivas,
>
> > We have already been alerted (by OEMs among others) that the modinfo
on
> > megaswr driver needlessly shows "GPL" as the license. Ours is a
binary
> > only proprietary driver. I have since corrected the MODULE_LICENSE
label
> > to "LSI Proprietary" and updated the OEM v
Hello Fred,
>
> There's a LSI 1068 chip that can be found on NEC hardware (also
> Intel/Supermicro/Hitachi, ...) and that can provide RAID 0 and 1 based
> on a MegaRAID BIOS.
>
Hmm, no. This is not MegaRAID BIOS.
>
> - LSI1068 'MegaRAID':
> pciid 1000:0055
> embedded MegaRAID BIOS, providing
>
>This patch reduces stack usage in megasas_probe_one() from to 2200 to
>156. A patched version of gcc 3.4.3 with -fno-unit-at-a-time disabled
>was used on i386 platform.
>
>Signed-off-by: Yum Rayan <[EMAIL PROTECTED]>
Rayan,
Thanks. I will be submitting shortly a consolidated patch that include
>On Sat, Mar 12, 2005 at 03:42:22AM -0800, Andrew Morton wrote:
>>...
>> All 606 patches:
>>...
>> megaraid_sas-announcing-new-module-for.patch
>> megaraid_sas: Announcing new module for LSI Logic's SAS
>based MegaRAID controllers
>>...
>
>Enormous stack usage:
>- megasas_init_mfi (due to ctrl_i
>
>With the 2.6.7 kernel there used to be information in /proc/megaraid.
>I do not see the same information using the 2.6.11.2 kernel.
>Is there anything in /proc using the 2.6.11.2 kernel setup ?
>If not there, then anywhere else ?
>
It is not so much that you had /proc/megaraid in 2.6.7. There a
>> >
>> >Even for kernels with a 64bit dma_addr_t you can get 32bit dma
>> >addresses
>> >only. As a start check whether the pci_set_dma_mask for
>the 64bit mask
>> >failed - in that case you can always use 32bit SGLs.
>> >
>>
>> Please help me understand: If dma_addr_t is 64 bit, I will get 64
>
>Even for kernels with a 64bit dma_addr_t you can get 32bit dma
>addresses
>only. As a start check whether the pci_set_dma_mask for the 64bit mask
>failed - in that case you can always use 32bit SGLs.
>
Please help me understand: If dma_addr_t is 64 bit, I will get 64bit
addresses in scatterl
>> >
>> >> . And since this is compile time
>> >> system-wide property, I kept it as driver global.
>> >
>> >that step I don't understand... why is it a global
>*VARIABLE* if it's
>> >compile time system-wide property...
>> >
>>
>> I see your point! Are you saying I should use
>if(sizeof(dma_add
>
>> . And since this is compile time
>> system-wide property, I kept it as driver global.
>
>that step I don't understand... why is it a global *VARIABLE* if it's
>compile time system-wide property...
>
I see your point! Are you saying I should use if(sizeof(dma_addr_t)==8)
instead of the shortcu
>>
>> I will make this an instance parameter if the idea to reduce as many
>> global variables as possible. But if the objection is because each
>> adapter
>> may have different value for variable, then it is indeed a global
>> value.
>> "is_dma64" - which is computed using the size of dma_addr_t
>> >
>> >> source "drivers/scsi/megaraid/Kconfig.megaraid"
>> >> +source "drivers/scsi/megaraid/Kconfig.megaraid_sas"
>> >>
>> >
>> >why a fully separate file and not add your ONE config option to
>> >Kconfig.megaraid instead ??
>> >
>>
>> Arjan, I didn't want to needlessly couple megaraid and
>
>> +static int is_dma64;
>
>the fact that this is a global variable worries me.
>
Matt also has the same concern. I am pasting my response from my reply
to his comment:
I will make this an instance parameter if the idea to reduce as many
global variables as poss
>Subject: Re: [ANNOUNCE][PATCH 2.6.11 2/3] megaraid_sas:
>Announcing new module for LSI Logic's SAS based MegaRAID controllers
>
>On Fri, Mar 04, 2005 at 10:06:00PM -0500, Bagalkote, Sreenivas wrote:
>> We are announcing a driver for LSI Logic's new SAS based MegaRAID
>
>> source "drivers/scsi/megaraid/Kconfig.megaraid"
>> +source "drivers/scsi/megaraid/Kconfig.megaraid_sas"
>>
>
>why a fully separate file and not add your ONE config option to
>Kconfig.megaraid instead ??
>
Arjan, I didn't want to needlessly couple megaraid and megaraid_sas.
Since they are i
Hello All,
We are announcing a driver for LSI Logic's new SAS based MegaRAID
controllers. I am submitting the inlined patch in three parts. Please
review the patches.
Thank you,
Sreenivas Bagalkote
LSI Logic Corporation
Patch 1 of 3:
Signed-off-by: Sreenivas Bagalkote <[EMAIL PROTECTED]>
dif
he problem though it
>may decrease the necessary counter value.
>
>I don't know this value is ok for environments other than mine.
>
>Bagalkote, Sreenivas wrote:
>> Please try:
>>
>> In mbox_post_sync_cmd_fast(...) replace
>>
>> for (i = 0; i
Please try:
In mbox_post_sync_cmd_fast(...) replace
for (i = 0; i < 0xF; i++) {
if (mbox->numstatus != 0xFF) break;
}
with
for (i = 0; i < 0xF; i++) {
if (mbox->numstatus != 0xFF) break;
rmb();
}
Additionally, increase the loop counter to a bigger value.
Thank
18 matches
Mail list logo
