linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Support for PATA in Promise 378 driver
@ 2004-02-23 13:16 Anton Starikov
  2004-02-23 13:35 ` Hendrik Visage
  2004-02-24  1:20 ` Support for PATA in Promise 378 driver Jeff Garzik
  0 siblings, 2 replies; 8+ messages in thread
From: Anton Starikov @ 2004-02-23 13:16 UTC (permalink / raw)
  To: linux-raid

Hi!

As I can see, there is no support for PATA port on promise 378 chip
currently.

Is this support planned?
If now, why? Is there some religious reasons?  ;) 
Or just matter of time?

I just see, that I'm not one person who can't migrate to 2.6 because of
using PATA port on 378.
There is no driver from Promise, driver from libata also does not
support.

So, now I see two solutions:
1) adopt promise driver from vendor (which use cam) for 2.6
kernel, if there is religious reasons ;)
2) try to work under libata promise driver in order to have
support for PATA port. 

First way is relatively easy. At least I know what to do, it just matter
of programming.
Second one is longer because I have to understand how
libata works, because I had nothing common with HW for a long time :)
But if later it will be merged to libata, there is more sense to go by
this way.

Finally, what to do? :)

Anton Starikov

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2004-06-03 21:07 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-02-23 13:16 Support for PATA in Promise 378 driver Anton Starikov
2004-02-23 13:35 ` Hendrik Visage
2004-02-23 13:45   ` Anton Starikov
2004-02-27 18:56     ` Jeff Garzik
2004-02-27 19:45       ` Anton Starikov
2004-02-24  1:21   ` Jeff Garzik
2004-06-03 21:07     ` PATA in Promise 378 & troubles with Promise 378 Hendrik Visage
2004-02-24  1:20 ` Support for PATA in Promise 378 driver Jeff Garzik

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).