All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Arjan van de Ven <arjan@infradead.org>,
	Martins Krikis <mkrikis@yahoo.com>,
	marcelo.tosatti@cyclades.com, linux-kernel@vger.kernel.org,
	alan@lxorguk.ukuu.org.uk
Subject: Re: [ANNOUNCE] "iswraid" (ICHxR ataraid sub-driver) for 2.4.29
Date: Thu, 10 Feb 2005 14:35:23 -0500	[thread overview]
Message-ID: <420BB77B.3080508@tmr.com> (raw)
In-Reply-To: <58cb370e05020607197db9ecf4@mail.gmail.com>

Bartlomiej Zolnierkiewicz wrote:
> On Sun, 06 Feb 2005 10:03:27 -0500, Jeff Garzik <jgarzik@pobox.com> wrote:
> 
>>Arjan van de Ven wrote:
>>
>>>>I consider it not a new feature, but a missing feature, since otherwise
>>>>user data cannot be accessed in the RAID setups.
>>>
>>>
>>>the same is true for all new hardware drivers and hardware support
>>>patches. And for new DRM (since new X may need it) and new .. and
>>>new ... where is the line?
>>>
>>>for me a deep maintenance mode is about keeping existing stuff working;
>>>all new hw support and derivative hardware support (such as this) can be
>>>pointed at the new stable series... which has been out for quite some
>>>time now..
>>
>>Red herring.
>>
>>2.4.x has ICH5/6 support -- but is missing the RAID support component.
>>
>>We are talking about hardware that is ALREADY supported by 2.4.x kernel,
>>not new hardware.
>>
>>We are also talking about inability to access data on hardware supported
>>by 2.4.x, not something that can easily be ignored or papered over with
>>a compatibility mode.
> 
> 
> the same arguments can be used for crypto support etc.,
> answer is - use 2.6.x or add extra patches to get 2.4.x working

It's fix in a sense. The hardware is supported now, just not very well. 
If an IDE chipset was capable of UDA4 and the driver only allowed UDA2 
it would be a fix, in this case thehardware is supported partially, the 
RAID conponent isn't working, and this is the fix.

It is stretching a point, but adding support for all the features of 
hardware which is currently supported just seems to be a valud operation 
to me. New crypto feels more like adding a whole new device.

Opinion offered for clarification only, I don't feel strongly on this or 
crypto, but I do identify because I have hardware with a 2.4 driver and 
I can't use it unless I give up 2.6.

-- 
bill davidsen <davidsen@tmr.com>
   CTO TMR Associates, Inc
   Doing interesting things with small computers since 1979

  reply	other threads:[~2005-02-10 19:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-29  1:15 [ANNOUNCE] "iswraid" (ICHxR ataraid sub-driver) for 2.4.29 Martins Krikis
2005-02-06  2:36 ` Jeff Garzik
2005-02-06  9:27   ` Arjan van de Ven
2005-02-06 12:45     ` Bartlomiej Zolnierkiewicz
2005-02-06 14:38       ` Jeff Garzik
2005-02-06 14:48         ` Christoph Hellwig
2005-02-06 14:49         ` Arjan van de Ven
2005-02-06 15:03           ` Jeff Garzik
2005-02-06 15:19             ` Bartlomiej Zolnierkiewicz
2005-02-10 19:35               ` Bill Davidsen [this message]
2005-02-10 20:05                 ` Bartlomiej Zolnierkiewicz
2005-02-10 22:04                   ` Bartlomiej Zolnierkiewicz
2005-02-10 18:39                     ` Marcelo Tosatti
2005-02-10 23:28                       ` Bartlomiej Zolnierkiewicz
2005-02-10 20:33                         ` Marcelo Tosatti
2005-02-11 10:46                       ` Arjan van de Ven
2005-02-06 15:28             ` Arjan van de Ven
2005-02-06 15:50             ` Christoph Hellwig
2005-02-06 16:09               ` Jeff Garzik
2005-02-06 16:27                 ` Christoph Hellwig
2005-02-07 16:45           ` Marcelo Tosatti
2005-02-07 18:29           ` Martins Krikis
     [not found]             ` <bc8bcc5105020711081f1de175@mail.gmail.com>
2005-02-07 19:30               ` Martins Krikis

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=420BB77B.3080508@tmr.com \
    --to=davidsen@tmr.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjan@infradead.org \
    --cc=bzolnier@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=mkrikis@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.