linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Flory <sflory@rackable.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Ruth.Ivimey-Cook@ivimey.org,
	Chad Kitching <CKitching@powerlandcomputers.com>,
	Steven Dake <sdake@mvista.com>,
	linux-kernel@vger.kernel.org
Subject: Re: IDE/Promise 20276 FastTrack RAID Doesn't work in 2.4.21, patchattached to fix
Date: Mon, 14 Jul 2003 10:31:28 -0700	[thread overview]
Message-ID: <3F12E8F0.5020107@rackable.com> (raw)
In-Reply-To: <200307121801.03776.ruth@ivimey.org>

Ruth Ivimey-Cook wrote:

>On Saturday 12 Jul 2003 5:14 pm, Bartlomiej Zolnierkiewicz wrote:
>  
>
>>I think you just need "pdc_ide=0,force" and "pdc_ide=0,noforce".
>>No need to complicate things.
>>Remember that ataraid is only software RAID driver and pdc202xx_new
>>is a chipset driver.
>>

  Doesn't the following already work "ide2=0 ide3=0 ...." for the 
promise binary driver?

>
>I am not forgetting, but I don't like this idea of 'force' -- it instantly 
>raises the question 'force what' and then you're in the quagmire again.
>
>Better to tell the kernel what you want and let the kernel worry about how to 
>make it happen.
>
>So the "pdc_ide2=jbod"  would be scanned and interpreted as a request to 
>activate ('force') the drive into IDE mode and not enable any ataraid (jbod 
>==> just disks),
>
>while "pdc_ide3=promise" would let the drive state be, and make the kernel do 
>a "modprobe promise-ft" (or whatever it's called) to load the rest of the 
>driver, as is done for 'scsi-hostadapter'. [Would you ever have to force a 
>promise chip into promise-raid mode?].
>

  This is getting really complex.  Weren't we trying to make things 
simple?  The simple solution is to have the single option, and let user 
space (initrd) determine if you want to load the pdcraid driver. 

>
>Do you see what I mean?
>
>If you prefer, the string could be "pdc=ide2:ide, ide3:ataraid".
>
>  
>
>>jbod/raid should be managed by ataraid driver not ide or pdc202xx_new.
>>    
>>
>
>I was using jbod as just that, not as meaning raid-0 or similar. Perhaps I 
>should have been clearer. So you've a choice of (just IDE), (RAID via 
>ataraid) and (RAID via Promise)
>
>  
>

  No you really have only 2 options.
1)Let linux see the ide controller.
2)Don't then linux see the ide controller.

#1 Will only see ataraid partitions if there exists a promise raid 
configuration, and the pdcraid driver is loaded.

>
>  
>
>>>Should I think about coding this?
>>>      
>>>
>>No, think about porting ataraid and pdcraid to 2.5 first.
>>    
>>
>
>pdcraid == ataraid module for PDC?? Haven't looked at the src yet.
>  
>
  Yes unless you insert the pdcraid module.  Linux will only see the raw 
drives.  Once you insert pdcraid you can see the raid devices, and raw 
disks.  Which can cause major issues at times.

-- 
Once you have their hardware. Never give it back.
(The First Rule of Hardware Acquisition)
Sam Flory  <sflory@rackable.com>



  reply	other threads:[~2003-07-14 17:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-10 22:05 IDE/Promise 20276 FastTrack RAID Doesn't work in 2.4.21, patchattached to fix Chad Kitching
2003-07-10 22:18 ` Samuel Flory
2003-07-10 22:29   ` Steven Dake
2003-07-10 22:51     ` Samuel Flory
2003-07-10 23:13       ` Bartlomiej Zolnierkiewicz
2003-07-10 23:57         ` Steven Dake
2003-07-10 23:24       ` Steven Dake
2003-07-10 23:43         ` Bartlomiej Zolnierkiewicz
2003-07-10 23:54           ` Samuel Flory
2003-07-11  0:18             ` Bartlomiej Zolnierkiewicz
2003-07-10 22:55 ` Bartlomiej Zolnierkiewicz
2003-07-10 23:04   ` Samuel Flory
2003-07-12 15:11     ` Ruth Ivimey-Cook
2003-07-12 16:14       ` Bartlomiej Zolnierkiewicz
2003-07-12 17:01         ` Ruth Ivimey-Cook
2003-07-14 17:31           ` Samuel Flory [this message]
2003-07-14 18:49             ` Alan Cox
2003-07-12 18:36 Bartlomiej Zolnierkiewicz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F12E8F0.5020107@rackable.com \
    --to=sflory@rackable.com \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=CKitching@powerlandcomputers.com \
    --cc=Ruth.Ivimey-Cook@ivimey.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sdake@mvista.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).